This post is a side-by-side video comparison of a late-90s PC game running under two different rendering paths on period-correct hardware: a Pentium-II 266MHz with 128MB of RAM and a 3D Blaster Voodoo Banshee 16MB. One pane shows the CPU-only software renderer; the other shows the same game rendered via Direct3D using the Banshee's hardware 3D pipeline.

What makes the clip educational is that it makes a piece of computing history visceral. In the mid-to-late 90s, 3D acceleration was a genuine paradigm shift, and this comparison lets you see exactly what changed:

• Texture filtering: The software renderer uses nearest-neighbor sampling, producing the chunky, pixelated textures that defined the era's look. The D3D path enables bilinear filtering, smoothing texels into the blurry-but-clean look that became standard.
• Perspective correction: Software renderers often used affine texture mapping (or cheap subdivided approximations) to save cycles, causing textures to warp and "swim" on surfaces near the camera. The Banshee handled perspective-correct mapping in hardware essentially for free.
• Resolution and color depth: Software mode was often locked to 320×240 or 640×480 in 8-bit color because the CPU couldn't push more pixels. Hardware mode unlocked 16-bit color and higher resolutions without melting the framerate.
• Frame rate: The OP's own comment is the real lesson — "anything above 15fps and I would be happy." A Pentium-II at 266MHz was burning nearly every cycle on rasterization in software mode. Offloading that to a $150 add-in card freed the CPU for game logic and AI.

The Voodoo Banshee is itself a fascinating artifact: 3dfx's attempt to combine the Voodoo2's 3D pipeline with a 2D core on a single chip, eliminating the need for a passthrough cable to a separate 2D card. It was a transitional product on the road from add-in 3D boards to the integrated GPUs we take for granted today.

For anyone who didn't live through it, this short video communicates more about the 1998-era hardware acceleration revolution than a chapter of text could. For those who did, it's a sharp reminder of how much hidden CPU work the software path was doing — and how transformative dedicated silicon felt the first time you flipped that toggle in the game's options menu.