LivedDevil69 Posted May 14, 2018 Share Posted May 14, 2018 My F4SE will not work with or without mods. As soon as I open it might load [press and key to continue] but just black screen and crash. Fallout 4 works perfectly on it's own so it isn't Fallout 4 itself (even re-downloaded the game). I am using the most recent F4SE and Fallout 4 game and followed the instructions from (a little old but I assume it's the same steps don't change). Link to comment Share on other sites More sharing options...
pitstop25 Posted May 16, 2018 Share Posted May 16, 2018 I am having the same problem. It all worked fine last night now after putting F4SE on it won't boot. I am using NMM and on windows 10. Link to comment Share on other sites More sharing options...
LivedDevil69 Posted May 17, 2018 Author Share Posted May 17, 2018 Further looking into my Mod Organzier 2 all the .pex from Fallout 4 and F4SE .pex data folders are conflicting so is the current F4SE out of date or is there something I can do to get around it? Link to comment Share on other sites More sharing options...
CtMrebelL10N Posted May 18, 2018 Share Posted May 18, 2018 (edited) I'm having the same CTD upon boot through MO2. I wonder if the latest (May) update for Windows 10 has anything to do with it? I could see how they (Win and F4SE) may not be playing nice as it crashed our work's computers when everyone installed the update. I'm going to update all of my audio and video drivers to see if that has an effect. I hate Windows sometimes... Edit:Updated my drivers and those don't seem to be the issue.I have run further experiments and have I can launch and load the game just fine straight from the f4se_loader.exe but encounter all of a CTD when I launch F4SE or the native launcher from MO2 v.2.1.1. I will do some more troubleshooting later today. Are you guys sure it is explicitly F4SE causing your issues? If so, check that it got set up correctly (i.e. delete it then add it back in) Edited May 18, 2018 by CtMrebelL10N Link to comment Share on other sites More sharing options...
LivedDevil69 Posted May 19, 2018 Author Share Posted May 19, 2018 When I launch through MO2 it doesn't work, I can launch the taskbar shortcut for F4SE and it will go but it won't pick up any mods so I have absolutely no clue what is wrong. Link to comment Share on other sites More sharing options...
LivedDevil69 Posted May 19, 2018 Author Share Posted May 19, 2018 The problem has to be with something and F4SE. All the ,pex from the F4SE/Data/Scripts installation are causing conflicts which I assume is the reason for the CTD during launch. Link to comment Share on other sites More sharing options...
instyne49 Posted May 19, 2018 Share Posted May 19, 2018 The problem has to be with something and F4SE. All the ,pex from the F4SE/Data/Scripts installation are causing conflicts which I assume is the reason for the CTD during launch. Bethesda just did another Fallout 4 update, and F4SE. Silverlock hasn't released a new version yet. Build 6.7 only works on Fallout 4 version 1.10.82 , I came here looking for news on the F4SE update. Guess we just have to wait. Link to comment Share on other sites More sharing options...
MissingMeshTV Posted May 19, 2018 Share Posted May 19, 2018 Last night after launching the game with F4SE through MO2 for the first time in two weeks I was also getting the CTD as others. I also thought it might be F4SE scripts in the Scripts folder, but that wasn't it. They had never caused me issues previously anyway. The actual solution I found was to update MO2 to the latest 2.1.3 version that was released on 9 May. After updating the game launched normally. The only changes in the past two weeks to my machine have been the Win10 April update, so I have to assume something in that borked MO2 as the game launched just fine with F4SE bypassing MO2. NOTE: the MO2 team has moved all their file downloads to the Skyrim SE page. I also believe you can get dev versions from their Discord, but the 3.2.1 from the Skyrim SE page is what I grabbed. Link to comment Share on other sites More sharing options...
evalsoidua Posted July 3, 2018 Share Posted July 3, 2018 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. 1 Link to comment Share on other sites More sharing options...
Kodey18 Posted July 4, 2018 Share Posted July 4, 2018 Sup dudes. I have something you can maybe try that worked for me. I was having that same problem with starting the f4se_loader through mod organizer 2 (Black screen, click to continue at the bottom and then crash). When I read the post i have quoted, I thought I had the same problem but my paths were correct. So I decided to remove the shortcut for the f4se_loader entirely and then I re-added it myself. And what do you know it worked again. 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. I hope this helps anyone. 1 Link to comment Share on other sites More sharing options...
Recommended Posts