ModOrganizer.log file size (1.0.7)

[pmchem]

I'm running MO 1.0.7 (RC8) with about 100 mods and just had a test run with them, using tgm/tcl at console to walk across part of skyrim.  After that travel, my ModOrganizer.log file is about 30mb in size and filled with "DEBUG" statements.   Is this 'working as intended'?   Seems odd to have so many DEBUG statements in a RC8.

 

They're basically a bunch of createfile and 'get file attributesex' calls.

 

In general, really enjoying MO.  Thanks!

[Tannin]

Yeah, that's normal. The debug messages are usually meaningless but in case of a bug they may help tremendously in finding the problem because they tell me (approximately) what the program was doing internally when it crashed.

They may even provide pointers in identifying problems with mods.

 

If the log size presents a problem you can lower the log level in the settings dialog so that debug messages aren't displayed.

[pmchem]

ok, cool. p.s., tannin - I had tried MO like a year ago and did not use it because of a 'qlocalsocket failed to connect' problem when trying to download mods from nexus.

 

this time around, I can reproduce that error if and only if I launch MO with 'run as admin' (this is in win8.1) and then click on a nexus 'download with nmm' link. If I launch it as normal, the error does not occur. Might help some users if this quirk isn't already well-known.

[TechAngel85]

You should probably look for this issue on the bug tracker and, if it's not present, create a new one: https://issue.tannin.eu/tbg/modorganizer/issues/open

 

I have Windows 8 (not 8.1) and just reproduced this.

[deathneko11]

Marked as SOLVED as the initial query was answered by Mod Author as intentional and functional behavior.

 

I agree with Techangel, on the issue of Windows 8 errors needing address via the official bug tracker for Mod Organizer.  If you have not made an account there then please do so and post your bug, but please check to see if it has already been posted by somebody else first!