Perfect machine for Quake 2.

Joakim wrote on 2023-10-23, 04:13:

Perfect machine for Quake 2.

That's definitely going on as well, and I wonder if this thing is just a bit too weak to handle Quake III Arena? I guess there's only one way to find out.

Voodoo2 ain't got the texture memory for Quake3 without it hitching nor the support for 32-bit textures so it'll look very banded and posterized in places. A "legendary" second V2 in SLI can't do anything about that (in fact the hitching will be worse as there's two cards to get starved with). That TNT2 M64 likely will handle that better.

Since you're using XP, you can't use DIrect3D with the Voodoo2, so that limits its use to Glide titles (and a few OpenGL ones that can use a minigl driver). XP also has problems of its own with some games from this time (the "NT is unsupported" fussiness for example, given NT4 had limited DirectX support)

Requiem, Rollcage, NFL Blitz 2000, Starsiege and Diablo 2 should be fine.

StarCraft 1 with patch 1.16.1 should work too, but not in the Battle.net
Warcraft II Battle.net edition too.

Newer games benefit Quake 3 benefits from a graphics card that supports "Hardware T&L", a feature none of the Voodoo cards ever had. This feature has been implemented since GeForce and Radeon.

Tomb raider 1-3 are good if you are into that.

What about GTA 1 and 2. Still cool games!

What about Turok or a personal favorite: Drakan. It might be stretching the hardware though.

Oh and one I personally would like to try again: Ignition.

Age of Empires I and II (the original versions), and Star Wars: Rogue Squadron 3D.

Disruptor wrote on 2023-10-23, 07:15:

Quake 3 benefits from a graphics card that supports "Hardware T&L", a feature none of the Voodoo cards ever had. This feature has been implemented since GeForce and Radeon.

Q3 doesn't use HWT&L (the renderer was already done before the Geforce256 came out). All of Quake3's transforms and lighting are explicitly software calculated and is designed that way to look consistent on basic OpenGL 1.1. It doesn't even have hardware fog use (all of the fog is a fillrate-destroying texture calc). What matters more is how a video driver's OpenGL ICD handles compiled vertex arrays and elements