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!!!

Kingpin benchmarks, Technical [Aoril 18, 1999]
        - Written by legion

Here are more benchmarks for Kingpin. It is basically a continuation of the benchmarks posted in my previous article. The machine stats are the same as before (e.g. 128 megs of RAM, PII 400Mhz, etc.).

Kingpin Benchmarks

    3dfx Voodoo II SLI DISABLED 3dfx Voodoo II SLI ENABLED   3dfx Voodoo III: 2000     ATi Rage 128 Fury   CL TNT
    Mesa v3.0 3dfx OpenGL Beta 2.1 3dfx miniGL v1.4 Mesa v3.0 3dfx OpenGL Beta 2.1 3dfx miniGL v1.4 3dfx miniGL v1.49 OpenGL ICD   OpenGL ICD  
    FPS Factor FPS Factor FPS Factor FPS Factor FPS Factor FPS Factor FPS Factor FPS Factor FPS Factor
640x480 default 26.70 1.00 28.70 1.00 55.00 1.00 27.80 1.00 29.50 1.00 58.70 1.00 58.40 1.00 27.90 1.00 35.10 1.00
  no fog 32.00 1.20 42.50 1.48 54.90 1.00 34.40 1.24 47.50 1.61 58.70 1.00 58.40 1.00 33.70 1.21 47.60 1.36
  no sync 30.10 1.13 36.70 1.28 55.00 1.00 31.00 1.12 32.40 1.10 58.70 1.00 58.30 1.00 32.40 1.16 37.10 1.06
                                       
800x600 default 23.60 1.00 25.70 1.00 43.40 1.00 26.50 1.00 27.00 1.00 55.80 1.00 56.80 1.00 25.50 1.00 34.00 1.00
  no fog 26.00 1.10 35.50 1.38 43.20 1.00 31.30 1.18 42.20 1.56 56.00 1.00 56.90 1.00 29.20 1.15 42.60 1.25
  no sync 26.00 1.10 31.40 1.22 43.60 1.00 30.20 1.14 30.70 1.14 55.40 0.99 57.00 1.00 31.30 1.23 35.80 1.05
                                       
1024x768 default             24.30 1.00 25.60 1.00 49.40 1.00 50.80 1.00 21.80 1.00 28.70 1.00
  no fog             28.30 1.16 36.80 1.44 49.10 0.99 50.70 1.00 23.70 1.09 31.20 1.09
  no sync             28.10 1.16 30.20 1.18 49.50 1.00 50.80 1.00 28.40 1.30 30.20 1.05

Last Updated on 04/18/1999
By Roscoe A. Sincero

As mentioned in my previous article, the settings are defined as follows:

default no fog no sync
  • texture quality: Max
  • 8-bit textures: No
  • sync every frame: Yes
  • shadows: Auto
  • specular: No
  • fog: Yes
  • pain skins: Max
  • texture quality: Max
  • 8-bit textures: No
  • sync every frame: Yes
  • shadows: Auto
  • specular: No
  • fog: No
  • pain skins: Max
  • texture quality: Max
  • 8-bit textures: No
  • sync every frame: No
  • shadows: Auto
  • specular: No
  • fog: Yes
  • pain skins: Max

I am unsure as to why the ATi Rage numbers are low. In fact, even in Quake II the numbers I have are lower than the TNT. I assumed that the problem was that I have been using the "release candidate drivers" for the ATi Fury benchmarks. So I downloaded the previous driver (build 4.11.6060) to see if that provides an improvement. There was an "improvement" alright. At higher resolutions (e.g. 1024x768), the older driver provided about 10% faster frame rates in Quake II. But it provided approximately a 1% decrease in performance in Kingpin. So the "release candidate drivers" were better in Kingpin. At lower resolutions, the older driver provided approximately 6% decrease in performance in Quake II. In Kingpin, the older driver provided almost 5% decrease in performance in Kingpin. So overall the "release candidate drivers" are actually better than the older driver. Still, I do not know why the numbers are so low in comparison to the TNT in Kingpin. The "hype" around the Fury is that it is just as fast, if not faster, than the TNT.

As you can see, the Voodoo III: 2000 provides a very slight improvement over the Voodoo II: SLI in performance. The Voodoo III's biggest advantage, however, is its ability to provide higher resolutions--if only my monitor can keep up with such resolutions. Looks like my next upgrade will not be a graphics card, but a new monitor. Boy, that will be very, very, very expensive.

And, of course, the "sync every frame" and "fog" has absolutely no effect on the 3dfx cards using the miniGL. Someone suggested that the "sync" issue maybe related to the high CPU requirements of Kingpin. I pre-ordered the TNT2. That is the only card coming out in the near future that has enough horsepower to provide performance numbers that is fairly close or higher than the Voodoo II: SLI and Voodoo III:2000. If CPU is the cause for the "sync" issue, then we should see a very similar effect with the TNT2. The TNT results seem to suggest that this maybe the case. Disabling "sync every frame" only has a small impact on the TNT (~5%). It will probably have even a much smaller impact on the TNT2.

As for the fog "issue", it would appear that I have to keep repeating this until it actually registers into the zealot's brain. The miniGL does not have any OpenGL fog functions. That is why there is no performance effect with fog being disabled or enabled. OpenGL compliants cards such as the ATi Rage Fury and the Creative Labs Graphics Blaster TNT both support OpenGL fog. Therefore, it stands to reason that enabling fog will hurt the performance numbers in comparison to the 3dfx cards using the miniGL. And you can see that the performance issue with fog is pretty standard--there is a very significant performance penality in using fog. Since the miniGL does not support OpenGL fog, it will never ever see a performance penalty from OpenGL fog. Yet, we still will see zealots proclaiming that such and such a card is the fastest card based on unfair comparisons.

Here's something easy to understand: if you want to see which cards are the fastest card, then you have ALL the cards be treated the same. So if you have two OpenGL ICD cards, then all the other cards MUST ALSO be OpenGL ICD compliant cards. Moreover, you make sure that all the settings are the same for all of the cards. This means that if fog is enabled for one card, it must be enabled for all. The 3dfx cards do not support OpenGL fog. Duh! Therefore, it is NEVER enabled for these 3dfx cards. Duh! I see people saying that fog was enabled for their Voodoo II/III benchmarks as if it actually means something. It does not.

If you want to see what kind of frame rates you'll get in a particular game or a class of games (e.g. Unreal-engine games, Quake II-engine games), then you post up a table of frame rates like the one above. It is not a table to see which card is the fastest card in the world, it is a table to see what kind of frame rates you'll get with certain settings and with all the advantages you can give that particular card (e.g. using a "miniGL" instead of a full OpenGL ICD, using OpenGL instead of Direct3D, using Glide instead of OpenGL, etc., etc.).






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.


.