Hard Light Productions Forums
General FreeSpace => FreeSpace Discussion => Topic started by: Kosh on June 30, 2006, 10:09:45 am
-
I was playing Derelict SCP edition (with of course SCP and slightly stripped down Media VP goodness). Everything was going fine until the mission where they bring the Nyarlotothep out of subspace for the first time. As soon as that happened I got a STOP error ( :eek2: :eek: )and had to restart.
So I get back into Windows and everything seems ok. Then I decide to fire up FS again and continue playing. When I opened it and tried loading that mission, I noticed that the loading time had increased a fair amount. The briefing music is more choppy than normal and the ANIs for ship and weapon selection load a lot slower than normal (so that it doesn't appear until several seconds after I click on the icon).
Then I accept the mission and then it REALLY slows down. The "gameplay" at the start of the mission is unplayable, but then after the Escher jumps in it is a little better (still a little choppy, even though my FPS is high). I notice some paging at this point. Then the Nyarlotothep jumps in and then it slows down again for about 25 seconds or so. Then the Clement opens fire, and then it gets really, really choppy (virtually unplayable if I needed to dogfight at that point). After the Nero starts shooting and several fighter and bomber wings jump in, the choppyness is even worse (like a couple of frames every three or four seconds) and I am noticing heavy paging.
At this point the game is unplayable. Despite this I was able to beat the mission to see if the next mission had the same paging issues, which it did. I also noticed that everytime I exit the game after playing a mission, I see a yellow triangle down in the taskbar that is none other than a low virtual memory warning ( :wtf:).
It is pretty obvious that my copy of FS has somehow managed to spring a pretty big memory leak and short of re-installing FS2 & SCP, is there anything else that I could do to fix this issue?
-
I actually go to vanilla FS2 on that mission, otherwise it's as you say: unplayable.
-
Works fine for me. I wonder if the problem could lie in the version of the SCP you're running? I run 3.6.8, Feb 2006 build, all media vp's activated.
-
i've played thru that mission with the 3.6.9 RC2 and zeta media vp's.
-
I actually go to vanilla FS2 on that mission, otherwise it's as you say: unplayable.
But like I said, everything was fine until I got that STOP error.
EDIT: I just tried a different mission, "The Third Man", and I still had the same problem. Something is definately wrong with my copy of FS..... :(
-
Probably is, I played through both those missions with no problems.
-
Redownload the build and try again.
-
That one mission has about a zillion different high-poly ship classes, so it's no wonder that you'd get severe slowdowns on it.
But if it's happening in less extreme missions, it's definitely a problem.
Possibly try clearing out your cache directory.