I’m not really sure about this, but I think it’s a limitation (not a problem, a limitation) in the hardware itself. In other words, you are more than stuck
This was a big limitation in the Voodoo and Voodoo 2 cards. I don’t know if every card of that generation had it but these did for sure. There was a wierd workaround that someone did where he tricked the card into thinking it took over the screen but it was too confusing, hampered performance and the next generation cards solved it anyway so it never really went mainstream. I’m sorry but I can not remember the name? Anyone?
I dont know the name, but i know that the first Linux mesa driver had this hack. They were copying the frame buffer from the V2 to the first card’s memory and displayed this stuff in a window. I’ve tried it out with V1, but on my system (that was P200) I did not get more than 15 fps (bandwidth problem).
Besides, 3dfx’s opengl drivers really suck. They have many bugs and are optimised for games only.
3dfx opengl driver isnt the default opengl driver under windows, so you have to load their driver and nop opengl32.dll (3dfxogl.dll i think) or just copy the dll to the program dir and rename it to opengl32.dll
Fullscreen in max 800x600 is not the only limitation. You must only use 16-bits color/depth for example. There are some more limitations aswell, but I don’t know about them.
DjinnKahn, the output of the Voodoo 2 is limited to 16 bit color. And 24 bit RGB textures get dithered down to 16 bit. Not sure about the alpha component though.
And do a search on this board or the beginner’s for that environment variable to disable the logo, I remember posting that info awhile back, but can’t remember what it was now.
" Dual texture units on the V2 1000 PCI deliver Patented Single Pass, Single Cycle Multi-Texturing for state-of-the-art special effects in an amazing 16.7 million colors."
if the output is 16-bit, then the quote above is misleading… does it mean only internal processing is 24-bit?