search

murkl / d2launcher

Diablo II • Median XL • Mod Launcher for Linux
https://github.com/murkl/d2launcher/releases/latest
37 stars 7 forks source link

Median XL fails to launch when D2Stats is running. #22

Open Oroborius opened 1 month ago

Oroborius commented 1 month ago

Running D2Stats under D2's wine prefix causes the game to not be able to launch, reports c0000005 error. This is also the case with the latest D2Stats.

Method of install and start:

  1. Install base 1.14b via Lutris and manually running the installers (providing the necessary keys).
  2. Update to 1.14d via Battle.net.
  3. Run d2launcher.
  4. Apply latest MXL patch.
  5. Install D2GL.
  6. Install and run D2stats (via d2launcher)
  7. Run Diablo II (via d2launcher)
  8. Witness game crash when d2stats is running.
  9. Close d2stats, run game, game runs fine.

System specifications: OS: Arch Linux Kernel: Linux 6.10.10-arch1-1 DE: KDE Plasma 6.2.0 WM: KWin (Wayland)

Not sure how to get this running if at all but D2Stats is sort of a staple at this point. However not sure if it's just a Linux or Wayland bug when it comes to DLL Injection but that's a common theme in Wine.

Here's also the d2launcher.log

Oroborius commented 1 month ago

Confirming it also fails to launch when using cnc-ddraw

murkl commented 1 month ago

Thanks for the report. I use Arch with Gnome and Wayland and have just tested and it works for me (using cnc-draw). Are you using the default config for d2launcher?

Oroborius commented 1 month ago

Everything was default, I had spoken with Thorinori on Discord and unfortunately we had identical setup scenarios with no luck with his working and mine not. Even under identical circumstances to the point of using the same wine.

Unfortunately due to an odd bug on latest packages after testing Sunshine for use with a friend OS on Wayland managed to brick itself so I can't actually test anything anymore for KDE Arch Wayland sadly.

murkl commented 1 month ago

Okay, but of course that makes it difficult to solve it now :) I also tested around a bit (also with D2GL) and got the same error when the D2 video test is set to 3dfx instead of D2GL. Maybe that was a similar cause for you.