for what it is worth
the game works in the glide emulation guilikoza created for dosbox. So you might want to contact him as he debugged the game a few times.

This is unusual because they released the Glide patch for the game after the Voodoo2's release 😖

Qbix wrote:

the game works in the glide emulation guilikoza created for dosbox. So you might want to contact him as he debugged the game a few times.

I assumed that something like this exists, but for now I would prefer to use the old hardware for the old game.

I'm not suggesting that you use dosbox. I suggest that you ask guilikoza for more information as he debugged the game in order to get it working with dosbox. So he might know what for tricks and weird things it does.

Oh! ... I will do that...

... the idea was good... the answer came quick... but unfortunately gulikoza has no solution either.

Maybe somebody else?

In detail it would be helpful to know:

- if the game needs a specific version of the glide2x.ovl (and the glide2x.dll?) to run
- which files have to be where - especially in DOS
- if it is necessary to use a special *.bat file / sst environment variables to make the voodoo2 voodoo1 compatible (like sometimes with early win95 games)

Hurray!

I finally got it working! 🙄 Here is how:

- I deleted the glidex.ovl that came with the game and replaced it with one of an early voodoo2 3dfx reference driver kit, namely glide version 2.50, dated 4-3-1998.

- I created a batch file, containing the following lines:

SET SSTV2_FASTMEM=1
SET SSTV2_FASTPCIRD=1
SET FX_GLIDE_ALLOC_COLOR=2
sf3dfx.exe

In fact I do not know what it exactly means, it was just trial and error. But the last line reffers to the triple color buffering of the voodoo2 the game seems to have problems with. If it is set to 3 (on?) it doesn't even start at all.

Hope that will help everyone who stumbles over this problem like me.

Silent Loon wrote:

- I created a batch file, containing the following lines: […]
Show full quote

- I created a batch file, containing the following lines:

SET SSTV2_FASTMEM=1
SET SSTV2_FASTPCIRD=1
SET FX_GLIDE_ALLOC_COLOR=2
sf3dfx.exe

I might be late replying, but here's a full list of Voodoo transitional variables --that is, the variables to run "Voodoo 1-only" games on Voodoo2.

set SST_GRXCLK=90 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_VOU […]
Show full quote

set SST_GRXCLK=90
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

Oddly enough, these variables use SST instead of SST_V2. Moreover, none of the variables you are using mentioned as "transitional variables". However, they might be worth a try.

Nonetheless, I think this kind of information deserves to be preserved.

Ghetto Edit: well, this is my first try to interpret what those "transitional variables" actually mean (from here:

set SST_GRXCLK = 90: Set graphic clock rate to 90 MHz.

set SST_FT_CLK_DEL=0x4: Set the access speed of Frame Buffer memory to 2. However, I don't know what the "2" here means. 2 MHz? 2 cycle per clock? Beat me.

set SST_TF0_CLK_DEL=0x6: Set texture chip 0 memory access in delayed clocks to 0x6. Again, I have no idea what the hell does it mean.

set SST_TF1_CLK_DEL=0x6: same as above, but this one is for texture chip 1.

set SST_VIN_CLKDEL=0x1: set the video in clock delay to 0x1. I have no idea about this one either.

set SST_VOUT_CLKDEL=0x0: same as above, but this one is for video out.

set SST_TMUMEM_SIZE=2: set the amount of texture RAM to 2. Again, I don't know whether it means 2Mb or 2Kb.

If only we can find a complete reference on what those variables actually mean.... 😢

Hi KAN!

That's what I found on that subject:

http://www.geocities.com/k_lupinsky/Voodoo_SST_FX.htm

But those are the variables for the voodoo 1 I think.
I collected the info for the batch file there:
http://www.3dgw.com/faq/moodys_voodoo2_faq.htm

Here are some informations about voodoo2 commands also - it's a little tutorial called tweak voodoo and you have to download it from 3dfxzone.it : http://www.3dfxzone.it/dir/3dfx/voodoo2/tweakers/)

But you're right, there should be some kind of accurate documentation somewhere...

Silent Loon wrote:

But those are the variables for the voodoo 1 I think.
I collected the info for the batch file there:
http://www.3dgw.com/faq/moodys_voodoo2_faq.htm

😳 That's the coolest page I've ever seen. Alas, all download links are broken, and when I tried to get those patches manually with command line FTP, I got "Connection closed by remote host" error message.

Hi there! I am also trying to get Archemdian Dynasty running in 3Dfx mode but it seems I am not so lucky with the glide2x.dll... Silent loon could you submit a link to download your glide2x.dll, for example via rapidshare?
I would be very grateful 😀.

xtal: check out Falconfly's Voodoo 2 page. I think the .ovl silent's referring to is included in the 06/04/98 driver release for win9x (first table, third item).

Not sure if there's any benefit in trying later ones, I'll be doing that myself later. The readme indicates it's designed to work with v2.42, so if it works with 2.50 you might be better sticking with that.

Silent Loon's thread in the FalconFly forum might be of interest:

http://www.falconfly.de/cgi-bin/yabb2/YaBB.pl?num=1194454008

Handy.

For me in Dosbox using the included glide files works insofar as it loads and gets to the menu, but once I start a mission the screen goes black - probably because I have a Voodoo 5 as my graphics card 😉 And despite their best efforts SFFT et al aren't there yet... I do get sound, mind.

It did set me to wondering whether some sort of pass-through driver would be possible, though. It may have been suggested before (and I suspect given the limited number of Voodoo users these days I'd be on a hiding to nothing asking for it), but it would be a neat idea as a workaround.