specknowsbest Posted November 14, 2017 Posted November 14, 2017 I know, I know, check the boards. Already have and it seems the issue I'm having, though shared, doesn't share the same origins or causations. Or they do, and I'm just an idiot. Anywho, updated to the new FOSE today, go to try to start up the game with it, and immediate CTD before the game even fully launches. Of course, I can run the game off of its original .exe which immediately limits the problem to FOSE itself. Now, I've perused my mod list, which is fairly extensive, and can't find any particular mod that'd be out of date and also relies upon FOSE to function properly. Outside of LooksMenu and Place Anywhere, I don't really have any mods that are actually reliant upon FOSE. So, what on earth is causing my game to CTD the moment I launch with FOSE? Yes, it's the most updated version, yes my game version is current, and yes my mods are current. Is there something just screwy with the latest game update or FOSE?
MissingMeshTV Posted November 14, 2017 Posted November 14, 2017 Any chance you're using ReShade...with an ENB maybe? At one point ReShade and F4SE were not compatible and running both would CTD at launch. Don't know if it's still an issue, but it's the only thing I know that can cause CTD with F4SE running other than an improper installation.
specknowsbest Posted November 14, 2017 Author Posted November 14, 2017 I'm not running any ENB, or ReShade. Hence my confusion. Maybe the installation was corrupted and I should retry FOSE? edit: Tried an uninstall/reinstall of FOSE and still CTD on start up
willyb9 Posted November 14, 2017 Posted November 14, 2017 are you sure f4se is installed correctly/in the right place? what mods are you using that require f4se? you should check those to see if they've been updated for the latest version of f4se
specknowsbest Posted November 14, 2017 Author Posted November 14, 2017 The only mods I'm using that require FOSE are Place Everywhere and Looks Menu, both of which I've updated to the latest version to match the current f4se. Their load order hasn't changed since original install when the game worked just fine with f4se. Edit: I forgot about my mod "Rename Anything" which also requires f4se. The mod author has not yet updated the mod itself, so that is what was causing CTD for me. So, looks like it was just the single, outdated mod that broke the game.
willyb9 Posted November 14, 2017 Posted November 14, 2017 this mod? https://rd.nexusmods.com/fallout4/mods/22105?tab=files looks like it was updated the other day if that's the one you're talking about. you should be good to go if that's the case.
specknowsbest Posted November 14, 2017 Author Posted November 14, 2017 this mod? https://rd.nexusmods.com/fallout4/mods/22105?tab=files looks like it was updated the other day if that's the one you're talking about. you should be good to go if that's the case. That's trippy, because NMM didn't show it needing an update. But yeah, that was the mod.
pra Posted November 15, 2017 Posted November 15, 2017 That's trippy, because NMM didn't show it needing an update. But yeah, that was the mod. That's normal, the new version recognition of NMM is awful. Anyway, I just had the same problem. In case anyone else does: look under Data\F4SE\Plugins if there are any leftover DLLs from mods you uninstalled. For me it was vertibird_jump.dll, which I uninstalled a long time ago. Otherwise, just keep renaming the DLLs or moving them somewhere else until you find the one which breaks it.
Recommended Posts