How to use Glide or ???

I finally got some time to play this weekend and from the new launcher, it says Rendering: DirectX or Glide and gives two unofficial graphics drivers.

1. What program should I use if I want to reshaders / skins, and would that be DirectX or Glide?
2. Based on the above, what driver do I need, and where do I get them?
3. >>How<< do I use the GFX Renderer? I used RESHADSE before, however it does NOT let me log into MP games for some reason now... No idea how these other shader programs work.

Thank you for any replies ahead of time :heart: :yay:

So inside the median-xl folder is glide-init.exe. I forgot this little prog even existed. I made some modifications but everytime I test, Glide just closes down so I'm 99% certain it's not working, and no idea what the problem is. Also, when I try and start MXl with Glide on, it keeps telling me Glide is not compatible with "-w" flag which for one I know is not true because I used to play with Glide in windowed mode, but secondly, I checked both game.exe and diablo II.exe and neither have any extension flags added, not even have the ability to add flags. IN GitHub, Gavin's d2gl requires -3dfx, so if LAUNCHER is opening game.exe, how do I add those flag extensions, and why does it keep saying there is an extension when there are none?

https://wiki.median-xl.com/D2GL_Wrapper this worked for me

oztor wrote:https://wiki.median-xl.com/D2GL_Wrapper this worked for me

Doesn't work. Keeps telling me:

Code: Select all

Unsupported argument detected!

D2GL Glide Wrapper is not compatible with "-w" flag. Remove "-w" flag and run game again.

I went into Diablo II and checked the glide-init.exe and made sure windowed mode is off. I did the same for the median-xl glide-init.exe file. I checked the properties of all "diablo II.exe" and "game.exe" and shortcuts and none have "-w" on them. IDK WTF is wrong with this!

0. I open "median-xl.msi" file and Uninstall Median XL | and | Diablo 2
1. CLEAN install of D2 and LoD in "C:\Games\" so now the full path is, "C:\Games\Diablo II"
2. I download a CLEAN Launcher from here: viewtopic.php?f=25&t=84914
3. I open the "median-xl.msi" file and install median-xl to "C:\Games\Diablo II"
4. I open the launcher and UPDATE. Then I click the COG and select GLIDE and the Hazard sign and select the two gfx drivers, then I hit the 'X' and quit.
******Nothing related to Diablo or the Launcher is open*******
5. I download Gavins d2gl from here: https://wiki.median-xl.com/D2GL_Wrapper
6. I rt-click properties and UNBLOCK it then extract Gavins d2gl directly to "C:\Games\Median-xl" because that's what it says to do (and NOT to "C:\Games\Diablo II")
7. I run LAUNCHER (after making sure it is running as Administrator) and hit PLAY... but I keep getting that fucking error every single time.
8. So at this point, I manually go into the "glide.init.exe" settings of both "C:\Games\Diablo II" and "C:\Games\Median-xl" and uncheck "window-mode" in "settings", then I QUIT to ensure it saves
9. I try to run the LAUNCHER and hit PLAY and get the same fucking error!
10. There is a SHORTCUT in "C:\Games\Diablo II" to game.exe and the shortcut has -direct -w. I just delete the shortcut, then try to run LAUNCHER. LAUNCHER won't run and just spins in circles.... WTF.... Okay, so I create a NEW shortcut to game.exe and exclude -direct -w and hope the LAUNCHER actually works... and it does! Hurray! Now I hit PLAY and get the same fucking error!

Using RESHADE, I had zero problems. But RESHADE does not seem to work with Median XL anymore since the new patch, and honestly, the game looks to me like the wasted pixels of an 8-bit system's leftover graphics without a shader, so I really haven't played much. I can't wait to see how much "fun" I have trying to get the item notifier working, because I loved d2stats previously. Honestly, these last two changes by the MXL team may be the nail in the coffin for my time with this game. I simply don't have the time resources to dedicate to dicking around with this kind of shit anymore. The system was working fine before goddamnit.

It's like Windows 10 keeps prompting me to convert to Windows 11, but I know W11 sells off all your personal data (without you even earning anything from those profits) and inundates you with ads, so I'm like, I'm goon on W10... by MS is sooo fucking pushy, I already installed a Linux backup and if I have any more fucking issues with W10, I will almost certainly switch to Linux using WINE for a sandboxed Adobe Photoshop and MS Office, which are really the only two critical PC program I use, the rest I can live without. My point, there comes a time when you are just pushed too far and are like, "naw, fuck this. It was fine before, I don't like being shoehorned."

Make sure to check the "Full Screen" setting in the MXL launcher settings. You can control the window size in-game via the Ctrl+O settings menu of D2GL.

and turn off Borderless. This error comes, when you enable borderless.
also thanks God, you can continue use d2stats, it can't hide loot, but it still notify you about dropped loot, and yes using it much easier and much more powerful, then ingame loot filter. Use ingame filter only for hiding stuff.

Taem
Sorry if you have issues, wasn't here week ago to help.
Anyway, glide-init.exe by Sven has nothing to do with D2GL by bayaraa/Gavin...

Also, Reshade was/is working perfectly fine on my side but I don't use it since I'm satisfied with the d2gl graphic shaders/settings.

As you can see in the launcher settings, more arguments can be sent to the game, Fullscreen/windowed, no sound, skip to mp...
So when your fullscreen option was unchecked game argument was -w of course and D2GL doesn't like that hence the message, d2gl has its own .ini with the settings it uses.

Will ask Gavin to edit that error window so it says that Fullscreen needs to be checked in the mxl launcher since it seems not all users understand that launcher can affect game arguments.

Sorry, I fixed this issue while ago but haven't had time to post the solution;

For whatever reason, when I uninstalled, there were artifacts leftover that did not remove so on a reinstall, they remained and were somehow affecting the install. To fix, I simply deleted the remaining (actual) D2 and MXL folders entirely, then reinstalled. This completely fixed the issue I was having and now I am using D2GL which I am pretty impressed with, to be honest! The only downside so far is the lack of options for skins and overlays, as opposed to ReShade, not withstanding the lack of options to replace the sidebars without ALSO installing ReShade... Nonetheless, a very nice gfx overlay.