try different voddo drivers

@Davros - thanks.

Any driver recommendations? My cards are from Creative Labs and are matched. Currently using latest reference driver (3.02.02). I could try official Creative drivers (which are older than what I'm using) or I could go with one of many versions of FastVoodoo2. Any suggestions from anyone?

Sorry mate its a bit of a lottery and even then it may not fix the problem
iirc moto racer isnt a glide game so its not a glide problem

Moto racer is a d3d game and glide doesn't have a native version as it's only supported through directx
Maybe this link will help?
https://steamcommunity.com/sharedfiles/filede … s/?id=814853718

I use wine where it runs fine OOTB

Thanks for the responses. Right now everything else runs great and I don't feel like experimenting with driver versions for one game, especially since it runs well on the Matrox G100. I'll leave it be. 😀

I'm having the same exact problem but with one voodoo 2 card in my sytem, and I'm also disabling D3D from the options menu... no go.

Any solutions yet?

Five years later... same exact problem. I can force the game to run on my GeForce card using the -OnlyPrimaryDisplay switch, same as the original poster, but the game isn't smart enough to deal with a 32-bit color depth on the desktop so it crashes out unless we switch to 16-bit colors manually before launching the game. It works but it feels so clunky. Also it would just be so much cooler to have it running on the Voodoo2's!

Please post if you've ever gotten this to work!

... or, as a fallback, is there a way to tell Windows 98 to switch to 16-bit color, launch the game, wait for it to exit, and then switch back, all with one click?
I've tried batching it but I cannot get the batch to wait until the game exits before trying to revert the color settings.

try timeout "X" in your batch file
or
PING localhost -n "X" >NUL (if your dos has a TCP/IP client)
or
CountDown.exe "X"

"X" = a number
(and 1 to the number of seconds you want in ping)

countdown.exe and sourcecode
https://www.robvanderwoude.com/files/countdown.zip

Davros wrote:

try timeout "X" in your batch file or PING localhost -n "X" >NUL (if your dos has a TCP/IP client) or CountDown.exe "X" […]
Show full quote

try timeout "X" in your batch file
or
PING localhost -n "X" >NUL (if your dos has a TCP/IP client)
or
CountDown.exe "X"

"X" = a number
(and 1 to the number of seconds you want in ping)

countdown.exe and sourcecode
https://www.robvanderwoude.com/files/countdown.zip

I appreciate that but don't all those solutions require that we specify a specific amount of time for the delay?
Problem is we don't know how long I'm going to play the game for, so we need a way to detect when the game exits and only then restore the original color depth.

Davros wrote:

try different voddo drivers

... I tried this too, out of curiosity. I ran through all Voodoo2 reference drivers in sequence, from 1.02.50 up to 3.02.02. The older drivers show a bit of texture glitching whereas newer ones do not - but they all crash in the same way at the same time, when clicking the "Race" button.

I'm really surprised by that. I mean, there must be some configuration that works... They must have had it working on a Voodoo2 test bench back in the day, in order to specifically mention that the 3.22 patch corrects crashing seen with the Voodoo2. WTH?

OMG! I got it to work!! ... on the Voodoo2's!

Here are all the steps that were required:
1. Patch the game to version 3.22 (there's a link to the patch earlier in the discussion)
2. It may be just me, but I also had to install a No-CD hack because after the game was patched it always claimed the CD was not inserted.
3. Launch the EXE with the following switches: -3DFX -NoPal256
The -Alpha switch also helps things look better IMO, as does setting D3D from "ON" to "Filtered" in the game's options screen. I still haven't found a way to correct texture imperfections under the bike's rear wheel, and with skid marks, but the alpha switch makes this less distracting at least.

This was found to work on a Voodoo2 SLI system using reference driver version 3.02.02, 640x480 screen resolution in-game.

Hi,
for information this trick works for Moto Racer 2 as well !
Thanks !

Just wanted to say thanks. This got me running!

AngieAndretti wrote on 2019-11-02, 12:04:

OMG! I got it to work!! ... on the Voodoo2's! […]
Show full quote

OMG! I got it to work!! ... on the Voodoo2's!

Here are all the steps that were required:
1. Patch the game to version 3.22 (there's a link to the patch earlier in the discussion)
2. It may be just me, but I also had to install a No-CD hack because after the game was patched it always claimed the CD was not inserted.
3. Launch the EXE with the following switches: -3DFX -NoPal256
The -Alpha switch also helps things look better IMO, as does setting D3D from "ON" to "Filtered" in the game's options screen. I still haven't found a way to correct texture imperfections under the bike's rear wheel, and with skid marks, but the alpha switch makes this less distracting at least.

This was found to work on a Voodoo2 SLI system using reference driver version 3.02.02, 640x480 screen resolution in-game.

I did the same but I have SLI of Voodoo2 of 8MB each one.

When the game loads I wait until the game on 3d appear but it says me "not enough video memory D3D mode not available". And the games runs without filtering.

It's strange cause I have 4MB for texture in each video card...perhaps it works only in a 12MB Voodoo2 cards with those switches.

biessea wrote on 2024-05-27, 12:57:

When the game loads I wait until the game on 3d appear but it says me "not enough video memory D3D mode not available". And the games runs without filtering.

Try to press Ctrl+F during gameplay, get back to the menu, enable direct 3d filtered and try to load the game again.

There is a know problem with big font size under some configurations and some hardware. I'm not sure if it's your case.