Inside3D
 • Front Page
 • Articles
 • Downloads
 • Forums
 • Hosting
 • Help Wanted
 • Interviews
 • Reviews
 • Staff

 
Allied Sites
 - AI Cafe
 - Bot Epidemic
 - Dark Places
 - Flat Earth
 - FrikBot
 - Ghoulish Art
 - Kilbert3D
 - Quake Info Pool
 - QSG: Quake Standards
 - Rusted Fork
 - Stroggs Gone Mad
 - More...
 
Quake
 - Getting Started
 - QuakeC Specs v1.0
 - QuakeC Tutorials
 - Quake Mod Index
 
Quake II
 - Getting Started
 - dll Sourcecode
 - Coding Tutorials
 
.dll Central
 - Getting Started
 - Learning
 - dll Primer
 - dll in C
 - dll in Delphi
 - Compilers
 
Jedi Knight
 - Getting Started
 - COG Specs
 - Sound Specs
 - Tutorials
 
Level Editing
 - Tutorials/Tips
 
 
Telefragged!!!

Voodoo 2/3 vs. TNT/2 [March 22, 1999]
        - Written by legion

One of the things that people love to talk about in regards as to which graphics card is the best is the performance issue. That is, what kind of frame rates can I expect to get with such and such a card? The weaklink is that these frame rates can not be obtained without benchmarks. The only way to get these benchmarks is to buy the cards and run some tests with it. Unfortunately, most of us are not made of money so we have to rely on others to do the tests for us.

Now here is the problem. These people have machines that most of us don't have. Even if some of us are lucky enough to get a high-octane 400Mhz Intel chip, there are even fewer of us who can afford to get a high-octane monitor. I see people doing benchmarks as high as 1600x1200 resolution in Quake II. My monitor can't support such a resolution. Moreover, my monitor refresh rate is not as high as some of the lucky few. This means that even though we have enough horsepower of a CPU and a kickass graphics card to go with it, our monitor may be letting us down by limiting our frame rate. Instead of getting 120 FPS at 1024x768, I "only" get 85. Instead of 90 FPS, I'd get just 60 FPS.

The benchmark tests themselves are also the weaklink. As the Average Joe would like you to believe in Bad Conclusions from Premature Data, Tom Pabst of Tom's Hardware does not know how to perform "good" 3D cards benchmarking tests. In fact, the Average Joe would have you believe that Tom Pabst is only telling you half the story. Average Joe will gladly tell you, for instance, that the TNT2 gives you a 40% drop in performance in going from 16-bit rendering to 32-bit rendering using the Forsaken "Ship" demo. The conclusion then is that for low-CPU intensive tests, the TNT2 is simply a faster cousin of the TNT. The average Joe, however, fails to mention that the TNT2 still delivers 70+ FPS (Sharky Extreme) in Forsaken at 1024x768 using 32-bit rendering. He fails to mention that at 16-bits, the frame rates are about 120 FPS in Forsaken "Ship" demo. He also fails to mention that his beloved Voodoo III: 3500 (Sharky Extreme) is actually a shade slower than the TNT2--120 FPS for the TNT2 vs 118 for the Voodoo III. So it is true, the TNT2 is a faster cousin--a MUCH FASTER cousin. It is so fast that it can still deliver frame rates greater than 60 in 32-bit rendering. If the Voodoo III: 3500 is so fast (as the benchmarks indicate) and it is roughly as fast as the TNT2 in 16-bits, it is a wonder why 3dfx is not including 32-bit rendering support? Their fastest card will cost roughly $40 dollars more than the TNT2! Why should we buy it, then?

But let me return to the topic at hand and talk about the benchmarks. Did it ever occur to people like the Average Joe that the so-called tests were designed to slant the results in 3dfx's favor? Let us look at the different APIs available for the TNT. There is Direct3D and OpenGL. When I play Half-life using the TNT, I see a marked difference in performance between OpenGL and Direct3D. This means that the API plays a role. When people use Quake II as a benchmarking device, what API do you think they are using? When they use the TNT, they use "default OpenGL". When they use 3dfx cards, they use "3dfx OpenGL". When I look into my Quake2 directory, I see a file called 3dfxgl.dll. I do not see a file called nvidiagl.dll or anything like that. Instead, Quake II uses the same "default OpenGL" for the TNT as it does for the i740 cards. The 3dfx cards get treated special. If I can see a difference between Direct3D and OpenGL, then why shouldn't I expect a performance difference between OpenGL and miniGL?

When one compares the TNT to the Voodoo II SLI while using Quake II as a benchmarking device, they are actually comparing apples and oranges. There is more than just two different cards being compared here. These tests are also comparing two different APIs. Look at the table below and you can see what a more fairer tests shows. The TNT is actually faster than the Voodoo II SLI. It is only when you specifically use drivers meant for the 3dfx cards do you see kick-ass high frame rates. This is no different from saying that using glide with 3dfx cards gives you faster performance than using Direct3D with 3dfx cards. The TNT cards do not use "specific" drivers. It gets treated like any other OpenGL cards such as the i740.

Graphics Card Comparison

3dfx SLI miniGL               average
demo1 1024x768 51.30 51.60 51.90 51.80 51.80   51.68
  800x600 74.20 74.30 74.30 74.00 74.40   74.24
  640x480 89.90 90.30 90.30 90.70 90.40   90.32
crusher 1024x768 33.70 34.30 34.50 34.50 34.50   34.30
  800x600 39.00 39.20 39.20 39.30 39.20   39.18
  640x480 40.90 41.30 41.20 41.30 41.30   41.20
3dfx SLI mesa                
demo1 1024x768 35.10 35.10 35.00 35.10 35.00   35.06
  800x600 42.60 42.60 42.60 42.60 42.60   42.60
  640x480 49.10 49.40 49.20 49.30 49.30   49.26
crusher 1024x768 20.20 20.00 20.30 20.30 20.30   20.22
  800x600 20.60 20.80 20.80 20.80 20.80   20.76
  640x480 20.70 20.90 20.90 20.90 20.90   20.86
3dfx SLI OpenGL Beta 2.1                
demo1 1024x768 47.70 48.10 48.00 48.00 48.10   47.98
  800x600 54.90 55.20 55.20 54.90 55.10   55.06
  640x480 56.80 57.20 57.10 56.80 57.10   57.00
crusher 1024x768 25.10 25.00 25.40 25.40 25.40   25.26
  800x600 25.50 25.80 25.90 25.90 26.00   25.82
  640x480 25.60 26.00 26.00 26.00 26.10   25.94
nVidia TNT                
demo1 1024x768 39.40 39.80 39.80 39.80 39.80   39.72
  800x600 60.30 60.80 60.60 60.40 60.70   60.56
  640x480 72.90 73.50 73.60 73.10 73.70   73.36
crusher 1024x768 30.00 30.20 30.30 30.30 30.30   30.22
  800x600 34.60 34.80 34.80 34.80 34.80   34.76
  640x480 35.30 35.50 35.60 35.60 35.60   35.52

Last Updated on 03/21/1999
By Roscoe A. Sincero
Email: legion@sincero.com

When nVidia and 3dfx are compared using the same API (e.g. Direct3D), then you see a much fairer comparison. Shogo, for instance, is a Direct3D game. Tom Pabst gladly provided benchmark comparisons. Unlike OpenGL, 3dfx allegedly has "excellent" D3D support while nVidia has "good" support. I don't know the difference between "excellent" and "good" but I do know that the TNT is slower that Voodoo II SLI. However, the TNT2 (slowest version) is faster than the Voodoo III: 3500 (Voodoo III's fastest sibling). By using a fairer comparison, it would seem that the TNT2 is faster than the Voodoo III. It is only when you use code that is specific to the 3dfx cards (e.g. like the "miniGL" for Quake II) that you get the ultra-fast frame rates.

The moral of the story is this: if card X is faster than card Y, is it really faster or was card X given an advantage? And how long would this advantage hold now that the "ace" will only work with old technology and future cards made from a specific manufacturer? How long will developers make games that would only work with specific cards?








UGO [an error occurred while processing this directive]

The Inside3D content and design is copyrighted by the Inside3D team, and may not be re-produced or copied without proper consent. All rights reserved. Any work credited to any author not part of Inside3D is copyrighted by that author. If you have any feedback, suggestions or flames please send it in to Inside3D or the author. Inside3D is hosted by telefragged and the design was originated by project-9.


.