Improving Performance on NVIDIA

If the hypotheses mentioned on the previous page hold true, then there may be some ways around these performance issues. The most obvious is through updated drivers. NVIDIA does have a new driver release on the horizon, the Detonator 50 series of drivers. However, Valve instructed us not to use these drivers as they do not render fog in Half-Life 2. In fact, Valve was quite insistent that we only used publicly available drivers on publicly available hardware, which is a reason you won't see Half-Life 2 benchmarks in our upcoming Athlon 64 review.

Future drivers may be the key for higher performance to be enabled on NVIDIA platforms, but Gabe issued the following warning:

"I guess I am encouraging skepticism about future driver performance."

Only time will tell if updated drivers can close the performance gap, but as you are about to see, it is a decent sized gap.

One thing that is also worth noting is that the shader-specific workarounds for NVIDIA implemented by Valve will not immediately translate to all other games that are based off of Half-Life 2's Source engine. Remember that these restructured shaders are specific to the shaders used in Half-Life 2, which won't necessarily be the shaders used in a different game based off of the same engine.

Gabe also cautioned that reverting to 16-bit floating point values will only become more of an issue going forward as "newer DX9 functionality will be able to use fewer and fewer partial precision functions." Although the theory is that by the time this happens, NV4x will be upon us and will have hopefully fixed the problems that we're seeing today.

NVIDIA's Official Response

Of course, NVIDIA has their official PR response to these issues, which we've published below:

During the entire development of Half Life 2, NVIDIA has had close technical contact with Valve regarding the game. However, Valve has not made us aware of the issues Gabe discussed.

We're confused as to why Valve chose to use Release. 45 (Rel. 45) - because up to two weeks prior to the Shader Day we had been working closely with Valve to ensure that Release 50 (Rel. 50) provides the best experience possible on NVIDIA hardware.

Regarding the Half Life2 performance numbers that were published on the web, we believe these performance numbers are invalid because they do not use our Rel. 50 drivers. Engineering efforts on our Rel. 45 drivers stopped months ago in anticipation of Rel. 50. NVIDIA's optimizations for Half-Life 2 and other new games are included in our Rel.50 drivers - which reviewers currently have a beta version of today. Rel. 50 is the best driver we've ever built - it includes significant optimizations for the highly-programmable GeForce FX architecture and includes feature and performance benefits for over 100 million NVIDIA GPU customers.

Pending detailed information from Valve, we are unaware of any issues with Rel. 50 and the drop of Half-Life 2 that we have. The drop of Half-Life 2 that we currently have is more than 2 weeks old. It is not a cheat or an over optimization. Our current drop of Half-Life 2 is more than 2 weeks old. NVIDIA's Rel. 50 driver will be public before the game is available. Since we know that obtaining the best pixel shader performance from the GeForce FX GPUs currently requires some specialized work, our developer technology team works very closely with game developers. Part of this is understanding that in many cases promoting PS 1.4 (DirectX 8) to PS 2.0 (DirectX 9) provides no image quality benefit. Sometimes this involves converting 32-bit floating point precision shader operations into 16-bit floating point precision shaders in order to obtain the performance benefit of this mode with no image quality degradation. Our goal is to provide our consumers the best experience possible, and that means games must both look and run great.

The optimal code path for ATI and NVIDIA GPUs is different - so trying to test them with the same code path will always disadvantage one or the other. The default settings for each game have been chosen by both the developers and NVIDIA in order to produce the best results for our consumers.

In addition to the developer efforts, our driver team has developed a next-generation automatic shader optimizer that vastly improves GeForce FX pixel shader performance across the board. The fruits of these efforts will be seen in our Rel.50 driver release. Many other improvements have also been included in Rel.50, and these were all created either in response to, or in anticipation of the first wave of shipping DirectX 9 titles, such as Half-Life 2.

We are committed to working with Gabe to fully understand.

What's Wrong with NVIDIA? More on Mixed-Mode for NV3x
Comments Locked

111 Comments

View All Comments

  • Anonymous User - Friday, September 12, 2003 - link

    another thing i just noticed looking at the doom 3 and hl2 benchies.

    take a look at the performance of 9800pro and 9600pro...

    in hl2, the 9800pro is about 27% ahead of the 9600pro, in doom 3 the 9800pro is near 50% faster than the 9600pro. the whole thing just feels weird.

    enigma
  • Anonymous User - Friday, September 12, 2003 - link

    I'm surprised that Anand mentioned nothing about the comparisons between 4x2 and 8x1 pipelines? Does he even know that MS is working to included paired textures with simutainious wait states for the nV arcitexture? You see the DX9 SDK was developed thinking only one path and since each texture has a defined FIFO during the pass the second pipe in the nV is dormant until the first pipe FIFO operation is complete, with paired textures in the pipe using syncronus wait states this 'problem' will be greatly relieved.
  • Anonymous User - Friday, September 12, 2003 - link

    its fake.... HL2 test are not ready today , great fake Anandtech :)
  • rogerw99 - Friday, September 12, 2003 - link

    #28
    Ooo Ooo Ooo... I know the answer to that one.
    It was Mrs. White, but it wasn't with the gun, it was the lead pipe.
  • Anonymous User - Friday, September 12, 2003 - link

    ATI The Way It Should Be Played
  • Anonymous User - Friday, September 12, 2003 - link

    Quote: 'So why is it that in the age of incredibly fast, absurdly powerful DirectX 9 hardware do we find it necessary to bicker about everything but the hardware? Because, for the most part, we've had absolutely nothing better to do with this hardware.'

    Don't we? Wrong!

    http://www.cs.virginia.edu/~gfx/pubs/multigridGPU/

    ;)
  • Anonymous User - Friday, September 12, 2003 - link

    one thing that i think is kinda interesting. check out this benchmark hardocp did - fx5900 ultra vs. radeon 9800 pro in doom 3 (with help from id software).

    http://www.hardocp.com/article.html?art=NDc0LDE=

    after reading this, read carmack's Jan 03 .plan, where he states that under the default openGL codepath, the fx architecture is about half as fast as the r300 - something that is pretty much resembled in the hl2 benchmarks. furthermore he states that using the default path the r300 is clearly superior (+100%), but when converting to vendor-specific codepaths, the fx series is the clear winner.

    conclusions? none, but some possibilities
    .) ati is better in directx, nvidia in opengl
    .) id can actually code, valve cannot
    .) and your usual conspiracy theories, feel free to use one you specifically like

    bottom line. neither ati nor nvidia cards are the "right ones" at the moment, wait for the next generation of video cards and upgrade THEN.

    enigma
  • Anonymous User - Friday, September 12, 2003 - link

    I'm so glad i converted to Ati, i have never regret it & now it feels even better. Ati rules
  • notoriousformula - Friday, September 12, 2003 - link

    i'm sure Nvidia will strike back.. prolly with DOOM III..well till then i'll enjoy my little army of ATI cards: ATI 9800NP>PRO, ATI 9700, ATI 9600PRO :P..long live ATI!!! :D
  • Anonymous User - Friday, September 12, 2003 - link

    Anand should have benchmarked on a more widely used computer like a 2400 or 2500+ AMD. Who here has the money to buy a p4 3Gb 8000mhz FSB cpu?

Log in

Don't have an account? Sign up now