MO Log File **HUGE** (30+ GB)

[robogamer]

Hey guys,

 

I'm new to STEP, but I encountered a problem that ground my experimentation to a halt yesterday.

 

After playing with MO for a couple of hours, my system started fussing about low disk space. I had installed MO itself to my C: drive (a 120GB SSD) and had set my mods/downloads directory to my D: drive (a 2TB HDD). Makes sense that there shouldn't be a problem, right? Because all of the big data stuff is stored on the big drive, and just the app files are stored on the small drive?

 

Well, as it turns out (and this may be a bug), MO has generated a 30.2GB log file on my C: drive, in its logs directory. Actually, it generated that and another log file that's about 1.5GB. I tried deleting these files but they require permissions from the "Administrator" (I am an admin on my PC) to delete.

 

Has anyone experienced any problems like this? If so, does MO do this on purpose, and if so, why? If not, is this a bug and should I report it?

 

Aaaand because I'm a new poster, here's the system specs thingy: https://wiki.step-project.com/User:Robogamer/SystemSpecs

 

Any help would be greatly appreciated. I'm planning on getting a much bigger SSD for my system, but that's still far away.

 

Edit: I found the solution. As it turns out, I had not one, but two TESV processes running that I didn't know about (no taskbar entry, no sounds, no nothing) that were a) launched by MO during my experimentaion yesterday and b) generating the huge log files because they had been running overnight.

 

So, my follow-up question is (and mods, if this needs to be a new post LMK): why did MO spawn two TESV processes that never showed up on my desktop? How can I fix this?

Edited September 30, 2014 by robogamer

[TheDane]

You are using MO 1.2.13? correct?

 

It happened to me as well. Revert to MO 1.2.11 (Works great) 

 

Edit: The logs are supposed to be tiny.

Edited September 30, 2014 by TheDane

[robogamer]

Nope, I'm on 1.2.11. Thanks for the tip, though.

 

Edit: I found the solution. Short answer: two rogue TESV processes spawned by MO created the logs. See OP for more details.

Edited September 30, 2014 by robogamer

[DoubleYou]

Most likely you didn't have Steam turned on when you launched, so it never could actually launch.