Tuesday, January 12, 2010

60 FPS



And that's on my Intel.

This is actually a bit of a weird one, as almost exactly one year ago (I'm maybe an hour or so later) I released the first ever screenshot of DirectQ running Marcher. So here we are again.

The original post can be viewed here. The real irony in this is that I had finished it off with a discussion of DrawPrimitive vs DrawPrimitiveUP, and had come down in favour of the latter on grounds of flexibility and convenience. Oh how times change. Todays work has probably been one of the most productive in terms of performance ever (I think that deconstructing the alias model format, and handling brush models in huge indexed batches would beat it, especially as without those I would never have pulled the extra performance today) and it's all been VBO stuff.

9 comments:

Andy said...

Not to change the subject, and call me stupid, yada, yada, yada, if you will, but I've tried for ages to find a download link for Marcher and have given-up way too easily and went "next time"; where can I get it with one click in this day and age?

Coranth said...

Andy,

http://www.quaddicted.com/

Quad-Addicted, a massive archive of Quake Maps; you'll find it here in the Single Player section.

=peg= said...

I tried this scene (marcher) in Fitz085, DirectQ1.7.666c and DirectQ1.8.0Alpha:

Nvidia GEFORCE6800GT 1280x1024x32 4xAF

skill 3
sv_cullentities 0
fog disabled

FitzQuake085: 8 fps
DirectQ1.7.666.c: 41 fps
DirectQ1.8.0Alpha: 50 fps

Can't wait to see what 1.8.0Beta does :D

mhquake said...

The more modest 41 to 50 jump seems roundabout right for this scene, as it's an incredibly difficult one to optimize for, with multiple potential bottlenecks everywhere. I'm quite surprised Fitz did so bad though; I would have expected about the same as 1.7.666c (if we were talking about some of the more difficult scenes in ne_tower we would have seen differences along those lines).

meTch said...

HURRAY for (new) yearly traditions :D

Andy said...

Duh, thanks much Coranth. I have that in my bookmarks, but never thought to look there. Idiot am I. Thank you!

=peg= said...

"I'm quite surprised Fitz did so bad though; I would have expected about the same as 1.7.666c"

Actually so was I, hence I tried that scene again (with the exact same settings) but this time I got 50-72 FPS in Fitz.. Must have been some setting in config.cfg that made it slow the first time I tried..

BTW, does anyone know the cvar for the FPS counter in Fitzquake? It only shows up occasionally.. and tab-completion gives me nothing..

mhquake said...

scr_showfps if memory serves.

=peg= said...

Aah yes, cheers!

And for the record.. it DOES show up with tab-completion.. somehow I just never saw it ;)