• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

How do I benchmark with Quake III

Bring your console down (by pressing the key under the ESC key, for you ~), and type : timedemo 1

Now go to the main menu, select demo's, and let either of the two run that are installed. After the demo finishes, bring your console down again, and voilà, you have your FPS.

Don't forget to type timedemo 0 again to get normal speeds back.
 
One thing that I've been wondering for a while is how one can run a demo looping indefinately. I want to test the stability of a machine and I want to run q3 for a long time.
 
q3 is probably not the way to do stability tests
I would say run Content Creation Winstone 2000 if you can get it. Or sysmark

Perhaps running Prime95 behind Q3A might do it.
Or more interstingly- run a FLASK encode behind Q3a- that would give it a run =-)
but even then, that's not a perfect test. CCWinstone seems best for that.

Also
Can anyone tell me the difference between Anand's "High Quality" and "Fastest" settings?!?

There's nothing like that in the menus for Q3a- is this some arbitrary settings he put together?

Thanks
Eric
 
Can anyone tell me the difference between Anand's "High Quality" and "Fastest" settings?!?

In Quake 3, at the top of the video settings page there is a "graphics settings" menu. Just toggle it to the settings you want.
 
IaPuP: q3 is appropriate to gauge stability of one's 3d system, agp etc. - which is what I wanted to do.

I have managed to find out how to do demo looping though. I can't remember the site I got it from (sorry) but here it is:

I created a file called 'demoloop.cfg' in the 'baseq3' dir - I should think you can call it whatever you want... 😛

You put the following in it:
set demoloop "demo demo001; set nextdemo vstr demoloop"
vstr demoloop

Of course one can change the 'demo001' to another demo.

Then all you do is type exec demoloop.cfg from the console and you're away. You may want to put it into timedemo mode beforehand, or not. (timedemo 1 - as BFG10K said)

This info really should be more readily available. It was quite hard to find.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top