DayDreamer Posted Thursday at 10:40 PM Posted Thursday at 10:40 PM After telling somebody recently that Skyrim SE never crashes, I've tried starting a New Game. Sadly, it now crashes all the time! During last summer's sale, I'd finally purchased AE CC expansion as Garthand had changed his unofficial CC patch to require it (he recently changed back). I'd never gotten around to playing, as Startfield's CK finally arrived, so I'd also bought Starfield. Other SKSE log files (BugFixesSSE, ScrambledBugs) appear in ~/Data/SKSE/Plugins. Eventually found Documents/My Games/Skyrim.INI/SKSE/EngineFixes.log. It is zero length, so that's what seems to be crashing. A year ago, an SSE Engine Fixes maintainer released a version compiled with an old version of CommonLib. The log file appears in the wrong place, because it is hooking the wrong vector. Other hooks don't always work properly either. According to discussion at https://stepmodifications.org/forum/topic/19517-sse-161170-or-mo2-now-making-skyrimini-folder/page/2/#comments, Ian Patterson (aka 'ianpatt', SKSE team) says that EngineFixes needs to be "recompiled against a newer version of CommonLib". But all 3 of the previous maintainers have retired.
Arthmoor Posted Thursday at 11:06 PM Posted Thursday at 11:06 PM Is this the one you tried? https://www.nexusmods.com/skyrimspecialedition/mods/17230 If so you need to be sure you've downloaded the correct parts. The Part 1 for game version 1.6.1170 (doesn't matter whether you bought AE DLCs or not) is the second file listed in the files tab, not the first one. A lot of people have made this mistake and walked away thinking it was broken. That version works for both Steam and GOG - I'm running it on those now. Can't speak for the others you mentioned because I don't use any of those in my game.
DayDreamer Posted Friday at 05:51 PM Author Posted Friday at 05:51 PM 18 hours ago, Arthmoor said: Is this the one you tried? Yes. I've been running that for many years, and have the correct parts. See screenshot. The symptom is where the log file appears. Where does yours appear? Do we know of a project to maintain stuff that the original folks have left behind? After all, that's how Skyrim and Oblivion and Morrowind patches came here....
Arthmoor Posted Friday at 08:06 PM Posted Friday at 08:06 PM 2 hours ago, DayDreamer said: The symptom is where the log file appears. Where does yours appear? They don't, apparently. I have no logs at all that are attributed to the Engine Fixes mod, other than the SKSE loader log acknowledging the DLL is working. Maybe it doesn't generate a log? 2 hours ago, DayDreamer said: Do we know of a project to maintain stuff that the original folks have left behind? Nope, I don't know of any such effort. It's not something that could end up in our hands since nobody on the UPP team knows enough C++ and RE stuff to have any shot at it. My suggestion would be to ask the xSE team about it and see if they know of anything.
DayDreamer Posted Sunday at 06:16 PM Author Posted Sunday at 06:16 PM On 5/9/2025 at 4:06 PM, Arthmoor said: Maybe it doesn't generate a log? The bug is writing the log in Documents\My Games\Skyrim.INI\SKSE\EngineFixes.log. It is supposed to be in Data\SKSE\Plugins\. instead. My log currently says: Quote F:\skyrim-dev\ef\EngineFixesSkyrim64\src\main.cpp(97): [info] Engine Fixes v6.1.1 F:\skyrim-dev\ef\EngineFixesSkyrim64\src\main.cpp(100): [info] loaded config successfully F:\skyrim-dev\ef\EngineFixesSkyrim64\src\main.cpp(128): [info] beginning pre-load patches F:\skyrim-dev\ef\EngineFixesSkyrim64\src\main.cpp(134): [info] pre-load patches complete F:\skyrim-dev\ef\EngineFixesSkyrim64\src\main.cpp(13): [info] beginning post-load patches F:\skyrim-dev\ef\EngineFixesSkyrim64\src\main.cpp(33): [info] post-load patches complete Does yours say the same? (I'm trying to find out why the version isn't 6.2 as Vortex is telling me.)
Arthmoor Posted Sunday at 08:05 PM Posted Sunday at 08:05 PM Well that's a silly place for it to show up, but yes, mine says the same even though I definitely have the 6.2 download. It looks like the DLL itself never had the version info updated on it.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now