Quake 4 Performance

There has always been a lot of debate in the community surrounding pure timedemo benchmarking. We have opted to stick with the timedemo test rather than the nettimedemo option for benchmarking Quake 4. To be clear, this means our test results focus mostly on the capability of each graphics card to render frames generated by Quake 4. The frame rates we see here don't directly translate into what one would experience during game play.

Additionally, Quake 4 limits frame rate to 60 fps during gameplay whether or not VSync is enabled. Performance characteristics of a timedemo do not reflect actual gameplay. So why do we do them? Because the questions we are trying to answer have only to do with the graphics subsystem. We want to know what graphics card is better at rendering Quake 4 frames. Any graphics card that does better at rendering Quake 4 frames will play Quake 4 better than another card for Quake 4. While that doesn't mean the end user will see higher performance in the game, it does mean that the potential for seeing more performance is there. For instance, if the user upgrades a CPU before the next graphics card upgrade.

Timedemos do walk a fine line between synthetic benchmarks and real world benchmarks. While we tend to favor real world data here at AnandTech, this type of benchmark is very capable of using a real world data set to test the maximum capabilities of the graphics cards under its particular work load without bottlenecking at other points in the system. To be sure, even timedemos can see memory and CPU bottlenecks, as data must be transfered to the graphics card some how. But this impact is much lower than the impact of running AI, physics, script management, I/O, and other game code at the same time.

What this means to the end user is that in-game performance will almost always be lower than timedemo performance. It also means that graphics cards that do slightly better than other graphics cards will not always show a tangible performance increase on an end user's system. As long as we keep these things in mind, we can make informed conclusions based on the data we collect.

Our benchmark consists of the first few minutes of the first level. This includes both inside and outdoor sections, with the initial few fire fights. We tested the game with High Quality settings (not Ultra), and we enabled all the advanced graphics options except for VSync and antialiasing. Id does a pretty good job of keeping framerate very consistent, and so in-game framerates of 25 are acceptable. While we don't have the ability to make a direct mapping to what that means in the timedemo test, our experience indicates that a timedemo fps of about 35 translates into an enjoyable experience on our system. This will certainly vary on other systems, so take it with a grain of salt. But the important thing to remember is that this is more of a test of relative performance of graphics cards when it comes to rendering Quake 4 frames -- it doesn't directly translate to Quake 4 experience.

Quake 4 Performance

The 7600 GT is able to run Quake 4 at this resolution with no problem, while the 6600 GT and the X1600 XT aren't up to the task. Running at 1600x1200 is a good solid resolution for Quake 4, as the low contrast edges and the pixel size (on a 21" monitor like the one we test on) is good enough to make aliasing less of an issue than in a game like Battlefield 2. Very interestingly, the X1900 GT bests the 7900 GT in an OpenGL game, where the opposite was true in more than a couple DirectX games in this series of tests.

The X1900 GT is a great value for Quake 4, offering performance beyond that of the 7900 GT while costing much less. Owners of the X1800 GTO (or similar class cards) aren't doing too poorly here, but owners of the 6600 GT would do well by running at 1024x768 for the best experience. Other cards that couldn't hold their own at 1600x1200 will do fine at 1280x1024.

Very interestingly, it seems that a benchmark traditionally ruled by NVIDIA hardware has lost ground to ATI. As this really is more of a pure OpenGL rendering benchmark, we are glad to see ATI doing so well where they haven't had strong performance in the past.

Half Life 2 Episode One Performance Rise of Nations: Rise of Legends Performance
Comments Locked

74 Comments

View All Comments

  • DerekWilson - Thursday, August 10, 2006 - link

    look again :-) It should be fixed.
  • pervisanathema - Thursday, August 10, 2006 - link

    You post hard to read line graphs of the benchmarks that show the X1900XT crushing the 7900GT with AA/AF enabled.

    Then you post easy to read bar charts of an O/Ced 7900GT barely eeking out a victory over the X1900XT ins some benchmarks and you forget to turn on AA/AF.

    I am not accussing you guys of bias but you make it very easy to draw that conclusion.
  • yyrkoon - Sunday, August 13, 2006 - link

    Well, I cannot speak for the rest of the benchmarks, but owning a 7600GT, AND Oblivion, I find the Oblivion benchmarks not accurate.

    My system:

    Asrock AM2NF4G-SATA2
    AMD AM2 3800+
    2GB Corsair DDR2 6400 (4-4-4-12)
    eVGA 7600GT KO

    The rest is pretty much irrelivent. With this system, I play @ 1440x900, with high settings, simular to the benchmark settings, and the lowest I get is 29 FPS under heavey combat(lots of NPCs on screen, and attacking me.). Average FPS in town, 44 FPS, wilderness 44 FPS, dungeon 110 FPS. I'd also like to note, that compared to my AMD 3200+ XP / 6600GT system, the game is much more fluid / playable.

    Anyhow, keep up the good work guys, I just find your benchmarks wrong from my perspective.
  • Warder45 - Thursday, August 10, 2006 - link

    The type of chart used just depends on if they tested multiple resolutions vs a single resolution.

    Similar to your complaint, I could say they are bias towards ATI by showing how the X1900XT had better marks across all resolutions tested yet only tested the 7900GT OC at one resolution not giveing it the chance to prove itself.

Log in

Don't have an account? Sign up now