Jump to content

WrinklyNinja

Members
  • Posts

    280
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

WrinklyNinja's Achievements

Initiate

Initiate (4/10)

65

Reputation

  1. LOOT v0.18.3 released! Thanks to everyone who contributed towards this release.
  2. Are you running the 64-bit build or the 32-bit build? If you disable LOOT checking for updates on startup, do you still see that error logged? LOOT doesn't use GnuTLS, but it looks line Wine implements Windows' Schannel using GnuTLS. I've got no idea if the error is due to some logic bug in that implementation, or if the error is due to something going wrong with the TLS connection.
  3. LOOT v0.18.1 released! Thanks to everyone who gave feedback on v0.18.0, this release features several improvements that should resolve many complaints about the new UI.
  4. LOOT v0.18.0 released! Thanks once again to everyone who tested and/or gave feedback for this release! This release has the largest changelog yet, including a completely reimplemented user interface.
  5. You can update the install path for each game in LOOT's settings to the new paths, and LOOT should then find the games. Alternatively, delete your %LOCALAPPDATA%\LOOT\settings.toml and have LOOT generate a new one when you start LOOT.
  6. Probably - see issue #1383 for some discussion on this. Can you send me copies of the plugins that LOOT is complaining about, and your LOOTDebugLog.txt?
  7. I don't know about sorting, but nothing about saving a load order has changed. LOOT basically just passes the load order to save down to libloadorder, and that hasn't been updated since v0.14.4. It definitely shouldn't be taking seconds... If you go back to v0.15.1, how long do sorting and saving take? EDIT: Someone else reporting far worse sort times (7 minutes!) still only sees applying the load order take 0.2 seconds.
  8. It's supposed to be a warning, not an error message, so just ignore it if it's not applicable. Warnings are used when something might be wrong, but LOOT can't tell, and errors are for when LOOT knows something is wrong.
  9. It's probably failing to download the MSVC redistributable, if you install it manually (e.g. from here) then the installer won't try to download it. I just ran the installer and it downloaded the redist fine, so if it is the redist, it's not a server issue.
  10. It looks like the warnings were added in April 2017, which is after the last update on the Nexus page you linked. I don't know enough about the mod to say what the issues are, so maybe you've just been lucky.
  11. "load after" does take precedence over "group" metadata, but when building up the plugin graph it's not obvious which bit of metadata is "responsible" for the cycle: in the example you gave, it could either be the group metadata that loads "AMatterOfTime.esp" after "RealisticWaterTwoMerge.esp" or the group metadata that loads "Alternate Start - Live Another Life.esp" after "AMatterOfTime.esp", and LOOT has no way of knowing which to ignore. Because it might not be the load after rule that you want to remove to break the cycle.
  12. This is the same issue as with ELFX - Exteriors.esp, ESMs can't load after ESPs (unless the ESP has its master flag set). I think you need to launch LOOT through NMM for LOOT to be able to see the plugins installed by NMM.
  13. It looks like you're right, I've filed issue #96 to track this. This isn't a metadata issue, it looks like you need to rebuild DynDOLOD.esm so that ELFX - Exteriors.esp isn't in its list of masters, because an ESM generally can't load after an ESP.
  14. What game was this for? I've seen a few of these 'object not found' errors recently, no idea why they're happening.
×
×
  • Create New...