Lestradae wrote:Screet wrote:The good thing about that is, that I finally got oolite to be highly stable, even when playing for some hours non-stop!
If you say that you managed to somehow stop Vista from always putting the dynamic files into that folder and got more stable afterwards, I for one would be curious as to how exactly you did that!
Well, the first big problem was to notice that Vista created a VirtualStore AddOn folder. That was causing immense problems!
After I did clean up things, I removed all oxp's and then did add a few at a time, I've not all back in, but almost.
To stop Vista creating the VirtualStore-files...that's not so easy, I'm afraid. Vista internal editors just fail when editing in the real folder, while the Notepad++ which I use falls victim to Vistas VirtualStore without any notice. I found out that, if I move the file from VirtualStore back to it's proper location, any further editing attempts did not re-create a VirtualStore copy. Other people suggested to install to "C:\oolite" instead, which might be the more safe approach.
Finally, I installed a test release of oxpconfig, which keeps the RAM usage down. Oolite now typically runs with 500megs, goes up to around 900 and as soon as I jump falls back to 500 megs. If you ever did the Assassins mission with the Thargoids...I was fighting the Thargoids for two hours non-stop in that system, then jumped out of it without any crash!
With few OXPs and all those fixes, I only had one crash so far...and it was one I never had until now: The game just didn't respond anymore. No log info, no stderr info, just an inactive window. The CPU load did not increase, nor the RAM usage, almost as if the program encountered a state of infinite waiting for something without caring about any other messages in that time.
However, the sad point is, that I noticed the current WIP OSE test causes immense RAM usage and sometimes caused an "out of memory" crash within seconds after launching the game. I'm not sure what's causing this behaviour. I've made some other observations to that test release but haven't gathered them into a nice feedback file yet, as it was my priority in the past days to solve some of the non-OSE general problems I was experiencing.
Screet
