1. Hiatus
2. RIP, Satoru Iwata
3. Let there be Robot Battles
4. Regarding pixel art!
5. 16-bit Star Wars
6. Goodbye, Spock.
7. James Randi Retires
8. More Star Wars on GOG
9. gives you DOS Games
10. Ralph Baer, RIP.
1. Quickie: Impressions June 2014
2. Quickie: Penny Arcade Episode 3
3. Quickie: The Amazing Spider-Man
4. Quickie: Transformers: Fall of Cybertron
5. Quickie: Prototype 2
6. Quickie: Microsoft Kinect
7. Quickie: X-Men Destiny
8. Spider-Man: Edge of Time
9. Quickie: Transformers Dark of the Moon
10. Quickie: Borderlands GOTY
1. Musings 45: Penny Arcade and The Gripping Hand
2. Movie Review: Pacific Rim
3. Movie Review: Wreck-It Ralph
4. Glide Wrapper Repository
5. Movie Review: Winnie The Pooh
6. Musings 44: PC Gaming? Maybe it's on Life Support
7. Video Games Live 2009
8. Movie Review: District 9
9. Musings: Stardock, DRM, and Gamers' Rights
10. Musings: How DRM Hurts PC Gaming
Main Menu

X-bit labs
The Tech Zone
Twin Galaxies


 Log in Problems?
 New User? Sign Up!

Reviewed: Annihilator Pro
Author: Michael Ahlf       Date: June 25th 2000
Page: 6

Quake 3 is pretty much the default test for a card's OpenGL performance nowadays; this test was performed with the geometry and texture details all the way up, on Demo 001 using the Timedemo feature. As can be seen below, at lower resolutions the CPU appears to be the bottleneck as there is little to no difference in framerate. At higher resolutions, the memory of the Gladiac finally catches up and slows it down a bit. The largest performance hits come in with FSAA turned on and full (FSAAQuality value of 2 in the registry). Note the immense dropoff in 32-bit color quality at high resolutions with the FSAA turned on; the fact that the FSAA was turned off by the card at 1280x1024x32 for lack of memory is a good indication of where the capabilities of this card lie and where it falls short.

3DMark 2000 was my Direct3D choice for benchmarking; this is pretty much the standard in 3D performance. There are a few funny spikes in the performance, due to the card itself not giving the FSAA result that was requested (NVidia's FSAA slider is actually a request bar; if the card doesn't have the memory to handle the FSAA method requested at the current resolution, it goes down in FSAA till it does).

As can be seen above, at 1280x1024 no FSAA level would turn on; in fact, reading the results it seems that full FSAA wouldn't enable even at 800x600x32-bit color. The only results which can be trusted are the no-FSAA 3Dmarks, which thankfully are pretty high up there. The unfortunate side is that the FSAA quickly takes a heavy toll on the board's performance thanks to its memory bandwidth limitations; a 64-MB card would probably hang in there a lot better. What the graph above really shows, unfortunately, is that the FSAA levels that are more intensive won't even enable at a decently high resolution (above 800x600) in 32-bit color.

Go To: [ Previous | Next | Home ] - Overclocking
Jump To: [ 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 ]

Added:  Sunday, June 25, 2000
Reviewer:  Michael Ahlf
Page: 6/8

Previous Previous (5/8)  1 2 3 4 5 6 7 8   Next (7/8) Next

[ Back to reviews index ]

Home :: Share Your Story
Site contents copyright Glide Underground.
Want to syndicate our news? Hook in to our RSS Feed.