Installation instructions for Engine Fixes 5.3.3+:
BEFORE YOU START: This is a SKSE64 plugin. Therefore, you need to have the correct version of SKSE64 installed for your game version in order for this mod to function. If you don't have SKSE64 installed or don't know what SKSE64 is, do not attempt to install this mod. Learn what SKSE64 is and why you might want it here. SKSE+SkyUI installation instructions here. Once SKSE64 is properly installed, follow the Engine Fixes install steps below:
(1) RECOMMENDED: Completely remove all files and uninstall any previous installations of SSE Engine Fixes prior to starting.
(2) Download, install and enable/deploy the required all-in-one Address Library for SKSE Plugins with your mod manager. You will need to install the latest 1.5.x or 1.6.x version of the Address Library depending on which version of the game you are playing. If you're getting error 1114 or 617, it's probably because the Address Library isn't installed or properly enabled.
(3) Download and install the latest x64 version of the required Microsoft Visual Redistributable for Visual Studio 2019. On the linked page, it's the download that reads x64: vc_redist.x64.exe. Yes, it's a Windows install. Double-click the downloaded exe, follow the prompts, and reboot. If you're getting error 126, it's probably because the C++ Redistributable isn't installed.
(4) From the Files page, download, install and enable Part 1 of Engine Fixes with your mod manager. You will need to install the correct version of Part 1 for your game version. For those playing the latest version of Skyrim (1.6.1170+), be sure to download Part 1 version 6.2 from the Files page. EngineFixes.ini has been replaced with EngineFixes.toml in 5.3.3+. Open the UTF-8 encoded .toml file in Notepad to make your setting changes. You can delete the old EngineFixes.ini.
(5) From the Files page, download Part 2 manually. Do not install Part 2 of SSE Engine Fixes with your mod manager. Instead, extract the Part 2 archive, then copy and paste the three dll files from the archive directly into the root game directory (the folder containing SkyrimSE.exe). Do not simply place the archive file in that directory. Do not create a folder with the 3 files in that directory. Do not place the extracted files in the /Data directory. Part 2 is compatible with all versions of the game. OPTIONAL: If you are using Vortex, you can download and install Part 2 using the Mod Manager Download, but before deploying, double click the item in Vortex and change the Mod Type to Engine Injector. Then enable/deploy Part 2.
Do not rename your skse64 executables. If you have already done so, you will need to change the file names back to the original skse executable names. That means skse64_loader.exe and SkryimSE.exe. Skyrim.exe and adding an INI, as several obsolete guides tell you to do to get skse launching from Steam will not work. SSE Engine Fixes needs the original skse64_loader.exe and SkyrimSE.exe file names and files.
If you want to launch from Steam, add skse64_loader.exe as a Non-Steam Game. If Steam is open you can also launch skse64_loader.exe from a shortcut or from the mod manager and still get achievements in your Steam SSE Library and the overlay. The original Steam SSE page will always execute the standard launcher, but you can still see your achievements and screenshots there if you launch via skse64 using one of these other methods.
If you are getting Error 193, you are running an Oldrim plugin and need to uninstall it and find the SE version.
If you want to verify that Engine Fixes is running ok, open your d3dx9_42.log in your SSE game folder. It should look something like below when Engine Fixes is running properly. Don't worry about the line reading "failed to search dll plugin directory" - this just means you don't have other plugins that use the \Data\DLLPlugins directory installed.
Spoiler:
Show
skse64 plugin preloader - d3dx9_42exe path: X:\SteamLibrary\steamapps\common\Skyrim Special Edition\SkyrimSE.exe loaded into SkyrimSE.exe or SkyrimVR.exe, proxying SkyrimSE d3dx9_42 funcs and registering preload hook successhook triggered, loading dll plugins (meh's loader) failed to search dll plugin directoryDLLPlugin loader finished hook triggered, loading skse pluginsfound plugin "EngineFixes" for preloading attempting to load found pluginsattempting to load "X:\SteamLibrary\steamapps\common\Skyrim Special Edition\Data\SKSE\Plugins\EngineFixes.dll" loaded successfully and Initialize() calledloader finished
To make installing this mod easier, I've spoken with aers and we've decided to give players the option of an "All-in-one" version of the Skyrim 1.5 and 1.6 versions of this mod. If you already have the Part 1/Part 2 installed, there is no need to swap over to this new format.
Install Instructions
Instructions are provided inside the archive itself, but if you're not able to check them please see the advice below:
Vortex 1.14.8+ (Recommended) - Install as any other mod, Vortex will pick up the "vortex_override_instructions.json" file and correctly deploy the files to the game root folder by setting the mod type to "Engine Injector".
Vortex 1.14.7 and below - Install by right-clicking the archive and using "Unpack as-is". Double-click the mod row. Change the "Mod Type" selector from "Default" to "Engine Injector". Deploy mods.
Manual Installation - Open the ZIP file and extract its contents to the game root folder (where SkyrimSE.exe is located).
Mod Organizer 2 (Advanced Users only) - MO2 doesn't support applying files outside of the data folder by default. You will need to install RootBuilder if you want to install this with MO2. For simplicity you may want to do the manual installation instead.
Troubleshooting
If this isn't working in Vortex, this can only be due to error in your modding setup. Follow the steps below for the best help.
Spoiler:
Show
Please collect the following information:
Vortex version - this is displayed in the top-right of the application or in the "About" menu option from the top-right menu.
Vortex extensions installed - List any extensions shown under the "Extensions" tab. It's very likely one of these is intercepting the install of the mod and breaking it. It may be an extension for a completely unrelated game.
Once you have the required information, please post in the Vortex Support forum where we can try and help you untangle it.
im truly an idiot i never noticed in my months of playing skyrim and modding that i never had part 2 installed, im surprised i didnt have problems sooner lmao
I have over 2,4K mods and I play 300 hours using (Part 1) SSE Engine Fixes for 1.6.629-1.6.640 (6.1.1v) no problems at all. I thought I'd update the mods before starting a new character, which is why I asked about the version.
From what I remember, GOG version 1.6.659 is exactly the same version as Steam 1.6.640. I use SKSe 2.2.3v (for 1.6.659), PapyrusUtil SE - Scripting Utility Functions 4.4v (for 1.6.659).
I don't want to update my Skyrim, so why do you think I can't use version 1.6.629-1.6.640 since it worked so far, is there actually something that doesn't work that can break the Skyrim GOG 1.6.659 game??
Life saver. When my game went from 2 False Save Corruption issues in 122 hours, to one every other hour, and then immediately on a new save, I knew I needed a fix. Have not seen it in over 11 hours now.
Same here, but I managed to solve the problem after seeing others sharing how they disabled Onedrive and changed the registry for the Documents folder. SKSE relies on the logs inside Documents, where Onedrive usually makes synchronization and backup. The path is usually like this: C:\Users\USERNAME\OneDrive\Document\My Games, and there should be at least two folders called Skyrim Special Edition and Skyrim.INI. To solve the issue, "Onedrive" must not appear in the path, so I disabled Onedrive by logging out my Microsoft account on it. Then I followed this article https://support.microsoft.com/en-gb/topic/operation-to-change-a-personal-folder-location-fails-in-windows-ffb95139-6dbb-821d-27ec-62c9aaccd720 Searched for Registry Editor on Windows and opened it, browsed for the path: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders, located the tag name Personal, which stands for the Documents folder, change the original value I saw into %USERPROFILE%\Documents, and I eventually restarted my computer. After restarting my computer, Windows then generated a whole new Documents folder without Onedrive in its path like this: C:\Users\USERNAME\Documents\My Games, then I started MO2 and open SKSE, they all worked.
I have no idea why but I've tried this countless times at this point and even other ways that I googled and it won't generate a new path without onedrive in the way. Any help at this point would be appreciated I'm desperate at this point.
Hi! How to fix the correct posting of reporting EngineFixes.log ? For some reason it is created on the way C:\Users\ - me name user - \ Documents \My Games \ Skyrim.INI \ SKSE \ EngineFixes.log === Engine Fixes ver. 6.2, АЕ 1.6.1170.0.8 The mod works well, but the report file ... TRABL =)
If the tutorial was done wrong, it's not an engine bug. If the tutorial should work, then it's an engine bug.
I did this tutorial step by step. It didn't work, attacking the pillar many times did nothing. Can you tell me if they did something wrong or this tutorial works and it's an engine bug?
Tutorial incorrect: No engine bug Tutorial correct: Engine bug
Perhaps try a translation program ... like Wolf said, the 'tutorial' has nothing to do with this mod. The only thing I could guess you might be asking is for help coding from the one you believe knows all the game code because of the release of this mod that simply fixes existing issues in Bethesda's game engine.
I suggest you check with whomever is referenced on that wiki page. Modders usually put links to 'how-to-use' the resources/methods being suggested.
Currently building my new LO and i keep running into a seemingly random CTD when entering/exiting cells, the crash log mentions this mod a good amount but im not experienced with reading crash logs or how to troubleshoot them so i figured i'd drop it here and see if anyone has a better clue than me
15072 comments
BEFORE YOU START: This is a SKSE64 plugin. Therefore, you need to have the correct version of SKSE64 installed for your game version in order for this mod to function. If you don't have SKSE64 installed or don't know what SKSE64 is, do not attempt to install this mod. Learn what SKSE64 is and why you might want it here. SKSE+SkyUI installation instructions here. Once SKSE64 is properly installed, follow the Engine Fixes install steps below:
(1) RECOMMENDED: Completely remove all files and uninstall any previous installations of SSE Engine Fixes prior to starting.
(2) Download, install and enable/deploy the required all-in-one Address Library for SKSE Plugins with your mod manager. You will need to install the latest 1.5.x or 1.6.x version of the Address Library depending on which version of the game you are playing. If you're getting error 1114 or 617, it's probably because the Address Library isn't installed or properly enabled.
(3) Download and install the latest x64 version of the required Microsoft Visual Redistributable for Visual Studio 2019. On the linked page, it's the download that reads x64: vc_redist.x64.exe. Yes, it's a Windows install. Double-click the downloaded exe, follow the prompts, and reboot. If you're getting error 126, it's probably because the C++ Redistributable isn't installed.
(4) From the Files page, download, install and enable Part 1 of Engine Fixes with your mod manager. You will need to install the correct version of Part 1 for your game version. For those playing the latest version of Skyrim (1.6.1170+), be sure to download Part 1 version 6.2 from the Files page. EngineFixes.ini has been replaced with EngineFixes.toml in 5.3.3+. Open the UTF-8 encoded .toml file in Notepad to make your setting changes. You can delete the old EngineFixes.ini.
(5) From the Files page, download Part 2 manually. Do not install Part 2 of SSE Engine Fixes with your mod manager. Instead, extract the Part 2 archive, then copy and paste the three dll files from the archive directly into the root game directory (the folder containing SkyrimSE.exe). Do not simply place the archive file in that directory. Do not create a folder with the 3 files in that directory. Do not place the extracted files in the /Data directory. Part 2 is compatible with all versions of the game.
OPTIONAL: If you are using Vortex, you can download and install Part 2 using the Mod Manager Download, but before deploying, double click the item in Vortex and change the Mod Type to Engine Injector. Then enable/deploy Part 2.
Do not rename your skse64 executables. If you have already done so, you will need to change the file names back to the original skse executable names. That means skse64_loader.exe and SkryimSE.exe. Skyrim.exe and adding an INI, as several obsolete guides tell you to do to get skse launching from Steam will not work. SSE Engine Fixes needs the original skse64_loader.exe and SkyrimSE.exe file names and files.
If you want to launch from Steam, add skse64_loader.exe as a Non-Steam Game. If Steam is open you can also launch skse64_loader.exe from a shortcut or from the mod manager and still get achievements in your Steam SSE Library and the overlay. The original Steam SSE page will always execute the standard launcher, but you can still see your achievements and screenshots there if you launch via skse64 using one of these other methods.
If you are getting Error 193, you are running an Oldrim plugin and need to uninstall it and find the SE version.
That is all.
skse64 plugin preloader - d3dx9_42exe path: X:\SteamLibrary\steamapps\common\Skyrim Special Edition\SkyrimSE.exeloaded into SkyrimSE.exe or SkyrimVR.exe, proxying SkyrimSE d3dx9_42 funcs and registering preload hook
successhook triggered, loading dll plugins (meh's loader)
failed to search dll plugin directoryDLLPlugin loader finished
hook triggered, loading skse pluginsfound plugin "EngineFixes" for preloading
attempting to load found pluginsattempting to load "X:\SteamLibrary\steamapps\common\Skyrim Special Edition\Data\SKSE\Plugins\EngineFixes.dll"
loaded successfully and Initialize() calledloader finished
To make installing this mod easier, I've spoken with aers and we've decided to give players the option of an "All-in-one" version of the Skyrim 1.5 and 1.6 versions of this mod. If you already have the Part 1/Part 2 installed, there is no need to swap over to this new format.
Install Instructions
Instructions are provided inside the archive itself, but if you're not able to check them please see the advice below:
Troubleshooting
If this isn't working in Vortex, this can only be due to error in your modding setup. Follow the steps below for the best help.
Please collect the following information:
Once you have the required information, please post in the Vortex Support forum where we can try and help you untangle it.
I'm using Skyrim SE GOG 1.6.659 (I use also Backported Extended ESL Support) Which version should I use??
I thought I'd update the mods before starting a new character, which is why I asked about the version.
From what I remember, GOG version 1.6.659 is exactly the same version as Steam 1.6.640.
I use SKSe 2.2.3v (for 1.6.659), PapyrusUtil SE - Scripting Utility Functions 4.4v (for 1.6.659).
I don't want to update my Skyrim, so why do you think I can't use version 1.6.629-1.6.640 since it worked so far, is there actually something that doesn't work that can break the Skyrim GOG 1.6.659 game??
Everything works, nothing broken.
SKSE relies on the logs inside Documents, where Onedrive usually makes synchronization and backup. The path is usually like this: C:\Users\USERNAME\OneDrive\Document\My Games, and there should be at least two folders called Skyrim Special Edition and Skyrim.INI.
To solve the issue, "Onedrive" must not appear in the path, so I disabled Onedrive by logging out my Microsoft account on it. Then I followed this article https://support.microsoft.com/en-gb/topic/operation-to-change-a-personal-folder-location-fails-in-windows-ffb95139-6dbb-821d-27ec-62c9aaccd720
Searched for Registry Editor on Windows and opened it, browsed for the path: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders, located the tag name Personal, which stands for the Documents folder, change the original value I saw into %USERPROFILE%\Documents, and I eventually restarted my computer.
After restarting my computer, Windows then generated a whole new Documents folder without Onedrive in its path like this: C:\Users\USERNAME\Documents\My Games, then I started MO2 and open SKSE, they all worked.
For some reason it is created on the way C:\Users\ - me name user - \ Documents \My Games \ Skyrim.INI \ SKSE \ EngineFixes.log
===
Engine Fixes ver. 6.2, АЕ 1.6.1170.0.8
The mod works well, but the report file ... TRABL =)
update
Use SKSE Log Redirector
This tutorial doesn't work. Either an engine bug or a tutorial done wrong. Which?
Thanks...
I did this tutorial step by step. It didn't work, attacking the pillar many times did nothing. Can you tell me if they did something wrong or this tutorial works and it's an engine bug?
Tutorial incorrect: No engine bug
Tutorial correct: Engine bug
That should be more clear...
I suggest you check with whomever is referenced on that wiki page. Modders usually put links to 'how-to-use' the resources/methods being suggested.
Good luck!
I don't have the skill level in modding to tell if it's done wrong. It's either done wrong or an engine bug.
End topic...
https://pastebin.com/tKCNV1aY