Asteldm wrote:I now have this issue after the update.► Show Spoiler
RequiemLux wrote:Asteldm wrote:I now have this issue after the update.► Show Spoiler
I'm not sure there is a proven solution right now fro that problem connected to the latest Win10 updates, and if there is I've probably missed it.
Anyway you might try a couple of things:
- Make sure that Diablo II.exe is set to run as an Administrator and in compatibility mode with Windows XP (Service Pack 3) and the Launcher is set to run as an Administrator. Then restart the PC.
- Uninstall both the Launcher and Diablo2+LoD, make sure your PC has not leftovers of Median and Diablo2 (use a cleaning software if needed, like Iobit Uninstaller for example). Restart the PC and install Diablo2+LoD again, make sure it runs fine, then download and install (running the installer as an Administrator) the latest iteration of the Median Launcher.
If the above didn't solve anything, if you're okay we could try a little experiment:
Backup your original glide3x.dll file into another folder, and replace it in its original place with this. It's an updated .dll from Zeus Software nGlide, maybe the problem doesn't present itself using this one, just an experiment.
Asteldm wrote:RequiemLux wrote:Asteldm wrote:I now have this issue after the update.► Show Spoiler
I'm not sure there is a proven solution right now fro that problem connected to the latest Win10 updates, and if there is I've probably missed it.
Anyway you might try a couple of things:
- Make sure that Diablo II.exe is set to run as an Administrator and in compatibility mode with Windows XP (Service Pack 3) and the Launcher is set to run as an Administrator. Then restart the PC.
- Uninstall both the Launcher and Diablo2+LoD, make sure your PC has not leftovers of Median and Diablo2 (use a cleaning software if needed, like Iobit Uninstaller for example). Restart the PC and install Diablo2+LoD again, make sure it runs fine, then download and install (running the installer as an Administrator) the latest iteration of the Median Launcher.
If the above didn't solve anything, if you're okay we could try a little experiment:
Backup your original glide3x.dll file into another folder, and replace it in its original place with this. It's an updated .dll from Zeus Software nGlide, maybe the problem doesn't present itself using this one, just an experiment.
I mean I don't get any errors but it doesn't follow the glide settings. It goes full screen even after configuring to windowed.
While launching one second its fullscreen one second its windowed then back to fullscreen and then the picture loads where I can select sp or realm.
RequiemLux wrote:Asteldm wrote:RequiemLux wrote:Asteldm wrote:I now have this issue after the update.► Show Spoiler
I'm not sure there is a proven solution right now fro that problem connected to the latest Win10 updates, and if there is I've probably missed it.
Anyway you might try a couple of things:
- Make sure that Diablo II.exe is set to run as an Administrator and in compatibility mode with Windows XP (Service Pack 3) and the Launcher is set to run as an Administrator. Then restart the PC.
- Uninstall both the Launcher and Diablo2+LoD, make sure your PC has not leftovers of Median and Diablo2 (use a cleaning software if needed, like Iobit Uninstaller for example). Restart the PC and install Diablo2+LoD again, make sure it runs fine, then download and install (running the installer as an Administrator) the latest iteration of the Median Launcher.
If the above didn't solve anything, if you're okay we could try a little experiment:
Backup your original glide3x.dll file into another folder, and replace it in its original place with this. It's an updated .dll from Zeus Software nGlide, maybe the problem doesn't present itself using this one, just an experiment.
I mean I don't get any errors but it doesn't follow the glide settings. It goes full screen even after configuring to windowed.
While launching one second its fullscreen one second its windowed then back to fullscreen and then the picture loads where I can select sp or realm.
So using the .dll I attached the error doesn't occur but you are unable to fully configure it? I suppose for now it would be better to replace the .dll with your backup one and use another video mode for the time being.