Fallout 4 1.3 Update Now Official!
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 beingYou 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.
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...
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.
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?
Anyways, this isn't the mod support forums :/
Anyways this isn't the mod support forum so it's not the place to post requests for support.
but at least we will have more Meat Clutter soon! zzzz...
Also, DLC support.
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
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...).
Brilliant
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...)
In a short:
It's pretty childish you hating on them because of your own f*** up, :/
I am pretty sure that was a feature.
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.
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...
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.