Jump to content

[RELz] LOOT - Load Order Optimisation Tool


WrinklyNinja

Recommended Posts

Alright. Got another one, once again related to index numbers .. though I'm not sure if it's related to the bug just mentioned, or unique to "loot_0.12.4-33-g3b912f8_modernise-frontend.7z"..

Anyway, while still in the same "LOOT session" (I did not close LOOT inbetween), I switched to Fallout 4 and got this, some index numbers got displayed wrongly. LOOTDebugLog.txt.

Opening the editor through doubleclick on DLCCoast.esm (which wasn't affected) did not change anything. However opening the editor through doubleclick on the affected plugins DID fix the issue, but only for those. Here's a screenshot after doubleclick-opening-the-editor on two of the affected plugins. Screenshot

Link to comment
Share on other sites

I'm currently testing for issue 910, but out of the blue I suddenly get this message when I start LOOT. LOOTDebugLog.txt:

Quote

[19:26:30.082911] [error]: Chromium console message from http://loot/ui/app.bundle.js at line 1: Error: 403 error making request GET

https://api.github.com/repos/loot/loot/releases/latest: "Forbidden"
    at new t (http://loot/ui/app.bundle.js:1:58764)
    at http://loot/ui/app.bundle.js:1:57842
    at <anonymous>

Not sure what to do or why that happened. Never had this problem before.

Happens with "loot_0.12.4-0-g62ca11c_dev", "loot_0.12.4-33-g3b912f8_modernise-frontend" and "loot_0.12.4-34-gf3fe927_modernise-frontend".

Edit: :huh: Now it's working again. Did I open LOOT to often within a short period of time?

Link to comment
Share on other sites

25 minutes ago, pStyl3 said:

I'm currently testing for issue 910, but out of the blue I suddenly get this message when I start LOOT. LOOTDebugLog.txt:

Not sure what to do or why that happened. Never had this problem before.

Happens with "loot_0.12.4-0-g62ca11c_dev", "loot_0.12.4-33-g3b912f8_modernise-frontend" and "loot_0.12.4-34-gf3fe927_modernise-frontend".

Edit: :huh: Now it's working again. Did I open LOOT to often within a short period of time?

Yes, that's the update check getting rate-limited.

Link to comment
Share on other sites

Hello, 

I just recently updated my LOOT keep receiving an error, this is my first time having this issue.

[20:37:39.166114] [warning]: Chromium console message: Styling master document from stylesheets defined in HTML Imports is deprecated, and is planned to be removed in M65, around March 2018. Please refer to https://goo.gl/EGXzpw for possible migration paths.

[20:37:39.230118] [warning]: Blocking load of resource at https://fonts.googleapis.com/css?family=Roboto+Mono:400,700|Roboto:400,300,300italic,400italic,500,500italic,700,700italic

[20:37:39.756148] [warning]: Chromium console message from http://loot/ui/bower_components/neon-animation/neon-animation-runner-behavior.html at line 40: Couldnt play

[20:37:40.697202] [warning]: No masterlist present at C:\Users\Leslie\AppData\Local\LOOT\FalloutNV\masterlist.yaml

[20:37:52.014849] [error]: Exception while executing query: Git operation failed. Details: -17; unknown certificate check failure: libgit2 error

[20:37:52.017849] [error]: Chromium console message from http://loot/ui/js/handlePromiseError.js at line 14: Error: Oh no, something went wrong! You can check your LOOTDebugLog.txt (you can get to it through the main menu) for more information.
    at onFailure (http://loot/ui/js/query.js:43:16)

 

My FalloutNV folder it has nothing in it, and a folder that appeared called "1e5b-d926-1d61-f8c5" it contains 4 files: loadorder.bak.0, loadorder.bak.1, loadorder.bak.2, and masterlist.yaml.

Nevermind, I followed one of the post #882 and the windows fix fixed me right up. Thank you so much!

Link to comment
Share on other sites

Greetings guys!

I've been using LOOT for a long time with no issues. It has always been saving me a lot of time and nerves sorting my plugins.

Today I thought "Why not download some more mods and play Skyrim?". With downloading and installing done I turned to LOOT to sort everything right, and to my displeasure, I saw a wall of red text saying this:
"An error occurred while parsing the metadata list(s): yaml-cpp: error at line 343, column 13: bad conversion: 'text' key missing from 'message content' object." LOOT offered me to either update masterlist (That gave me an error too) or to edit metadata in 'userlist.yaml' (which I nor could find, neither would be able to edit right). Ok, I noticed there was a 0.12.4 update and installed it. Nothing changed.

Then I decided to check whether it works for other supported games. Sorting plugins and updating masterlists for Fallout NV, Fallout 3 and even Oblivion doesn't work too, instead it gives me this:

"Oh no, something went wrong! You can check your LOOTDebugLog.txt (you can get to it through the main menu) for more information."

I myself can not understand a thing in the Debug Log, for I am not really advanced in this kind of things.

Looking forward to your help guys, please!

LOOTDebugLog.txt

Link to comment
Share on other sites

17 minutes ago, pStyl3 said:

Go to C:\%localappdata%\LOOT

Backup that folder and then delete it. Did that help?

In order to fix the second problem (downloading the masterlist), you need to make sure, that you have enabled TLS 1.2 support. Updating your Windows is also recommended. (here's why this is necessary now)

Deleting the Loot folder rid me of the wall of red text. Still, Loot can't update masterlist or sort plugins. I am still getting the "oh no, something went wrong error. Attaching the new Loot debug log.

Found some more info on similar issues and installed this (https://support.microsoft.com/en-us/help/3140245/update-to-enable-tls-1-1-and-tls-1-2-as-a-default-secure-protocols-in) "easy fix". Didn't help.

Edit: So, I've read this (https://githubengineering.com/crypto-removal-notice/). Does that really mean I can not use LOOT anymore?

LOOTDebugLog.txt

Link to comment
Share on other sites

Rebooted my pc. No change. Will enabling TSL 1.1, 1.2 manually like it is done here by "jeffrey-opdam" help? (https://github.com/libgit2/libgit2sharp/issues/1524) Or where can I get the registry edit (kind of scary to do it manually tbh)?

Edit: No matter the cost, I decided to try. Executed the following commands in the command prompt:

reg add "HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client" /v DisabledByDefault /t REG_DWORD /d 0 /f

reg add "HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client" /v Enabled /t REG_DWORD /d 1 /f

reg add "HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client" /v DisabledByDefault /t REG_DWORD /d 0 /f

reg add "HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client" /v Enabled /t REG_DWORD /d 1 /f

And it did nothing.

 

Plan B

May anyone here be ever so kind and drop me an up-to-date masterlist for skyrim? With "Update masterlist before sorting" turned off in LOOT it may as well work, might it not?

Link to comment
Share on other sites

6 hours ago, RomRomRya said:

Rebooted my pc. No change. Will enabling TSL 1.1, 1.2 manually like it is done here by "jeffrey-opdam" help? (https://github.com/libgit2/libgit2sharp/issues/1524) Or where can I get the registry edit (kind of scary to do it manually tbh)?

Edit: No matter the cost, I decided to try. Executed the following commands in the command prompt:

reg add "HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client" /v DisabledByDefault /t REG_DWORD /d 0 /f

reg add "HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client" /v Enabled /t REG_DWORD /d 1 /f

reg add "HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client" /v DisabledByDefault /t REG_DWORD /d 0 /f

reg add "HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client" /v Enabled /t REG_DWORD /d 1 /f

And it did nothing.

 

Plan B

May anyone here be ever so kind and drop me an up-to-date masterlist for skyrim? With "Update masterlist before sorting" turned off in LOOT it may as well work, might it not?

Try replacing the loot_api.dll in your LOOT install with this one.

Link to comment
Share on other sites

7 hours ago, WrinklyNinja said:

Try replacing the loot_api.dll in your LOOT install with this one.

Did that. And that didn't work.

Thought the reason was my old pc (haven't updated windows 7 in like 5 years). Downloaded all of the updates and installed most of them (except those which cause my PC to show me blue screen). And... LOOT still told me "oh no! Something went wrong".

I'm out of ideas.

Edit: Attaching Log file. Maybe something changed?

Edit2: Loot is running as administrator. Also gave it full permission in the firewall. Deleted my antivirus. Just in case attaching dxdiag: maybe something is horribly wrong with my system?

LOOTDebugLog.txt

DxDiag.txt

Link to comment
Share on other sites

Could you tell us your exact Windows 7 version? So which one of these do you use: Home Basic / Home Premium / Professional / Ultimate / Enterprise

Link to comment
Share on other sites

24 minutes ago, pStyl3 said:

Could you tell us your exact Windows 7 version? So which one of these do you use: Home Basic / Home Premium / Professional / Ultimate / Enterprise

Windows 7 ultimate x64. You could find this info in dxdiag.txt

Edit: oh, somewhy it is in russian there...

Edit2: Is there a way to test if my TLS 1.2 protocol even works?

Link to comment
Share on other sites

hello everyone.
got here because of the problem that romromrya described over the last few comments.
some things are/were different in my case:
1) win 7 64bit home premium, manually keeping it up to date (not older than 7 days).
2) no red text when starting LOOT.

since i like tools that don't have to be installed, i always used the 7z version. after letting skyrim rest for months, i decided to get back to it and updated all my mods via NMM. then LOOT (v0.11.0) told me to update.
did it, got the same problems like RomRomRye (except the mentioned red text).
went to the loot.github page -> download section -> FAQ link -> common issues #17. -> microsoft TLS link. there you get the KB through some catalogue thingie. did that, saw i was already installed.
found the link to the "MSVC 2015 x86 redistributable" in the documentation of v0.12.4 and "repaired" it.
scanned for OS updates, found two and installed them.
rebooted my system, deleted the LOOT folder in my locals, installed the .exe version of v0.12.4 and started it with admin rights.
LOOT still didn't work.
then i found this forum/topic and the link to the v0.12.5-api-dll, and tried it with the new dll.
now it works! :)
decided to sign up to tell you that your api-dll works for me.

kind regards.

Link to comment
Share on other sites

Thanks for some info, Manji!

Could you decipher this abbreviation: MSVC 2015 x86 redistributable. Is it Microsoft Visual C++? If so, I've just installed the newest version.

For some reason, I missed that "catalogue thingie". Found it now, thanks to you. Installing it right now. Really do hope it'll help.

Edit: Okay, this is getting ridiculous. I'm getting the same errors in the log as before. No change at all.

I'm probably missing something...

 

Edit2: Yes, indeed I did miss something! After all the things done the last necessary step was to delete the LOOT folder in %appdata%/local! And LOOT finally managed to update the masterlist.

Was that the hidden ".git" folder that was causing this? I was practically completely reinstalling LOOT after every step.

Anyway, thanks a whole ton guys for your help! Don't even want to imagine what would I have to do without you.

Cheers!

 

Edit3: Excuse me for making the matter ten times harder than it really was.

Link to comment
Share on other sites

 [warning]: Chromium console message: Styling master document from stylesheets defined in HTML Imports is deprecated, and is planned to be removed in M65, around March 2018. Please refer to https://goo.gl/EGXzpw for possible migration paths.
 [warning]: Blocking load of resource at https://fonts.googleapis.com/css?family=Roboto+Mono:400,700|Roboto:400,300,300italic,400italic,500,500italic,700,700italic
 [warning]: No masterlist present at C:\Users\David\AppData\Local\LOOT\Skyrim\masterlist.yaml
 [error]: Exception while executing query: Git operation failed. Details: -17; unknown certificate check failure: libgit2 error
 [error]: Chromium console message from http://loot/ui/js/handlePromiseError.js at line 14: Error: Oh no, something went wrong! You can check your LOOTDebugLog.txt (you can get to it through the main menu) for more information.
    at onFailure (http://loot/ui/js/query.js:43:16)


This is all I get when I try to use LOOT, does anyone know whats wrong with it?

Link to comment
Share on other sites

5 hours ago, spiritwolf said:

 [warning]: Chromium console message: Styling master document from stylesheets defined in HTML Imports is deprecated, and is planned to be removed in M65, around March 2018. Please refer to https://goo.gl/EGXzpw for possible migration paths.
 [warning]: Blocking load of resource at https://fonts.googleapis.com/css?family=Roboto+Mono:400,700|Roboto:400,300,300italic,400italic,500,500italic,700,700italic
 [warning]: No masterlist present at C:\Users\David\AppData\Local\LOOT\Skyrim\masterlist.yaml
 [error]: Exception while executing query: Git operation failed. Details: -17; unknown certificate check failure: libgit2 error
 [error]: Chromium console message from http://loot/ui/js/handlePromiseError.js at line 14: Error: Oh no, something went wrong! You can check your LOOTDebugLog.txt (you can get to it through the main menu) for more information.
    at onFailure (http://loot/ui/js/query.js:43:16)


This is all I get when I try to use LOOT, does anyone know whats wrong with it?

I may be wrong, but it seems you've got the same problem as I had. Update your windows, exterminate LOOT from your PC, reboot and install LOOT again.

Don't forget to wipe out the LOOT folder in %appdata%/local

Link to comment
Share on other sites

LOOT v0.12.5 released!

The big change in this release is that libgit2 was updated to opt-in to TLS 1.2 support, so I updated the LOOT API to include that, and Windows 7 users should no longer have to do anything to fix GitHub connectivity.

 

5 hours ago, spiritwolf said:

 [warning]: Chromium console message: Styling master document from stylesheets defined in HTML Imports is deprecated, and is planned to be removed in M65, around March 2018. Please refer to https://goo.gl/EGXzpw for possible migration paths.
 [warning]: Blocking load of resource at https://fonts.googleapis.com/css?family=Roboto+Mono:400,700|Roboto:400,300,300italic,400italic,500,500italic,700,700italic
 [warning]: No masterlist present at C:\Users\David\AppData\Local\LOOT\Skyrim\masterlist.yaml
 [error]: Exception while executing query: Git operation failed. Details: -17; unknown certificate check failure: libgit2 error
 [error]: Chromium console message from http://loot/ui/js/handlePromiseError.js at line 14: Error: Oh no, something went wrong! You can check your LOOTDebugLog.txt (you can get to it through the main menu) for more information.
    at onFailure (http://loot/ui/js/query.js:43:16)


This is all I get when I try to use LOOT, does anyone know whats wrong with it?

Try updating to the new release.

  • Thanks 2
Link to comment
Share on other sites

Just about to update Nexus :beer:

@pStyl3 I will only update the file and the Changelog, just to get it out there.

Edit : Its done, and a test download proved to be fine .. I used it to update myself.

Link to comment
Share on other sites

Woah heck no, Wrinklyninja deserves all praise for this project, and if anyone deserves thanks for maintaining the Nexus Page that would be pStyl3, he does an excellent job of fielding all questions and problems there. I just jumped in because I was loafing around at the time :), and had a rough guess pStyl3 might not be around for a while.

Link to comment
Share on other sites

After a few bumps along the way, I think I've finally implemented plugin groups, and they're ready for some testing in this build. Along with adding support, I've also updated the masterlists (apart from Oblivion's and original Skyrim's, they're still to do) replacing priorities with groups in new "v0.13" branches, and the linked build uses those branches by default. I haven't yet removed support for priorities, they currently get evaluated after groups. Also the group editor UI is still very rough, but it's functional.

To recap plugin groups for anyone not following their associated GitHub issues, they will replace priorities and are a way of saying "load this set of plugins after that set of plugins". Groups have a name and a list of zero or more other groups they load after. Each plugin belongs to one group (the "default" group by default). At sorting time groups are transformed into sets of plugins, so each plugin can load after a set of other plugins that is the superset of the groups its group loads after, the groups they load after, and so on recursively.

Group sorting has a couple of rules that are hopefully intuitive but which I haven't found a way to explain succinctly.

  1. Groups aren't allowed to cyclicly load after one another.
  2. A group can't load after a group that has not been defined.
  3. Group sorting derives "soft" rules that have lower precedence than "hard" rules derived from plugin masters, master flag values and requirement and "load after" metadata. This means that if enforcing a group-derived rule between two plugins in presence of all "hard" rules and the absence of any other "soft" rules would introduce a cycle, the rule is skipped instead. Note that this doesn't guard against the case where two group-derived rules are acyclic when applied individually but cause a cycle when both are enforced.

Whereas priorities can never cause a cycle, as the above mentions groups can, so it's possible my masterlist updates have broken things. Unfortunately it's impractical to exhaustively test this, but I'm interested if anyone comes across a breakage, as well as any bugs, opinions on usability, suggestions for improvements, etc.

Link to comment
Share on other sites

I will give this a proper testing Wednesday and Thursday evening.

Once we find this to be working just right, it would probably be a good idea to perform an "open beta" of some sort, in order to stress test the adjusted masterlists. I imagine in addition to posting here, pinning a new post over at Nexus and/or writing up something on reddit will do the job to get the word out.

Link to comment
Share on other sites

Something that's just crossed my mind is that I don't actually know the performance impact of debug logging: it's a toggle that's off by default because I've been assuming it can have a significant impact, but I can't remember actually testing that. My PC isn't a good setup for doing so, so I'd be very grateful if anyone's got a more middling-spec machine with lots of mods installed and can compare how long LOOT takes to do things (e.g. startup, masterlist update, sorting) with and without debug logging enabled. Stopwatch accuracy should be fine.

If it turns out there isn't really an impact, I can remove that setting and just have debug logging enabled all the time, putting an end to having to ask for debug logs but with the setting enabled.

On 20/03/2018 at 7:01 AM, pStyl3 said:

I will give this a proper testing Wednesday and Thursday evening.

Once we find this to be working just right, it would probably be a good idea to perform an "open beta" of some sort, in order to stress test the adjusted masterlists. I imagine in addition to posting here, pinning a new post over at Nexus and/or writing up something on reddit will do the job to get the word out.

That's a good idea, we'll do that.

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