https://bugs.winehq.org/show_bug.cgi?id=46891
Bug ID: 46891 Summary: Memory Access Error in World of Warcraft 8.1.29814 Product: Wine-staging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: juergen.sauer@automatix.de CC: leslie_alistair@hotmail.com, z.figura12@gmail.com Distribution: ---
Created attachment 63967 --> https://bugs.winehq.org/attachment.cgi?id=63967 crashed app debug dialog
Battle.net.exe works as expected. Patching Wow works also fine.
Entering the Game works. Selection the Char and Menue Access outside the game works.
But entering a Realm end in an Error #132 of Wow.exe, which shows up if the exe code tries to access illegal adress segments.
https://bugs.winehq.org/show_bug.cgi?id=46891
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|blocker |normal CC| |dark.shadow4@web.de
--- Comment #1 from Fabian Maurer dark.shadow4@web.de --- Not a blocker. Does this only affect wine-staging or also vanilla wine?
https://bugs.winehq.org/show_bug.cgi?id=46891
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be
--- Comment #2 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Possible duplicate of bug 46416.
Do you use vkd3d/directx12?
https://bugs.winehq.org/show_bug.cgi?id=46891
--- Comment #3 from juergen.sauer@automatix.de --- No. I do not use vkd3d/directx12.
As I can see, the problem must exist Wine-staging 4.3.1 ... 4.4
I tried 4.2.1 staging, thus is working. In game I can chose "DirectX 11 Legacay", this works fast performant. (1080p @ 40 fps).
Changing to "DirectX 11" (NO LEGACY) fps falls down to 1..3 fps.
https://bugs.winehq.org/show_bug.cgi?id=46891
--- Comment #4 from juergen.sauer@automatix.de --- (In reply to Fabian Maurer from comment #1)
Not a blocker. Does this only affect wine-staging or also vanilla wine?
wine-staging, current has the bug. staging 4.2.1 has not.
https://bugs.winehq.org/show_bug.cgi?id=46891
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #5 from joaopa jeremielapuree@yahoo.fr --- Does the bug still occur with vanilla wine-5.14?
https://bugs.winehq.org/show_bug.cgi?id=46891
--- Comment #6 from juergen.sauer@automatix.de --- Do not know. On daily use case "WowClassic.exe" wine staging 5.9 is really fine. But 5.14 fails to start the game at all. :(