GabeCPB0 Posted September 10 Share Posted September 10 On 7/3/2018 at 5:34 PM, evalsoidua said: I was having trouble with black screen CTDs on startup with f4se. Turns out my executable path for f4se in Mod Organizer was set to D:\Program Files (x86)\Steam\steamapps\common\Fallout 4\Fallout 4\ for whatever reason. Delete the second Fallout 4, D:\Program Files (x86)\Steam\steamapps\common\Fallout 4\ and BAM! It works again. Not sure why that was the default path but simple fix for me. Greetings. I'm necroing this thread in order to thank this guy. I was having the exact same problem of this forum, and searched a lot around Google. It just so happened that what he wrote was the solution, that second "\Fallout4" in "D:\Program Files (x86)\Steam\steamapps\common\Fallout 4\Fallout 4\" in my executable path was exactly the problem. Was close of losing hope, did a lot of other stuff and nothing helped, but alas, checked this, and after correcting it, it worked flawlessly. So if anyone else is having this problem, as it seems a somewhat recurring or common problem between ModOrganizer 2 users of the Fallout 4 community, especially post-patch, you may want to try this solution. God Bless. Link to comment Share on other sites More sharing options...
Recommended Posts