AuraMaster7 Posted April 29, 2016 Share Posted April 29, 2016 Uninstalled all my UI mods, and everything worked. I also have linked my bethesda.net account, so im not sure if that contributed, but all textures and everything are working now. Now the work begins to see what mod did it. Link to comment Share on other sites More sharing options...
foxcool Posted April 29, 2016 Share Posted April 29, 2016 I can confirmed that sResourceDataDirsFinal= and bInvalidateOlderFiles=1 does NOT cause crash, I got the game started with mods working with both lines in the ini. It's the mods that cause crashes. Link to comment Share on other sites More sharing options...
speedynl Posted April 29, 2016 Share Posted April 29, 2016 [Archive] bInvalidateOlderFiles=1 sResourceDataDirsFinal= works fine for me, no problems at all, peeps use just to many mods that cause troubles after any update, beth have only to make 1 change and mods are f*#@ up the game Link to comment Share on other sites More sharing options...
EvanH123 Posted April 30, 2016 Share Posted April 30, 2016 Uninstalling Def-UI fixed it for me Link to comment Share on other sites More sharing options...
Sorpaijen Posted April 30, 2016 Share Posted April 30, 2016 [Archive]bInvalidateOlderFiles=1sResourceDataDirsFinal= works fine for me, no problems at all, peeps use just to many mods that cause troubles after any update, beth have only to make 1 change and mods are f*** up the game This is the proper thing to do --- add those lines to the Fallout4Custom.ini file --- but doing so causes crashes for some because of ~something~ in the Interface folder. Many people have cited DEF_UI, I believe it was, as a problem and noted that the patch to it (or removing it) fixed the issue. I still do not know what mod put some file in there, but there were several files in my Interface folder.... I deleted the folder (having un-installed all my mods --- or so I thought). With the Interface folder deleted, the InvalidateOlderFiles worked like it used to do before patch 1.5 and let my custom textures show through like normal. The problem was those "orphan" files in the INTERFACE folder. With them gone, I no longer crashed with the InvalidateOlderFiles change to Fallout4Custom.ini, and with that INI change, the textures work fine again. Link to comment Share on other sites More sharing options...
Higgenboober Posted April 30, 2016 Share Posted April 30, 2016 Is the interface folder thing related to textures not showing up? I have Vivid Fallout and other texture replacers but they're not loading in game (all my .esp mods seem to work). Link to comment Share on other sites More sharing options...
Ceophthra Posted May 3, 2016 Share Posted May 3, 2016 I,too, was having the same experience with DEF_UI. I found that by deleting the \INTERFACE folder, the game worked. After reading all the comments in this thread I reinstalled the DEF_UI mod, with an eye to the miscellanous files in that folder. Long story short, I found I had NO default program assigned to .swf files. I downloaded the latest standalone Flash Player Projector, and configured it as the default app for .swf files for Windows 10, and suddenly my save game load-up CTDs disappeared.I should have picked up on it when I first installed DEF_UI, because I had to click and drop the .swf files onto the mod-provided version of the player in order to customize. I wracked by brain and the internet for answers, and finally ended up here. Not sure which of the comments above turned the light on. It may have been that I've seen some people say they were unaffected, while others were. It got me to thinking about base OS configurations.Anyway, I hope this helps... Link to comment Share on other sites More sharing options...
Sorpaijen Posted May 4, 2016 Share Posted May 4, 2016 Is the interface folder thing related to textures not showing up? I have Vivid Fallout and other texture replacers but they're not loading in game (all my .esp mods seem to work). I don't think the Interface folder has anything to do with textures ~unless~ they involve the UI (User Interface) somehow. The reason MY custom textures were not showing up, but my ESPs were "working", doing what functions they were supposed to do, was because I had eliminated the bInvalidateOlderFiles line from my Fallout4Custom.INI file in order to prevent crashing (which was caused by the interaction with the Interface folder, which had some junk in it apparently). In short, you need to make sure you have the bInvalidateOlderFiles=1 line (and I think one other?) in your Fallout4Custom INI file... can't remember the exact lines at the moment, but they should be easy enough to find --- that's how mods "used" to work back before Patch 1.5 confused things. Link to comment Share on other sites More sharing options...
jexbo1987 Posted July 29, 2016 Share Posted July 29, 2016 Guys Here is a Possible Fix. Hope it helps. https://www.youtube.com/watch?v=NNZOy14tWJk Link to comment Share on other sites More sharing options...
Recommended Posts