PDA

View Full Version : New X3dfx Community Voodoo 3/4/5 Drivers fow Win2k!


Mwarhead
August 26th, 2001, 17:40
Hi,
I'm the one that writes the win2k X3dfx Community Drivers. I just wanted to inform you that new drivers were released yesterday.

New Features Include:
1. Seperated infs
2. Ability to overclock your graphics cpu and memory in 3dfx tools. GLOBAL
3. Zculling OGL/GLIDE
4. SLI global
5. A couple refresh optimizations Global
6. Enviroment Anti Aliasing d3d/ogl
7. FORCE MMX -This forces games to use mmx instructions improving speed. (Can cause some graphic glitches with some games.) OGL/GLIDE
8. Voodoo Rush Emulation OGL/GLIDE
9. The ability to force a refresh rate in glide
10. Water Mark Splash Screen GLIDE
11. Guardband Glipping d3d
12. 3d Studio Plugin d3d
13. Frame Buffer Swaping d3d
14. Iteration Banding d3d
15. L-Delay d3d
16. Pixel Blending d3d
17. STacceleration d3d
18. Trilinear Texture Filtering d3d
19. Triple Buffering d3d
20. Guardband clipping Glide
21. Bump Map Size OGL/GLIDE
22. Enviroment Bump Mapping OGL/GLIDE
23. Invisible Walls OGL/GLIDE
24. Pixel Clock Rendering OGL/GLIDE
25. Zcull Far OGL/GLIDE
26. Zcull Near OGL GLIDE

and that was just for the voodoo 3!

The Voodoo 5 driver contains all that plus
27. FSAA (FIXED) d3d/ogl/glide
28. FSAA JITTER d3d/ogl/glide
29. AADEMOKEY d3d/ogl/glide

Get them at www.herculesgamers.com

-Mwarhead

Ak37
August 27th, 2001, 12:49
Got to try this...Will it show wireframe view for OpenGL Games ??

chp
August 27th, 2001, 16:34
Thank you Mwarhead,

That's exactly what every 3Dfx owner need.
But... Not yet drivers for Win2K... Hope you'll work on that.

Phuzzi
August 28th, 2001, 20:03
Are there any explanations of what each new setting actually changes? Not all of them are self-explanatory, and it'd be very useful to actually know what they do.

Phuzzi
August 28th, 2001, 22:49
I was looking through the board at the x3dfx community site for some answers to my previous post and stumbled across this.

http://pub43.ezboard.com/fx3dfxfrm1.showMessage?topicID=2606.topic

Now, for someone who ports drivers to win2k, how could you possibly so wrong about something that is so heavily explained on pretty much any hardware site?