bayaraa
Voodoo GLIDE2X
Could a voodoo 1 GLIDE2X.dll be made to work? I tried renaming glide3x to 2x. Don't know if it's working. I'm on win98se and Diablo 2 classic. I know i know I read the compatibility list and thought I'd try it anyway. I've been tinkering with the other mods in conjunction with this one.SGD2Freeres and FPS mod. It definitely seems like something is speeding my game up. Trying to track that down right now. I've used the ddraw.dll as well. I'm using Dosbox-Pure on Retroarch. Which uses openGL hardware acceleration for voodoo1.
If u are not sure if it is working i suggest you to open 2x Copies of the game separately one with the GLIDE2X.dll and another one with the glide3x and see if u notice any difference !
its hard to run 2 copies simultaneously on win98se using dosbox on my phone. renaming it to 2x doesn't give any errors...Also pressing ctrl-O doesn't bring up D2Gl options.
This is never going to work.
- Diablo II, IIRC, requires a Voodoo 2 or higher.
- You cannot use a Voodoo card with D2GL: D2GL translates GLIDE3 to OpenGL so your emulated Voodoo1 won't work and you will use your OS's software OpenGL render instead (at least on Win95 and NT4).
- At least on XP, Diablo II will only load glide3x.dll when launched with "-3dfx":
cd C:\path_to_d2
Game.exe -3dfx
- Renaming glide3x.dll to glide2x.dll will just break D2GL and prevent it from working.
- If you press [Ctrl]+[o] and do not get the D2GL menu overlay... D2GL is not working/loaded. Simple as that.
What you should do, is run Diablo II under Wine (or whatever port there is of Wine for phone's OS) using version 1.14d, and then it will work. Make sure you have ALL the .MPQ files in your Diablo 2 directory (D2*.MPQ and D2X*.MPQ) so you don't need to fool around with emulating a CDROM drive and loading ISO files.
In any case, DOSBox is a bad idea for Diablo II. It works great for Diablo I and Hellfire though. But DevilutionX is vastly superior to running DOSBox, as it is a native binary.
Worst case scenario, you could use 86Box to emulate a Voodoo3 with a Win98SE guest. This would provide full OpenGL rendering on the hypervisor (your phone's OS) and GLIDE3 for rendering Diablo II on the guest OS (Win98SE). And no, you can't use D2GL on the guest OS unless the emulated GPU supports OpenGL.
Funny because im playing Diablo 2 on Win98 using an emulated Voodoo 1 card that uses hardware GL (gles 3.0).
Just because you have an emulated Voodoo 1 avaliable doesn't mean it is being used. You are likely using D3D or DDraw, not Glide. Look up the game's specs, it uses glide3x.dll which is only supported on Voodoo 2 and higher.
I think you are very confused how emulation on the host and the Windows guest graphics stacks work.
I use D2 vidtest and that gives me a glide option which i use then just to make sure i use -3dfx from the command line. So from my end it appears to be using glide. The emulated video card is a voodoo 1 and 2. its either or depending on how much v-ram you choose. Just saying im pretty darn sure its using an emulated voodoo card, plus the emulated card is capable of doing things an original could not. And no im not confused, because ive been doing emulation trickery for a long time and you'd be suprised how you can get things to run that technicaly should not by doing stuff like for instance renaming glide3x to glide2x, but in this case that does not work. I'm using Dosbox-Pure through RetroArch on iOS and it mentions specifically that glide is used through its voodoo emulation.
The easy way to tell if you are using GLIDE is to observe the game lighting. DDraw will look darker/grittier while GLIDE will be very bright. 3DFX turned up the gamma to make games appear to "look better" subjectively to gamers, which pissed off a lot of game makers and other video card mgfs at the time.
And, again, D2GL translates GLIDE3 to OpenGL 3.3. An emulated Voodoo wants to consume GLIDE not OpenGL--but you can get Voodoos to use really old OpenGL API, but it won't be new enough for D2GL to work (requires newer OpenGL features that are not available with old 3DFX OpenGL to GLIDE wrappers).
The Voodoo 1 won't work with D2, so you would need to emulate, at the very minimum, a Voodoo 2.
The -3dfx argument only works for version 1.14b and up -- read the patch notes:
- Patch 1.14b
Specific Changes & Improvements
- Glide Wrapper will now load properly on PC by adding -3dfx to the end of the game shortcut
- Mercenaries will no longer become "An Evil Force"
- Fixed Mac client crash on "Save & Exit"
- Capped the frame rate to 200 to save batteries, spare system load, and prevent hot lap syndrome
- Created new German installers to fix localization issues in Act V (Will require a fresh install to fix the missing dialogue data)
D2GL requirements are:
Diablo 2 LoD: 1.09d, 1.10f, 1.11, 1.11b, 1.12a, 1.13c, 1.13d, 1.14d. Windows 7/8/10/11, Linux with Wine (Proton, Lutris etc), MacOS with Wine (Crossover). GPU with minimum OpenGL 3.3 support.
Let's look at Voodoo OpenGL support:
The Voodoo cards do not support OpenGL; their equivalent API is known as '3dfx Glide', but OpenGL can be accessed effectively using the Glide Miniport Driver (MiniGL 1.48/1.49) ,OpenGL 1.1 ~ 1.0.0.0761 ICD, WickedGL (up to OpenGL 1.2), or MesaFX (up to OpenGL 1.4). These are standalone GL drivers which act as an abstraction layer between the OpenGL application software and Glide 2.x/3.x drivers, respectively. The basic differences:
3dfx Miniport driver: Glide2x, ID software 'Quake' engine games only. (a 'MiniGL') OpenGL 1.1 ICD: Glide3x, almost any software that uses SGI OpenGL 1.1 as its API (a standalone full implementation). WickedGL: Glide2x for Voodoo2/3, Glide3x for Voodoo4/5. Usually works only for the supported games (plus games based on Quake3 engine). MesaFX: Glide3x. Brand-new OpenGL driver, should work with any game or application.
So far, we can say that you need Diablo 2 1.14d to use -3dfx with D2GL, per the patch notes and D2GL requirements. Further, D2GL converts GLIDE3 to OpenGL 3.3, so you cannot use D2GL with any Voodoo natively via GLIDEx and require a GPU with OpenGL 3.3. But the highest OpenGL version ever supported by any 3rd party wrapper was OpenGL 1.4 with MesaFX. So that means D2GL will NEVER work in a Windows XP/2k/NT/9x guest OS using an emulated Voodoo 2 through 5 GPU. And further, D2GL is only supported on Windows 7 or newer. So I don't know why you ever though this was going to be possible.
An option is to use 86box with a Voodoo 5 and run the game natively with GLIDE3 inside the guest OS (WinXP or Win9x) while the hypervisor (86box) will translate that to OpenGL on the host (android/linux) graphics stack. You won't get any of the nice features D2GL provides, but the game will have accelerated graphics and you will get the improved visuals only available with the GLIDE game engine.
The absolute best method is to eliminate the virtual machine entirely and just use Wine to play D2 with D2GL. Much faster gameplay and infinitely simpler (no need for windows, drivers, etc.). You will want to use the SGD2FreeRes mod with D2GL to configure custom game resolutions to better suit your display aspect ratio / resolution.
For help with drivers and hardware capabilities for Voodoos check out: http://helppage.3dfx.sk/
Reading that should clear up a lot of misconceptions regarding what a Voodoo can and cannot do.
For example, with 3rd party drivers the Voodoo 5 can play D3D8 games, but OpenGL caps out at 1.4 with MesaFX.
Regardless, you need to understand how virtual machines work, the graphics stacks used by different operating systems, and why graphics API wrappers exist and how they are used. Without knowing this you will waste your time trying to do something impossible (like use D2GL in a DOSBox Win9x VM with an emulated Voodoo 1).
Yeah i just confirmed dosbox pure uses voodoo 1 but with enhanced capabilities. Yes i see i was wrong about commandline -3dfx not usable 1.05b, i just assumed it did, yet i only get glide option in d2vidtest (which i assume is being used), can it fallback to ddraw? It seems to be using the emulated voodoo 1 because it is enhanced speed versus software rendering. Yep i missed 1.05b not being compatible rats. maybe a future update with somehow overcoming my limitations. i forgot to add that i use JHRobotics wine for win98 and a i believe modified mesafx gl opengl32.dll that i drop in game folder. i used to tinker with exagear for Android and its essentially wine for Android but geared toward gaming with hardware acceleration. i went down this rabbit hole using iOS and dosbox and trying to see if maybe there was a way. plus my win98 installation is heavally modified (slimed through win98 lite, patched with unofficial service pack 3.x (which purportedly gives a blend of XP, vista, win7 environment , and kernelEX. i thought maybe fitting these together could get something to work. fun way to learn about this stuff. lastly dosbox-pure is not a vm.