VagabondXar

You can manually re-enable your mods by opening the plugins.txt file and putting a * infront of each mod name. This will activate your mods again. People were doing this during 1.5 beta time and it worked. Same deal now with the public 1.5.157 patch. Oh and to those that get a CTD, it is due to UI mods. Now remember that the UI mods were file drop ins and not actual .ESP type mods. Some of the first mods when FO4 released. A lot of people probably forgot that you had to manually make folders and edit fallout ini files to enable that stuff. Just remove anything from interface folder in your Data root and you should have your CTD solved. If you don't you can't load old saves OR start new game. The new 1.5 patch has new UI elements within it yeh, that's why the old outdated UI mods/changes are crashing the game. Hope this helps others as not a lot of people are cluing into this or bothering to tell people on forums/reddit etc...

You can manually re-enable your mods by opening the plugins.txt file and putting a * infront of each mod name. This will activate your mods again. People were doing this during 1.5 beta time and it worked. Same deal now with the public 1.5.157 patch. Oh and to those that get a CTD, it is due to UI mods. Now remember that the UI mods were file drop ins and not actual .ESP type mods. Some of the first mods when FO4 released. A lot of people probably forgot that you had to manually make folders and edit fallout ini files to enable that stuff. Just remove anything from interface folder in your Data root and you should have your CTD solved. If you don't you can't load old saves OR start new game. The new 1.5 patch has new UI elements within it yeh, that's why the old outdated UI mods/changes are crashing the game. Hope this helps others as not a lot of people are cluing into this or bothering to tell people on forums/reddit etc...