Jump to content
  • 0

Launching LOOT shows a blank white screen


rolandito

Question

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.  It's unresponsive to clicks or keypresses, but it can be killed normally.

 

I tried launching LOOT natively, and got the same result.

 

So I reinstalled LOOT from its archive, and the problem vanished...for a while.  After a couple runs, the white screen bug hit again.

 

This time I went and looked at the LOOT installation before reinstalling, and I found that everything within the "/resources" subdirectory had been deleted.  Sure enough, I found it all in my recycle bin.

 

For some reason, MO decides to nuke that subdirectory during LOOT execution.  Not always, though.  I can't predictably reproduce the behavior, so I've no idea what's triggering it.

 

It's easy enough to workaround, just re-extract the "resources" subdir from the archive...but it is an annoying PITA.

 

Any of the MO devs care to take a look and/or shed some light on what's happening?

 

 

FYI, my setup is:

LOOT v0.10.3-0-g0fcf788_dev_Win32

Mod Organizer v1_3_11

Win7 x64, Core i5-3570 @ 3.4GHz, 16GB RAM, 2GB GTX660

Skyrim LE + STEP:Core

Link to comment
Share on other sites

5 answers to this question

Recommended Posts

  • 0

MO does not, indeed cannot, delete anything from anywhere when calling any executables. Calling LOOT is just a system call defined in the INI, which you should post so we can examine it, and once LOOT is called MO makes no further calls to it until you exit LOOT and MO regains focus.

 

If you are indeed seeing that folder deleted then I would check that your AV software isn't doing something it shouldn't. Perhaps you may need to add MO as an exemption in whichever AV software you use.

Link to comment
Share on other sites

  • 0

If you are indeed seeing that folder deleted then I would check that your AV software isn't doing something it shouldn't. Perhaps you may need to add MO as an exemption in whichever AV software you use.

 

I don't use AV software.

 

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).

 

I'm guessing this is the relevant section of the MO.ini file you were referring to.  I haven't changed anything from the defaults.

[customExecutables]
1\title=SKSE
1\custom=true
1\toolbar=false
1\ownicon=true
2\title=Skyrim
2\custom=false
2\toolbar=false
2\ownicon=false
size=8
3\title=Skyrim Launcher
3\custom=false
3\toolbar=false
3\ownicon=false
4\title=LOOT
4\custom=true
4\toolbar=false
4\ownicon=true
4\binary=C:/Games/ModOrganizer/loot/LOOT.exe
4\arguments=
4\workingDirectory=
4\closeOnStart=false
4\steamAppID=
5\title=TES5Edit
5\custom=true
5\toolbar=false
5\ownicon=true
5\binary=C:/Games/ModOrganizer/TES5Edit/TES5Edit.exe
5\arguments=-o:\"C:\\Users\\xxxxxx\\Documents\\My Games\\skyrim\"
5\workingDirectory=
5\closeOnStart=false
5\steamAppID=
6\title=Wrye Bash
6\custom=true
6\toolbar=false
6\ownicon=true
6\binary=C:/Games/TESV Skyrim LE/Mopy/Wrye Bash.exe
6\arguments=
6\workingDirectory=
6\closeOnStart=false
6\steamAppID=
1\binary=C:/Games/TESV Skyrim LE/skse_loader.exe
1\arguments=
1\workingDirectory=C:/Games/TESV Skyrim LE
1\closeOnStart=false
1\steamAppID=
7\title=DynDOLOD
7\custom=true
7\toolbar=false
7\ownicon=true
7\binary=C:/Games/ModOrganizer/DynDOLOD/DynDOLOD.exe
7\arguments=
7\workingDirectory=
7\closeOnStart=false
7\steamAppID=
8\title=DynDOLOD TexGen
8\custom=true
8\toolbar=false
8\ownicon=true
8\binary=C:/Games/ModOrganizer/DynDOLOD/TexGen.exe
8\arguments=
8\workingDirectory=
8\closeOnStart=false
8\steamAppID=
Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.