Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: AqueousShadow on April 24, 2004, 01:30:19 am
-
Umm...just recently, my FSO has been acting up in game, and it's been quite...annoying. I have yet to find out what the cause of the problem is.
Anyway, the problem is that everytime have a sun on-screen, have a capital ship on-screen, have the teal afterburners on-screen, have Turambar's thrusters and trails on-screen (for testing purposes to see what was the problem), and have the new suns on-screen (maybe more things), my framerates completely get PWNED. They sink all the way down to about +/-10.
At first I thought that maybe it is the tgas, but then again, Lightspeed's nebulae are all tgas and I just played a test mission with them and they work fine. Plus, the maps on the capships are all pcxs. Odd thing is, I called in a Shivan Ravana and it didn't slow down one bit. The three ships I've seen slow me down are the Deimos, the Psamtik, and the Fenris.
The most mind-boggling factor about my problem is that I've never seen it happen before. I thought maybe the problem lay within the latest build I installed, but I used the 3-28-04 build and it had the same problems.
Someone HELP ME! :sigh:
-
system specs?
-
try without turambars trails.
If it doesnt help, try without my suns. Those are the two things that could possibly lead to what youre describing.
-
Originally posted by Lightspeed
try without turambars trails.
If it doesnt help, try without my suns. Those are the two things that could possibly lead to what youre describing.
Well, I've tried without turambar's trails because that was my original setting (as I said, I only used his trails to see if the other thrusters were the problem). I just tried taking out all your suns and looking at the sun isn't so bad anymore. I can also look at a Fenris (non-high-poly, mind you) ok.
Just for reference, I've been playing the Homesick campaign. It is the mission where you have to capture the PC Shield in an asteroid field with that HUGE blue sun. Anyway, I still can't look at the Deimos without killing my fps. Also, the greenish-reddish nebulae in the mission kills my frames too.
I'm just so confused because my game NEVER did this before. I'm not sure if my specs matter much, but here they are anyway:
Windows 2000
AMD Athlon ~1.2 GHz
384 Mb RAM
Direct X 9.0b
Sound Blaster Live!
GeForce2 Ultra
My beautiful FSO....*sniff* It was working perfectly before... :shaking:
-
what build starting this happening in?
-
Originally posted by kasperl
what build starting this happening in?
I recently installed the April build, but I don't believe the problems lay within the build. It might have begun after I installed and then deleted Karma's and VA's high-poly Fenris, but that shouldn't have mattered because I deleted it (it killed my frames too, sadly, but then again, it might not have been the ship itself, but everything else that was going on). This was the same mission in Homesick. After all these problems, I couldn't get passed that mission.
I just reverted to the 3-28-04 build right now and tested the same mission as well as Surrender Belisarius! The Deimos doesn't seem to slow me down anymore, but the nebula still does. And then the Psamtik is still giving me problems. So you can see why I don't think it's the builds. Argh....:hopping:
-
I also had a slowdown in FPS before. I only had to remove my sounds.tbl, because it was using a sound that didn't exist(I guess).
-
Originally posted by TopAce
I also had a slowdown in FPS before. I only had to remove my sounds.tbl, because it was using a sound that didn't exist(I guess).
Don't have any sounds tbl. Don't have any other tbls that might be using nonexistent files. I'm losing it...:wtf:
-
Try without the media vp.
Plain ol' FSO style. Let's see what it does.
-
If its not a build (FSO based) problem, it sounds like your system is f*cked up, which regularily happens on Windows systems.
Reinstall Windows and FS2 - you'll be amazed how much faster things will be ;)
-
See if the problem persists with normal FreeSpace.