Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Diablo 3 mousebug - since 2.6.1 mouse-downs register as mouse clicks #298

Open
andreasgu opened this issue Dec 13, 2017 · 0 comments
Open

Comments

@andreasgu
Copy link

In Diablo 3, mouse-downs (pressing and holding the mouse button) often register as mouse clicks (pressing and immediately releasing the mouse button) which make the game nearly unplayable.

there is a workaround on winehq that explains how to fix this bug in wine-staging by compiling wine-staging without the "server-send_hardware_message" patch or by compiling wine-vanilla with only the "kernel32-SetFileCompletionNotificationModes" which are necessary for the battlenet client.

here the link: https://bugs.winehq.org/show_bug.cgi?id=44032#c6

this workaround worked fine for me if i do not use "gallium nine".

wine-vanilla + d3d9 + kernel32-SetFileCompletionNotificationModes (with deactivated "gallium nine") is playable without mousebug but because of the missing gallium-nine with poor performance.
if i activate "gallium nine" in winecfg the performance is good but the bug appears that makes the game nearly unplayable.

same if i compile wine-any (which is "wine-vanilla" + "staging patchset" + "gallium nine") without the "server-send_hardware_message" patch. the game is playable normal without mousebug until i activate "gallium-nine".

looks like the "gallium nine" patchset includes something similar to the "server-send_hardware_message" patch of the staging-patchset that cause the problem on wine-staging.

something like one year ago i was trying how to improve the the diablo 3 performance and i have made a testinstall with "windows version" set to "windows 7" and i got exactly the same problem with my mouse! before diablo 3 patch 2.6.1 (that requires windows 7) windows 7 havent been required and i have been able to switch back to "windows xp" as a workaround.

it looks like that the "server-send_hardware_message" together with "windows 7" as windows version cause the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant