The 3D Accelerator Wars, 1998–2005
Between 1998 and 2005, consumer PC graphics moved from mostly fixed-function accelerators and vendor-specific features toward programmable shaders, richer filtering, larger memories, and a new expansion bus. 3DChipset’s publishing life sat almost exactly across that transition.
A crowded accelerator field
3dfx Voodoo hardware had made add-in 3D acceleration familiar, while PowerVR, Rendition, Matrox, S3, ATi, NVIDIA, and 3Dlabs pursued different designs and markets. Games might expose Direct3D, OpenGL, or a vendor-specific path. The 3dfx history provides broader context for Voodoo and Glide.
GeForce and hardware T&L
3DChipset opened with a vendor-wide driver rail and daily news about TNT2, Rage, Voodoo3, G400, Savage4, and other boards. NVIDIA introduced the GeForce 256 in 1999 and made hardware transform and lighting a defining part of its message. The GeForce overview traces that family from the RIVA TNT2 successor onward.
GeForce2, Radeon, and Voodoo5
The GeForce2 line divided into value, mainstream, and Ultra variants. ATi launched the Radeon name and combined 3D performance with video and display features. 3dfx pushed full-scene antialiasing in Voodoo5 discussions. Driver coverage became as important as the board announcement because Windows 2000, Windows Me, Direct3D, and OpenGL support varied.
DirectX 8 features reach enthusiasts
GeForce3 and Radeon 8500 made programmable pixel and vertex work central to reviews. Kyro boards kept tile-based rendering in the consumer conversation. 3DChipset merged with Gamers Ammo, expanded its driver records, and tracked rapid Detonator and Radeon revisions. The Radeon overview places the 7000, 8000, and 9000 families in the early brand sequence.
GeForce4, Parhelia, and Radeon 9700
GeForce4 Ti refined the GeForce3 direction, while the MX branch served a different value segment. Matrox Parhelia emphasized image quality and multi-display use. The Radeon 9700 arrived as DirectX 9 became the next dividing line. 3DChipset’s March and June pages show reviewers balancing frame rate with filtering, antialiasing, outputs, cooling, and board cost.
Shader precision and benchmark scrutiny
GeForce FX and Radeon 9800 coverage focused on programmable-shader behavior, heat, power, cooling, antialiasing, anisotropic filtering, and prerelease drivers. Version 51.75 became part of a larger debate about how benchmarks should handle driver optimizations. DirectX 9 and shader model 2 reshaped what “feature support” meant.
New architectures and PCI Express
GeForce6 brought shader model 3 into NVIDIA’s consumer line, while Radeon X-series cards extended ATi’s DirectX 9 family. PCI Express began replacing AGP in new systems. Driver forums continued to track Catalyst and ForceWare revisions because software maturity remained central to real-game behavior.
The field consolidates
GeForce7 and Radeon X1000-era hardware pushed the established rivalry forward as AGP receded. Other desktop accelerator names became less central, although PowerVR continued along a different path in licensed and lower-power designs. 3DChipset’s later review URLs also show a publication widening toward memory, cooling, power, and storage.
The lasting shift
The era changed the unit of comparison. A graphics card was no longer only a fixed collection of pixel pipelines and memory clocks; it was a programmable platform whose output depended on APIs, drivers, application code, and quality settings. The glossary explains those layers, and the reviews index shows how an enthusiast publication tried to examine them together.
Reading across generations
Family names alone can hide overlapping lifetimes. Budget versions of an older design often remained on shelves after a new flagship appeared, and driver support tied several generations together. A fair comparison therefore needs the date, market tier, API features, memory configuration, and software environment as well as the chip name.
The sequence also shows a shift in review language. Early coverage asked whether acceleration worked and how much faster a game became. Later coverage increasingly examined programmable effects, antialiasing, texture filtering, multi-display use, power, cooling, and driver consistency. Those changing questions are as important to the history as any single benchmark result.