RIVA TNT

Overview

The TNT was designed as a follow-up to the RIVA 128 and as a response to 3Dfx's introduction of the Voodoo2. It added a second pixel pipeline, practically doubling rendering speed, and used considerably faster memory. Improved mipmapping and texture filtering techniques, including newly added support for trilinear filtering, dramatically improved quality compared to the TNT's predecessor. TNT also added support for up to 16 MiB of SDRAM. Like RIVA 128, RIVA TNT is a single chip solution.

The TNT shipped later than originally planned, ran quite hot, and was clocked lower than Nvidia had planned at 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 did not quite 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). Voodoo2 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 Voodoo2. 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 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 TNT chips that couldn't reach the TNT's specified clock speeds, a practice known as binning, 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 benefited 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.

The TNT was the last Nvidia graphics accelerator to have support for Windows 3.1x.

Chipset table

Competing chipsets

• 3dfx Voodoo2
• 3dfx Voodoo Banshee
• Matrox G200
• ATI Rage Pro
• S3 Savage

References

References

1. "Velocity4400 Press Release".
2. "RIVA 128 Brochure". Nvidia.
3. "TNT2". Nvidia.
4. "NVIDIA Riva TNT Specs {{char".
5. Turner, Daniel Drew. (May 16, 2002). "The prince of polygons". Salon.
6. Unlike the Voodoo2 (but like the slower [[Matrox G200]]) it also added support for a 32-bit ([[24-bit color. truecolor]]) pixel format, 24-bit [[Z-buffering
7. [https://archive.today/20130205005908/http://www.tomshardware.com/reviews/3d-chips,83.html Tom's Hardware : New 3D Chips - Banshee, G200, RIVA TNT And Savage3D]- 1:01 PM - 18 August 1998 by Thomas Pabst / Source: Tom's Hardware US
8. [http://www.ixbt.com/video/matroxg200.html iXBT: Matrox G200 - First PreView]
9. Anand Lal Shimpi. (September 6, 1998). "Canopus SPECTRA 2500 Riva TNT".
10. AnandTech]
11. [https://www.pcgamesn.com/pc-retro-tech/3dfx-voodoo-graphics 3dfx Voodoo - the graphics card that revolutionized PC gaming]. PCGamesN
12. Pabst, Thomas. [https://www.tomshardware.com/reviews/nvidia-rocks-boat-tnt2,102-4.html NVIDIA rocks the Boat with TNT2], Tom's Hardware, March 12, 1999.
13. Hwang, Kenn. [http://www.firingsquad.com/hardware/pentium3/page10.asp Exclusive Pentium III Review], Firing Squad, January 13, 1999.
14. Ajami, Amer. (1999-12-06). "3dfx Open Sources Glide". [[GameSpot]].
15. (1999). "Nvidia RIVA TNT Detonator Drivers". ActiveWindows.
16. "3D accelerator database".