On Thu, 15 Jul 2004 15:15, Caleb Sawtell wrote:
> On Wed, 14 Jul 2004 02:41, Gareth Williams wrote:
> > On Wed, 14 Jul 2004 11:50, Luuk Paulussen wrote:
> > > Although, the guy who made the post has only made one post on the
> > > forum, so I wouldn't put to much faith in him.  I would expect the
> > > score to be much higher...
> > >
> > > On Wed, 14 Jul 2004 23:17:38 +0000, Caleb Sawtell
> > >
> > > <[EMAIL PROTECTED]> wrote:
> > > > On Tue, 13 Jul 2004 22:19, Luuk Paulussen wrote:
> > > > > This link shows somebody getting similar speeds (same card) with a
> > > > > reply that the result is fine.
> > > > > http://www.nvnews.net/vbulletin/showthread.php?s=ad13ddb1c8153c3064
> > > > >63 d6 2b76 a97665&p=339920#post339920
> > > >
> > > > That means I was totaly ripped off with this card :'(
> >
> > <snip>
> >
> > Caleb, what are the spec's of your machine? Is it possible that the frame
> > rate you're getting is limited by something else, like CPU speed? And
> > what size is your glxgears window? Perhaps your version starts with a
> > different default resolution to people you're comparing to?
>
> er AMD Athlon xp 2500+ barton
> 512 MB ram (dual channel)
> um 40 gig hard drive (don't think that matters but its going on here
> anyway) 8x agp
> thats about it
>
> dunno I think its the default resolution..
>
> > For high frame rates and high performance cards, glxgears probably isn't
> > an appropriate benchmark :-) I'm not familiar with your card, but it
> > probably has a whole bunch of features that glxgears doesn't take
> > advantage of, even if it's raw polygon-drawing-speed isn't quite up
> > there.
>
> ah ok
>
> > A more appropriate benchmark might be to use something like Quake 3 (if
> > you have it) in "timedemo mode" to test your FPS.
>
> how do I put it in "timedemo mode"?

Start Quake 3. When you're at the main menu, press your quake console key, 
which should be your tilde / backtick key (~ or `). When your console slides 
down, type the following in it:

\timedemo 1

which will put it into "timedemo mode". Then run a demo, you probably have one 
called "four", I think it comes with quake3 by default, so type:

\demo four

With a bit of luck the demo will load, and run through very fast (in timedemo 
mode game speed is not moderated, all the frames are drawn, and as fast as 
possible - thus if you have a very high frame rate, the game will appear to 
run very very fast).

When the demo finishes you'll end up back at the main menu. Press your tilde 
key, and you should see as one of the last lines on the console a message 
like:
"X frames drawn in Y seconds: Z FPS", telling you the framerate (Z) you got.

Of course the framerate you get will be dependant on your CPU speed, graphics 
card, and the graphics settings you are using in quake3, and likely the demo 
that you run. I use 800x600, Bilinear filtering, 32-bit colour depth, highest 
detail on everything else, and got (just now, when I tried) 53 FPS on my poor 
old celeron 700 (overclocked to 1GHz) with a Geforce2 MX, using the "four" 
demo. Although I had a bunch of other stuff running that I didn't want to 
close, which probably impacted performance - I swear I've had at least 70 
once ;-)

Maybe someone with a machine with specs closer to Calebs could give him a 
better comparison? With his hardware I would imagine / hope to get several 
hundred FPS at least... ?

Cheers,
Gareth

ps. Sorry this is a bit off topic everyone. But I'm running Quake3 on 
(GNU/)Linux, if that counts? :-)

Reply via email to