Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: DaBrain on October 23, 2008, 05:52:13 am
-
I ran some tests for SoL, on a rather weak system.
For testing, I choose our currently most demanding setting, which consists of several huge meshes with pretty big textures.
I was surprised that it ran quite decent on the test system. However, when I started shooting, there was a huge performance drop.
I've disabled collisions and weapon rendering, but it didn't have any effect.
Is this a bug and should be on Mantis, or is it some kind of engine limitation, we have to live with?
(The same problem was noticed by two other members.)
-
You didn't notice if any of the ship textures or engine glows had become garbled/corrupted, did you? I've been experiencing that myself, and it's always coupled with a big framerate slowdown, which seems to multiply when I start shooting. Might not be related at all to what you're experiencing, but it's worth a shot.
-
I ran some tests for SoL, on a rather weak system.
For testing, I choose our currently most demanding setting, which consists of several huge meshes with pretty big textures.
I was surprised that it ran quite decent on the test system. However, when I started shooting, there was a huge performance drop.
I've disabled collisions and weapon rendering, but it didn't have any effect.
Is this a bug and should be on Mantis, or is it some kind of engine limitation, we have to live with?
(The same problem was noticed by two other members.)
Have that too. I've made a mission ( cutscene ) with several large capships ( 8 ships and Ragnar station ).
It works fine as long i don't start shooting.
Since it happens with all builds, my thought was, that this performance drop from ~60fps to ~15fps is because of my system.
Specs are:
Win XP
Xeon CPU 2,40 GHz
1 GB RAM
ATI Radeon HD 2600 XT AGP with 512 MB DDR RAM.
-
Water also noticed a performance drop when he looked into the sun, can you check that as well?
-
Checked it, but didn't notice a drop in performance.
It's stable ( more or less at 55-65fps ) all the time as long i don't start shooting.
-
Tried the latest Nightly Build for Windows today ( 24 October - Revision 4920 ), and the frame rate drops from 60 fps to 50 only because of looking in the sun, as soon i look in a different direction frame rate goes back to 60.
-
Has anyone noticed that if you have the Windows task manager open and updating the process list, you see a framerate lapse on FS2_Open that correlates with the task manager's update rate?