gooboo Posted December 17, 2017 Posted December 17, 2017 Hi everyone. After updating my game to 1.10.50 from 1.9.4 I seem to have run into a problem and I don't know what to do. Whenever I edit the Fallout4Custom.ini file to enable modding by adding these lines- [Archive] bInvalidateOlderFiles=1 sResourceDataDirsFinal= the game just doesn't want to work anymore. I can get the game to start fine without editing the Custom.ini file, but then that means none of my mods are showing up in-game. I've tried deactivating all of my mods (except for official DLC) in the mod manager, and that doesn't change anything. If I edit the file by adding those lines it just crashes before it ever gets to the main menu screen, whether I'm playing with my mods or none at all. I've successfully started the game both from Steam and from f4se, so I don't think that's the problem either. What's going on here? I have absolutely no interest in Fallout 4 without mods, so I really would like to be able to fix this problem. Never ran into this issue when I was playing 1.9.4, so I'm not sure what the update screwed up.
VonHelton Posted December 17, 2017 Posted December 17, 2017 8 minutes ago, gooboo said: Hi everyone. After updating my game to 1.10.50 from 1.9.4 I seem to have run into a problem and I don't know what to do. Whenever I edit the Fallout4Custom.ini file to enable modding by adding these lines- [Archive] bInvalidateOlderFiles=1 sResourceDataDirsFinal= the game just doesn't want to work anymore. I can get the game to start fine without editing the Custom.ini file, but then that means none of my mods are showing up in-game. I've tried deactivating all of my mods (except for official DLC) in the mod manager, and that doesn't change anything. If I edit the file by adding those lines it just crashes before it ever gets to the main menu screen, whether I'm playing with my mods or none at all. I've successfully started the game both from Steam and from f4se, so I don't think that's the problem either. What's going on here? I have absolutely no interest in Fallout 4 without mods, so I really would like to be able to fix this problem. Never ran into this issue when I was playing 1.9.4, so I'm not sure what the update screwed up. Try putting it in the other INI files & see if that works...
gangstamick Posted December 17, 2017 Posted December 17, 2017 1.10.50 required a new version of f4se, 0.6.4
gooboo Posted December 18, 2017 Author Posted December 18, 2017 After spending the evening looking around some more, I figured out the problem. Turns out I needed to delete the Interface folder after updating to 1.10.50. I don't use any UI mods, so I have no idea what that was about, but after I deleted it the game started fine. Weird.
lepus Posted December 27, 2017 Posted December 27, 2017 I have the same problem, but don't seem to have an interface folder to delete, at least not one I can fine.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.