#BOCHS WINDOWS 98 3DFX 32 BIT#

The Voodoo3's 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 render. However, the controversy came about over what happened next. To save framebuffer space, the Voodoo3's rendering output was then dithered to 16 bit, which is fundamentally entirely different to (and much higher quality than) running the whole thing in 16 bit.

#BOCHS WINDOWS 98 3DFX 32 BIT#

This was in fact quite complex, as Voodoo3 operated to full 32 bit precision (8 bits per channel, 16.7M colors) 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. Much was made of Voodoo3 (as Avenger was christened) and its 16-bit only rendering.

Avenger was thus merely a Voodoo2 with an integrated 128 bit 2D video accelerator and twice the clock speed.

Avenger was no more than the Banshee core with a second texture mapping unit (TMU) added - the same TMU which Banshee lost compared to Voodoo2. Due to quite staggering mismanagement by 3dfx, this caused the next-generation 'Rampage' project to suffer delays which would prove to be fatal to the entire company.Īvenger was pushed to the forefront as it offered a quicker time to market than the already delayed Rampage. The 'Avenger' graphics core was originally conceived immediately after Banshee.

Bochs windows 98 3dfx