Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: kasperl on December 07, 2003, 11:16:16 am
-
Goober asked me to arrange this, so i will.
could you please do the following?
Originally posted by Lightspeed
Ookay people. Download this (http://www.penguinbomb.com/lightspeed/SCPTest/SCP-test.zip) .
It contains three missions.
SCP_POL for testing Poly & texture performance
SCP_WEP for testing effect performance
SCP_ANI for testing ANI performance.
Of course these are only aspects of the game. You might, or might not see any difference in the builds there.
Instructions:
Use the following command lines: -htl -jpgtga (on older builds -t32 and -32bit) - fps
to use SCP POL, just jump in mission.
- Press 1. Wait 5 seconds. Note your FPS.
- Press 2. Wait 5 seconds. Note your FPS.
- Press 3. Wait 5 seconds. Note your FPS.
- Press 4. Wait 5 seconds. Note your FPS.
to use SCP WEP, also jump in mission
- Press 1. Look at your FPS counter, note down the range and average
- Press 2. Look at your FPS counter, note down the range and average
- Press 3. Look at your FPS counter, note down the range and average
to use SCP ANI, you need to do the following:
STEP A:
- Press 1. Look at your FPS counter, note down the range and average
- Press 2. Look at your FPS counter, note down the range and average
- Press 3. Look at your FPS counter, note down the range and average
STEP B:
Jump directly in-mission and immediately press "3". Look at the mission time, and note the time when your lowest FPS are reached.
To start with, here are my results:
Intel P4 2.4 GHz 800 MHz FSB
512 MB DDR 400 RAM (dual channeled)
Asus P4C800 Deluxe
Radeon 9800
Build: 12_05 (i'll edit this post to fill in the other builds later)
Polygon Test:
1 - 70 FPS (maximum due to V_Sync)
2 - 70 FPS
3 - 35 FPS
4 - 35 FPS
Effects Test:
1 - Steady 70 FPS
2 - Steady 70 FPS
3 - 58 - 68 FPS (average: 65)
ANI Test:
1 - 70 FPS
2 - 70 FPS
3 - minimum at 34 FPS
Time to reach minimun: 1:01 minutes.
use colours to distinguish the different builds.
Also, in the weapons test, fire all your weapons continually.
old post:
run the mission "Clash of the Titans II" (bastion escort), and post your framerates using the following builds:
first 32-bit build / 18_11 build / 1_12 build / 5_12 build
use the -fps command line, and write down the following, in this order and style, please:
max FPS: 70 / 36 / 51 / 42
min FPS: 50 / 17 / 37 / 20
avg FPS: 65 / 20 / 41 / 31
then post this in this thread, together with your systems specs, version of DX, and everything like that. also add any commannd lines you might be using, and try turning them on and off.
this would help the coding effort acccording to goober, and i will add all of this into an excell fiile and i'll provide graphs and such.
edit:
Originally posted by Lightspeed
Also, you need the right builds and command lines.
first 32_bit build: it should be the _32-bit build, it supports tgas and jpgs as well as HT&L. HT&L should have serious flickering issues and the lighting should be rather flickery too. The thrusters will _not_ be displayed through the ships though.
Command lines: -htl (duh.) (-t32 -32bit older builds) (-jpgtga newer builds) -fps
[/size]
-
To Parts Unknown? :confused:
-
bad mission choice. I dont think everyone has Technical Superiority installed. I suggest Clash of the Titans II as a test mission, as it is a campaign mission.
Also, you need the right builds and command lines.
first 32_bit build: it should be the _32-bit build, it supports tgas and jpgs as well as HT&L. HT&L should have serious flickering issues and the lighting should be rather flickery too. The thrusters will _not_ be displayed through the ships though.
Command lines: -htl (duh.) (-t32 -32bit older builds) (-jpgtga newer builds) -fps
Clash of the Titans II:
max FPS: 70 / 47 / 70 / 62
min FPS: 63 / 20 / 49 / 33
avg FPS: 69 / 27 / 58 / 41
edit: i'll test some more since the drain seems to be sporadic and does not happen every time.
-edit2: or better yet, i'll make a test mission to cover various slow down issues.
-
Originally posted by Lightspeed
bad mission choice. I dont think everyone has Technical Superiority installed. I suggest Clash of the Titans II as a test mission, as it is a campaign mission.
Also, you need the right builds and command lines.
first 32_bit build: it should be the _32-bit build, it supports tgas and jpgs as well as HT&L. HT&L should have serious flickering issues and the lighting should be rather flickery too. The thrusters will _not_ be displayed through the ships though.
Command lines: -htl (duh.) (-t32 -32bit older builds) (-jpgtga newer builds) -fps
Clash of the Titans II:
max FPS: 70 / 47 / 70 / 62
min FPS: 63 / 20 / 49 / 33
avg FPS: 69 / 27 / 58 / 41
edit: i'll test some more since the drain seems to be sporadic and does not happen every time.
-edit2: or better yet, i'll make a test mission to cover various slow down issues.
lightspeed, i would be very happy if you made a mission, it would be very nice, very nice indeed.
also, thank you for posting those command lines.
-
Okay, prepare to be very happy ;)
-
Do you want the FPS at the start of the mission or the lowest we saw?
-
well, the lowest, the highest, and a good estimated average would be very nice, and if you could do it over a good part of the mission, it'd be very nice.
-
(http://nodewar.penguinbomb.com/aotd/kasperl/SCP_FPS/Image2.gif)
that is some of the graphs, http://nodewar.penguinbomb.com/aotd/kasperl/SCP_FPS/SCPFPS.xls , this is the complete sheet
edit:
could some code-god please write a tiny little program that outputs the following to a file:
processor
OS
mem
DX version
Graph card
and all that is needed to search for performance problems.
if it is all in a standard format, i could perhaps make something that throws all data toghether, and searches for common things from people with low framerates.
-
anyone?
-
theyre all waiting for my mission, and a new thread :)
Which will be here.... shortly :)
-
good.
-
*first part removed... look at kasperls first post... its all up there now*
here are my results:
Intel P4 2.4 GHz 800 MHz FSB
512 MB DDR 400 RAM (dual channeled)
Asus P4C800 Deluxe
Radeon 9800
Build: 11_18 12_05 (i'll edit this post to fill in the other builds later)
11_18
Polygon Test:
1 - 70 FPS
2 - 68-69 FPS
3 - 35 FPS
4 - 22 FPS
Effects Test:
1 - 53-60 FPS (average: 63)
2 - 29-40 FPS (average: 42)
3 - 28 - 31 FPS (average: 30)
ANI Test:
1 - 60-65 FPS (average: 62)
2 - 40-69 FPS (average: 67, weird huh?)
3 - minimum at 20 FPS
Time to reach minimun: 0:50 minutes.
12_05
Polygon Test:
1 - 70 FPS (maximum due to V_Sync)
2 - 70 FPS
3 - 35 FPS
4 - 35 FPS
Effects Test:
1 - Steady 70 FPS
2 - Steady 70 FPS
3 - 58 - 68 FPS (average: 65)
ANI Test:
1 - 70 FPS
2 - 70 FPS
3 - minimum at 34 FPS
Time to reach minimun: 1:01 minutes.
use colours to distinguish the different builds.
-
now, we need to make this an even larger pimp.
i'll turn all of this into a nice excell file tomorow, probably during english class.
edit: also, please post your specs.
-
I forgot to mention. On the weapons test, keep shooting your primaries and secondaries :)
I'm adding the 11_18 results now.
-
ok, this is going to be one large set of graphs. i'll have to play around some before i'll get all of this working nicely, but i'll see.
-
The keys we're supposed to press are the communication keys or nimpad keys ?
-
comm, i guess, they are the standard to use on is-key-pressed thingy's.
-
please, sil vous plait, bitte, alstublieft?
-
Links to all the relavent builds would help. Most of us are too lazy to look them up :D
-
jesus.
and i am only doing this in my spare free time during my english/biology classes because i thought it was usefull.
i geuss it is not.
-
Didn't say I was too lazy :) I'm actually looking them up right now. Just explaining why you'd got such a poor response.
EDIT : Okay here are the links. These really should go in the top post somewhere though.
18/11 build (http://fs2source.warpcore.org/wip/11_18_2003.zip)
01/12 build (http://fs2source.warpcore.org/wip/12_01_2003.zip)
05/12 build (http://fs2source.warpcore.org/wip/12_05_2003.zip)
Those were easy but I can't find the first 32 bit build which one is it?
-
lightspeed - turn off your VSync for christ sake!@ that radeon 9800 should be able to exceed 300 fps in fs2! [atleast on an athlon-based system, don't know what that craptacular PIV is doing to it ]
-
Originally posted by karajorma
Didn't say I was too lazy :) I'm actually looking them up right now. Just explaining why you'd got such a poor response
thanks.
-
Originally posted by Kazan
lightspeed - turn off your VSync for christ sake!@ that radeon 9800 should be able to exceed 300 fps in fs2! [atleast on an athlon-based system, don't know what that craptacular PIV is doing to it ]
How do you do that? I've also got a Radeon 9800 and I was rather suprised by my frame rates considering it's supposedly such a cool card.
EDIT : Read up a bit on VSync in the last few mins so at least I understand a little bit about it.
From what I understand disabling VSync is a technique to be used when you are running a low powered card that is getting low FPS in order to make the game playable.
FS2 shouldn't really be getting performance low enough to make disabling VSync necessary especially when you consider the fact that you'll probably get tearing because of it.
So in other words as far as I could see you'd be introducing graphical glitches into all of your games (unless you went through the tedious step of turning it on and off again before and after a game of FS2) just for the sake of making FS2 run faster (to cure a problem which is in the FS2 code anyway and not due to the machine being underpowered or misconfigured)
Anyway that's the gist of what I could figure out from the articles I read on the net so if I've got the wrong end of the stick I'd be happy to hear it.
BTW the articles didn't say much about how to do it so I couldn't test things out for myself.
-
From what I understand disabling VSync is a technique to be used when you are running a low powered card that is getting low FPS in order to make the game playable.
FS2 shouldn't really be getting performance low enough to make disabling VSync necessary especially when you consider the fact that you'll probably get tearing because of it.
Wrong. V-Sync synchronizes the FPS with your monitor refresh rate. If V-Sync is disabled you get nasty flicker lines in your screen since the card will send new images when the monitor is still drawing the picture. V-Sync is a must if you don't want ugly graphics.
lightspeed - turn off your VSync for christ sake!@ that radeon 9800 should be able to exceed 300 fps in fs2! [atleast on an athlon-based system, don't know what that craptacular PIV is doing to it ]
no. For the reasons stated above. I dont want 1/7 explosions on my screen, and ships that tile in the middle. And yes, It could easily do 300 FPS, but my eye will only see about 40 anyway so I dont really see a reason why it should. -- And those quality problems would be there without V-synch anyway. V-synch only needs a bit of performance, it simply limits the max FPS to your refresh rate. And an Athlon based system would do lots worse, since it has a ubar crappy FSB, which is what you'll need in terms of 3D applications. FYI, I DO dislike Intel, it's just that their current processors are - in gaming applications - crushing whatever AMD can come up with for the same price. Also, heating is less an issue; and in case of the fan dying i won't have a fried processor.
(edit: about the fan dying: here (http://www.tomshardware.com/cpu/20010917/index.html), video (http://www12.tomshardware.com/images/thg_video_1_cpu_cooling.zip) )
-
back on topic, please????
or should i just forget all of this an return to lurking and spamming?
-
Actually, as an interesting tidbit, I run without vsync on and do not notice the tearing effect one usually gets from this. Even when it's going at 87FPS.
-
Yes, and your refresh rate is ~85 Hz i assume, so the difference is minimalistic. However with a refresh rate of 70 (my monitor's dead) and 300 FPS it's completely another story :doubt:
-
Originally posted by Lightspeed
Wrong. V-Sync synchronizes the FPS with your monitor refresh rate. If V-Sync is disabled you get nasty flicker lines in your screen since the card will send new images when the monitor is still drawing the picture. V-Sync is a must if you don't want ugly graphics.
How am I wrong if you've basically agreed with everything I said? :confused:
I said that if you disabled VSync you'd get tearing (i.e nasty flicker lines in your screen since the card will send new images when the monitor is still drawing the picture) and I said that from what I've read it's only worth doing if your game is already running at only 10--20 fps because graphical glitches are better than laggy gameplay.
Kazan : I went to Display -> Settings -> Advanced -> Direct 3D and slid the "wait for Vertical Sync" option down to Always off and tried FS2 open. I didn't spot the blindest bit of difference (FPS remained around 40-50) so either I didn't actually turn Vsync off or the bottleneck is in the code itself
(I'm running a XP2100, Asus A7NX8 Deluxe with 1 Gig of ram, Radeon 9800, Windows XP and DX9 so I doubt anything else is slowing me down).
Kasperl : I'll quite happily run the tests when someone points me in the direction of the first 32bit build.
-
Oops read you wrong then. My faulty
As for your V_Sync thingy. There's a command line that can turn it off in FS2_open.
However, note that as soon as the FPS with V_sync enabled drop below your V_sync maximun you will have exactly the same FPS with V_sync turned off.
So yes, you would still be getting 40-50 FPS, no matter if it's enabled or disabled. With the exception that when it's turned on, the visual quality is loads better ;)
-
That's what I thought. If only I understood all the graphics card terminology so quickly :D