#loot

/

      • NOTICE: [13loot] 15twist3dimages commented on issue #872: Also,... 02https://git.io/vAvXe
      • NOTICE: [13skyrim] 15igotsometrouble opened issue #166: Skyrim LOOT sorting plugins issue. 02https://git.io/vAvM6
      • NOTICE: [13loot] 15pStyl3 commented on issue #872: Since this is related to Vortex: @TanninOne 02https://git.io/vAfq0
      • NOTICE: [13loot] 15pStyl3 commented on issue #872: Since this is related to Vortex: @TanninOne... 02https://git.io/vAfq0
      • NOTICE: [13skyrim] 15WrinklyNinja commented on issue #166: The LOOT debug log shouldn't be empty, but can you enable debug logging and try again? See [How To Report Issues Helpfully](http://loot.github.io/docs/help/How-To-Report-Issues-Helpfully.html) for details. 02https://git.io/vAfGc
      • NOTICE: [13loot] 15WrinklyNinja commented on issue #872: I don't know anything about Vortex or how it is using LOOT, but it looks like there's invalid metadata. The FO4 masterlist's CI isn't showing any errors, so I guess this is user metadata? If you know where it stores the metadata it passes to LOOT, posting it may be useful. 02https://git.io/vAfGd
      • Thallassa joined the channel
      • Guigle17 joined the channel
      • Guigle17 has quit
      • lootuser joined the channel
      • lootuser
        Hey! I have an issue with LOOT on Windows 7 - it doesn't pop up a window, it simply disappears from taskman after three-four seconds.
      • I am using the latest release.
      • Are there any log files that LOOT generates as a part of its working?
      • ~\AppData\Local\LOOT is empty.
      • NOTICE: [13loot] 15AndreF111 opened issue #873: LOOT 0.12.2 won't start 02https://git.io/vAJwW
      • NOTICE: [13loot] 15WrinklyNinja commented on issue #873: Does 0.12.1 work? What happens if you create the `settings.toml` file and enable debug logging in it as described [here](http://loot.github.io/docs/help/How-To-Report-Issues-Helpfully.html)? 02https://git.io/vAJrU
      • 0.12.1 works, strangely.
      • I just downloaded it.
      • Thanks, WrinklyNinja!
      • lootuser has quit
      • NOTICE: [13loot] 15AndreF111 commented on issue #873: I have created a text file, called it settings.toml and pasted enableDebugLogging = true into it.... 02https://git.io/vAJK3
      • NOTICE: [13loot] 15AndreF111 commented on issue #873: I have created a text file, called it settings.toml and pasted enableDebugLogging = true into it.... 02https://git.io/vAJK3
      • NOTICE: [13loot] 15AndreF111 commented on issue #873: These are the log files for 0.12.1... 02https://git.io/vAJ6v
      • NOTICE: [13loot] 15AndreF111 commented on issue #873: The latest version that works 100% on my machine is 0.11.0 02https://git.io/vAJ6d
      • NOTICE: [13loot] 15WrinklyNinja commented on issue #873: I bet this is because the TOML parser just uses standard streams and they don't support unicode paths (your username's `é`) on Windows...... 02https://git.io/vAJP5
      • NOTICE: [13loot] 15WrinklyNinja created 06fix-unicode-toml-path (+1 new commit): 02https://git.io/vAJHk
      • NOTICE: 13loot/06fix-unicode-toml-path 14c31b51b 15Oliver Hamlet: Fix parsing settings.toml at a non-ASCII path
      • NOTICE: [13loot] 15WrinklyNinja commented on issue #871: Also, this may have the same probable cause as #873, what's your user directory? 02https://git.io/vAJHG
      • NOTICE: [13loot] 15WrinklyNinja 04force-pushed 06fix-unicode-toml-path from 14c31b51b to 14c6eb940: 02https://git.io/vAJQY
      • NOTICE: 13loot/06fix-unicode-toml-path 14c6eb940 15Oliver Hamlet: Fix parsing settings.toml at a non-ASCII path
      • NOTICE: loot/loot#2010 (fix-unicode-toml-path - c6eb940 : Oliver Hamlet): The build passed.
      • NOTICE: Change view : https://github.com/loot/loot/compare/c31b51be5962...c6eb94070955
      • NOTICE: Build details : https://travis-ci.org/loot/loot/builds/338712957
      • NOTICE: [13loot] 15WrinklyNinja commented on issue #873: Also, try [this build](https://bintray.com/wrinklyninja/loot/download_file?file_path=loot_0.12.2-1-gc6eb940_fix-unicode-toml-path.7z), it should fix the issue. 02https://git.io/vAJdl
      • NOTICE: [13loot] 15AndreF111 commented on issue #873: That way it works. 02https://git.io/vAJd8
      • NOTICE: [13loot] 15AndreF111 commented on issue #873: Adding --loot-data-path=C:\LOOT to a shortcut fixes it, but the issue persists on that build you linked. 02https://git.io/vAJF3
      • NOTICE: [13loot] 15WrinklyNinja commented on issue #873: Is the error still the same? 02https://git.io/vAJF7
      • NOTICE: [13loot] 15WrinklyNinja commented on issue #873: Is the error still the same? 02https://git.io/vAJF7
      • NOTICE: [13loot] 15WrinklyNinja commented on issue #873: Hmm, there must be something else not liking the path too. 02https://git.io/vAJb4
      • NOTICE: [13loot] 15twist3dimages commented on issue #872: @WrinklyNinja what would the metadata look like? 02https://git.io/vAJbp
      • NOTICE: [13loot] 15twist3dimages commented on issue #872: @WrinklyNinja what would the metadata look like?... 02https://git.io/vAJbp
      • NOTICE: [13loot] 15AndreF111 commented on issue #873: These are the logs for the build you linked, when accessed with the command line parameter.... 02https://git.io/vAJN2