I was having this issue yesterday after a complete reinstall of SSE, my mods, and tools, and by the time I figured this out, I was just so happy it worked that I ran Loot, made a bashed patch, and started playing. I apologize that I don't have any logs to go with this. I figure 14gb of ram is plenty for Windows 10 or Arch Linux and whatever game I'm running.
This is a setup that I do for any game that's under 32gb of size. What I do is either mount the image to a dummy drive (stuff that'll increase image size) or to a ramdisk (to play), and I keep a junction that points to my image (either setup) in my steam directory. For some reason, I wasn't able to change the install directory from within Loot, tried both as a regular user and running as administrator, but after changing it by hand, it works just fine and I haven't had a single issue since.įor some info on my setup, I have SSE, my mods (not archives), and various mod tools installed to a 30GB ramdisk\image because I have a bunch of ram (48gb) and no SSD.
Luckily it is a simple fix of modifying "%LocalAppData%\LOOT\settings.yaml" and manually entering the path to where Skyrim SE is physically located and not the path of the junction (for me it is Steam's default Skyrim SE folder). I've discovered that Loot isn't able to always detect or sort plugins after installation when the Skyrim SE install directory has a junction to a different location.
0 kommentar(er)
