Wererommel Posted July 12 Posted July 12 Playing Skyrim SE v.1.5.97 in Windows 10. I just moved my game to a different folder. (It had been in a "Fallout 4" folder for years, but I reinstalled Steam in a "SteamLibrary" folder and moved everything there.) But when I run FNIS in Vortex, I get this message: >>Warning: Expected generator path: D:\Fallout 4\steamapps\common\Skyrim Special Edition\data\tools\GenerateFNIS_for_Users not found<< Even though the FNIS installation in Vortex now says: D:\SteamLibrary\steamapps\common\Skyrim Special Edition\Data\tools\GenerateFNIS_for_Users The old address is still stored somewhere, and I can't find it or change it.
Wererommel Posted July 12 Author Posted July 12 Could the problem be with Steam? Starting Skyrim SE with the Launcher gets me this. There is no problem with my files.
ChemBoy1 Posted July 12 Posted July 12 Did you move the game in the Steam interface? You cannot just move files around. That will absolutely never work. You have to move the game to a new library location in the Steam app. Also the old path you were using (inside a "Fallout4" folder) doesn't make any sense for Steam. Steam ONLY puts games in the default "Program Files (x86)" folder or in a "SteamLibrary" folder at the root of a drive.
Wererommel Posted July 12 Author Posted July 12 I did that, I moved it according to instructions. According to Steam, Skyrim is installed where it presently resides, in the SteamLibrary on the D drive. (Incidentally, it ran fine for years in the Fallout 4 folder.) (Sorry about the German, I am practicing that language.)
Wererommel Posted July 12 Author Posted July 12 Steam has a Library Repair function (Who knew?), but it didn't change anything, so I guess that isn't the problem.
TheGreatFalro Posted July 12 Posted July 12 Try running the game with the vanilla launcher once, then run FNIS again.
Wererommel Posted July 12 Author Posted July 12 Like I said, the Launcher produces this error message. If anyone know what it means, please tell me!
TheGreatFalro Posted July 13 Posted July 13 Sorry, missed that. I would use the "Purge Mods" button in Vortex, then verify the game in Steam. Note that this will restore it to the latest version, so if you've downgraded, you'll need to do it again. EDIT: Actually, have you downgraded? From some research it seems that error comes from a broken downgrade.
Wererommel Posted July 13 Author Posted July 13 The downgrade was working fine. I had been playing 1.5.97 for years, until one stupid unimportant update to a mod ruined everything. Naturally, removing the mod didn't help. My saves were trashed, so I had to start over. There were a lot of changes to consider. I began by trying Wabbajack. No one had told me that it only worked with English. So I had to reinstall, unfortunately with the latest version, so then I had to downgrade and restore my load order. Vortex worked like a champ and soon brought me back to where I was before, but still without saves. My next effort was to upgrade the graphics. I tried Skyrim Remastered – Optimized, not knowing that it only worked with the AE edition. So I had to strip all that out and try Skyland AIO, a simple texture collection that I figured would not cause a lot of problems, and it did not, until I added Majestic Mountains, which was incompatible. Once again, I had to rebuild my load, with MM loaded last. That worked great, and I thought I had it licked, but there were a lot of mod updates to go through. Half my load had to be updated. I figured this would be tedious and time consuming, but at least I knew that these mods were compatible. Bad mistake! After I had gone through a long list of updates, I tested it, and the game wouldn’t start at all, it crashed at the first screen. So then, I had to strip the updates out, one by one, testing with FNIS as I went, and monotonously crashing over and over without finding the problem. After about a hundred mods, Skyrim blessed me with an error message: “DMSE Error! ConsoleUtil 1.04 or newer must be installed.” Having taken care of that, I got another message: Steam_api64.dll was missing. WTF? Following instructions online, I downloaded and installed Steam_api64.dll. When that didn’t work, I found other instructions that said I should NEVER do that, because these download sites were scams and full of viruses. Also, I had the wrong version. I reinstalled from BU, following the new instructions, but it still wouldn’t run. Seeking further instructions, I saw someone recommended reinstalling Steam, which sounded like a good plan, but I didn’t know that Steam can only be installed into an EMPTY folder. So then, I had to move all my games to the new folder and delete the old one, which brings me to where I am now.
Wererommel Posted July 13 Author Posted July 13 I am deep in the weeds now, poking through the various files in the SteamLibrary folder, trying to find the error. Not there yet, but I did find this in the GameOverlayUI.exe.log: Sun Jul 13 06:46:30 2025 UTC - GameOverlay process started: pid: 18028 Sun Jul 13 06:46:30 2025 UTC - GameOverlay process connecting to: pid: 16348 Sun Jul 13 06:46:30 2025 UTC - BuildID: 1751405894 Sun Jul 13 06:46:30 2025 UTC - Steam Path: D:\SteamLibrary Sun Jul 13 06:46:31 2025 UTC - Got gameid on commandline: 289070 Sun Jul 13 06:46:35 2025 UTC - Detected possibly crashed/killed game, exiting Sun Jul 13 06:46:35 2025 UTC - Shutting down overlay Sun Jul 13 06:46:35 2025 UTC - src\common\pipes.cpp (861) : CClientPipe::BWriteAndReadResult: BWrite failed Sun Jul 13 06:46:35 2025 UTC - src\common\pipes.cpp (861) : Fatal assert; application exiting Sun Jul 13 06:46:35 2025 UTC - _ExitOnFatalAssert What this says to me is that Steam tried to run Skyrim, but found it had already crashed. So I would assume that there is nothing wrong with the Steam setup. The problem lies elsewhere. I also found this in vortex.deployment.dinput.json, from the Skyrim Special Edition folder: "instance": "d8862461-96a8-41a4-97e9-53ff65e9c4ec", "version": 1, "deploymentMethod": "hardlink_activator", "gameId": "skyrimse", "deploymentTime": 1752279201181, "stagingPath": "D:\\Vortex Mods\\skyrimse", "targetPath": "d:\\steamlibrary\\steamapps\\common\\Skyrim Special Edition", So Vortex apparently has the correct paths to run Skyrim. So where did the faulty path reported by FNIS come from? Still working on that. The Vortex log in Roaming under AppData on the D drive says this: 2025-07-12T21:02:25.328Z [DEBUG] [fnis-integration] fnis tool setup {"path":"D:\\SteamLibrary\\steamapps\\common\\Skyrim Special Edition\\Data\\tools\\GenerateFNIS_for_Users\\GenerateFNISforUsers.exe","version":"7.6.0.0"} Which only tells me that Vortex thinks FNIS is set up correctly. Vortex thinks everything is cool, only the game doesn’t run. The GenerateFNIS_LogFile log on the D drive says this: 0 Start Debug FNIS Behavior V7.6 7/12/2025 2:05:19 PM Generator: D:\SteamLibrary\steamapps\common\Skyrim Special Edition\Data\tools\GenerateFNIS_for_Users\GenerateFNISforUsers.exe Skyrim SE 64bit: ??.??.?? - D:\Fallout 4\steamapps\common\Skyrim Special Edition\ (Steam) >>Warning: Expected generator path: D:\Fallout 4\steamapps\common\Skyrim Special Edition\data\tools\GenerateFNIS_for_Users not found<< What is going on here? Where did this “Expected generator path” come from? I still don’t know. I am attaching the latest crash log which is from two days before, when the game ran long enough to crash. Just in case it might be useful. Crash Log 2025-07-10-14-30-29.txt
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