vvbee wrote on 2026-01-05, 13:39:

Not accepting random donations, not asking for them either.

It's possible I'll remove some of the currently supported games in the future as well, since some of them are on the edge. The original goal for the project was the same as for my Glide/S3d wrapper, to focus on games that have a chance of running well on the Rage. Neither the Rage nor the ViRGE match the Voodoo in features and neither can afford to lose performance on extra work, also if the game has a Direct3D version then by default that's going to play better to the strengths of other cards than code written for the strengths of the Voodoo would. That leaves a small selection of games that would benefit from wrapping. In some cases even when a Direct3D version works better a CIF version may be useful if ATI's drivers have specific issues with that game otherwise.

They are on the edge more at Rage Pro / Rage LT Pro / Rage XL / XC 32bit, than on Rage XL AGP (64bit), i can show more higher fps with them. This selection takes more time and effort? If its not hard, leave one open, other closed, more focused on those selected games and i share them both in my drivers. Have i shared my old 3DMark results with Rage XL AGP? Its not that hard to make Rage XL world record on 3DMark99 i think. Every way i am pleased where you are going with it.

I have some RagePro/XL cards results. These results are without game tweaks, bilinear on / off and vga memory oc.
Old 2024 results at 3DMark99Max and Quake1&2,i can do it better.Pentium3 results are close with those Pentium4.

You have to find someone else to write a general purpose Glide/CIF wrapper. In the meantime you can assume that this project has met its goals already, just needs to trim some fat. Grand Prix Legends would be a nice addition if its quirks don't get in the way too much. I have some plans for S3d/CIF or MSI/CIF, ideally at least one of them is a good fit for CIF in terms of the feature set being fully within CIF.

vvbee wrote on 2026-01-05, 16:55:

You have to find someone else to write a general purpose Glide/CIF wrapper. In the meantime you can assume that this project has met its goals already, just needs to trim some fat. Grand Prix Legends would be a nice addition if its quirks don't get in the way too much. I have some plans for S3d/CIF or MSI/CIF, ideally at least one of them is a good fit for CIF in terms of the feature set being fully within CIF.

Can you trim some fat off from v5 or turn off osd from v5 latest alpha? Can it be with osd on/off switch? Just ideas.
For me all your new cif ideas are great,like s3d/cif and msi/cif,amazing.I can back off with my askings also,its all fun.

There are no versions as such, it's a rolling release. When I say trim the fat I mean decide what to remove so that the wrapper has a clear purpose. For example I may remove games that also support Direct3D or OpenGL. It needs to work well for a specific purpose, not randomly here and there.

What are your thoughts about the dos glide games that use GLIDE2X.OVL?
e.g. Screamer 2

Although I know very little about it, I would have thought CIF for Rage Pro only works in Windows (because Tomb Raider was converted from dos to Windows for the CIF version) and so a CIF wrapper for the dos OVL would be impractical.

Apparently there is a single known CIF game that runs in dos, although that was a very early title and didn't work on Rage Pro anyway. Re: 3D Accelerated Games List (Proprietary APIs - No 3DFX/Direct3D)

Doesn't Glidos already let you run Screamer 2 and some others with whatever Glide wrapper you want in the backend? I think I tried it with the Glide/S3d wrapper and it sort of worked, but I never went anywhere with it so maybe not that well.

Sort of works:

Looks to be having to update a lot of textures per frame which tanks the FPS. Annoying side effect of CIF baking too much metadata into textures that Glide keeps separate, but can be worked around to some extent.

I think Glidos recently removed the watermark from free versions, but they don't work in Windows 98. I don't have any plans of writing my own OVL translation.

Thanks for taking a look, interesting results.

Updates:
- support Grand Prix Legends
- optimize GLQuake
- remove Die by the Sword demo
- remove Monaco Grand Prix: Racing Simulation 2 demo
- remove Monster Truck Madness 2 demo
- remove Motorhead

Games that also support Direct3D were removed so that the wrapper can have better focus. But in cases where the Rage drivers have notable issues with a particular Glide + Direct3D game wrapping it to CIF would be worth looking into still.

GLQuake now runs about 4% faster than ATI's OpenGL (without multitexturing) thanks to some optimization and pruning a few small things out. I think a potential future purpose for GLQuake support in the wrapper would be to have the game playable on the Rage IIc, which I don't think has OpenGL in Windows 9x. In this case the focus would be on speed at the cost of image quality, i.e. stripping things out basically since the IIc is slow.

Grand Prix Legends is now mostly supported, with some issues. It's an interesting game in that it'll sometimes reset or glitch the card's video mode. In any case the game normally wants to run at 72 Hz but the wrapper doesn't yet implement custom refresh rates.

Support for DOS games using existing OVL translators is worth looking into.

Some games now have occasional texturing issues.

I shortly used bit faster pc and also other cif drivers for testing, i have good speed and i dont see any problem with pandemonium 2 (exlusive to glide) and its fps, maybe had older glide2x.dll before. Pod Gold has only tiny sky issue, pod gold has glide and d3d. Pod game is not error free, some glitches are there without any wrapper (from pod video). Pod Gold renders fastest and Pandemonium has 30fps game limit, where i am.

Rendering at pod is different with different API-is.
https://www.youtube.com/watch?v=DU5Zi69QPQs

Pandemonium 2 Trailer
https://www.youtube.com/watch?v=UswwyPXqfEw

Glide2CIF wrapper likes resolution 640x480? Switching to other resolution it quits games, at 640x480 starts ok. I have seen Tomb Raider @ CIF, that it likes same resolution as desktop its at, 640x480 usually or 800x600.

The desktop resolution has to be at least the resolution of the game, otherwise it only renders in that area. There was a note in the readme about it earlier but I figure people won't typically run their desktop at 640 if they game at 800 for example. It looks like an ATI bug because setting the CIF clipping regions after the video mode change should be all that's required but has no effect. I only tried a higher res in Motorhead I believe and it worked there, also Gex's 512 or whatever works, so I assume as long as the desktop resolution is set it should work. Then again if games are quitting rather than just having clipped rendering then it's something else, at least for running higher than desktop resolution, but could still be a limitation of the driver in how it internally manages the render buffers or something.

I have used to lower its direction, like 512x384, 400x300 and 320x240, i have not used higer than 640x480, usually i use this.

I tried three games and they don't quit at other resolutions. Also please don't report issues using old iterations of the DLL, they're unsupported for a reason. Any issue you can't replicate with the latest download can fuck off.

Latest glid2cif: GLQuake have visible speed improvements, it near to regular OpenGL speed without tweaks. 👍
Celeron 533Mhz i got latest glide2cif 29.5fps and ATi OpenGL 30.4, with my unoptimized test ati2drab cif drv.
Without ATi OpenGL tweaked settings they are basicly even and faster than any other OpenGL wrapper before.
Its with 8bit paletted textures that any ATi OpenGL does not truly have. Unique in that way for Rage Pro cards.

Latest glide2cif used your settings
set FX_GLIDE_SWAPINTERVAL=0
GLQuake

Rage LT Pro = 29.5fps (640x480) OpenGL32 1.49
ATi OpenGL = 30.4fps (640x480) OpenGL 1091

RageXLAGP= 33.1fps (640x480) OpenGL32 1.49

Great result for the Quake!

Maybe that matters and helps. Some ATi CIF games and ATi side of the table, it likes more 5 5 5, games like Tomb Raider ATi, F1 Formula ATi Edition video, in the Glide side, it likes 5 6 5, so maybe this helps you for the compability part of the CIF. Some CIF games do not care, others do. Maybe i need to change some driver files to make it work better at 5 6 5 and CIF. This is the case why ATi has it by default in 555@historical reason or speed reason.

Can it be like, ATi Rage Pro Tweaker 565 (Desktop 565) -> Glide 565 -> CIF 555 -> Game 555 or Glide game must be also 565, from higher 16bit back to lower 15bit to go should be ok. OpenGL is the same, both works for ATi RagePro, 16bit and 15bit or there it does not care or cares less or this setting is only for d3d/cif

Maximum @ Rage3 and 8MB at 3D
Its possible to go up to 1280x1024x16, over that, Rage3 quits 3D support. In that resolution games are slow, just to know where it hits the wall.

Updates:
- support Screamer 2 via Glidos
- remove Manx TT Super Bike demo
- fix mirrors and improve menus in Grand Prix Legends
- work around apparent ATI driver bug with fast CPUs
- some changes to the environment variables

As always, any game that isn't on the list of supported games is unsupported.

Screamer 2 now runs via Glidos, but you have to accept 15-25 FPS and sometimes less. Manx TT Super Bike regressed into not working, so for now it's off the supported list.

Apart from visual improvements I think Grand Prix Legends runs faster now. By default it's about 20 FPS at 640 x 480 with solo practice in Monaco, about the same as the Voodoo Rush. If you disable the new fast CPU bug workaround then it's about 30 FPS, with some extra glitches that may or may not occur on slower CPUs. At 1024 x 768 you can get about 15 FPS.

Actually GitHub hasn't regenerated the frontend for the changes. But when you see the readme talk about these new things then you know it's been updated.

Screamer 2 + Glidos, these two work with latest glide2cif?
https://download.glidos.net/Glide2x-ovl-vvbeefix.zip
http://download.glidos.net/Glidos_v1_59.exe

You don't take a hint do you. Almost all of your posts make me less interested in working on the wrapper.