boogiePls Posted January 16, 2016 Share Posted January 16, 2016 Alright so after spending most of today uninstalling and reinstalling mods to find the wtf was making the saves crash, I found out the culprit, Fallout VI Gore Overhaul. I wasn't even using the plugin, using the textures is enough to make the game crash with the beta patch, other people in the mod comments were having the same issue as well.Keep in mind there might be other mods that cause this same issue too, hope this helps. Link to comment Share on other sites More sharing options...
ZombieTech Posted January 16, 2016 Share Posted January 16, 2016 (edited) Alright so after spending most of today uninstalling and reinstalling mods to find the wtf was making the saves crash, I found out the culprit, Fallout VI Gore Overhaul. I wasn't even using the plugin, using the textures is enough to make the game crash with the beta patch, other people in the mod comments were having the same issue as well.Keep in mind there might be other mods that cause this same issue too, hope this helps. Hrm, I'm having the same issue where I can't even start a new vanilla game without it crashing. And it's INSTANT... as soon as I try to load a game, CTD... only once did it ever pop up and say that some data is no longer associated do I wish to keep loading, and it CTD before I could even answer anything, like as soon as it came up. When starting a new game, takes about 3-5 seconds to CTD. However, I'm not, nor have I ever installed Gore Overhaul (will double-check just to be certain). I noticed one person said making plugins.txt read-only fixed it (which I thought NMM already did? Or was that another file?). Also see people mentioning to roll back before the beta patch. So guess those are my steps...1. Check to see if I've ever used Gore Overhaul.2. Check to make sure plugins.txt is read-only.3. Roll back patch. Thanks Bethesda... could you please stop taking business-practices from Microsoft/Windows in the future!? FFS! >_< EDIT: Confirmed; Gore Overhaul doesn't look familiar. Though, does have me thinking/wondering if there's a chance that there's other texture-replacements that could be causing the issue. If so, gonna' be a bumpy ride as I've installed tons of texture-replacements... form Pipboy-map, to trees, to stars, to sky, to armor, to clothing, to some weapons, to world textures, even to junk items like Mac'n'Cheese, Abraxo, etc. -_- EDIT2: Seems my plugins.txt AND loadorder.txt (loadorder wasn't originally, but still no luck after read-only and restart of NMM) in Users/<username>/AppData/Local/Fallout4 is already set as read-only. So guess my final solution is to rollback the beta patch... lovely. >:-/ Edited January 16, 2016 by ZombieTech Link to comment Share on other sites More sharing options...
Deleted3507349User Posted January 16, 2016 Share Posted January 16, 2016 I must admit I'm starting to become very suspicious of Bethesda's motives in what they're doing vis-a-vis modding. First they hide the Data Files section, then they remove it entirely and make it so that it automatically disables mods without a workaround, and now THIS? I hate to be one of 'those people', but it seems like the long amount of time they're taking to release these patches (with very few actual fixes listed) may be mostly due to them trying to figure out how to block unofficial modding. I really hope that's not what's on their minds. If they thought the kerfluffle over paid mods was loud wait until they see the backlash of doing something like that. Link to comment Share on other sites More sharing options...
BinaryMessiah Posted January 16, 2016 Share Posted January 16, 2016 (edited) Alright so after spending most of today uninstalling and reinstalling mods to find the wtf was making the saves crash, I found out the culprit, Fallout VI Gore Overhaul. I wasn't even using the plugin, using the textures is enough to make the game crash with the beta patch, other people in the mod comments were having the same issue as well.Keep in mind there might be other mods that cause this same issue too, hope this helps. Hrm, I'm having the same issue where I can't even start a new vanilla game without it crashing. And it's INSTANT... as soon as I try to load a game, CTD... only once did it ever pop up and say that some data is no longer associated do I wish to keep loading, and it CTD before I could even answer anything, like as soon as it came up. When starting a new game, takes about 3-5 seconds to CTD.However, I'm not, nor have I ever installed Gore Overhaul (will double-check just to be certain).I noticed one person said making plugins.txt read-only fixed it (which I thought NMM already did? Or was that another file?). Also see people mentioning to roll back before the beta patch.So guess those are my steps...1. Check to see if I've ever used Gore Overhaul.2. Check to make sure plugins.txt is read-only.3. Roll back patch.Thanks Bethesda... could you please stop taking business-practices from Microsoft/Windows in the future!? FFS! >_<EDIT: Confirmed; Gore Overhaul doesn't look familiar. Though, does have me thinking/wondering if there's a chance that there's other texture-replacements that could be causing the issue. If so, gonna' be a bumpy ride as I've installed tons of texture-replacements... form Pipboy-map, to trees, to stars, to sky, to armor, to clothing, to some weapons, to world textures, even to junk items like Mac'n'Cheese, Abraxo, etc. -_-EDIT2: Seems my plugins.txt AND loadorder.txt (loadorder wasn't originally, but still no luck after read-only and restart of NMM) in Users/<username>/AppData/Local/Fallout4 is already set as read-only. So guess my final solution is to rollback the beta patch... lovely. >:-/ Disabling Gore Overhaul worked! I rolled back the patch several times and confirmed that 1.3 crashes the game. After disabling the Gore Overhaul it all works fine. I will message the mod creator and let him know. I guess Bethesda didn't disable mods, just messed them up. Edited January 16, 2016 by Ivory_Soul Link to comment Share on other sites More sharing options...
ZombieTech Posted January 16, 2016 Share Posted January 16, 2016 (edited) UPDATE: So, opting out of beta seems to get the game working again. Just right-click Fallout 4 in library, go to Betas tab, select "opt-out of Beta". It does a validation for about 10 minutes, and then I'm assuming it uninstalled the beta-patch, because game works again.Now, what I also HIGHLY suggest... since this is the SECOND TIME IN A ROW that Bethesda has done f'ed it up... while under properties for Fallout 4 in Steam, go to the tab "Updates" and select "Only Update Game When I Launch It". Wish there was a way to tell it to not auto-update at all (will look into seeing if I can't turn it off for now). Be better to have to go and manually tell it to update, that way we can read up and make sure it's safe first. -_-What pisses me off even more, is from everything I've seen Bethesda released this patch and were all boasting and proud in saying, "oh, trust us, this one won't mess with your mods this time"... BULL****!!!As others have stated, this seems VERY suspect as though they're purposely trying to knee-cap modding/Nexus to FORCE users to have to use their crappy Bethesda.net or whatever that junk is meant to be. Wouldn't be surprised if not long after they launch it, they start pushing monetization of mods the same way they did with Skyrim for a bit. >:( Edited January 16, 2016 by ZombieTech Link to comment Share on other sites More sharing options...
Nixsy Posted January 16, 2016 Share Posted January 16, 2016 Thank you 7zip. It could be a good idea now for you to backup your game directory. You can play Fallout from a different location on your computer outside of the steam directory. when steam officially pushes this update you will at least have a backup that is playable. Link to comment Share on other sites More sharing options...
Deleted3507349User Posted January 16, 2016 Share Posted January 16, 2016 I'm lucky, the mods I'm using don't seem to be affected by the new beta (plugins and loadorder txt files set to read-only). Also, if you fire up Big Picture Mode and look through the game properties it has a 'never ever update EVER' option. Link to comment Share on other sites More sharing options...
dangwoot Posted January 16, 2016 Share Posted January 16, 2016 I can also confirm that my game is now 100% working again after removing gore overhaul.... weird how it's textures caused a crash on the new patch but not on the old one :/ Link to comment Share on other sites More sharing options...
Bankstercide Posted January 16, 2016 Share Posted January 16, 2016 (edited) It's called beta for a reason. :smile: Their beta patch went live on my non-beta game with the same results. This kind of sloppiness is god-damned stupid. Especially if it's not a hotfix. More so, since this nonsense happened with the last patch. To the OP: I'm getting CTD right before I get to the main menu. I am using Bilago's F4 Config Tool. Edited January 16, 2016 by Bankstercide Link to comment Share on other sites More sharing options...
bladexdsl Posted January 16, 2016 Share Posted January 16, 2016 As others have stated, this seems VERY suspect as though they're purposely trying to knee-cap modding/Nexus to FORCE users to have to use their crappy Bethesda.net or whatever that junk is meant to be. Wouldn't be surprised if not long after they launch it, they start pushing monetization of mods the same way they did with Skyrim for a bit. >:(i can tell you right now this is their plan. i'm this close to installing an unofficial patch that blocks steam altogether from fallout :down: Link to comment Share on other sites More sharing options...
Recommended Posts