You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
loot / loot Public
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I've been using LOOT alongside Mod Organizer for a long time, and I was pretty surprised when, for some reason, LOOT isn't showing anything at all when I launched it through MO. It's been working fine in the past few days, however.
Here's how it looks like on my end. The window shows up fine but nothing else follows. As you can see I can't do anything useful with the UI not actually showing up. Minimizing and restoring the window doesn't work.
At that time I was using LOOT 0.7, so I checked the repo if there's a new release. Turns out 0.8 is already out so I updated (by grabbing the latest installer). However, the problem still persists.
I tried running LOOT directly from Explorer inside its directory. The UI is blank for quite some time, but after about a minute or two it starts up normally, however, it's not really useful for me at that point as I use MO and all my third-party ESMs and ESPs are absent from the list. Running LOOT through MO still doesn't work. I could try waiting for it and hope it works after maybe an hour but having to wait hours just so that I can manage my load order is a frustrating idea.
I turned on enableDebugLogging in the settings.yaml file, ran LOOT through MO again, and here's the resulting log:
[0831/150942:WARNING:resource_bundle.cc(304)] locale_file_path.empty() [0831/150942:ERROR:main_delegate.cc(567)] Could not load locale pak for en-US [0831/150942:WARNING:resource_bundle.cc(501)] locale resources are not loaded [0831/150942:ERROR:child_process_launcher.cc(479)] Failed to launch child process [0831/150942:ERROR:child_process_launcher.cc(479)] Failed to launch child process Apologies in advance if all the information I've submitted isn't that quite helpful. I'll be ready to answer any follow up questions that you may have. Additionally I'll also try checking if this is an MO issue (I currently use an outdated version of MO), and I'll update this issue if anything useful turns up.
The text was updated successfully, but these errors were encountered: