Well, I tried it and in opengl can do 512*512 textures without problems but I think it can´t do it in d3d, this happens because it has an opengl 1.3 emulator, suppossedly, also it can do the dot3 bump mapping in opengl

Ups, the program is opengl extension viewer

When I run it, the first screen of activision appears but just after it, I come back to the desktop

Could someone post the compatibility in % showed in GLview in each opengl(1.1,1.2,...) with mesafx and a voodoo5?

voodoo3´s don´t support it. It´s why the agp texture size in the bios isn´t very important for v3

Yes, but you gain compatibility with lots of games and it´s an advance
Also, now I think the most important thing is the compatibility but it´s only an opinion

The thing is that this game, supports 256x256 textures and 16bit colors so...

Why in spiderman:the movie, with the 3danalyzer patch, can be run in v4/5 and not in v3?
What difference are there between this cards (apart from the speed, fsaa and the memory)

Thanks, the same to you and all people:)

Of course, amigamerlin 2.9 in win98SE

In quake3 arena it doesn´t work[:p]

Anyone read this?
I feel that the ideas we post here doesn´t make difference to the developers of the drivers[xx(]

The files 3dfx16vs.drv and 3dfx32vs.dll in the version 4.13.01.0028 which are in mikepedo´s 1.1 driver and x3dfx 1.07.00 drivers supports the dx texture compresion although it results in white textures. Why don´t develop this?

Another clue, the mikepedo´s 1.1 driver used an opengl emulator made by xpentor optimizers that supported 512x512 textures in v3 in opengl and glide, so, why don´t develop it?.