View source for Engineering:Voodoo3

{{short description|Series of gaming video cards}}
[[Image:Voodoo3boxart.jpg|300px|thumb|3dfx Voodoo3 box art]]
'''Voodoo3''' was a series of computer gaming video cards manufactured and designed by [[Company:3dfx|3dfx Interactive]]. It was the successor to the company's high-end [[Engineering:Voodoo2|Voodoo2]] line and was based heavily upon the older Voodoo Banshee product. Voodoo3 was announced at COMDEX '98 and arrived on store shelves in early 1999.<ref>[http://www.prnewswire.com/cgi-bin/stories.pl?ACCT=104&STORY=/www/story/11-16-1998/0000803667&EDATE= 3Dfx Interactive Blasts COMDEX with Voodoo3 Debut And Four Voodoo Banshee PC-OEM Announcements], 3dfx Press Release, November 16, 1998.</ref> The Voodoo3 line was the first product manufactured by the combined [[Company:STB Systems|STB Systems]] and 3dfx.<ref>Brown, Peter. [http://www.findarticles.com/p/articles/mi_m0EKF/is_2259_45/ai_54249305 3Dfx Takes Chance on Boards - Voodoo3 2000, Voodoo3 3000, and Voodoo3 3500 - Product Announcement], Electronic News, March 1, 1999.</ref>

==History==
The 'Avenger' graphics core was originally conceived immediately after Banshee. Due to  mis-management by 3dfx, this caused the next-generation 'Rampage' project to suffer delays which would prove to be fatal to the entire company.

Avenger was pushed to the forefront as it offered a quicker time to market than the already delayed Rampage. Avenger was no more than the Banshee core with a second [[Texture mapping unit|texture mapping unit]] (TMU) added - the same TMU which Banshee lost compared to [[Engineering:Voodoo2|Voodoo2]]. Avenger was thus merely a Voodoo2 with an integrated 128-bit 2D video accelerator and twice the clock speed.

==Architecture and performance==
[[Image:Voodoo3-2000AGP.jpg|thumb|3dfx Voodoo3 2000 AGP]]
[[Image:Voodoo3-2000PCI.jpg|thumb|3dfx Voodoo3 2000 PCI]]
[[Image:Voodoo3-3000AGP.jpg|thumb|3dfx Voodoo3 3000 AGP]]

Much was made of Voodoo3 (christened 'Avenger') and its 16-bit color rendering limitation. This was in fact quite complex, as Voodoo3 operated to full [[24-bit color|32-bit]] precision (8 bits per channel, 16.7M colours) in its texture mappers and pixel pipeline as opposed to previous products from 3dfx and other vendors, which had only worked in 16-bit precision.

To save framebuffer space, the Voodoo3's rendering output was dithered to 16 bit. This offered better quality than running in pure 16-bit mode.  However, a controversy arose over what happened next.

The Voodoo3's [[Engineering:RAMDAC|RAMDAC]], which took the rendered frame from the framebuffer and generated the display image, performed a 2x2 box or 4x1 line filter on the dithered image to almost reconstruct the original [[24-bit color|24-bit color]] render. 3dfx claimed this to be '22-bit' equivalent quality.<ref>Beets, Kristof. [http://www.beyond3d.com/content/articles/59/ 3dfx '22Bit Colour' Explored], Beyond3D, May 7, 1999.</ref>  As such, Voodoo3's [[Framebuffer|framebuffer]] was not representative of the final output, and therefore, screenshots did not accurately portray Voodoo3's display quality which was actually much closer to the 24-bit outputs of NVIDIA's [[Engineering:RIVA TNT2|RIVA TNT2]] and ATI's [[Engineering:ATI Rage|Rage 128]].

The internal organisation of Avenger was not complex. Pre-setup notably featured a guardband clipper (eventually part of hardware transformation and lighting) but the pixel pipeline was a conventional single-issue, dual-texture design almost identical to that featured on Voodoo2, but capable of working on 32-bit image data as opposed to Voodoo2's pure 16-bit output. Avenger's other remarkable features included the 128-bit [[Software:Graphics Device Interface|GDI accelerator]] debuted in Banshee. This 2D engine led the Voodoo3 to be considered one of the more high-performance video cards of its generation.<ref>Fastsite. [http://www.xbitlabs.com/articles/video/display/matrox-g400.html Matrox Millennium G400 16MB Review] {{Webarchive|url=https://web.archive.org/web/20060721225400/http://www.xbitlabs.com/articles/video/display/matrox-g400.html |date=2006-07-21 }}, X-bit Labs, July 2, 1999.</ref><ref name=AnandVoodoo3>Lal Shimpi, Anand. [http://www.anandtech.com/showdoc.aspx?i=923 3dfx Voodoo3], Anandtech, April 3, 1999.</ref>

The Voodoo3 2000, 3000 and 3500 differed mainly in clock frequencies (memory and core were synchronous). The clock rates were 143 [[Hertz|MHz]], 166&nbsp;MHz and 183&nbsp;MHz respectively. While this gave the 3000 and 3500 a notable theoretical advantage in multi-textured fillrate over its main rival, the TNT2 clocked at 125&nbsp;MHz, the TNT2 had nearly twice the single-textured fillrate of the Voodoo3. In addition, the Voodoo3 consisted of one multi-texturing pipeline, the TNT series consisted of twin single texturing pipelines.<ref>[http://www.beyond3d.com/misc/chipcomp/ Beyond3D 3D Chip Tables] {{webarchive|url=https://web.archive.org/web/20060118025659/http://www.beyond3d.com/misc/chipcomp/ |date=2006-01-18 }}, Beyond3D.Com, accessed August 30, 2006.</ref> As a result, Voodoo3 was disadvantaged in games not using multiple texturing. The 2000 and 3000 boards generally differed in their support for TV output; the 3500 boards also carried a TV tuner and provided a wide range of video inputs and outputs.

At the time modern multi-texturing games such as ''[[Software:Quake III Arena|Quake III Arena]]'' and ''[[Software:Unreal Tournament|Unreal Tournament]]'' were considered Voodoo3's performance territory, as Voodoo3's primary competition upon release was the dated RIVA TNT.<ref name=AnandVoodoo3 /> NVIDIA's RIVA TNT2 arrived shortly thereafter and the two traded places frequently in benchmark results.<ref>Lal Shimpi, Anand. [http://www.anandtech.com/showdoc.aspx?i=940 NVIDIA Riva TNT2], Anandtech, April 27, 1999.</ref>

Although the Voodoo3 was a replacement for the Voodoo2, it was often beaten by Voodoo2 SLI cards in direct comparisons.<ref>Pabst, Thomas.[http://www.tomshardware.com/reviews/preview-3dfx-voodoo3,100-7.html], Tom's Hardware, February 22, 1999.</ref>

Voodoo3 remained performance competitive throughout its life, eventually being comprehensively outclassed by NVIDIA's [[Engineering:GeForce 256|GeForce 256]] and ATI's Radeon. 3dfx created the ill-fated [[Engineering:Voodoo 5|Voodoo 5]] to counter.

==3dfx Velocity==
3dfx released a line of business / value-oriented cards based on the Voodoo3 Avenger chipset. With the purchase of STB Systems, 3dfx had acquired several popular brand names. The Velocity brand had appealed to OEM system builders for years, with boards such as the [[Company:S3 Graphics|S3 Graphics]] [[Engineering:S3 ViRGE|ViRGE VX]]-based ''STB Velocity 3D'' and NVIDIA [[Engineering:RIVA 128|RIVA 128]]-based ''Velocity 128'' being used in many OEM systems from companies such as [[Company:Gateway, Inc.|Gateway]]. The 3dfx Velocity boards came with only 8 MiB of RAM, compared to 16 MiB on a regular Voodoo3. In addition, one of the texture management units came disabled as well, making the board more like a Banshee. Enthusiasts discovered that it was possible to enable the disabled TMU with a simple registry alteration.<ref>{{cite web|url=https://www.anandtech.com/show/401/3|title=Exploring the Velocity|access-date=2018-07-26}}</ref> The board's clock speed was set at 143&nbsp;MHz, exactly the same as a Voodoo3 2000.<ref>Andrawes, Mike. [http://www.anandtech.com/showdoc.aspx?i=1076 3dfx Velocity 100], Anandtech, October 29, 1999.</ref>

==Drivers==

The last set of drivers officially released for the Voodoo 3 on Win9x was version 1.07.00. For Win2000 the latest version is 1.03.00. Dual monitor support with V1.1.3b for [[Software:Mac OS 8|Mac OS 8]] and 9.<ref>[http://www.falconfly.de/voodoo3.htm Voodoo3 Drivers<!-- Bot generated title -->]</ref> After 3dfx shut its doors 3rd party drivers for Windows 98/98SE, Windows 2000 and XP were developed by loyal 3dfx customers .{{citation needed|date=November 2012}}

== Models ==
{| class="wikitable" style="font-size:85%; text-align:center;"
|-
! rowspan="2" |Model
! rowspan="2" |Launch
! rowspan="2" |Fab (nm)
! rowspan="2" |Bus interface
! rowspan="2" |Core clock ([[Hertz|MHz]])
! rowspan="2" |Memory clock (MHz)
! rowspan="2" |Core config<sup>1</sup>
! colspan="3" |[[Fillrate]]
! colspan="4" |Memory
! colspan="2" |[[Application programming interface|API]] compliance
|-
!MOperations/s
!MPixels/s
!MTexels/s
!Size ([[Mebibyte|MiB]])
!Bandwidth ([[Gigabyte|GB]]/s)
!Bus type
!Bus width ([[Bit|bit]])
!Direct3D
![[Software:OpenGL|OpenGL]]
|-
! class="table-rh" {{rh}} |3Dfx Velocity 100
|July 26, 1999
|250
|AGP 2×
|143
|143
|1:0:1:1<sup>1</sup>/1:0:2:1
|143
|143
|143<sup>1</sup>/286
|8
|2.288
|SDR
|128
|6.0
|1.1
|-
! class="table-rh" {{rh}} |3Dfx Velocity 200
|July 26, 1999
|250
|AGP 2×
|143
|143
|1:0:1:1<sup>1</sup>/1:0:2:1
|143
|143
|143<sup>1</sup>/286
|12
|2.288
|SDR
|128
|6.0
|1.1
|-
! class="table-rh" {{rh}} |3Dfx Voodoo 3 1000
|March 1999
|250
|AGP 2×, PCI
|125
|125
|1:0:2:1
|125
|125
|250
|8, 16
|2
|SDR
|128
|6.0
|1.1
|-
! class="table-rh" {{rh}} |3Dfx Voodoo 3 2000
|April 7, 1999
|250
|AGP 2×, PCI
|143
|143
|1:0:2:1
|143
|143
|286
|16
|2.288
|SDR
|128
|6.0
|1.1
|-
! class="table-rh" {{rh}} |3Dfx Voodoo 3 3000
|April 7, 1999
|250
|AGP 2×, PCI
|166
|166
|1:0:2:1
|166
|166
|333
|16
|2.656
|SDR
|128
|6.0
|1.1
|-
! class="table-rh" {{rh}} |3Dfx Voodoo 3 3500 TV
|June 1999
|250
|AGP 2×
|183
|183
|1:0:2:1
|183
|183
|366
|16
|2.928
|SDR
|128
|6.0
|1.1
|}
1 - 3Dfx Velocity cards only have 1 working TMU enabled on OpenGL and Glide games, but both TMUs working under DirectX games<ref>{{Cite news|url=http://www.vgamuseum.info/index.php/cards/item/9-3dfx-velocity-100|title=VGA Legacy MKIII - 3Dfx Velocity 100|last=Vlask|access-date=2017-05-25|language=en-gb}}</ref>

==Competing chipsets==
*[[Engineering:RIVA TNT2|NVIDIA RIVA TNT2]]
*[[Engineering:ATI Rage|ATI Rage 128]]
*[[Engineering:Matrox G400|Matrox G400]]
*[[Engineering:S3 Savage|S3 Graphics Savage4]]

==References==
{{reflist|2}}

{{3dfx Graphics Processors}}
{{Graphics Processing Unit}}

[[Category:Video cards]]

{{Sourceattribution|Voodoo3|1}}