DirectX 1.0 (1995)Originally called the Games SDK, it was Microsoft’s answer to OpenGL and DOS gaming. It introduced DirectDraw for 2D graphics and DirectSound for audio. It was the first step toward a unified driver model.
For modern developers, studying the DirectX 8 SDK offers a clean, less abstracted view of the GPU without the complexity of modern bindless rendering. For retro gamers, hunting down the correct runtime DLLs is a rite of passage. And for driver engineers, the DDK for these versions represents the last time you could control a graphics card with pure assembly and a prayer.
The runtime was version-locked to the operating system. You couldn’t install DirectX 8 on Windows 95—only Windows 98 or 2000. And if a game required DirectX 7, but you had DirectX 5 installed? You had to upgrade the entire runtime. There was no side-by-side assembly like modern Windows. This led to the infamous "DLL hell" where newer runtimes would break older games that expected specific behaviors. DirectX 1-8 SDK DDK Runtime
If DirectX 1 was the proof of concept, DirectX 2 and 3 were the growing pains.
The End of Fixed Function (Almost). The SDK added Transform & Lighting (T&L) via hardware. Unreal Tournament and Quake III Arena used DX7. The DDK now required hardware T&L (which allowed GeForce 256 to crush Voodoo 3). The runtime became the standard on Windows 2000. However, the SDK was still split into DirectDraw (2D) and Direct3D (3D) – two separate pipelines. DirectX 1
DirectX 2.0 and 3.0 (1996)These versions refined the API. Version 2.0 added Direct3D, though it was notoriously difficult to code for. Version 3.0 was the first "stable" standard, shipping with Windows 95 OSR2.
In the modern era of gaming, terms like "Ray Tracing," "DirectStorage," and "Mesh Shaders" dominate the conversation. Players casually update their DirectX versions through Windows Update without a second thought. However, the stability and ubiquity of the DirectX application programming interface (API) today were forged during a chaotic, turbulent, and innovative era between 1995 and 2002. For modern developers, studying the DirectX 8 SDK
The Runtime is what the gamer installed. When you inserted Half-Life or Diablo II , you often saw a dialog box saying "Installing DirectX Runtime." Crucially, the runtime included the D3DIM (Direct3D Immediate Mode) and D3DRM (Direct3D Retained Mode – a failed high-level API). The runtime translated the SDK calls (made by the game) into the Driver calls (written via the DDK). Versions 1 through 8 were notorious for being "side-by-side" unfriendly; installing a new runtime often overwrote old DLLs, leading to the infamous "DLL Hell."