VOGONS


First post, by RaVeNsClaw

User metadata
Rank Newbie
Rank
Newbie

Hello everyone!
I've been collecting early 3D accelerators for many years, but a few weeks back I came across some informations that caught my attention.
I've always thought that Direct3D came with DirectX 3. But it actually came with the short lived DirectX 2.

I was listening to the German podcast "Stay Forever", Episode SFT 23-2 and they called out the Terminal Reality games Hellbender and Monster Truck Madness to be the very first games with Direct3D support.
Both games were released around Aug 1996 and were published by Microsoft itself.

So I bought the CDs on ebay, went through all the files and documentation on the CDs and went down a very steep rabbit hole.

Early Direct3D
First of all: Yes, Hellbender and Monster Truck Madness came with the very first release of Direct3D:
Included in DirectX 2.00a, version 4.03.00.1096 from May–Jun 1996.

The D3D implementation was still so experimental, it's almost funny:
The readme files only list cards that won't work, but they don't list the cards that do.
And there's a good reason for that.

While the included DirectX package comes with a whole bunch of driver files for graphics cards, almost all of them will run Direct3D in software.
And back then you probably wouldn't notice, unless you check if "useDirect3D" is activated in the game INI file.

When looking through the actual DirectX files, there were only two GPUs that could use 3D acceleration out of the box:
- ATI Mach64 GT (VEN_1002·DEV_4754), later called 3D Rage.
- Rendition Verite 1000 (VEN_1163·DEV_0001), but readme says the driver is known-bad and the compatible Verite driver was not released at the time of shipping.

So at the release of Direct3D only the Ati 3D Rage could run it.

Unreleased D3D drivers
Now the interesting part:
The DirectX 2 SDK from June 1996 can be found on Archive.org.

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

Holy moly! There are acutal Direct3D beta drivers for the GLint 300SX from 1994!
I guess I'll have to grab my card from the attic and test it again: Gaming on 3DLabs GLint 300SX

Now, why aren't these drivers in the DirectX2.0a release?
Well, the early GLint cards were no longer on the market and 3DLabs wanted to focus on Permedia. So there probably never was a full release of these drivers.

Also: MMX
Hellbender and Monster Truck Madness already have MMX support in Aug 1996, about half a year before the first Pentium MMX was released.
There's a "useMMXFlag" in the MONSTER.INI and HELLBEND.INI to activate it.

Reply 1 of 8, by RaVeNsClaw

User metadata
Rank Newbie
Rank
Newbie

The DirectX 2 SDK also comes with game samples!
There's exactly one D3D game:
ROCKEM3D, from May 26, 1996.

So while that wasn't a release, it's probably the very first Direct3D game.

Reply 2 of 8, by marxveix

User metadata
Rank Oldbie
Rank
Oldbie

Here is one list of early 3d games : The partially-Direct3D-compliant video card compatibility list (ATi 3D Rage, Matrox Millennium, #9 Imagine 128-II)

Best ATi Rage3 drivers for 3DCIF / Direct3D / OpenGL / GLUT / DVD : ATi RagePro drivers and software
33+MiniGL / OpenGL Win 9x dll files for all ATi-Rage3 based cards : ATi RagePro OpenGL files

Reply 5 of 8, by leileilol

User metadata
Rank l33t++
Rank
l33t++

MobyGames is also potentially misinformation for technical specs, especially as they've gamified contributions (but not corrections)

FUCK "AI". It is a tool of fascism. We do not need it. We do not use it.

Reply 6 of 8, by kingcake

User metadata
Rank Oldbie
Rank
Oldbie
leileilol wrote on 2026-11-02, 04:05:

MobyGames is also potentially misinformation for technical specs, especially as they've gamified contributions (but not corrections)

It's good enough to make a punch list of games to look into.

Reply 7 of 8, by Trashbytes

User metadata
Rank l33t
Rank
l33t

I saw this thread and it made me remember the hell hole that early D3D was ...so much fun with so many GPUs either fully supporting it, partially supporting it or drivers that claimed as such but didn't actually support it. Then you had the developers / game developers trying their best to stick to Microslop guidance on how to fully implement D3D on hardware, software and drivers but come to find Microslop has released a dozen updates to it before you could release your program, drivers or game that broke what support you had.

Oh and then you had to contend with DirectX updates breaking every time they installed or breaking the GPU drivers or sound drivers or obscure drivers you had no idea DirectX even interfaced with. This was a real pain in the ass to fix with Win95 and 9/10 it was faster to just nuke the OS and reinstall everything that try to rollback a broken DirectX update that usually caused BSODs.

It was little wonder that Glide and OpenGL were the most popular APIs back then until D3D became stable and nVidia killed off Glide and Microslop stuck it to OpenGL by buying out developers and publishers to force D3D adoption. (Not that OpenGL went anywhere but MS certainly made sure it took back stage to D3D on windows)

AI is inevitable, there is nothing you can do to stop it, no Ironman snap to save you from the Basilisk.

Reply 8 of 8, by Jo22

User metadata
Rank l33t++
Rank
l33t++

Hi, I'm afraid I'm not that much of a gamer but I can imagine that MS had proceedet on two fronts.
Direct3D on Windows 9x, OpenGL on Windows NT.
Many moons ago, I noticed this with my Elsa Gloria L graphics card.
On Windows NT4 the GLint Delta chip had OpenGL drivers,
while on Windows 98 it was unsupported but here the S3 Virge3D (VGA chip) had Direct3D drivers.

"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel

//My video channel//