I would greatly appreciate any help or suggestions on how to get things working again, and will provide any necessary additional information!
#LOOT FOR SKYRIM STEP MOD#
My load mechanism is set to Script Extender and I am closing out of Mod Organizer before trying to run the game through Steam. I tried disabling the DLCs just in case, no change. However, when I create a new vanilla profile, not changing any ini settings or load order of the DLCs, I crash before the main menu can load. I can load the vanilla game along with OBSE installed using the "default" profile of MO. I am using the Steam GOTY edition with all DLCs. Upon reinstalling though I've encountered a new issue. After a lot of trial and error and aggravation I ended up discovering my issue with the CSE was not related to MO at all. However, I was encountering an issue using the Construction Set Extender, and decided to use the nuclear option and re-install, backing up my MO profiles and such. I have been using Mod Organizer as the manager for my Oblivion installation for some time, and thanks in part to the information in this forum it has worked out pretty well. I haven't changed anything from the defaults.Ĥ\binary=C:/Games/ModOrganizer/loot/LOOT.exeĥ\binary=C:/Games/ModOrganizer/TES5Edit/TES5Edit.exeĥ\arguments=-o:\"C:\\Users\\xxxxxx\\Documents\\My Games\\skyrim\"Ħ\binary=C:/Games/TESV Skyrim LE/Mopy/Wrye Bash.exeġ\binary=C:/Games/TESV Skyrim LE/skse_loader.exeġ\workingDirectory=C:/Games/TESV Skyrim LEħ\binary=C:/Games/ModOrganizer/DynDOLOD/DynDOLOD.exeĨ\binary=C:/Games/ModOrganizer/DynDOLOD/TexGen.exe I'm guessing this is the relevant section of the MO.ini file you were referring to. I suppose it's possible that LOOT itself is doing this, as this whole installation is new from scratch (I've had Skyrim in mothballs for over a year).
#LOOT FOR SKYRIM STEP SOFTWARE#
Perhaps you may need to add MO as an exemption in whichever AV software you use. If you are indeed seeing that folder deleted then I would check that your AV software isn't doing something it shouldn't. It's easy enough to workaround, just re-extract the "resources" subdir from the archive.but it is an annoying PITA.Īny of the MO devs care to take a look and/or shed some light on what's happening? I can't predictably reproduce the behavior, so I've no idea what's triggering it. Sure enough, I found it all in my recycle bin.įor some reason, MO decides to nuke that subdirectory during LOOT execution. This time I went and looked at the LOOT installation before reinstalling, and I found that everything within the "/resources" subdirectory had been deleted.
After a couple runs, the white screen bug hit again. So I reinstalled LOOT from its archive, and the problem vanished.for a while. I tried launching LOOT natively, and got the same result.
It's unresponsive to clicks or keypresses, but it can be killed normally. I've run into the bug/issue where I launch LOOT from within MO, and the window that comes up is an empty white box.
0 kommentar(er)
