Glide.dll

[Eliecer Brathwaite]

Downloadglide.dll below to solve your dll problem. We currently have 1 version available for this file.

If you have other versions of this file, please contribute to the community by uploading that dll file.

Errors related to glide.dll can arise for a few different different reasons. For instance, a faulty application, glide.dll has been deleted or misplaced, corrupted by malicious software present on your PC or a damaged Windows registry.

In the vast majority of cases, the solution is to properly reinstall glide.dll on your PC, to the Windows system folder. Alternatively, some programs, notably PC games, require that the DLL file is placed in the game/application installation folder.

Do you have information that we do not?

Did our advice help or did we miss something?

Our Forum is where you can get help from both qualified tech specialists and the community at large. Sign up, post your questions, and get updates straight to your inbox.

SST1INIT.DLL/GLIDE.DLL are not meant for anything other than Voodoo1. There are list of 3Dfx env vars for a Voodoo2 to emulate Voodoo1 floating around in the web which you can google it by yourself. If this works, then you're good. For me, that doesn't work reliably when I used to have Canopus 3D2. Frankly, Voodoo2 is only good for Glide 2.4x or beyond.

What I had also done in the past was to create a stub GLIDE.DLL to redirect GLIDE calls from GLIDE 2.11 to GLIDE 2.4x. It worked with MechWarrior 2 3Dfx almost perfectly. Unfortunately, I lost the work due to HDD crash and since dgVoodoo came to the rescue, I void the plan to recreate the work. All I really care back then was MechWarrior 2 3Dfx, and dgVoodoo had been able to do it beautifully.

Cool! I still remember your post to OpenGlide requesting Glide 2.11 support. I seem to recall nagging Fabio to try to get your patch applied. Can't remember where we left that, I _think_ it was applied. Sadly, development pretty much stopped several years back...

-requests/3/

QEMU Glide pass-through supports unique Glide2.1.1 -> Glide2x conversion. Mech2 and Pandy1 were tested and even run with acceleration, that implies state-of-the-art CPU performance for those games. Despite the issue of jumpjets slow recharge rate, Mech2 is amazing playing with such CPU power. I am not as familiar with Pandy1 as with Mech2, but the few first rounds played very well. Cybergladiators and Scorched Planet are last on the list that I haven't checked out.

I have 1 theory about constant "grSstQueryHardware failed!".

P4P800 SE, WinME.

Pcirw.exe from the glide 2.1.1 SDK detects Intel PCI devices only.

Pcirw.exe from the glide 2.43 SDK detects all. But there is the "bus id" column. With 00 for Intel PCI devices, 01 for AGP and 02 for PCI slots...

Maybe glide.dll uses the similar approach (bus_id 00 only) and then grSstQueryBoards and grSstQueryHardware fail the detection.

I think you're right. I seem to recall similar conclusion tracing glide.dll/sst1init.dll that it only search for PCI device on Bus 0 only. Not surprising since the era of 1st Voodoo, all chipsets in consumer's space had Bus 0 for PCI, and PCI bus was the same bus that connected North and South bridges.

@Gamecollector Are you still interested in testing Glide 2.1.1 games on the Voodoo2?

Recent GNU GCC toolchain improvements make writing redirection DLL very simple. I just cooked up a full implementation of Glide 2.1.1 wrapper that wraps into Glide 2.4, ie. glide.dll -> glide2x.dll. It allows me to play Mechwarrior 2 31st 3Dfx on Linux (..finally.. yeah ?)from QEMU KVM with MESA GL pass-through with Zeckensack's Glide wrapper. Pandemonium! also works. I thought I may as well share it out for others to check out for those games on Voodoo2/Banshee/V3/V4/V5.

It requires SSE2 capable CPUs because it was compiled with GCC vector intrinsics for pixel formats conversion dealing with LFB for games that do not make use of Voodoo native LFB write mode which is RGB565. Mechwarrior 2 31st happens to be one, it uses RGB555, so it supports this game.

Unfortunately, getting rid of CMOV instructions will require switching toolchain because of MSYS2/mingw-w64 CRT startup. And, GCC vectorizer only works with SSE/AVX, the i686/MMX build does not seem to generate codes that make use of MMX instructions. So that's about it, I don't think it is worth to spend more time into hand-tuned MMX assembly.

I just tried POD on my 1998 gaming pc (pentium 2 + 3dfx in sli) and the setup doesn't allow me to install the 3Dfx version because I'm "missing" a 3Dfx card. I can only install the regular version or the regular version.

This game "detection" uses a very dumb method. If you have glide.dll and sst1init.dll in the %system% directory - then you have a 3dfx card.

So just create 2 empty files with these names, install then delete these 2 files.

Ubisoft is so Ubisoft.

And yes, the original POD uses glide 2.1.1 (glide.dll and sst1init.dll).

P.S. You can force install the 3dfx patch (21_3dfx.bin) if you run it twice. This will replace others .exes to the 3dfx one. Or ypu can use Pod Gold, it uses the standard method (_grSstQueryBoards).

P.S.S. Another game with this "detection" method: F1 Racing Simulation. Ubisoft related of course... And this case is worse - the game itself uses glide2x.dll but the installer wants glide.dll and sst1init.dll. *Censored*.

replace the glide2x.ovl and glide2x.dll files in the game directory with the ones in your voodoo 2 driver directory. The game comes with voodoo 1 glide files and those don't really work with a voodoo 2.

err ... there are no glide2x.ovl/glide2x.dll in the game directory. Only glide.dll and sst1init.dll (wich is strange since they are actually real files, and not the copy from the ones that I made in order to install the game with 3Dfx)

1) You MUST delete the glide.dll and sst1init.dll files from the POD installation since these files are intended for the original Voodoo card (not Voodoo2). You only need those files in order to install the 3dfx version or patch an existing 3dfx installation. Once you are done patching, remove glide.dll and sst1init.dll from the POD installation and the %system% folder (usually \Windows\System for most users) if you followed Gamecollector's advice above.

2) kanecvr is saying you should put copies of the glide2x.ovl and glide2x.dll from your Fastvoodoo (or whatever driver package you use) drivers into the POD installation folder (don't rename them). Standard 3dfx driver installations put copies of these files into the %system% (usually \Windows\System for most users) folder and most programs will find them without issues, but putting them into the POD installation folder guarantees that that particular Glide .dll and overlay file will be used when you run POD. Hopefully, your Fastvoodoo package put copies into %system%, but you may need to check your documentation to see where it put them.

Okay, I understand now. But deleting glide.dll and sst1init.dll and replacing them by glide2x.dll and glide2x.ovl doesn't work ... The game is really asking for glide.dll (and if I'm using the link that the game made on the desktop, then an ubisoft utilitary is saying that I don't have a 3Dfx card anymore.) : a popup windows is telling me that glide.dll couldn't be found :s

No, the shortcut on the desktop only says that I don't have a 3Dfx card while pod3dfx.exe found in the pod directory displays the error "could not find glide.dll" so I don't think that making a shortcut to that exact exe would make a difference

So if you have the OEM version, you need to apply the OEM Version 1 to Retail Version 2 patch. If you have the ordinary retail POD release (or have upgraded an OEM copy to Version 2 Retail), you need to apply the Version 2.1 3dfx update (since you have a Glide card). The POD Gold release is already patched to Version 2.8 (at least mine is) and doesn't need additional patches.

There are a few patches available for POD. This page will hopefully allow you to work out which one is the right one for you to use. If you need help actually installing POD in the first place, check the Installing POD page.

Over the lifetime of POD, the answer to this question has changed greatly. The choice these days is pretty simple. To get POD to run properly on modern hardware, and to be able to add a greater number of tracks and cars, the patch process now boils down to this:

If you have an AMD CPU - You will most likely need to use the Forcefeedback patch, since this patch is the only one that seems to allow POD to run on AMD CPUs

You will want to use the Game Service 2 patch as well, since it corrects a problem where POD runs too fast on modern hardware, so fast that the game becomes unplayable. It, of course, also allows you to race POD on-line

3a8082e126