Half-Life 2 Performance Benchmark Preview
by Anand Lal Shimpi on September 12, 2003 12:34 AM EST- Posted in
- GPUs
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.
Facebook
Twitter
RSS
111 Comments
View All Comments
Anonymous User - Sunday, September 14, 2003 - link
Umm.. could you PLEASE not use shockwave for thosetables? Our firewalls & browser configs also won't let it through, so these reviews become pretty much useless to read.
Anonymous User - Sunday, September 14, 2003 - link
where are the benchmarks comparing HL2 at different CPUs? I mean, i obviously know I'm gonna have to upgrade my gf3 to a new card (first game to make me even think of that... didnt care for ut2k3), but what about my venerable athlon xp 1800+ ? :(Anonymous User - Saturday, September 13, 2003 - link
#98, look at the 9700 Pro numbers, subtract 4-5%.Still, if I were to see another set of benchmarks, I'd DEFINITELY want these:
GeForce4 MX440 OR GeForce2 Ti - As an example of how well GF2/GF4MX cards perform on low detail settings, being DX7 parts.
GeForce3 Ti200 OR GeForce3 Ti500 - It's a DX8 part, and still respectably fast; lots of people have Ti200s, anyway.
GeForce4 Ti4200 - This is an incredibly common and respectably fast card, tons of people would be interested in seeing the numbers for these.
GeForce FX 5600 Ultra - Obvious.
GeForce FX 5900 Ultra - Obvious.
Radeon 8500 - It's still a good card, you know.
Radeon 9500 Pro - Admit it, you're all interested.
Radeon 9600 Pro - Obvious.
Radeon 9700 vanilla - Because it would show how clock speed scales, and besides these (and softmodded 9500s) are quite common.
Radeon 9700 Pro - Obvious.
Radeon 9800 Pro - Obvious.
The GeForce FX 5200 and GeForce4 Ti4600 might be nice too, but the Radeons 9000 through 9200 would be irrelevant (R200-based).
Also, obviously, I'd like to see them on two or three different detail levels (preferably three), to show how well some of the slower ones run at low detail and see how scalable Source really is. Speaking of scalability, a CPU scaling test would be extremely useful as well, like AnandTech's UT2003 CPU scaling test.
This sort of thing would probably take a lot of time, but I'd love to see it, and I bet I'm not alone there. I think something like what AnandTehc did with UT2003 would be great.
Just my ~$0.11.
clarkmo - Saturday, September 13, 2003 - link
I can't believe the Radeon 9500 hacked to a 9700 wasn't included in the benchmarks. What was he thinking? I guess Anand didn't have any luck scoring the right card. There are some still available, you know.Anonymous User - Saturday, September 13, 2003 - link
Quote from the Irari information minister:"Nvidia is kicking ATI's butt. Their hardware is producing vastly superior numbers."
Anonymous User - Saturday, September 13, 2003 - link
Nvidia quote: "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."3Dfx said some years ago that no one ever would use or notice the benefits of 32 bit textures. Nvidia did and 3Dfx is gone. Will Nvidia follow the 3Dfx path?
Anonymous User - Saturday, September 13, 2003 - link
Anyone remember when ati.com sold rubber dog crap?Pete - Saturday, September 13, 2003 - link
#74, straight from the horse's mouth:http://www.nvnews.net/#1063313306
"The GeForce FX is currently the fastest card we've benchmarked the Doom technology on and that's largely due to NVIDIA's close cooperation with us during the development of the algorithms that were used in Doom. They knew that the shadow rendering techniques we're using were going to be very important in a wide variety of games and they made some particular optimizations in their hardware strategy to take advantage of this and that served them well. --John Carmack"
Of course those D3 numbers were early (as are these HL2 ones), so things can change with updated drivers.
Anonymous User - Saturday, September 13, 2003 - link
I don't know if it has already been asked, but even if it has I ask again for emphasis.Anand, it would be nice if you could add a 9600 non-pro bench to the results. You mention raw GPU power being the determining factor now, and as the 9600 Pro's difference in memory clock is more significant than its engine clock, it would be interesting and informative to the budget/performance croud to note the 9600 non-pro performance in HL2.
Thanks for all your informative, insightful, accurate, in-depth articles.
Anonymous User - Friday, September 12, 2003 - link
I always find it interesting how people say ATI is the "little guy" in this situation.ATI has been a major player in the video card market since the eighties (I had a 16-bit VGA Wonder stuck in an 8-bit ISA slot in an 8088/2 system) and that didn't change much even when 3dfx came onto the scene. A lot of those voodoo pass through cards got their video from an ATI 3d expression or some other cheap 2d card (Cirrus Logic or Trident anyone?).
Nvidia and ATI have been at each others throats ever since Nvidia sold its first video card on the OEM market. 3dfx was just a little blip to ATI, Nvidia stealing away a bunch of its OEM sales with a bad 2d/good 3d video card on the other hand, well, that was personal.
I imagine someone at ATi saying something like this:
"All of you guys working on making faster DACs and better signal quality are being transferred to our new 3d department. Its sort of like 2d cept its got one more d, thats all we know for right now.".
ATI knows how to engineer and build a video card, they have been doing it for long enough. Same with Matrox (Matrox builds the Rolls Royce's of video cards for broadcast and video editing use), Nvidia on the other hand knew how to build 3d accelerators, and not much else. The 2d on any early Rage card slaughtered the early Nvidia cards.
Course, the 3d sucked balls, thats what a Canopus Pure 3d was for though.
Now ATI has the whole "3d" part of the chip figured out. The driver guys have their heads wrapped around the things as well (before 3d cards came around ATI's drivers were the envy of the industry). Its had many years of experience dealing with games companies, OS companies, standards, and customers. And its maturity is really starting to show after a few minor bumps and bruises.
ATI wants its market back, and after getting artx it has the means to do it. Of course, Nvidia is going to come out of this whole situation a lot more grown up as well. Both companies are going to have to fight blood tooth and nail to stay on top now. If they don't Matrox might just step up to the plate and bloody both of their noses. Or any of those "other" long forgotten video card companies that have some engineers stashed away working on DX 7 chips.
God knows what next month is going to bring.
Anyways, sorry for the rant..