Added OpenGL 4.11.1062 to this Rage3-GL_Win9x package and now it is easy to
change OpenGL files and atidbg.ini settings with Autoexec.bat (without restart).

Rage3-GL_Win9x.7z and Rage3-GL_Win9x.zip have these MiniGL and OpenGL files for Win9x
MiniGL (unpacked Opengl32.dll) 4.10.1005 Beta1, 4.10.1010 Beta2, 4.10.1021 Beta3, 4.10.1036.

OpenGL (packed Atoglrp9.dl_ and unpacked Atoglrp9.dll ) 4.10.1045, 4.11.1049, 4.11.1051, 4.11.1058, 4.11.1060, 4.11.1062, 4.11.1065, 4.11.1068,
4.11.1073, 4.11.1076, 4.11.1077, 4.11.1079, 4.11.1084, 4.11.1085, 4.12.1088, 4.11.1091, 4.12.1091, 4.11.1094, 4.12.1094, 4.12.1095, 4.12.1096, 4.12.1100,
4.12.1103, 4.12.1104, 4.12.1106, 4.12.1107

Download links for 7z and 7zip archive (both packages have same files inside)
https://www.upload.ee/files/16386911/Rage3-GL_Win9x.7z.html
https://www.upload.ee/files/16386889/Rage3-GL_Win9x.zip.html

marxveix wrote on 2024-03-13, 21:58:

Added OpenGL 4.11.1062 to this Rage3-GL_Win9x package and now it is easy to change OpenGL files and atidbg.ini settings with Au […]
Show full quote

Added OpenGL 4.11.1062 to this Rage3-GL_Win9x package and now it is easy to
change OpenGL files and atidbg.ini settings with Autoexec.bat (without restart).

https://www.upload.ee/files/16386911/Rage3-GL_Win9x.7z.html
https://www.upload.ee/files/16386889/Rage3-GL_Win9x.zip.html

Link to the full driver 4.11.1062?

Takedasun wrote on 2024-03-14, 13:34:

marxveix wrote on 2024-03-13, 21:58:

Added OpenGL 4.11.1062 to this Rage3-GL_Win9x package and now it is easy to change OpenGL files and atidbg.ini settings with Au […]
Show full quote

Added OpenGL 4.11.1062 to this Rage3-GL_Win9x package and now it is easy to
change OpenGL files and atidbg.ini settings with Autoexec.bat (without restart).

https://www.upload.ee/files/16386911/Rage3-GL_Win9x.7z.html
https://www.upload.ee/files/16386889/Rage3-GL_Win9x.zip.html

Link to the full driver 4.11.1062?

Let me search it few days. 😀

Edit: Here is one of the M6.00 driver that has 4.11.1062 i think,7505325.exe - M6.00-PCD16
https://no.softoware.org/get-7505325-exe.html?ir=1

marxveix wrote on 2024-03-14, 15:41:

Edit: Here is one of the M6.00 driver that has 4.11.1062 i think,7505325.exe - M6.00-PCD16
https://no.softoware.org/get-7505325-exe.html?ir=1

Thanks, added it to the driver collection.

I wonder why RagePro has such inconsistent driver numbering.

As far as can tell, there were three (maybe four) different version numbers used: ATI's reference drivers for desktop, ATI's reference drivers for mobility, OEM drivers, and Microsoft's drivers.

Takedasun wrote on 2024-03-15, 14:00:

Thanks, added it to the driver collection.

Hopefully i can find more Rage3 OpenGL versions and drivers. 😀

Kahenraz wrote on 2024-03-15, 14:13:

As far as can tell, there were three (maybe four) different version numbers used: ATI's reference drivers for desktop, ATI's reference drivers for mobility, OEM drivers, and Microsoft's drivers.

Different cards, mostly all the same ATi Rage Pro ( Mach64 ).
Rage3=Rage Pro/Rage Pro Turbo/LTPRO/XL/XC/Mobility-P/M

Two main Win9x driver lines, Desktop and Mobility, J5.xx and M6.xx series (ATI2DRAB and ATI2DRAE) + older drivers (MACXW4 and ATI2DDAD).

Someone please explain why there is two ICD versions of the same 4.12.1107 OpenGL file that have different size and performance (both, V1 and V2 are from latest Rage3 DX81 drivers package).ATOGLRP9.DLL 1107 V2 is the latest, added both 4.12.1107 Rage3 OpenGL files here to download, check the new V2 version out.

Many atidbg.ini settings that increased performance before, now decreases OpenGL performance if i quickly tested 4.12.1107 V2 out with Quake2, so in some or maybe many cases you should look what OpenGL you are using and what Game you are playing, i have made my performance results with older OpenGL versions before, not the latest 11xx.

I have not so big experience with hex, but i opened them up with hex editor and they are totally different with partly of the same code. OpenGL 1107 V1 is from wme-j5-30-1-b02 (J series driver) and 1107 V2 is from 021112a_006561CATi (M series driver) package that has drivers from Win98 up to XP. These are the latest driver that i know for Rage3 cards, even newer than well known wme-j5-30-1-b02 (J5.30 DriverVer=02/28/2002, 4.13.1.2655), M6.12 DriverVer=11/12/2002, 4.13.01.3022, not so far away from year 2003.

M6.12-021112a-006561C-ATI downloaded from here (021112a_006561CATi.zip):
https://www.br-automation.com/cs/ke-stazeni/i … n98/me/2000/xp/

They forgot to correct the file version.

Takedasun wrote on 2024-03-29, 00:22:

They forgot to correct the file version.

Probably yes, 4.12.1107 V2 ATOGLRP9.DL_ (ATOGLRP9.DLL) OpenGL file should be named at least version 4.12.1108 or later. 😀

Joseph_Joestar wrote on 2023-07-12, 11:24:

Takedasun wrote on 2023-07-12, 11:07:

I have looked through the contents of the atoglrp9.dll file and found several values that can be used to enable SGIS_multitexture and ARB_multitexture support.

Interesting. Is there a setting which can enable GL_EXT_shared_texture_palette as well?

I'm asking because the Rage Pro and XL cards do support paletted textures in Direct3D games, with period correct drivers. Not sure why this isn't available under OpenGL though.

Re: Table Fog & 8-bit Paletted Textures

May it be that Rage3 (Rage Pro/Rage XL) cards can accelerate OpenGL at 16 bit only, no other bit color are supported @ OpenGL! Rage3 Direct3D acceleration has no such limit. Is there any Direct3D to OpenGL wrapper or ATI3DCIF to OpenGL wrapper that can help Rage3 out at this?

For Rage3 cards i always use 16bit @ desktop now, sometimes i forget and no OpenGL works then, turn it back to 16bit and voila, OpenGLworks again.Even some old Direct3D games require 16bit mode only, MotoRacer is good example.

ATi Rage128 cards can accelerate other bit depths also at OpenGL, maybe there is more chance to get it going for both (Direct3D and OpenGL).

The only hangup I have with the Rage 128 is the terrible 16-bit dithering. Pattern dithering is ugly, and the noise dithering is nauseating on LCDs. Dithering was much better on the Rage3.

I would love it if there was a way to improve on this. For example, patch the noise dithering to sample the random seed only once, so that it doesn't flicker annoyingly. Or patch it out altogether.

I believe rage's noise dither follows a 1D lookup table. If you want better dithering on an ATI card you'd have to jump ahead to R300

How are they changing the dithering pattern every frame? It it possible to use a fixed seed?

Spark wrote on 2024-03-02, 09:31:

Or you can use the gamma slider in the graphics properties panel provided by the ATI driver, but that doesn't display a figure for the adjustment so makes it a bit of a guessing game.

Latest driver by ATi that shows gamma adjustment numbers @ Ati settings is 4.11.2628 as i know, so extra gamma software not needed there.

Kahenraz wrote on 2024-03-02, 02:54:

An older v4.12.1094 can be used instead, but this can cause graphical glitches that necessitate rebooting the system. This can be demonstrated by running the Quake 2 demo and changing the OpenGL resolution from 640x480 to 800x600 and then quitting the game.

20240301_182106.jpg

Use 4.11.1091/4.12.1091 exit Quake1/Quake2 without getting stuck at exit, 4.11.1094/4.12.1094 has this behavior sometimes. Are all other OpenGL games same boat with OpenGL 4.11.1094/4.12.1094 @ game exiting crash? Maybe it is related to the ATi driver or is this with all driver versions and for everybody? I use 4.11.1091/4.12.1091 more at the moment, than i use 4.11.1094/4.12.1094.

Quake2 3DNow with ATi Rage Pro / XL and how to get small performance boost with your 3Dnow! CPU and ATi card.
1.I use ATi Rage driver that has 3Dnow support (i think any DX6.0 driver or newer ones)
2.Extract the AMD Quake 2 3DNow! patch to your Quake 2.
3.Start Quake 2. Under the video options menu, choose 3DNow! OpenGL as your rendering device (not OpenGL or 3Dnow! 3dfxGL).
4. very early ATi MiniGL/OpenGL maybe do not support 3Dnow! with OpenGL, i have not tested all Rage3 OpenGLs for this, just some.

Direct3D games will take advantage of 3DNow! as long they require DirectX 6.0 to operate.
Is there any non Quake2 based OpenGL games that use 3DNow at OpenGL?

I know there was Quake1 build with 3DNow support, that is lost by now:
Re: MMX/3DNow!/SSE usage

OpenGL setting BreakPageFlipping=1 makes some OpenGL versions run faster than BreakPageFlipping=0/or without that setting.

I did some testing with my retro-setup again. I had tested every PCI-matrox-card but none worked in that setup.
Every card I tested (mystique/millenium2/g200) locked up the machine after a dos-fullscreen and back to win98 desktop.
I checked verious drivers for the card, the chipset and the bios-setting for pci-clocks/ticks delayed transaction etc. ...nothing worked.

so I got the next best option which is a RagePro PCI 8MB.

What did I find out:
DX2/DX5/DX6/DX7 drivers are available.

I started with DX7 drivers, they are good, but break compatibility for dosgames and ATI-CIF
The DX5/6 drivers work but have issues when playing xvid oder dvd-content (terrible mouse-lag)
The DX2 driver I am currently using (2440) 4.10.2440? works great but does not offen opengl-icd
Drivers which do not offer opengl-icd require the miniglide (opengl32.dll) from the atiquake package, it's not working to rename a later atioglr...dll to opengl32.dll because it's not integrated in the driver and therefore does not work.
It's not true that these beta opengl-drivers a very slow...I benchmarked glquake and still got 35+ fps with the rage-pro. same performance as my voodoo1 but different look.
doomgl is another thing, the floor and the light are not rendered correctly with this beta icd.
my own generated demos with osdm which require DX7 are still working with the DX2 compatible driver (DX7 is still installed though) and are obviously faster than with later drivers. Logo-effects are still broken because they seem to be hard-coded to nvidia or ati. (my intros don't require these)
3dmark99 is broken with the early-drivers, though it's much faster in scenes as the later 3d mark99 max but there are lot's of glitches in the picture.
3dmark 99 max is working but much slower and has some minor glitches.

beside the opengl issue on doomgl the 2440 driver with the minigl (atiquake-package) is currently the best option for me.
the overall picture impresses me...it looks better / sharper to me than the voodoo1 which has washed-out colors and less detail on the textures.

too bad the 2d acceleration on amithlon does not work on my card....that would be a hell of a thing, because the ragepro still offers native win3x/9x/nt/2k/os2/winos2/linux drivers.

RagePro is an excellent chip!

On first testing neither opengl or D3D is great on HL1 or Gunman on the ragePro...voodoo1 with opengl seems to be that best option here....less glitches good performance.

dr.zeissler wrote on 2024-07-01, 11:56:

On first testing neither opengl or D3D is great on HL1 or Gunman on the ragePro...voodoo1 with opengl seems to be that best option here....less glitches good performance.

I waited from December 1998 until spring 2000 to get a working OpenGL driver for the Rage Pro, and ended up playing through most of the game using one of the Quake II mini-drivers that was fine except that every surface that was a grate would flicker. Eventually a beta driver (and eventual release driver) came out that solved that problem, but by then I was literally a week or two from buying a Savage4-based Stealth III S540 that was better in pretty much every way aside from 2D image quality.

I think that the Rage Pro/XL would be the perfect retro card for early OpenGL and Direct3D if the last few bugs were worked out. Unfortunately, there were bugs in the latest release that broke things that worked fine in older versions, but the older versions have their own bugs. It's too bad that it took so long to get there, only to have it fail at the finish line.

I would say that these cards are good for "most" things, but I suppose that can be said for pretty much all cards of this generation. Driver development moved forward with the new products and the old ones were left to rot.

I think you could take it a step farther and say that if it released with good drivers, we'd look back on it very differently. Performance near or above a Voodoo, with great multimedia and solid 2D at that price point would have been a godsend. It's a shame that either the hardware and/or the driver codebase was too buggy to cash in on the potential.