[Bug 55642] New: Diablo 2 mods: Connectivity issues
https://bugs.winehq.org/show_bug.cgi?id=55642 Bug ID: 55642 Summary: Diablo 2 mods: Connectivity issues Product: Wine Version: 8.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mysteryx93(a)protonmail.com Distribution: --- Diablo 2, Project Diablo 2 mod https://www.projectdiablo2.com If launched via Lutris, it fails to connect at all: "Cannot connect to Battle.Net". If launched via Bottles, it connects, but I get 1000ms lag spikes. Either way, the game is unplayable. Running it in a VM works fine. OS: Garuda Linux -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55642 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC| |o.dierick(a)piezo-forte.be --- Comment #1 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, Issues in a single application are severity level 'normal'. Read more about severity levels descriptions there: https://wiki.winehq.org/Bugs#severity Please read & follow the bug writing guidelines: https://wiki.winehq.org/Bugs - Retest in a clean wineprefix, without any third party software. - Attach a normal (=without WINEDEBUG) terminal output. Instructions to get a log can be found there: https://wiki.winehq.org/FAQ#get_log - Make sure that the base game is playable before using mods. Regards. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55642 --- Comment #2 from Etienne <mysteryx93(a)protonmail.com> --- Now this is interesting. I followed these steps and ran it directly through WINE installed in the default location via the command-line. It worked perfectly!! In Lutris, I try to disable "Prefer system libraries" and enable "Disable Lutris runtimes" and it still fails to connect. Any idea of some settings that could be causing the problem? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55642 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #3 from joaopa <jeremielapuree(a)yahoo.fr> --- Third party software is not supported here. If vanilla plain wine works and not third party please report to Lutris. This bug should be closed as INVAILD. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55642 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Resolution|--- |INVALID --- Comment #4 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- (In reply to Etienne from comment #2)
Now this is interesting. I followed these steps and ran it directly through WINE installed in the default location via the command-line. It worked perfectly!!
In Lutris, I try to disable "Prefer system libraries" and enable "Disable Lutris runtimes" and it still fails to connect.
Any idea of some settings that could be causing the problem?
Hello, There could be a number of additional things that Lutris does, like installing windows components with winetricks or changing DLL overrides, or other settings that you can't just revert easily. You may check that by running winecfg in both wineprefixes and compare the settings. You could also compare windows registries for changes in specific Wine keys (See [1]). If you find something, you should report it to Lutris. I'm not familiar with Bottles, so I can't tell why there are lag spikes there, but you could compare the settings there too. Again, if you find something, you should report it to the Bottles maintainers. [1] https://wiki.winehq.org/Useful_Registry_Keys Regards. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55642 --- Comment #5 from Etienne <mysteryx93(a)protonmail.com> --- Interesting; playing with vanilla WINE, every now and then, I start having those 1000-3000ms lag spikes. Once it starts lagging, I have to close the game for it to come back. Happens seldomly and very randomly, so hard to reproduce... I can run the log to file; but by the time the problem happens, it might be 150mb+ in size... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55642 --- Comment #6 from Etienne <mysteryx93(a)protonmail.com> --- There is indeed a connectivity issue with Wine vanilla. It takes a while to reproduce, but once it happens, the only way to fix it is to close the game. Join back the game and it's back to normal. Full log file is 118MB. Can download it here. https://mega.nz/file/zEQgAbTK#g9Cus9K3UJu6sLipVvclQSonv6Uo58RfOvXQ6D-ux_Q -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55642 Etienne <mysteryx93(a)protonmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |--- Status|RESOLVED |REOPENED --- Comment #7 from Etienne <mysteryx93(a)protonmail.com> --- Bug reproduced with log. Reopening. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55642 --- Comment #8 from Etienne <mysteryx93(a)protonmail.com> --- Some more update on the issue. On Windows, sometimes I get 1000-3000ms lag spikes, then the game comes back to normal. On Linux, the lag spikes remain and breaks the game until I quit and rejoin. Those quick lag spikes on Windows seem to coincide with when the problem starts on Linux. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla