To use commands and variables, you need to either add them to suitable configuration files (i.e: autoexec.cfg) or enter them into the in-game console.
How configuration files work:
Quake Live uses the following configuration files:
- - repconfig.cfg: this auto-generated file contains all of your key bindings and preference settings (never manually edit this file!)
- - qzconfig.cfg: this auto-generated file contains other settings not listed in the repconfig (never manually edit this file!)
- - autoexec.cfg: a user-generated file. When this exists, the game automatically applies all the settings contained in it to your repconfig when the game loads.
Any other configuration files will need to be loaded in-game using the ‘exec ' command in the console, unless the config file is already loaded by the autoexec.
Configuration files use the ‘.cfg' file extension and are essentially basic text files which can be edited with a program such as WordPad. Never use Notepad for editing as it may format the file incorrectly and the game will not be able to read it.
How to reset your game settings:
Delete your repconfig.cfg and qzconfig.cfg (autoexec.cfg too if it exists), reset your settings from the site, and reload the game. You will have brand new configurations generated.
'The game won't save my settings, what do I do?'
This is a common issue with the game in recent times. To solve this problem, you should load the game and change your settings as you wish, then type writeconfig autoexec in the console to save your settings. If you do this every time you change any settings then your settings will be saved. Alternatively, you could manually edit your autoexec.cfg in WordPad.
How to access your in-game console:
While you're in-game, press Ctrl+Alt+~ to bring down the console screen. Type com_allowConsole '1' in the console, this will alow you to access the console by simply pressing the tilde (~) key in future.
Auto-complete feature:
To save time typing out commands and variables in the console, press Tab while typing to auto-complete it. If there are multiple options, a list of these options will be printed to the console. This feature also works for map names.
Scrolling through the console entries:
Press PgUp to scroll up and PgDn to scroll down when you're searching for entries through many other entries.
The console is your friend – USE IT!
- Using the anti-aliasing setting via a config generated via R1GL config generator resulted in my FPS going from 2300 FPS to 213 FPS (running demo1.dm2). However, using Nvida Control panel for anti-aliasing (all settings set to maximum quality image), I get 511 FPS. So clearly using Nvidia controls is less impactful when running quake 2.
- Also that will help to improve FPS in Quake Champions! Set up all graphics configuration to lowest and quit the game. Run NVIDIA Inspector. Switch to NVIDIA Profile Inspector. Choose 'Quake Champions' from 'Profiles' drop-down list, like in the picture below (under number 1).
- For Quake II on the PC, GameFAQs has 2 guides and walkthroughs.
Quake II using DEMOMAP DEMO1.DM2
As title says, capping works only on the max fps, but it won't cap your minimum fps, as your minimum depends on system perfomance. ( Link, Reply ).
NOTE: Frame-rates for Quake 2 are completely different than for GLQuake. Quake 2 uses a different animation and rendering engine than Quake, so comparing their frame-rates is like comparing apples and oranges. The minimum acceptable frame-rate for solo play in Quake 2 is about 12 fps, and maybe around 15 for netplay. More is certainly better. Quake 2 puts even more strain on a 3D graphics subsystem than GLQuake does.
THE TEST:
The test used is the same one Brian Hook described using in his .plan for his frame-rate tests on a souped up P-II 300 system.
If you would like to perform the exact same test I've performed here, using the same settings so you can compare your system to the following chart, you can download the test by clicking here.. Unzip the files into an empty directory and follow the instructions in the included README.TXT file.
USE THESE TEST RESULTS ONLY AS A GUIDE! Please be aware that frame-rate tests are not very precise. It's not unusual for two systems with identical processors and 3D cards to have scores that differ by as much as 8 fps due to differences in motherboard design, BIOS settings, design of the secondary cache algorithm, etc. There are many variables involved! Even the same system can test differently on two different days depending on the temperature inside the case (the 3D card's processors, and even your CPU, are sensitive to temperature - one good reason to invest in a cooling fan for your 3D card). Don't e-mail me pissing and moaning that your P-200 gets 5 fps less than the one tested here, and you want to know how to fix it - DON'T WORRY, BE HAPPY! Again, use these test results only as a guide. Your mileage may (will!) vary.
'BUT WHY SHOULD I TEST MY FRAMERATE WITH THE SOUND DISABLED?'
These test configs set all display variables to defaults and disable sound as recommended by Brian Hook). Why disable sound? In a nutshell, having sound enabled will cap your framerate in the timedemo. A timedemo can run much faster than a normal game (you can't actually play Q2 at the speed that a timedemo runs at, can you now?). It can run so fast that the sound card buffer fills up. Once this happens, the 3D card and CPU must wait until the sound card clears it's buffer before it can render a frame, thus the system is bottlenecked at the sound card. At that point you're not testing the fps of the 3D video subsystem anymore - instead you're testing the fps of the sound card since the rest of the system is waiting on it.
BEFORE YOU WRITE IN COMPLAINING ABOUT THE WAY I DO MY TESTS..
1. The purpose of the tests I've performed is to make a COMPARISON. The game doesn't matter and Quake2 is as valid a testbed as Q3 or UT. I use Q2 because I already have a VAST database of systems benchmarked running Q2 with EXACTLY the same settings using the Brian Hook standard timedemo test. I don't have time to retest all these systems on every other game out there. I have started to test some systems running Quake3 and I will post the results here as they come in. Don't nag me to test other games as I have more important things to do - like watch porn and play computer games.
2. It's logical to assume that if you see a 25% improvement in framerate going from CPU A to CPU B in Quake2, then you'll likely see the same 25% improvement in other first person shooters. Yes, I know that's simplistic, but we're talking RELATIVE comparisons of different CPUs running 3Dfx hardware. If you want ABSOLUTE numbers get them from some other sites, but unless the tests are done EXACTLY the same way with EXACTLY the same settings, they're meaningless for purposes of comparison.
3. Along the same lines as #2 above, even if you have a different brand of video card, you can use this chart to see POTENTIALLY what kind of performance increase you'll get by upgrading your CPU. Again, if I got a 25% improvement in FPS going from CPU A to CPU B on a V3-3000, you'll probably see ROUGHLY the same percentage of improvement on a G400, a TNT2 or a GeForce using the same processors (yes I know some of these other cards are less CPU dependent than others, but it still applies as a valid comparison guide). I only own 3Dfx hardware (I'm not a 3Dfx advocate, that's just the hardware I've chosen to use - something better comes along that I can afford, I'll buy it).
4. The purpose of my page is to help people decide on a CPU upgrade, NOT to sell you on a 3Dfx card or a particular CPU. I'm trying to answer this question which you constantly see posted in various forms on 3D hardware forums: 'Is it worth it for me to upgrade my CPU to a CPU, and how much of difference will I see?'
5. I don't give a rat's behind what framerate you're getting on YOUR system with YOUR video card with YOUR settings. Please don't e-mail me to brag. I fully agree that there may be better hardware out there, this is just the hardware I'm using and have access to. You want to mail me your video card for a few weeks so I can do tests? No problem. I'm more than happy with the framerate I'm getting on my personal system thank you, and bragging is NOT the point of my framerate page (see #4 above). Don't treat me like a deprived child, and don't start any flame wars. I'm trying to provide information here.
TEST 1: System Performance Comparison in Software 2D Mode
This section is for the benefit of you poor deprived folks out there who STILL don't own a 3D card. Quake2 doesn't perform very well in software 2D mode, except on very high-end systems with very fast 2D graphics cards. Even so, there's no way you can get the performance in software mode that you can get in 3D mode.
So you can better appreciate what a 3D card will do for you, here's some systems tested running in 2D software mode.
All following tests were done with the viewsize set for 100 and the sound handler turned off. All computers are running version 3.14 (or later) of Quake 2.
| Computer System | 512x384 | 3D Card |
| Pentium II 400 MMX (Overclocked to 448 Mhz), 128 Mb SDRAM, Win95, Aopen AX6b mobo | 33.4 | Matrox Millenium II, PCI |
| Pentium II 400 MMX, 128mb SDRAM, Win98, Soyo 6BA mobo | 31.1 | Matrox Millenium II, AGP |
| Pentium II 300 MMX, 128mb SDRAM, Win98, Soyo 6BA mobo | 20.9 | Matrox Millenium II, AGP |
| P-233 MMX, 64mb SDRAM, Win98, FIC PA-2007 mobo | 12.6 | Diamond Stealth 2000 3D, PCI |
| P-200, 64mb, Win95, FIC PT-2003 mobo | 12.4 | Matrox Millenium I, PCI |
COMMENTS: I would consider the 30 fps barely acceptable for serious net-play. All the other systems would only get acceptable performance at lower resolutions (400x300 or 320x240).
TEST 2: System Performance Comparison in 3Dfx OpenGL 3D Mode
This is what we're all really here for. This is a comparison of a variety of systems using either Voodoo, Voodoo2 or Voodoo3 video cards in a variety of resolutions.
All following tests were done with the viewsize set for 100 and the sound handler turned off. All computers are running version 3.14 (or later) of Quake 2. Vsync was disabled for best performance and to avoid an artificial framerate cap.
NOTE: The latest drivers for 3Dfx video cards don't allow you to disable VSync. There is no need to disable VSync in normal play, and doing so will give you horrible image tearing. However, with VSync disabled your framerate will never exceed your monitor's vertical refresh frequency in a timedemo test. To perform benchmark testing properly you should temporarily disable VSync for the test. If your driver supports it, disable VSync in the the advanced video properties tab. Otherwise, you can download the V2 or V3 Overclocker utility form my Files & Drivers Page which adds a new display properties tab with VSync and clock adjustments.
Systems running with a Voodoo 1 card are displayed with blue text.
Systems running with a Voodoo 2 card are displayed with red text.
Systems running with a Voodoo 3 card are displayed with green text.
| Computer System | 512x384 | 640x480 | 800x600 | 1024x 768 | 1280x 960 | 3D Card |
| Pentium III 550E (Overclocked to 733 MHz 133x5.5), 128Mb, Abit BE6 II mobo, Win98 | 163.9 | 125.3 | 87.3 | 3Dfx Voodoo3 3000 AGP (Overclocked to 186 MHz) | ||
| Pentium III 550E (Overclocked to 733 MHz 133x5.5), 128Mb, Abit BE6 II mobo, Win98 | 159.1 | 118.3 | 82.5 | 3Dfx Voodoo3 3000 AGP (Overclocked to 176 MHz) | ||
| Pentium III 550E (Overclocked to 733 MHz 133x5.5), 128Mb, Abit BE6 II mobo, Win98 | 155.2 | 111.6 | 77.7 | 3Dfx Voodoo3 3000 AGP | ||
| Pentium III 550E (Overclocked to 666 MHz 121x5.5), 128Mb, Abit BE6 II mobo, Win98 | 149.8 | 117.4 | 82.4 | 3Dfx Voodoo3 3000 AGP (Overclocked to 176 MHz) | ||
| Pentium III 550E (Overclocked to 666 MHz 121x5.5), 128Mb, Abit BE6 II mobo, Win98 | 146.6 | 110.9 | 77.7 | 3Dfx Voodoo3 3000 AGP | ||
| Pentium III 550E (Overclocked to 633 MHz 115x5.5), 128Mb, Abit BE6 II mobo, Win98 | 143.5 | 116.5 | 82.4 | 3Dfx Voodoo3 3000 AGP (Overclocked to 176 MHz) | ||
| Pentium III 550E (Overclocked to 633 MHz 115x5.5), 128Mb, Abit BE6 II mobo, Win98 | 141.2 | 110.5 | 77.6 | 3Dfx Voodoo3 3000 AGP | ||
| Pentium III 550E, 128Mb, Abit BE6 II mobo, Win98 | 127.1 | 111.6 | 81.7 | 3Dfx Voodoo3 3000 AGP (Overclocked to 176 MHz) | ||
| Pentium III 550E, 128Mb, Abit BE6 II mobo, Win98 | 126.2 | 107.5 | 77.4 | 3Dfx Voodoo3 3000 AGP | ||
| Pentium III 500 (Overclocked to 560), 128Mb, Abit BX6 mobo | 128.8 | 127.7 | 117.7 | 87.0 | na | Metabyte Wicked3D Voodoo2 12 Mb SLI |
| Pentium III 500, 128Mb, Abit BX6 mobo | 128.8 | 127.7 | 117.7 | 87.0 | na | Metabyte Wicked3D Voodoo2 12 Mb SLI |
| Pentium III 500, 128Mb, Asus P2B-LS mobo | 125.7 | 124.1 | 114.5 | 82.9 | 55.2 | 3Dfx Voodoo3 3000 AGP |
| Pentium II 400 MMX (Overclocked to 448 MHz), 128 Mb, Win95, Aopen AX6b mobo | 116.9 | 98.7 | 63.4 | na | na | Creative Voodoo2 8 Mb |
| PentiumII 400 MMX (Overclocked to 448 MHz- 112x4), 128mb, Win98, Soyo 6BA mobo | 109.3 | 107.5 | 95.7 | 65.3 | na | Creative Labs Voodoo2 12 Mb SLI |
| Celeron 300a (Overclocked to 450 Mhz 100x4.5), 128 Mb, Win98, Abit BH6 mobo | 104.5 | 103.8 | 98.5 | 74.6 | na | Creative Labs Voodoo2 12 Mb SLI (overclocked to 100 Mhz) |
| Pentium II 400 MMX, 128Mb, Win98, Soyo 6BA mobo | 104.6 | 103.3 | 92.6 | 65.4 | 3Dfx Voodoo3 2000 AGP | |
| Pentium II 400 MMX, 128mb, Win95, Dell Dimension XPS R400 | 102.9 | 102.8 | 100.3 | 70.9 | na | Creative Labs Voodoo2 12 Mb SLI |
| PentiumII 400 MMX, 128mb, Win98, Soyo 6BA mobo | 98.3 | 97.9 | 89.9 | 65.0 | na | Creative Labs Voodoo2 12 Mb SLI |
| Celeron 300a (Overclocked to 450: 100x4.5) MMX, 64mb, Win98, Asus P2B mobo | 98.3 | 90.0 | 58.9 | na | na | Quantum 3D Obsidian2 (Voodoo2) 12 Mb |
| Pentium II 400 MMX, 128mb, Win98 RC0, Dell Optiplex GX-1 | 94.1 | 94.0 | 91.0 | 74.2 | na | Creative Labs Voodoo2 12 Mb SLI |
| Celeron 400, 128 Mb, Abit BH6 mobo | 93.4 | 93.4 | 93.4 | 79.0 | 3Dfx Voodoo3 3000 AGP | |
| AMD K6-2 400 (Overclocked to 420 4x105MHz), 192 Mb 192 MB sdram | ---- | 87.0 | 86.7 | 80.0 | na | Creative Labs Voodoo2 12 Mb SLI |
| Pentium II 300A Celeron (Overclocked to 338 MHz 4.5x75), 64mb SDRAM, Win95, ABit LX6 mobo | 79.6 | 76.3 | 56.7 | na | na | Guillemot MaxiGamer Voodoo2 12 Mb |
| Pentium II 300 MMX (Overclocked to 338 MHz), 128mb SDRAM, Win98, Soyo 6BA mobo | 75.7 | 75.6 | 74.9 | 66.9 | na | Creative Labs Voodoo2 12 Mb SLI |
| Pentium II 300 MMX (Overclocked to 338 MHz), 128mb SDRAM, Win98, Soyo 6BA mobo | 75.9 | 73.9 | 56.8 | na | na | Creative Voodoo2 12 Mb |
| AMD K6-2 350 (Overclocked to 375 MHz 5x75),128mb SDRAM, Win98, Asus TX97XE mobo | 75.0 | 75.4 | 71.0 | 64.1 | na | Guillemot Maxigamer Voodoo2 12 mb SLI |
| Pentium II 300 MMX, 128mb SDRAM, Win98, Soyo 6BA mobo | 67.4 | 67.3 | 66.8 | 54.8 | na | Creative Labs Voodoo2 12 Mb SLI |
| Pentium II 300 MMX, 128mb SDRAM, Win98, Soyo 6BA mobo | 67.3 | 66.3 | 54.8 | na | na | Creative Voodoo2 12 Mb |
| AMD K6-2 266 (using 3DNow! Quake2 miniport), 128 Mb, Win98 | 57.4 | 65.3 | 57.5 | na | Diamond Monster 3D II Voodoo2 8 Mb | |
| Pentium II 233 MMX (Overclocked to 262), 64 Mb, Win98, Asus P2L97 mobo | 55.1 | 50.6 | 49.0 | na | Quantum Obsidian 2 PCI 12 Mb | |
| Pentium II 233 MMX, 64Mb | 50 | 39.6 | 35.9 | na | na | Monster Fusion Voodoo Banshee |
| Pentium II Celeron 300 MMX (Overclocked to 333 MHz), 128 Mb, Win95 | 48.0 | na | na | na | Canopus Pure3D Voodoo | |
| P-233 MMX, 128mb SDRAM, Win98, FIC PA-2007 mobo | 47.0 | 47.1 | 46.8 | na | na | Creative Voodoo2 8 Mb |
| Pentium II 266 MMX, 64mb, Win95 | 45.0 | na | na | Creative Voodoo2 12 Mb | ||
| Pentium II 300 MMX, 128mb, Win95 | 42.4 | na | na | na | Monster 3D Voodoo | |
| Pentium II 300 MMX, 96mb, Win95 (Brian Hook's test system) | 39.3 | na | na | na | Monster 3D Voodoo | |
| P-233 MMX, 32mb, Win95 | 38.1 | na | na | na | Monster 3D Voodoo | |
| Pentium II 300 MMX, 64mb, NT4.0 | 36.9 | na | na | na | Monster 3D Voodoo | |
| P-200, 64mb, Win95, FIC PA-2007 mobo | 35.7 | na | na | Creative Voodoo2 8 Mb | ||
| P-200, 40mb, Win95, FIC PA-2007 mobo | 34.2 | na | na | na | Monster 3D Voodoo | |
| P-200 MMX, 32mb, Win95 | 32.8 | na | na | na | Righteous 3D Voodoo | |
| P-166, 40mb, Win95, IC PA-2007 mobo | 30.1 | na | na | na | Monster 3D Voodoo | |
| P-200, 64mb, Win95, FIC PT-2003 mobo | 29.1 | 28.9 | 28.8 | na | na | Creative Voodoo2 12 Mb |
| K6-233 MMX, 64mb, Win95 | 27.6 | na | na | na | Monster 3D Voodoo | |
| P-166, 64mb, Win95, FIC PT-2003 mobo | 26.2 | 25.8 | 25.5 | na | na | Creative Voodoo2 12 Mb |
| P-133, 64mb, Win95, FIC PA-2007 mobo | 25.9 | na | na | Creative Voodoo2 8 Mb | ||
| P-133, 48mb, Win95, FIC PA-2007 mobo | 25.9 | na | na | na | Monster 3D Voodoo | |
| P-133, 64mb, Win95, FIC PT-2003 mobo | 22.7 | 22.9 | 23.0 | na | na | Creative Voodoo2 12 Mb |
| P-120, 64mb, Win95, FIC PT-2003 mobo | 20.3 | 20.5 | 20.6 | na | na | Creative Voodoo2 12 Mb |
| P-90, 64mb, Win95, FIC PT-2003 mobo | 18.0 | 12.6 | 13.0 | na | na | Creative Voodoo2 12 Mb |
| Cyrix PR-200+, 32mb, Win95 | 15.3 | na | na | na | Monster 3D Voodoo |
Quake 2 Max Fps Mod
Any of these systems will give you okay performance in solo play (although it's going to bog down sometimes on anything less than a P-133), but realistically you need at least 30 fps to enjoy netplay. Competative netplay requires about 40 fps. I would consider a minimal system for competative netplay to be a P-233 with a Voodoo2 or Voodoo3, and I'd disable dynamic lighting (set gl_dynamic 0) to keep the framerate near 40 fps.
You should also look carefully at the scores for the P2-400 with the single Voodoo2 card as opposed to the scores for the P2-400 with dual cards running in SLI mode. The single card system slightly outperformed the dual card system at 512x384 because it's CPU is over-clocked to 448 MHz. However, it lags far behind the dual card system at 800x600 resolution. This clearly demonstrates the improved performance you get when using dual-card SLI on a high performance system - the framerates on the dual card system remain practically the the same at all resolutions (although there's nothing shabby about the 64 fps the single card system got at 800x600, I might point out).
Many of you have expressed surprise (or dismay, as the case may be) at the showing of the Cyrix PR-200+ system. However, this performance is not surprising considering the fact that the Cyrix CPU has a very weak floating-point unit compared to Intel processors and even compared to the K6. However, at 15.3 the Cyrix is at least (barely) playable in solo mode, although the framerate is not acceptable for serious deathmatch play. And before you ask, I wouldn't expect the score to be any higher if you put a Voodoo2 in the Cyrix machine - you can't make a cow run like a gazelle..
VOODOO 2: You might be surprised that Voodoo2 cards performed so poorly on low-end systems, but this is to be expected. The Voodoo 2 only really shines when it's running on a high-end Pentium II or better system. However, it is worth noting that even on a low-end system, the Voodoo 2 produced excellent framerates at all resolutions on up to 800x600. Also, while it's not reflected in these scores, the Voodoo 2 plays much smoother on low-end systems than the Voodoo cards do. This is mostly thanks to the Voodoo 2's dual texture units and larger texture memory, which results in a reduction in frames dropped due to texture thrashing. That's worth the price of a Voodoo2 alone - it sucks getting fragged all the time because your system slows to a crawl when there's a lot of Hyberblaster fire going on. It's worth noting here that on a Voodoo2 you probably won't be playing Quake 2 at 512x384, as the Voodoo 2 is capable of maintaining a high frame rate while running at 640x480 and 800x600 (see Test 2 below for the results of Voodoo2 tests on low-end systems at various resolutions) - and oh boy does it look pretty at those high resolutions, childrens..
To use commands and variables, you need to either add them to suitable configuration files (i.e: autoexec.cfg) or enter them into the in-game console.
How configuration files work:
Quake Live uses the following configuration files:
- - repconfig.cfg: this auto-generated file contains all of your key bindings and preference settings (never manually edit this file!)
- - qzconfig.cfg: this auto-generated file contains other settings not listed in the repconfig (never manually edit this file!)
- - autoexec.cfg: a user-generated file. When this exists, the game automatically applies all the settings contained in it to your repconfig when the game loads.
Any other configuration files will need to be loaded in-game using the ‘exec ' command in the console, unless the config file is already loaded by the autoexec.
Configuration files use the ‘.cfg' file extension and are essentially basic text files which can be edited with a program such as WordPad. Never use Notepad for editing as it may format the file incorrectly and the game will not be able to read it.
How to reset your game settings:
Delete your repconfig.cfg and qzconfig.cfg (autoexec.cfg too if it exists), reset your settings from the site, and reload the game. You will have brand new configurations generated.
'The game won't save my settings, what do I do?'
This is a common issue with the game in recent times. To solve this problem, you should load the game and change your settings as you wish, then type writeconfig autoexec in the console to save your settings. If you do this every time you change any settings then your settings will be saved. Alternatively, you could manually edit your autoexec.cfg in WordPad.
How to access your in-game console:
While you're in-game, press Ctrl+Alt+~ to bring down the console screen. Type com_allowConsole '1' in the console, this will alow you to access the console by simply pressing the tilde (~) key in future.
Auto-complete feature:
To save time typing out commands and variables in the console, press Tab while typing to auto-complete it. If there are multiple options, a list of these options will be printed to the console. This feature also works for map names.
Scrolling through the console entries:
Press PgUp to scroll up and PgDn to scroll down when you're searching for entries through many other entries.
The console is your friend – USE IT!
- Using the anti-aliasing setting via a config generated via R1GL config generator resulted in my FPS going from 2300 FPS to 213 FPS (running demo1.dm2). However, using Nvida Control panel for anti-aliasing (all settings set to maximum quality image), I get 511 FPS. So clearly using Nvidia controls is less impactful when running quake 2.
- Also that will help to improve FPS in Quake Champions! Set up all graphics configuration to lowest and quit the game. Run NVIDIA Inspector. Switch to NVIDIA Profile Inspector. Choose 'Quake Champions' from 'Profiles' drop-down list, like in the picture below (under number 1).
- For Quake II on the PC, GameFAQs has 2 guides and walkthroughs.
Quake II using DEMOMAP DEMO1.DM2
As title says, capping works only on the max fps, but it won't cap your minimum fps, as your minimum depends on system perfomance. ( Link, Reply ).
NOTE: Frame-rates for Quake 2 are completely different than for GLQuake. Quake 2 uses a different animation and rendering engine than Quake, so comparing their frame-rates is like comparing apples and oranges. The minimum acceptable frame-rate for solo play in Quake 2 is about 12 fps, and maybe around 15 for netplay. More is certainly better. Quake 2 puts even more strain on a 3D graphics subsystem than GLQuake does.
THE TEST:
The test used is the same one Brian Hook described using in his .plan for his frame-rate tests on a souped up P-II 300 system.
If you would like to perform the exact same test I've performed here, using the same settings so you can compare your system to the following chart, you can download the test by clicking here.. Unzip the files into an empty directory and follow the instructions in the included README.TXT file.
USE THESE TEST RESULTS ONLY AS A GUIDE! Please be aware that frame-rate tests are not very precise. It's not unusual for two systems with identical processors and 3D cards to have scores that differ by as much as 8 fps due to differences in motherboard design, BIOS settings, design of the secondary cache algorithm, etc. There are many variables involved! Even the same system can test differently on two different days depending on the temperature inside the case (the 3D card's processors, and even your CPU, are sensitive to temperature - one good reason to invest in a cooling fan for your 3D card). Don't e-mail me pissing and moaning that your P-200 gets 5 fps less than the one tested here, and you want to know how to fix it - DON'T WORRY, BE HAPPY! Again, use these test results only as a guide. Your mileage may (will!) vary.
'BUT WHY SHOULD I TEST MY FRAMERATE WITH THE SOUND DISABLED?'
These test configs set all display variables to defaults and disable sound as recommended by Brian Hook). Why disable sound? In a nutshell, having sound enabled will cap your framerate in the timedemo. A timedemo can run much faster than a normal game (you can't actually play Q2 at the speed that a timedemo runs at, can you now?). It can run so fast that the sound card buffer fills up. Once this happens, the 3D card and CPU must wait until the sound card clears it's buffer before it can render a frame, thus the system is bottlenecked at the sound card. At that point you're not testing the fps of the 3D video subsystem anymore - instead you're testing the fps of the sound card since the rest of the system is waiting on it.
BEFORE YOU WRITE IN COMPLAINING ABOUT THE WAY I DO MY TESTS..
1. The purpose of the tests I've performed is to make a COMPARISON. The game doesn't matter and Quake2 is as valid a testbed as Q3 or UT. I use Q2 because I already have a VAST database of systems benchmarked running Q2 with EXACTLY the same settings using the Brian Hook standard timedemo test. I don't have time to retest all these systems on every other game out there. I have started to test some systems running Quake3 and I will post the results here as they come in. Don't nag me to test other games as I have more important things to do - like watch porn and play computer games.
2. It's logical to assume that if you see a 25% improvement in framerate going from CPU A to CPU B in Quake2, then you'll likely see the same 25% improvement in other first person shooters. Yes, I know that's simplistic, but we're talking RELATIVE comparisons of different CPUs running 3Dfx hardware. If you want ABSOLUTE numbers get them from some other sites, but unless the tests are done EXACTLY the same way with EXACTLY the same settings, they're meaningless for purposes of comparison.
3. Along the same lines as #2 above, even if you have a different brand of video card, you can use this chart to see POTENTIALLY what kind of performance increase you'll get by upgrading your CPU. Again, if I got a 25% improvement in FPS going from CPU A to CPU B on a V3-3000, you'll probably see ROUGHLY the same percentage of improvement on a G400, a TNT2 or a GeForce using the same processors (yes I know some of these other cards are less CPU dependent than others, but it still applies as a valid comparison guide). I only own 3Dfx hardware (I'm not a 3Dfx advocate, that's just the hardware I've chosen to use - something better comes along that I can afford, I'll buy it).
4. The purpose of my page is to help people decide on a CPU upgrade, NOT to sell you on a 3Dfx card or a particular CPU. I'm trying to answer this question which you constantly see posted in various forms on 3D hardware forums: 'Is it worth it for me to upgrade my CPU to a CPU, and how much of difference will I see?'
5. I don't give a rat's behind what framerate you're getting on YOUR system with YOUR video card with YOUR settings. Please don't e-mail me to brag. I fully agree that there may be better hardware out there, this is just the hardware I'm using and have access to. You want to mail me your video card for a few weeks so I can do tests? No problem. I'm more than happy with the framerate I'm getting on my personal system thank you, and bragging is NOT the point of my framerate page (see #4 above). Don't treat me like a deprived child, and don't start any flame wars. I'm trying to provide information here.
TEST 1: System Performance Comparison in Software 2D Mode
This section is for the benefit of you poor deprived folks out there who STILL don't own a 3D card. Quake2 doesn't perform very well in software 2D mode, except on very high-end systems with very fast 2D graphics cards. Even so, there's no way you can get the performance in software mode that you can get in 3D mode.
So you can better appreciate what a 3D card will do for you, here's some systems tested running in 2D software mode.
All following tests were done with the viewsize set for 100 and the sound handler turned off. All computers are running version 3.14 (or later) of Quake 2.
| Computer System | 512x384 | 3D Card |
| Pentium II 400 MMX (Overclocked to 448 Mhz), 128 Mb SDRAM, Win95, Aopen AX6b mobo | 33.4 | Matrox Millenium II, PCI |
| Pentium II 400 MMX, 128mb SDRAM, Win98, Soyo 6BA mobo | 31.1 | Matrox Millenium II, AGP |
| Pentium II 300 MMX, 128mb SDRAM, Win98, Soyo 6BA mobo | 20.9 | Matrox Millenium II, AGP |
| P-233 MMX, 64mb SDRAM, Win98, FIC PA-2007 mobo | 12.6 | Diamond Stealth 2000 3D, PCI |
| P-200, 64mb, Win95, FIC PT-2003 mobo | 12.4 | Matrox Millenium I, PCI |
COMMENTS: I would consider the 30 fps barely acceptable for serious net-play. All the other systems would only get acceptable performance at lower resolutions (400x300 or 320x240).
TEST 2: System Performance Comparison in 3Dfx OpenGL 3D Mode
This is what we're all really here for. This is a comparison of a variety of systems using either Voodoo, Voodoo2 or Voodoo3 video cards in a variety of resolutions.
All following tests were done with the viewsize set for 100 and the sound handler turned off. All computers are running version 3.14 (or later) of Quake 2. Vsync was disabled for best performance and to avoid an artificial framerate cap.
NOTE: The latest drivers for 3Dfx video cards don't allow you to disable VSync. There is no need to disable VSync in normal play, and doing so will give you horrible image tearing. However, with VSync disabled your framerate will never exceed your monitor's vertical refresh frequency in a timedemo test. To perform benchmark testing properly you should temporarily disable VSync for the test. If your driver supports it, disable VSync in the the advanced video properties tab. Otherwise, you can download the V2 or V3 Overclocker utility form my Files & Drivers Page which adds a new display properties tab with VSync and clock adjustments.
Systems running with a Voodoo 1 card are displayed with blue text.
Systems running with a Voodoo 2 card are displayed with red text.
Systems running with a Voodoo 3 card are displayed with green text.
| Computer System | 512x384 | 640x480 | 800x600 | 1024x 768 | 1280x 960 | 3D Card |
| Pentium III 550E (Overclocked to 733 MHz 133x5.5), 128Mb, Abit BE6 II mobo, Win98 | 163.9 | 125.3 | 87.3 | 3Dfx Voodoo3 3000 AGP (Overclocked to 186 MHz) | ||
| Pentium III 550E (Overclocked to 733 MHz 133x5.5), 128Mb, Abit BE6 II mobo, Win98 | 159.1 | 118.3 | 82.5 | 3Dfx Voodoo3 3000 AGP (Overclocked to 176 MHz) | ||
| Pentium III 550E (Overclocked to 733 MHz 133x5.5), 128Mb, Abit BE6 II mobo, Win98 | 155.2 | 111.6 | 77.7 | 3Dfx Voodoo3 3000 AGP | ||
| Pentium III 550E (Overclocked to 666 MHz 121x5.5), 128Mb, Abit BE6 II mobo, Win98 | 149.8 | 117.4 | 82.4 | 3Dfx Voodoo3 3000 AGP (Overclocked to 176 MHz) | ||
| Pentium III 550E (Overclocked to 666 MHz 121x5.5), 128Mb, Abit BE6 II mobo, Win98 | 146.6 | 110.9 | 77.7 | 3Dfx Voodoo3 3000 AGP | ||
| Pentium III 550E (Overclocked to 633 MHz 115x5.5), 128Mb, Abit BE6 II mobo, Win98 | 143.5 | 116.5 | 82.4 | 3Dfx Voodoo3 3000 AGP (Overclocked to 176 MHz) | ||
| Pentium III 550E (Overclocked to 633 MHz 115x5.5), 128Mb, Abit BE6 II mobo, Win98 | 141.2 | 110.5 | 77.6 | 3Dfx Voodoo3 3000 AGP | ||
| Pentium III 550E, 128Mb, Abit BE6 II mobo, Win98 | 127.1 | 111.6 | 81.7 | 3Dfx Voodoo3 3000 AGP (Overclocked to 176 MHz) | ||
| Pentium III 550E, 128Mb, Abit BE6 II mobo, Win98 | 126.2 | 107.5 | 77.4 | 3Dfx Voodoo3 3000 AGP | ||
| Pentium III 500 (Overclocked to 560), 128Mb, Abit BX6 mobo | 128.8 | 127.7 | 117.7 | 87.0 | na | Metabyte Wicked3D Voodoo2 12 Mb SLI |
| Pentium III 500, 128Mb, Abit BX6 mobo | 128.8 | 127.7 | 117.7 | 87.0 | na | Metabyte Wicked3D Voodoo2 12 Mb SLI |
| Pentium III 500, 128Mb, Asus P2B-LS mobo | 125.7 | 124.1 | 114.5 | 82.9 | 55.2 | 3Dfx Voodoo3 3000 AGP |
| Pentium II 400 MMX (Overclocked to 448 MHz), 128 Mb, Win95, Aopen AX6b mobo | 116.9 | 98.7 | 63.4 | na | na | Creative Voodoo2 8 Mb |
| PentiumII 400 MMX (Overclocked to 448 MHz- 112x4), 128mb, Win98, Soyo 6BA mobo | 109.3 | 107.5 | 95.7 | 65.3 | na | Creative Labs Voodoo2 12 Mb SLI |
| Celeron 300a (Overclocked to 450 Mhz 100x4.5), 128 Mb, Win98, Abit BH6 mobo | 104.5 | 103.8 | 98.5 | 74.6 | na | Creative Labs Voodoo2 12 Mb SLI (overclocked to 100 Mhz) |
| Pentium II 400 MMX, 128Mb, Win98, Soyo 6BA mobo | 104.6 | 103.3 | 92.6 | 65.4 | 3Dfx Voodoo3 2000 AGP | |
| Pentium II 400 MMX, 128mb, Win95, Dell Dimension XPS R400 | 102.9 | 102.8 | 100.3 | 70.9 | na | Creative Labs Voodoo2 12 Mb SLI |
| PentiumII 400 MMX, 128mb, Win98, Soyo 6BA mobo | 98.3 | 97.9 | 89.9 | 65.0 | na | Creative Labs Voodoo2 12 Mb SLI |
| Celeron 300a (Overclocked to 450: 100x4.5) MMX, 64mb, Win98, Asus P2B mobo | 98.3 | 90.0 | 58.9 | na | na | Quantum 3D Obsidian2 (Voodoo2) 12 Mb |
| Pentium II 400 MMX, 128mb, Win98 RC0, Dell Optiplex GX-1 | 94.1 | 94.0 | 91.0 | 74.2 | na | Creative Labs Voodoo2 12 Mb SLI |
| Celeron 400, 128 Mb, Abit BH6 mobo | 93.4 | 93.4 | 93.4 | 79.0 | 3Dfx Voodoo3 3000 AGP | |
| AMD K6-2 400 (Overclocked to 420 4x105MHz), 192 Mb 192 MB sdram | ---- | 87.0 | 86.7 | 80.0 | na | Creative Labs Voodoo2 12 Mb SLI |
| Pentium II 300A Celeron (Overclocked to 338 MHz 4.5x75), 64mb SDRAM, Win95, ABit LX6 mobo | 79.6 | 76.3 | 56.7 | na | na | Guillemot MaxiGamer Voodoo2 12 Mb |
| Pentium II 300 MMX (Overclocked to 338 MHz), 128mb SDRAM, Win98, Soyo 6BA mobo | 75.7 | 75.6 | 74.9 | 66.9 | na | Creative Labs Voodoo2 12 Mb SLI |
| Pentium II 300 MMX (Overclocked to 338 MHz), 128mb SDRAM, Win98, Soyo 6BA mobo | 75.9 | 73.9 | 56.8 | na | na | Creative Voodoo2 12 Mb |
| AMD K6-2 350 (Overclocked to 375 MHz 5x75),128mb SDRAM, Win98, Asus TX97XE mobo | 75.0 | 75.4 | 71.0 | 64.1 | na | Guillemot Maxigamer Voodoo2 12 mb SLI |
| Pentium II 300 MMX, 128mb SDRAM, Win98, Soyo 6BA mobo | 67.4 | 67.3 | 66.8 | 54.8 | na | Creative Labs Voodoo2 12 Mb SLI |
| Pentium II 300 MMX, 128mb SDRAM, Win98, Soyo 6BA mobo | 67.3 | 66.3 | 54.8 | na | na | Creative Voodoo2 12 Mb |
| AMD K6-2 266 (using 3DNow! Quake2 miniport), 128 Mb, Win98 | 57.4 | 65.3 | 57.5 | na | Diamond Monster 3D II Voodoo2 8 Mb | |
| Pentium II 233 MMX (Overclocked to 262), 64 Mb, Win98, Asus P2L97 mobo | 55.1 | 50.6 | 49.0 | na | Quantum Obsidian 2 PCI 12 Mb | |
| Pentium II 233 MMX, 64Mb | 50 | 39.6 | 35.9 | na | na | Monster Fusion Voodoo Banshee |
| Pentium II Celeron 300 MMX (Overclocked to 333 MHz), 128 Mb, Win95 | 48.0 | na | na | na | Canopus Pure3D Voodoo | |
| P-233 MMX, 128mb SDRAM, Win98, FIC PA-2007 mobo | 47.0 | 47.1 | 46.8 | na | na | Creative Voodoo2 8 Mb |
| Pentium II 266 MMX, 64mb, Win95 | 45.0 | na | na | Creative Voodoo2 12 Mb | ||
| Pentium II 300 MMX, 128mb, Win95 | 42.4 | na | na | na | Monster 3D Voodoo | |
| Pentium II 300 MMX, 96mb, Win95 (Brian Hook's test system) | 39.3 | na | na | na | Monster 3D Voodoo | |
| P-233 MMX, 32mb, Win95 | 38.1 | na | na | na | Monster 3D Voodoo | |
| Pentium II 300 MMX, 64mb, NT4.0 | 36.9 | na | na | na | Monster 3D Voodoo | |
| P-200, 64mb, Win95, FIC PA-2007 mobo | 35.7 | na | na | Creative Voodoo2 8 Mb | ||
| P-200, 40mb, Win95, FIC PA-2007 mobo | 34.2 | na | na | na | Monster 3D Voodoo | |
| P-200 MMX, 32mb, Win95 | 32.8 | na | na | na | Righteous 3D Voodoo | |
| P-166, 40mb, Win95, IC PA-2007 mobo | 30.1 | na | na | na | Monster 3D Voodoo | |
| P-200, 64mb, Win95, FIC PT-2003 mobo | 29.1 | 28.9 | 28.8 | na | na | Creative Voodoo2 12 Mb |
| K6-233 MMX, 64mb, Win95 | 27.6 | na | na | na | Monster 3D Voodoo | |
| P-166, 64mb, Win95, FIC PT-2003 mobo | 26.2 | 25.8 | 25.5 | na | na | Creative Voodoo2 12 Mb |
| P-133, 64mb, Win95, FIC PA-2007 mobo | 25.9 | na | na | Creative Voodoo2 8 Mb | ||
| P-133, 48mb, Win95, FIC PA-2007 mobo | 25.9 | na | na | na | Monster 3D Voodoo | |
| P-133, 64mb, Win95, FIC PT-2003 mobo | 22.7 | 22.9 | 23.0 | na | na | Creative Voodoo2 12 Mb |
| P-120, 64mb, Win95, FIC PT-2003 mobo | 20.3 | 20.5 | 20.6 | na | na | Creative Voodoo2 12 Mb |
| P-90, 64mb, Win95, FIC PT-2003 mobo | 18.0 | 12.6 | 13.0 | na | na | Creative Voodoo2 12 Mb |
| Cyrix PR-200+, 32mb, Win95 | 15.3 | na | na | na | Monster 3D Voodoo |
Quake 2 Max Fps Mod
Any of these systems will give you okay performance in solo play (although it's going to bog down sometimes on anything less than a P-133), but realistically you need at least 30 fps to enjoy netplay. Competative netplay requires about 40 fps. I would consider a minimal system for competative netplay to be a P-233 with a Voodoo2 or Voodoo3, and I'd disable dynamic lighting (set gl_dynamic 0) to keep the framerate near 40 fps.
You should also look carefully at the scores for the P2-400 with the single Voodoo2 card as opposed to the scores for the P2-400 with dual cards running in SLI mode. The single card system slightly outperformed the dual card system at 512x384 because it's CPU is over-clocked to 448 MHz. However, it lags far behind the dual card system at 800x600 resolution. This clearly demonstrates the improved performance you get when using dual-card SLI on a high performance system - the framerates on the dual card system remain practically the the same at all resolutions (although there's nothing shabby about the 64 fps the single card system got at 800x600, I might point out).
Many of you have expressed surprise (or dismay, as the case may be) at the showing of the Cyrix PR-200+ system. However, this performance is not surprising considering the fact that the Cyrix CPU has a very weak floating-point unit compared to Intel processors and even compared to the K6. However, at 15.3 the Cyrix is at least (barely) playable in solo mode, although the framerate is not acceptable for serious deathmatch play. And before you ask, I wouldn't expect the score to be any higher if you put a Voodoo2 in the Cyrix machine - you can't make a cow run like a gazelle..
VOODOO 2: You might be surprised that Voodoo2 cards performed so poorly on low-end systems, but this is to be expected. The Voodoo 2 only really shines when it's running on a high-end Pentium II or better system. However, it is worth noting that even on a low-end system, the Voodoo 2 produced excellent framerates at all resolutions on up to 800x600. Also, while it's not reflected in these scores, the Voodoo 2 plays much smoother on low-end systems than the Voodoo cards do. This is mostly thanks to the Voodoo 2's dual texture units and larger texture memory, which results in a reduction in frames dropped due to texture thrashing. That's worth the price of a Voodoo2 alone - it sucks getting fragged all the time because your system slows to a crawl when there's a lot of Hyberblaster fire going on. It's worth noting here that on a Voodoo2 you probably won't be playing Quake 2 at 512x384, as the Voodoo 2 is capable of maintaining a high frame rate while running at 640x480 and 800x600 (see Test 2 below for the results of Voodoo2 tests on low-end systems at various resolutions) - and oh boy does it look pretty at those high resolutions, childrens..
Quake 2 Max Fps Unlocker
VOODOO 3: Notice that the Voodoo3 essentially performs on par with Voodoo2 SLI. However, image quality is much better on the V3.Overclocking the V3 generally didn't make much of a difference until the Pentium 3 came along - especially the Coppermine CPUs. Check out the overclocked V3 results for the P3-550E. The Coppermine CPU itself also overclocks easily (too easily!), and most people are doing just that. The P3-550E results posted above are from my own personal system. This system easily overclocked to a fully stable 666 MHz using PC100 SDRAM. It ran stable enough at 733 MHz to run benchmarks, but it would occasionally lockup. It's likely that with PC133 SDRAM it would run fine at 733. I've seen this processor get as high as 800 MHz on some systems.
Compiled by Robert Osorio, 'Flying Penguin (Mercenary)'
Last updated on 3/22/00
