It's ScriptError_DESKTOP-A7P96HU<u>12-18-2016</u>19-25-03__DA214010.rar. It's now happened several times on start-up, and the worst consequence is that I often cannot switch out of the window when it's saving to see how much memory I'm using, as it sometimes crashes when I do that-- a very important thing, to know when I'm using memory to the point it won't save so I need to restart. This last time, I was doing okay on memory, and I'm sure it would have saved had I not checked the memory usage. But switching out of the window made it crash.

The error trap doesn't say much, so I don't know what anyone can get from it-- but I'm hoping....

Not much, I'm afraid. That's a routine ErrorTrap cleanup Correction Log, nothing to do with crashing. It's supposed to do that; I bet those are leftover pieces of data from LN Professional Bars that Overwatch now corrects for us on startup. Or something similar.

Are you in full screen mode when switching windows or using an app switcher like alt-tab? That's always a dicey proposition and it's more of a Windows issue than TS3. I always switch the game to windowed mode so I can use the taskbar to switch apps and see the Task Manager, etc., then return to full-screen mode when ready to resume play. That's an annoying lot of extra steps in both directions, but one of my colleagues here convinced me a long while back that it was better, safer, and he was right, TS3 never gets stuck to the Task Bar or crashes on switching anymore.

Hmm, how do I switch to windowed mode after the game starts? I've probably done that before, but I don't remember. I may be able to figure it out, but in case I don't, please tell me.

I normally am in full screen mode, and when the game is running (reasonably) well, the safest time to alt-tab out of full screen to see how much memory I'm using is when it's saving. If I try to check it some other time, there's always a crash risk...but it's been months since it crashed when alt-tabbing out while it was saving. Just now, I did the alt-tab out right after saves, so at the worst I'd have had to restart even if I weren't low on memory. The game would at least still be saved, barring E12. That actually worked.

But you're right-- the best way, if it works, is to switch to windowed mode to check out the memory usage and then back to full screen to play it. That's easily worth the relatively minor inconvenience. I may figure out how to do it, but please post how to do that in case I don't.

I do have a theory as to why the game's memory usage was up and possibly why it crashed. I decrapified all my custom content. Today, I uploaded a bunch of roofs from MTS. Until just before I wrote this, I hadn't decrapified it. It was my first new CC in a while. Un-decrapified stuff doesn't mix well with decrapified stuff...so soon I'll find out if I don't get the error on startup, if startup is faster, and if crash risks are much lower now that it is also decrapified. I hope that's it, but switching windowed/full screen seems worth doing anyway, because I always have occasional crashes if I switch out of the window (though normally never if I do it while saving).

Thanks!

The long way: hit the "..." button to get Game Options, de-select full screen mode, accept the change. Same in reverse.
The shorter way: alt-enter.

Yep...it was easy to figure out when I got in. I saw when it was about to fail to save, so was able to get out. Decrapifying the new CC didn't fix the error on load, and the overuse of memory. I'll try disabling the new CC. If it's not that, I could have played with a tuning mod I shouldn't have (or somehow my addition of the "Meanies" personalities in Story Progression, but that's unlikely to be causing an error).

Yes, definitely changing to windowed to check memory is useful. The only bad thing in my game now is that something is making the memory leak worse than usual (TS3 always has some memory leakage). It's probably whatever is causing that error, but that error is so generic that it doesn't necessarily narrow things down....

Perhaps try starting up with NRaas mods only in place? If the problem is cleared then add half of your CC back in and proceed backwards and forwards by remaining halves until you can isolate the culprit.

Well, here's an update...at one time or another I disabled every mod I had changed or downloaded since before the error (I'd already had done it with the only bit of CC I'd downloaded-- CC is different from mods, from how I use the terms, as CC is things that change the look in the game rather than the functionality). I never got the error to stop, and everything is back in-- there were only a few such changes and whatever I disabled, nothing fixed things. But...while I still get that script error whenever loading the game, the memory leak is back to its normal, tolerable levels-- with the added bonus of my being able to move in and out of full screen to get an idea when memory usage is getting too high, due to your great suggestion there. My best guess is that while I did not "reset everything" with the Master Controller, I reset a lot of objects. That seemed to be about when the memory leak stopped being a bad problem.

So, it seems to be solved and I'm a bit better off than before, except for a much more minor problem that existed before the error that I'll get into on Chatterbox when I feel like writing it out.