vetz wrote on 2014-05-09, 06:51:
Glide2x.ovl version shouldn't matter afaik in Carmageddon. You have probably installed the wrong patch (or something else is wrong with your system).
Sems version DOES matter. I had this same problem on 86Box emulator (PCEm fork). First I thought it was a problem on the voodoo 2 emulation, but as I see this problem also happens on real hardware.
I did a lot of tests and I think I've found what the problem is. If you check the modification date of the file "voodoo2c.exe" is 22/06/98. So when the SCi employee did this fast hack to support voodoo 2:
- the Directx 7 compatible reference drivers from year 2000 everybody is using (3.02.02) didn't exist, neither
- Directx 6 compatible 3.01.01 drivers
- Directx 5 compatible 2.10 drivers
And all of them hang the game when starting the race.
But when using drivers 1.x ( I tested 1.02.51 and 1.03.00) voodoo2c.exe runs without any problem. Even carmav.exe runs directly over voodoo2, but with some flickering prblems in the top bar (as I barely remember also seeing when using my voodoo Banshee on my pentium mmx 25 years ago). And these 1.x drivers are from mar-jun 1998, the date the patch was published...
So yes, the voodoo2c.exe patch was checked for working over 1.x drivers, the ones available on that time, and unfortunately isn't compatible with any of the later versions (hangs when entering ingame).
To allow having later 3dfx drivers installed systemwise (under Win 9x) I just copied the file glide2x.ovl (attached) from 1.03.00 drivers on the Carmageddon folder, where voodoo2c.exe is located, and it works like a charm.
You can easily know if your game is running using 1.x or later 3dfx drivers: 1.x show the old logo, with a white spiky background, on the start animation, 2.x and newer drivers show the new animation, only with the word 3dfx and any background.
Tip: also 1.x drivers add the environment variables for configuring speeds, etc, on the autoexec.bat, while 2.x and newer use the windows registry, and run a program on startup to load them. It can cause problems when installing ones over the others as those entries are not deleted on uninstall.