RIVA TNT
| |
Release date | 1998 |
---|---|
Codename | NV4 |
Cards | |
Entry-level | Vanta |
High-end | TNT |
Rendering support | |
Direct3D | Direct3D 6.0 |
The RIVA TNT, codenamed NV4, is a 2D, video, and 3D graphics accelerator chip for PCs that was manufactured by Nvidia. It was released in mid-1998 and cemented Nvidia's reputation as a worthy rival within the developing consumer 3D graphics adapter industry. The first RIVA TNT based card released on June 15, 1998 by STB Systems: Velocity 4400. RIVA is an acronym for Real-time Interactive Video and Animation accelerator.[1] The "TNT" suffix refers to the chip's ability to work on two texels at once (TwiN Texel).[2]
Overview
The TNT was designed as a follow up to the RIVA 128 and a response to 3Dfx's introduction of the Voodoo2. It added a second pixel pipeline, practically doubling rendering speed, and used considerably faster memory. Unlike the Voodoo2 (but like the slower Matrox G200) it also added support for a 32-bit (truecolor) pixel format, 24-bit Z-buffer in 3D mode, an 8-bit stencil buffer and support for 1024×1024 pixels textures. Improved texture filtering techniques, partially assisted by newly added trilinear filtering, dramatically improved image quality compared to the TNT's predecessor. It also added support for up to 16 MiB of SDR SDRAM. TNT was a single chip solution.
The TNT shipped later than originally planned, ran quite hot, and was clocked lower than Nvidia had planned (90 MHz instead of 110 MHz). Originally planned specifications should have placed the card ahead of Voodoo2 in theoretical performance for Direct3D applications, but at 90 MHz it didn't match the Voodoo2. At the time, most games supported 3dfx's proprietary Glide API which gave the Voodoo2 a large advantage in speed and image quality, and some games only used the Glide API for 3D acceleration, leaving TNT users no better off than people who didn't have a 3D accelerator. Even in "OpenGL only" comparisons such as the case in Quake 2, The Voodoo2 had the upper hand as a custom "MiniGL" driver was made specifically for 3dfx cards to run the game (and most other OpenGL games at the time). The 3dfx MiniGL driver was not a fully featured OpenGL driver, but a wrapper that mapped certain OpenGL functions to their equivalents in Glide, and was able to attain a speed advantage because of that. Later on when fully featured OpenGL drivers were made for the 3dfx line of cards, it was noticed that it was much slower when compared to its cut down MiniGL brother. The TNT had 32-bit color support while the Voodoo2 only supported 16-bit (although internally dithered down from 24-bit color, beating the TNT in 16bit quality). Voodoo 2 cards also gained an even larger speed advantage over the TNT because of the ability to link two Voodoo2 cards together in an "SLI" setup.
TNT did not match the sales of the incredibly popular Voodoo 2. 3Dfx's customer mind share was at its peak during this time and Nvidia was still a somewhat new player. Again, like with the RIVA 128, the lack of Glide API support hindered Nvidia's opportunities for market share growth. Glide was still considered the best 3D gaming API available by both gamers and developers. However, TNT gained Nvidia much attention and paved the way for the refreshed version called the RIVA TNT2. After all, unlike the rest of the competition, Nvidia had come close to the Voodoo2 in performance in some games, and beaten it in 32bit image quality.
In what would become standard industry practice on a massive scale in later years, Nvidia released a budget version of TNT called Vanta. This board used the same TNT chip but lowered its clock speed and halved both memory data bus width (to 64-bit) and memory size (to 16 MiB). By doing this, Nvidia was able to still sell somewhat defective TNT chips that couldn't reach the TNT's specified clock speeds, and cut board costs significantly by using a narrower bus and less RAM. The board proved popular with OEM computer builders because of its capable feature-set and low price. Vanta also was implemented as integrated graphics on some motherboards.
TNT itself was used on several popular cards, such as the Diamond Viper V550 and STB Velocity 4400, both of which managed OEM wins with the likes of Dell and Gateway, among others.
Drivers
Nvidia's driver development with TNT was the beginning of their notably aggressive efforts to maintain the best set of drivers possible. TNT received the first branded driver within the industry, called Detonator.
These drivers were a huge success. While the TNT had always performed well on Intel based systems, it previously lagged behind in terms of performance on then current AMD based systems. At the time, Quake2 was the benchmark for performance and the 3dfx-made Voodoo2 enjoyed a large performance difference over the TNT because it had 3DNow! optimizations that negated the performance penalty of the weak, unpipelined FPU on then current AMD processors. The Detonator drivers included 3DNow! optimizations and the TNT's Quake2 performance jumped 30%. In fact, all OpenGL and DirectX applications benefitted from such optimizations. This made the TNT a much more attractive 3D accelerator for AMD owners than previously.
The Detonator drivers also fixed compatibility issues with motherboards of the time, and improved overall software compatibility.[3]
Competing chipsets
- 3dfx Voodoo2
- 3dfx Voodoo Banshee
- Matrox G200
- ATI Rage Pro
- S3 Savage
See also
- Comparison of Nvidia graphics processing units
References
- ↑ "RIVA 128 Brochure". Nvidia. Archived from the original on July 6, 1997. Retrieved October 9, 2007.
- ↑ "TNT2". Nvidia. Retrieved October 12, 2007.
- ↑ "Nvidia RIVA TNT Detonator Drivers". ActiveWindows. 1999. Retrieved June 15, 2008.
External links
Wikimedia Commons has media related to Riva TNT series. |
- "Nvidia and ABIT Announce Integrated Motherboard Graphic Solution" (Press release). Nvidia. June 1, 1999.
- "Nvidia Broadens Market Reach with Vanta 3D Processor" (Press release). Nvidia. March 22, 1999.
- Nvidia Riva TNT last supported Forceware Unified Display Driver (version 44.03)
|