VOGONS


First post, by Aebtdom

User metadata
Rank Member
Rank
Member

Hi everyone,
I've recently got hold of an original copy of Blue Shift and I would like to run it on 3dfx mode with my voodoo2 sli.
Now the game states that it does not support the voodoo2 and in this case I should run it in D3D. And I indeed get the message that the selected OpenGL mode are not supported by ypur video card.
I have wickedGL installed but blue shift is not on the list.
But isn't Blue Shift a variant the same engine as the original Half Life?
Has anyone got it to work on Blue Shift?

20210531_211951.jpg
Filename
20210531_211951.jpg
File size
1.6 MiB
Views
240 views
File license
Fair use/fair dealing exception
20210531_212031.jpg
Filename
20210531_212031.jpg
File size
1.15 MiB
Views
240 views
File license
Fair use/fair dealing exception
20210531_212045.jpg
Filename
20210531_212045.jpg
File size
1.16 MiB
Views
240 views
File license
Fair use/fair dealing exception
20210531_212100.jpg
Filename
20210531_212100.jpg
File size
1.16 MiB
Views
240 views
File license
Fair use/fair dealing exception

AMD XP2400+, 768MB DDR 333, GA-7VRXP KT333
Diamond Viper V770 Ultra
3Dfx Voodoo 2 12MB SLI
SATA 150 TXII + 80GB WD SATA, 40GB WD IDE, Creative SB Live
Win98 SE Dx9.0c, IIyama Vision Master 1451 19"

Reply 1 of 5, by auron

User metadata
Rank Member
Rank
Member

i'm not sure, but could it have something to do with the hi-def pack? did you try with that on/off? i'd also try installing the 1.0.0.1 patch for blue shift. what are the exact reasons for not just going with d3d anyway?

it's mildly interesting that they recommend to actually use d3d on these old 3dfx cards because if memory serves, in the readme for uplink (and maybe even the original release) they say to use the 3dfx minigl for v1/v2 and explicitly state that d3d is not supported on those cards, but then again three years passed in the meantime.

Reply 2 of 5, by Garrett W

User metadata
Rank Member
Rank
Member

There is no 3Dfx mode, what you are trying to run is the OpenGL renderer using the 3Dfx miniGL driver.

I'm not really sure you need the MiniGL for Voodoo2 SLI, but just in case, try updating it using either version 1.47 or the latest one, 1.49.
If using the MiniGL driver keeps producing the same error, try running it without it, just use the OpenGL ICD that should be installed when using the latest drivers for Voodoo2 cards.

Is the rest of your system the one your signature? If so, then using both a Voodoo5 and Voodoo2 cards could complicate manners a bit. I've never tried such a combo, so I have no real comment on .dll switching and the like. WickedGL further complicates things and I'm not really sure you really need it. I haven't used it since ~2009 or so, if I recall it's a faster MiniGL driver, right? Does it supplant the OpenGL ICD driver in the system? If so, it could be causing you all sorts of headaches.

Reply 3 of 5, by Aebtdom

User metadata
Rank Member
Rank
Member

Well the difference between 3dfx mini driver and d3d is that with the first one on half-life my fps are pinned on 99fps and this never changes during the game. On D3d I have framedrops down to 45fps (still really playable) but if it is possible, I'd prefer the mini driver.

But what Garrett W says, makes a lot of sense. Since there is no 3dfx splash screen either. I will try to run some comparisants in performance on the earlier released HL and HL:OF between de mini driver and default openGL and D3D.

And yes, It sometimes is a pain in the butt to run the voodoo 5 next to the vd2 sli, but it is manageble.

AMD XP2400+, 768MB DDR 333, GA-7VRXP KT333
Diamond Viper V770 Ultra
3Dfx Voodoo 2 12MB SLI
SATA 150 TXII + 80GB WD SATA, 40GB WD IDE, Creative SB Live
Win98 SE Dx9.0c, IIyama Vision Master 1451 19"