Spark wrote on 2023-07-18, 07:54:
Thanks marxveix it's great that multitexture can get you a few more fps on Quake 2.
Interesting I couldn't get multitexture to work with GLQuake, when starting it detects multitexture support in the console then just crashes, I had to remove the multitexture extensions from atidbg.ini to get it started.
I did some quick testing and it seems that multitexture crashes come from newer driver, not directly from OpenGL itself and its related to ATi driver version. My latest 540x2611x3d drivers work with multitexture and macxw4 and ati2ddad drivers are working with multitexture, but ati2drab / ati2drae driver are not. Someone maybe would like to test more drivers and get full picture from situation. Many single driver drv file: macxw4.drv or ati2ddad.drv or ati2drab.drv or ati2drae.drv wont work with all Rage3 cards. Example, sometimes RageXL card is kicked out from OpenGL party, even if D3D and 3DCIF is working with the same driver and this is with all OpenGL versions for Win9x, but not Rage3 MiniGL-s, they are all working and GLDirect wrapper also work. Picture gets clearer that after ati2ddad drivers some of the good old stuff gets ripped off, driver by driver.
Example:
Rage XL OpenGL is missing + D3D/3DCIF ok
Macxw4.drv = 4.11.2598 is one such file
Ati2drab.drv= 4.11.1014 up to 1027 is another
Two simple and good options here below if multitexture is working with your ATi driver and with multitexture and bilinear enabled + its easy to check if it crashes or not. Multitexture enabled situation gives performance boost with bilinear enabled and fastest max performance you get if you disable both options (bilinear + multitexture).
atidbg.ini@multitexture (fast: bilinear on)
Multitexture and bilinear enabled
[OPENGL]
EnableMTSGI=1
EnableMTARB=1
[Kelvin]
Bilinear=1
atidbg.ini@ (max fast: bilinear off)
Multitexture and bilinear disabled
[OPENGL]
EnableMTSGI=0
EnableMTARB=0
[Kelvin]
Bilinear=0
30+ MiniGL/OpenGL Win9x files for all Rage3 cards: Re: ATi RagePro OpenGL files