You’ve been living too perfect of a life if you’ve never used the phrase “it’s been a long day,” and for NVIDIA it has most definitely been a very long day. Just over two weeks ago the graphics industry was shook by some very hard hitting comments from Gabe Newell of Valve, primarily relating to the poor performance of NVIDIA cards under Half Life 2. All of the sudden ATI had finally done what they had worked feverishly for years to do, they were finally, seemingly overnight, crowned the king of graphics and more importantly – drivers. There were no comments on Half Life 2 day about ATI having poor drivers, compatibility problems or anything even remotely resembling discussions about ATI from the Radeon 8500 days.

Half Life 2 day was quickly followed up with all sorts of accusations against NVIDIA and their driver team; more and more articles were published with new discoveries, shedding light on other areas where ATI trounced NVIDIA. Everything seemed to all make sense now; even 3DMark was given the credibility of being the “I told you so” benchmark that predicted Half Life 2 performance several months in advance of September 12, 2003. At the end of the day and by the end of the week, NVIDIA had experienced the longest day they’ve had in recent history.

Some of the more powerful accusations went far beyond NVIDIA skimping on image quality to improve performance; these accusations included things like NVIDIA not really being capable of running DirectX 9 titles at their full potential, and one of the more interesting ones – that NVIDIA only optimizes for benchmarks that sites like AnandTech uses. Part of the explanation behind the Half Life 2 fiasco was that even if NVIDIA improves performance through later driver revisions, the performance improvements are only there because the game is used as a benchmark – and not as an attempt to improve the overall quality of their customers’ gaming experience. If that were true, then NVIDIA’s “the way it’s meant to be played” slogan would have to go under some serious rethinking; the way it’s meant to be benchmarked comes to mind.

But rewind a little bit; quite a few of these accusations being thrown at NVIDIA were the same ones thrown at ATI. I seem to remember the launch of the Radeon 9700 Pro being tainted with one accusation in particular – that ATI only made sure their drivers worked on popular benchmarking titles, with the rest of the top 20 games out there hardly working on the new R300. As new as what we’re hearing these days about NVIDIA may seem, let us not be victim to the near sightedness of the graphics industry – this has all happened before with ATI and even good ol’ 3dfx.

So who are you to believe? These days it seems like the clear purchase is ATI, but on what data are we basing that? I won’t try to build up suspense senselessly, the clear recommendation today is ATI (how’s that for hype-less journalism), but not because of Half Life 2 or any other conspiracies we’ve seen floating around the web these days.

For entirely too long we’ve been basing GPU purchases on a small subset of tests, encouraging the hardware vendors to spend the majority of their time and resources optimizing for those games. We’re not just talking about NVIDIA, ATI does it too, and you would as well if you were running either of those two companies. We’ve complained about the lack of games with built-in benchmarks and cited that as a reason to sticking with the suite that we’ve used – but honestly, doing what’s easy isn’t a principle I founded AnandTech on 6+ years ago.

So today we bring you quite a few new things, some may surprise you, some may not. ATI has released their Fall refresh product – the Radeon 9800XT and they are announcing their Radeon 9600XT. NVIDIA has counterattacked by letting us publish benchmarks from their forthcoming NV38 GPU (the successor to the NV35 based GeForce FX 5900 Ultra). But quite possibly more important than any of those announcements is the suite of benchmarks we’re testing these cards in; how does a total of 15 popular games sound? This is the first installment of a multipart series that will help you decide what video card is best for you, and hopefully it will do a better job than we have ever in the past.

The extensive benchmarking we’ve undertaken has forced us to split this into multiple parts, so expect to see more coverage on higher resolutions, image quality, anti-aliasing, CPU scaling and budget card comparisons in the coming weeks. We’re working feverishly to bring it all to you as soon as possible and I’m sure there’s some sort of proverb about patience that I should be reciting from memory to end this sentence but I’ll leave it at that.

Now that the long-winded introduction is done with, let’s talk hardware before we dive into a whole lot of software.

The Newcomers
POST A COMMENT

262 Comments

View All Comments

  • Anonymous User - Friday, October 03, 2003 - link

    FSAA does work in Halo you need to add two lines to the config.txt file to enable it. FSAA is working fine in Halo now.

    Reply
  • Anonymous User - Friday, October 03, 2003 - link

    Where are the DX9 benchmarks?

    What is going on at Anandtech? Why all the Dx9 titles?

    Old cards can do dx8 well I want to see how dx9 titles run. Aquamark is mostly dx8.

    You for some reason are using buggy Nvidia drivers for this test why?

    Something is fishy here. I smell a sellout.

    Reply
  • Anonymous User - Friday, October 03, 2003 - link

    Reply
  • Anonymous User - Friday, October 03, 2003 - link

    Good article and nice new testing sweet. But look into adding SOE's Planetside to the mix that game eats anything less then a 5600 for lunch running at no more then 20 fps. my heavily oced 5600 (350/550) never gets over 70 or so. Reply
  • Anonymous User - Friday, October 03, 2003 - link

    #206
    everything that was able to run aa/af was run in aa/af ... how can you complain about that?

    There is exactly one (sucky) dx9 game out that they didn't test: TRAOD ...

    meh
    Reply
  • Anonymous User - Friday, October 03, 2003 - link

    I'd like to see Nascar Racing 2003 tested, rather than F1Challenge. Since F1C is CPU limited, it makes the results rather useless for GPU testing.

    As #159 notes, starting from the back of a full-field AI race will definitely show what your hardware is capable of doing. But the AI calculations may eat up a lot of CPU cycles. (FWIW, NR2003 is multithreaded and MP-aware, so this scenario might make for a good CPU/system test.)

    However, one could create a _replay_ of a full-field race. The replay is then repeatable on any system. And, although I haven't tested this, I imagine the replay might be more GPU-intensive since there's less real-time AI and physics processing happening.

    OTOH, both games have DX8.x graphics engines AFAIK.
    Reply
  • Anonymous User - Friday, October 03, 2003 - link

    Almost all the games were cpu-limited.

    Relatively few used AA/AF, which is even more important with a slow cpu, given that you have videocard power to burn. Another failure.

    Few of the games were DX9. Is this some sort of sop for Nvidia?

    All-in-all a very annoying and disappointing non-review.

    rms
    Reply
  • Anonymous User - Friday, October 03, 2003 - link

    Still using Flash for benchmarks.. again? Come on, cut that out. Reply
  • Anonymous User - Friday, October 03, 2003 - link

    i dont even play games at 1024x768 cause i have an nvidia and it does suck! Reply
  • Anonymous User - Friday, October 03, 2003 - link

    Pete --

    The ATI 9600 Pro would not run Homeworld 2 at all ... Oops on leaving that out of the write up, but that's a good catch on your part.

    NWN problems are known, but didn't exist until introduced by the Cats released *after* NWN was on the shelves (so says Bioware iirc).

    But we will touch on this in the next article.

    The 9600 Pro will be addressed when we do our budget card section of the roundup ...

    J Derek Wilson
    (Wading through 180 posts as I work on the next set of benchies and IQ tests)
    Reply

Log in

Don't have an account? Sign up now