Notifications
Notification preferences
notifications_off

No unread notifications right now

You're up to date
View All

You're up to date

Fallout 4 1.3 Update Now Official!

  • Comment
More articles
The Fallout 4 1.3 Update is officially out of beta and is now available for mass consumption. There's a fairly healthy list of new features, fixes and improvements even more comprehensive than the beta patches.

More info can be found at the official Bethesda site: 
https://bethesda.net/#en/events/game/fallout-4-1.3-update/2016/02/01/70

The update will be applied the next time you start the game if you have automatic updates turned on.

At first glance mods seem to be working fine, but only time will tell how this update will effect each mod individually. Again, no issues reported so-far but feel free to comment below if you have general thoughts or concerns about this patch. Authors of mods that have specific issues should be contacted directly or via their file comments.

Additionally, users of F4SE may want to be sure to keep up with the latest release in case there are any updates: http://f4se.silverlock.org/

Thanks, Bethesda! Happy Monday!

354 comments

Comments locked

A moderator has closed this comment topic for the time being
  1. UlithiumDragon
    UlithiumDragon
    • premium
    • 150 kudos


    Spoiler:  
    Show



     
    In response to post #34580070. #34593695 is also a reply to the same post.


    Spoiler:  
    Show

    UlithiumDragon wrote:
    *Sigh* I got bored of Fallout 4, and didn't bother trying to figure out WHY I was all of a sudden getting instant CTD's after the patch. Turns out it was one of my own damn mods - a bloody simple-ass texture mod...
     
    I have no f*cking idea WHY THE HELL a simple "texture" would cause a game to violently implode, but as Bethesda games have been moving slowly towards MAXIMUM instability, who the f*ck knows...
     
     
    I mean, ffs- it was just a simple recolor of the laser projectile from red to purple. It must be tied to the export settings I used in GIMP, though, since I have several other textures I've made that are in use that DON'T cause CTD's...
     
    Either that, or the last patch changed how "gradients" work (which seems unlikely, as I have other mods installed that edit gradients...).

    Eruadur wrote: So in short: you ff-ed up and you blame Bethesda for it.
    Brilliant


    Name one other situation where a bad texture would cause a game it VIOLENTLY EXPLODE, rather than just not show up, or not look right...

    THis is NOT "my fault" - look, THIS is what was happening before when I had the encoding set incorrectly - the game just didn't render them correctly:

    http://i.imgur.com/sBCAcUM.jpg

    (He was supposed to be all white, no clue why not setting a compression type caused only certain parts of the coloring to change...)
     



    Your modding is not officially supported, therefore whatever results it might incur are your fault only, as well as your own responsibility.


     
    You are continuing to avoid my main question - how could a game be SO UNSTABLE that a *TEXTURE* would cause instant CTD's without even RENDERING said texture...?
     
    >Because Bethesda game, and because Gamebryo.
    1. KimberJ
      KimberJ
      • BANNED
      • 10 kudos
      This is Creation Engine. Look it up on the wikipedia if you wana talk about it. I doubt anyone that read about it or worked with Skyrim/FO4 CE to make mods would make this claim that it's Gamebyro.
    2. UlithiumDragon
      UlithiumDragon
      • premium
      • 150 kudos
      I just *KNEW* someone would call me out for calling it "Gamebryo".

      It doesn't matter how many changes they made - the "Creation Engine" is still build ON TOP OF the Gamebryo Engine, and suffers from MANY of the same limitations and restrictions said engine possesses.

      You can put some more makeup on the the body all you want, but that wh*%# will still be dead, and Gamebryo is SOOOOO dated at this point it's not even funny...

    3. Fatalmasterpiece
      Fatalmasterpiece
      • premium
      • 35 kudos
      Your gif of Todd Howard should be replaced by every Bethsoft fan who can't let go of whining about Gamebryo.

      It's Bethesda's engine, who cares what it's called. The game runs stable for many people, myself included. If you installed some crap incorrectly it's your fault. No amount of whining is going to change that.

      You wouldn't open up your PC chassis, pluck a single capacitor from your motherboard and then complain about how unstable your mobo is that it can't even handle losing a single little piece.
  2. RiOrus2
    RiOrus2
    • member
    • 0 kudos
    Still having CTD issues, at completely random times and locations.

    So far, to try to rectify:

    I've uninstalled all texture mods
    deleted ini's and restarted game to create new.

    Interestingly, doing this didn't create a fallout4custom.ini, only the fallout4.ini and fallout4prefs.ini. Incidentally, running the game without the fallout4custom.ini in the folder allowed for a stable gaming session for 2 or 3 hours, which is a vast amount more than the approx. 15 to 20 mins I normally get before CTD.

    Obviously this would prevent me from using other mods but it's interesting it provided improved stability.

    Anyone concur or explain?
    1. DarkTitanV
      DarkTitanV
      • premium
      • 1 kudos
      If you have Gore overhaul isntalled, update it, that is causing CTD. Just update it to v4.0
    2. Fatalmasterpiece
      Fatalmasterpiece
      • premium
      • 35 kudos
      You shouldn't be having that many CTDs. Sounds like you have some bad mod installs. Texture mods will generally not cause CTDs like that. I would recommend a fresh install of the game after backing up your save files.

      Anyways, this isn't the mod support forums :/
  3. thekhajitslayer83
    thekhajitslayer83
    • member
    • 0 kudos
    im having a problem where any mod weapon i download and install is invisible in the game happens with modded armor too.however mods that alter vanilla weapons seem to not be invisible in game i tried unistalling the modded weapons/armor and reinstalling but the issue persists i looked online and no one else seems to have the same problem as this? does anyone know how to fix it?
    1. MasterVin
      MasterVin
      • member
      • 0 kudos
      I'm having the same problem...still looking for an asnwer
    2. Fatalmasterpiece
      Fatalmasterpiece
      • premium
      • 35 kudos
      Sounds like you probably have installed the mod's files in the wrong folder. Check your file paths are correct.

      Anyways this isn't the mod support forum so it's not the place to post requests for support.
  4. Fatalmasterpiece
    Fatalmasterpiece
    • premium
    • 35 kudos
    Still waiting for them to fix the hotkey weapon switching glitch...

    but at least we will have more Meat Clutter soon! zzzz...
  5. Ethreon
    Ethreon
    • premium
    • 645 kudos
    Suddenly new beta patch which adds some new items here and there. Wonder if they're new items or just copies already in the game files.
    Also, DLC support.
  6. bben46
    bben46
    • premium
    • 781 kudos
    @cassellcorey: Your post and the replies are now gone - this is NOT the place and you are guilty of an attempt to hijack a topic that has nothing to do with your problem - We actually have separate forums for each of the over 230 games we support. Post your problem in the proper forum - make a new topic of your very own ( no extra charge for that) and give some information - "It's broke" is totally useless for trying to get help.
     
    Or, you could read the stickies and FAQs for whatever game you are using As that is one of many things you didn't tell us, Here is a generic 'How to ask for help' post from my own blog.
    http://s1.zetaboards.com/bbenlibrary/topic/5686144/1/?x=0#post949222
  7. UlithiumDragon
    UlithiumDragon
    • premium
    • 150 kudos
    *Sigh* I got bored of Fallout 4, and didn't bother trying to figure out WHY I was all of a sudden getting instant CTD's after the patch. Turns out it was one of my own damn mods - a bloody simple-ass texture mod...
     
    I have no f*cking idea WHY THE HELL a simple "texture" would cause a game to violently implode, but as Bethesda games have been moving slowly towards MAXIMUM instability, who the f*ck knows...
     
     
    I mean, ffs- it was just a simple recolor of the laser projectile from red to purple. It must be tied to the export settings I used in GIMP, though, since I have several other textures I've made that are in use that DON'T cause CTD's...
     
    Either that, or the last patch changed how "gradients" work (which seems unlikely, as I have other mods installed that edit gradients...).
    1. Eruadur
      Eruadur
      • BANNED
      • 7 kudos
      So in short: you ff-ed up and you blame Bethesda for it.
      Brilliant
    2. UlithiumDragon
      UlithiumDragon
      • premium
      • 150 kudos
      Name one other situation where a bad texture would cause a game it VIOLENTLY EXPLODE, rather than just not show up, or not look right...

      THis is NOT "my fault" - look, THIS is what was happening before when I had the encoding set incorrectly - the game just didn't render them correctly:

      http://i.imgur.com/sBCAcUM.jpg

      (He was supposed to be all white, no clue why not setting a compression type caused only certain parts of the coloring to change...)
    3. DarkTitanV
      DarkTitanV
      • premium
      • 1 kudos
      I don't see how you ffing up a texture is Bethesda's fault, that's like me making a mod wrong, and causing me to CTD then cry to Bethesda claiming how their engine is bad because my mod wasn't working. If I were you; I'd just try and find the problem in YOUR textures, which YOU added, updates can cause breaks, and mature people would fix them to work with the new engine update, instead of crying to Bethesda about why your mod 'works' even though it clearly doesn't, then flaming Bethesda about their engine for it.

      In a short:
      It's pretty childish you hating on them because of your own f*** up, :/
    4. shinthomas
      shinthomas
      • premium
      • 0 kudos
      Actually, if the mod was working just fine pre-patch it was very likely something the devs changed. But Bethesda is the publisher, not the the dev. So yea, it's not 'their' fault. But the devs likely changed a few things that might break some mods. That's what happens you get patches.
  8. featherhead021
    featherhead021
    • member
    • 0 kudos
    Mine can't even start up. On steam it just says Preparing to Launch Fallout 4....
  9. Madrock
    Madrock
    • supporter
    • 0 kudos
    "Fixed an issue where the player could no longer get Preston as a companion"

    I am pretty sure that was a feature.
  10. Ethreon
    Ethreon
    • premium
    • 645 kudos
    Spoiler:  
    Show



     
    In response to post #34615300. #34623920 is also a reply to the same post.


    Spoiler:  
    Show

    UlithiumDragon wrote:


    Spoiler:  
    Show



     
    In response to post #34580070. #34593695 is also a reply to the same post.


    Spoiler:  
    Show

    UlithiumDragon wrote:
    *Sigh* I got bored of Fallout 4, and didn't bother trying to figure out WHY I was all of a sudden getting instant CTD's after the patch. Turns out it was one of my own damn mods - a bloody simple-ass texture mod...
     
    I have no f*cking idea WHY THE HELL a simple "texture" would cause a game to violently implode, but as Bethesda games have been moving slowly towards MAXIMUM instability, who the f*ck knows...
     
     
    I mean, ffs- it was just a simple recolor of the laser projectile from red to purple. It must be tied to the export settings I used in GIMP, though, since I have several other textures I've made that are in use that DON'T cause CTD's...
     
    Either that, or the last patch changed how "gradients" work (which seems unlikely, as I have other mods installed that edit gradients...).

    Eruadur wrote: So in short: you ff-ed up and you blame Bethesda for it.
    Brilliant


    Name one other situation where a bad texture would cause a game it VIOLENTLY EXPLODE, rather than just not show up, or not look right...

    THis is NOT "my fault" - look, THIS is what was happening before when I had the encoding set incorrectly - the game just didn't render them correctly:

    http://i.imgur.com/sBCAcUM.jpg

    (He was supposed to be all white, no clue why not setting a compression type caused only certain parts of the coloring to change...)
     



    Your modding is not officially supported, therefore whatever results it might incur are your fault only, as well as your own responsibility.


     
    You are continuing to avoid my main question - how could a game be SO UNSTABLE that a *TEXTURE* would cause instant CTD's without even RENDERING said texture...?
     
    >Because Bethesda game, and because Gamebryo.

    KimberJ wrote: This is Creation Engine. Look it up on the wikipedia if you wana talk about it. I doubt anyone that read about it or worked with Skyrim/FO4 CE to make mods would make this claim that it's Gamebyro.


    I just *KNEW* someone would call me out for calling it "Gamebryo".

    It doesn't matter how many changes they made - the "Creation Engine" is still build ON TOP OF the Gamebryo Engine, and suffers from MANY of the same limitations and restrictions said engine possesses.

    You can put some more makeup on the the body all you want, but that prostitute will still be dead, and Gamebryo is SOOOOO dated at this point it's not even funny...

    F2cqIOo.gif 



    And unity5 is build on unity4 which is built on unity3 etc. All engines go through this. An engine that comes out and never gets newer versions means it's a bad engine. I'll take the gamebryo that allows me this freedom of modding and open world over your shiny engines that can only function inside limited, tiny rooms. Anyway, whatever you did to your game is your doing. Beth can change the damn textures as they please, and you'll have to deal with it.