Stealthmaster wrote:I guess I'll just wait for the final release. Nevertheless, thanks, Quirinus for your work!
Not sure if you re-downloaded the installer and tried again, I'm pretty sure it will work if you do that. It would help me if you tried.
Talic wrote:Marco wrote:Features:
- Installs Median on any Diablo II version.
Interesting, luckily I do read log files, and log say "Error: patch_d2.mpq doesn't exist in "Game directory"".
I thought we can install it on any version, anyway, here are some screens:► Show Spoiler
EDIT: Works fine with glide, default settings since I just installed diablo once again just to test the launcher.
Marco wanted to say that it will turn any D2 version into 1.13c, and that if it's some old median or other mod version, it will offer to install MXLU XVI (aka 16.1.0), not that it will allow you to run any D2 version and any mod.
Glad to see it works.
@ShadowDawn:
Thanks for the PM, glad to see the game works now.
As for the glide thing, I'll check it out.
Can you open regedit, and check the registry entry for "Game.exe" in HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers ? What is the value of that key?
Kyromyr wrote:Uninstalled, re-downloaded setup and getting different errors now. This appears when setup finishes if run without administrator privileges.
The unlink error no longer appears on start, but this does. Version number loads afterwards, 16.1.10 with a link to the changelog. Loading icon doesn't disappear, settings stay greyed out and there's no option to start the game.
Replacing the median patch_d2.mpq with the cLoD one made the install button appear. Patch downloaded correctly, followed by the same callback error. Gonna try reinstalling the game and see if that fixes it.
Error log (pastebin)
The first error is not important, it's probably because you reinstalled over the old launcher, and it has admin rights, but the installer doesn't, so it can't run it. If you run the launcher manually it will work. I'll fix this soon.
----- wrote:I hope you all will care about us Linux Wine users.
Error during install (after choosing directory, etc.):
https://pastebin.com/raw/56hDZSN2
After this failed install, here is the error with wine Median\ XL.exe:
https://pastebin.com/raw/gndM8LNq
BTW I follow you on Github...I imagine this is a private repo?
Never used wine, so I can't give wine support. Sorry.
Maybe I can check that after I've ironed out the beta version.
Yeah, the repo is private, at least for now.
Talic wrote:@Kyromyr
That first error is not so important imo, it "started" with the "next" .exe file after Quirinus said to re-download.
It should open that window after setup finish where you select diablo 2 game folder but instead that error shows up.
That occurs if you install median launcher outside the diablo folder, if is installed inside diablo folder all should be ok, without that error.
Yeah, something like that, as I wrote above. It remembered to run the launcher as admin from the previous installation, but if you install it in another place it, then the laucher exe doesn't have the "run as admin" flag.
Kyromyr wrote:Callback error resolved. Seems to happen when D2VidTst.exe isn't in the diablo 2 directory. Seems like everything's working now. Game runs without issue in all three video modes.
Opening and closing the settings screen eight times causes the program to soft-lock. Switching to glide has a small but noticable delay before the glide options appear. The play button has no visual feedback when pressed, and still accepts clicks while fading out.
I somehow managed to crash the program while fiddling with starting the game and closing an instance while the two-instances-only message was open, but didn't take a screenshot and can't seem to reproduce.
Edit: Can't say I'm too thrilled by it forcing the game into xp sp3 compatibility mode.
The callback error isn't a problem in itself (I just had one too many, fixed it), but what causes it. It's something with copying the D2VidTst.exe (unlink = delete), as you figured out. It should copy it to the D2 folder if it's missing, no idea why it didn't work for you. Maybe something with paths, I'll figure it out.
Yeah that soft lock is weird, I've seen it before, not sure if it's caused by the platform that's used by the launcher (in which case I can't do anything about it), or the code itself (will try to see in more detail if I can find what's causing it.
Switching to glide delay is normal. I'll try to speed up the whole launcher in the future, but it's not a priority now.
Yeah, good point about the Play button, I'll add a pressed effect.
Weird about the crash error. Anyway, the right way to open 2 instances of D2 is to just un-minimize the launcher and press play again.
The compatibility mode is useful to fix some problems. Can you tell me what do you not like about it so I can see if I can do something about it?
Segolia wrote:Oh boy, lets see how this goes on windows 10
---
Quick, easy, and absolutely zero problems. Very nice guys! I was expecting at least one error being on W10 o_o
Awesome!
Seekers wrote:Is launcher compatible with d2se? (As in, if I install it and my D2 folder has D2SE, will it not work at all or will D2SE get deleted/not work)
The launcher will replace patch_d2.mpq with the median xl one and D2 game.exe with the 1.13c version, so the only thing that will be different in D2SE is that it will launch MXL instead of cLoD if you click on cLoD in D2SE, everything else should be fine.
Edit: I think it should all work fine, D2SE has its core files separate from D2. So the launcher and D2SE should both work.
Thanks for all the feedback, I really appreciate it!