Yup, that's the one.

OpenGVS is great. It works with any OpenGL capable professional GPU.
I had it running on all kinds of crazy Intergraph cards.

Just make sure your OpenGL doesn't default to "GDI Generic". That's your CPU doing the lifting.

weedeewee wrote on 2026-04-26, 11:02:

janskjaer wrote on 2026-04-26, 10:27:

RaVeNsClaw wrote on 2025-03-29, 15:29:

Ok, some updates. After some trouble with automatic standby, the OpenGVS RealWorld benchmark finished in blistering fast 3 hours […]
Show full quote

Ok, some updates.
After some trouble with automatic standby, the OpenGVS RealWorld benchmark finished in blistering fast 3 hours and 20 minutes in 640x480 and 32Bit.

The attachment OpenGVS_RealWorld.jpg is no longer available

Sorry for the blurry picture. I've recorded the whole sequence over a VGA to HDMI adapter and a HDMI video capture card.
It works fine when recording in 640x480, but for this screenshot I had to switch to 1024x768.

To my surprise UT99 GOTY works out of the box in OpenGL.
Well with less than 1 FPS it works. 😉

I'm now trying to make a video about this card, as there are currently none.

EDIT: I was wrong here! These numbers apply to the Microsoft software OpenGL renderer, see screenshot above.

Would you mind sharing a copy/image of the OpenGVS RealWorld version you have, or point to a link where it can be downloaded?

Is this http://www.xin.at/thrawn/files/opengvs-realwo … Q3D_RWB_242.zip what you're looking for ?

Found the link on the vogonswiki after searching for the correct filename to download Q3D_RWB_242.zip .

I believe it is. Thank you.
I will give this an install and see how it goes.

The only reason I remembered about OpenGVS was because I was using the game, Barrage, as a benchmark a few days ago, and realised it too, was developed using the OpenGVS engine. If you run a Voodoo2 and another 2D card on separate displays, the OpenGVS info is reported on the 2D card's display.

You are right, the screenshots of that game look exactly like OpenGVS.

That's really interesting! It's hard to find OpenGL games that run on old CAD cards, but this is definetly a candidate!

Thanks for making this!

Thanks! All those Elsa Gloria demos run well on Win9x and ATi Rage3

Cool OpenGVS Bencmark and Demos. Are those demos all 16 bit or not and any eralier versions available to download or they are lost?
I did run some of them and many work accelerated@ATi RagePro and some at software render. I did run them on 640x480 resolution.

Re: ATi RagePro OpenGL files

RaVeNsClaw wrote on 2025-03-29, 01:06:

I've submitted pictures of my card to "The Retro Web": https://theretroweb.com/expansioncards/s/elsa-gloria-4

I'm interested how you were able to create such good quality images of your cards. Did you use a scanner or camera? I've tried with a flatbed scanner but the results are hit and miss; mostly miss.
Were your submissions to both The Retro Web and The VGA Museum easy to do, and what is the process for getting these uploaded?
And finally, did you resolve the "Generic GDI" device selection for the ELSA cards? This should be somehow possible to overcome. The situation is the same on Windows 95, as it too includes a "software" OpenGL library. Yet, I don't see a way to either select the device, or choose a difference OpenGL ICD that is tailored towards your card.

@janskjaer: Sorry for the late reply, I'm rarely on vogons these days.

I've used a Olympus PEN E-PL9 with a Panasonic H-H025 lens and multiple light sources.
I bought that camera years ago due to its looks. It's actually all plastic and pretty average.

There are no OpenGL capable drivers for Win9X for this card. It needs Win NT.
I've got it fully running and made some videos in action, see:
Re: Gaming on 3DLabs GLint 300SX under Win98

Holy moly!
There are acutal Win95 Direct3D beta drivers for the GLint 300SX!

They're included in the DirectX 2.0 SDK from June 1996 and can be found on Archive.org.

There's a EXTRAS folder that comes with D3D drivers that "have not completed the Microsoft QA process".
There are BETA Direct3D drivers for:
- Creative folder = 3DLabs GameGLINT = Creative Labs 3D Blaster VLB
- 3DLabs folder = PCI\VEN_3D3D&DEV_0001 = 3DLabs GLint 300SX

In the documentation there's some facts about these drivers:
- 300SX Reference board: Direct3D HAL in BETA, 16-bit color modes only, Gouraud/flat + specular + Z-buffer; no texturing, no line/point primitives, no fog, no anti-aliasing.
- Creative 3D Blaster: HAL is further along. Flat/Gouraud, textures with or without perspective correction, Z buffering, lines/points. Missing: fogging, alpha blending, stipples, specular textures; 16-bit only; 640x480 needs a memory extension on a 1+1 MB card.
- Both INFs ship with 3DExtensions.Disable = 1 . 3Dlabs themselves defaulted Direct3D off, and hook up an OpenGL ICD (3dogldrv.dll) instead.
- EAGLE.DRV (3D Blaster) is byte-for-byte identical to GLINT.DRV (300SX). The 3D Blaster version resource still says OriginalFilename=GLINT.DRV, "BETA 3Dlabs Win95 Mini Display Driver", version 4.02.0098, 3Dlabs 1995.

The 300SX can do texturing, but has no own texture memory. That's probably the reason they deactivated texturing.
But since both drivers are pretty much the same, I might be able to put a driver together...