Hi guys! I am new here and I introduce myself with a question:

I am having troubles to run DI Apache Longbow with my Voodoo 3 3000. This game initially doesn't support 3dfx. It was added later with a patch. This patch was for Voodoo 1 but they released a patch for Voodoo 2 later. The patch's readme says that it is not compatible with Banshee.
Well, I supposed that my Voodoo 3 could run it, but it doesn't! Don't matter if I use Voodoo 1 or Voodoo 2 patch, I get the same result, just after 3Dfx splash screen I get crash to desktop. I think that the game "thinks" its a Banshee and crash.
I need help, please, what can I do to get it to work? Is there any way to trick the game to think that I have a Voodoo1 or 2?
The game runs great with software render, but running a Glide capable game in software render owning a Voodoo is like, you know, owning a Ferrari and go by bicycle...
I know there are also Glide wrappers, but...

My system config:

AMD K6-2 300Mhz
Superpower SP-A586B Mobo
96Mb RAM
Voodoo 3 3000 AGP
Windows 98 SE
Sound Blaster 16 audio

Greetings from a spanish Voodoo fan. Thank you!

Thank you for your answer! At least you gave me a start point.

I didn't know anything about environment variables, so I am not sure if I am doing it right or not.

I understand that I have to put the variables in autoexec.bat file or in a .bat file created by me. Is that right?

Well, I tried with these variables (From the first post):

set SST_GRXCLK=50
set SST_FT_CLK_DEL=0x4
set SST_TF0_CLK_DEL=0x6
set SST_TF1_CLK_DEL=0x6
set SST_VIN_CLKDEL=0x1
set SST_VOUT_CLKDEL=0x0
set SST_TMUMEM_SIZE=2

But no way... Still doing the same.

I have the doubt however if I am doing something wrong...

The game is Windows version, not DOS, by the way.

I also thougt about buying a Voodoo1 card, but what I've seen so far is expensive in my oppinion. What do you think?

Quote:


As long as you are taking care to reboot after inserting the lines into autoexec.bat, you are doing it properly (assuming you are applying it to an Apache installation with the first patch and the Voodoo 1 patch, but not the Voodoo 2 patch).  You might try the set of Voodoo 1 variables from the second post (with the same Apache installation just mentioned):

REM ===== VOODOO 1 ENVIRONMENT VARIABLES =====
set SST_GRXCLK=50
SET SST_FT_CLK_DEL=0x4
set SST_TF0_CLK_DEL=0x6
set SST_TF1_CLK_DEL=0x6
set SST_VIN_CLKDEL=0x1
set SST_VOUT_CLKDEL=0x0
SET SST_FASTMEM=0
set SST_TMUMEM_SIZE=2
SET SST_SCREENREFRESH=60

The next thing to try would be to use the Voodoo 2 set of variables to get the game to work with all of the patches applied (start with these):

REM ===== VOODOO 2 ENVIRONMENT VARIABLES =====
SET SSTV2_GRXCLK=50
SET SSTV2_SWAP_EN_WAIT_ON_VSYNC=0
SET SSTV2_SCREENREFRESH=60
SET SSTV2_VIDEO_24BPP=1

The main thing to pay attention to would be to make sure you are not effectively overclocking your card by inadvertently or indiscriminately changing values.  The GRXCLK environment variables allow you to adjust clock rates, and the values for Voodoo 1 and Voodoo 2 above effectively underclock a Voodoo 3, and that's fine.  But some Voodoo users may be trying to overclock the card and suggest using environment variable values that can damage the card, so bear that in mind as you experiment.

Also, you might consider posting your problem at VOGONS ( http://www.vogons.org/ ).  Someone may have tried to do exactly what you are doing and have found a solution.

I don't know the this game (and/or the patch) but lot's of DOS games use the GLIDE2X.OVL file which is often located in the root of the games' installation directory. If the file is from the Voodoo Graphics driver then it won't run with a Voodoo2.

Perhaps you can try (long shot!) the same trick with this Windows game? Try to copy the .OVL and .DLL files from the Voodoo3 drivers into the root of the game folder.

Thandor wrote on 19.12.13 at 20:44:36:


I've had no luck so far... neither with using variabes, neither copying .ovl and .dll files to game's root directory.

Quote:


I am interested. Please, tell me price of each. Thank you