Freshly updated LOOT generates empty error logs

[MaulMachine]

Hello,

I was using LOOT to sort my Fallout: New Vegas plugins, and whenever I tried to update the masterlist, it spat out an error box saying to check LOOTDebugLog. When I opened said document, it was blank. My changes were not applied.

Thanks.

[MaulMachine]

And now it works perfectly, despite literally nothing changing.

Thanks anyway.

[Ortham]

Which version did you update from?

[MaulMachine]

1.2. I got it working through a simple reinstall, then closing all active programs and trying again.

[Ortham]

There is no LOOT v1.2...

[MaulMachine]

It was a typo, I meant 12.2.

[Ortham]

I'm confused. 0.12.2 is the latest version of LOOT, what version of LOOT were you using before you upgraded to it?

EDIT: And did you have still have LOOT running when you opened the log and found it empty? I'm suspecting this is a buffer flushing thing, the old logger would do it after every statement, but this doesn't.

[MaulMachine]

Okay. I was using 0.12.0, I upgraded to 0.12.2, and after reinstalling it and closing all my other programs, I got it to work. I did not have it running when I opened the log and found it empty.

[SuperSandro2000]

I had the same problem. Delete C:\Users\Sandro\AppData\Local\LOOT and it should work after a restart. maybe a config conversion problem.

[Ortham]

I think I've fixed this in 0.12.3, but I was unable to replicate it. If it's still happening, this can be reopened.