[Bug 44032] New: Diablo 3 2.6.1: Mouse-downs register as mouse clicks

wine-bugs at winehq.org wine-bugs at winehq.org
Tue Nov 14 16:26:18 CST 2017


https://bugs.winehq.org/show_bug.cgi?id=44032

            Bug ID: 44032
           Summary: Diablo 3 2.6.1: Mouse-downs register as mouse clicks
           Product: Wine
           Version: 2.20
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: minor
          Priority: P2
         Component: -unknown
          Assignee: wine-bugs at winehq.org
          Reporter: sts33nvyb at gmail.com
      Distribution: ---

Created attachment 59696
  --> https://bugs.winehq.org/attachment.cgi?id=59696
Terminal output (not that I expect this to be useful)

In Diablo 3, mouse-downs (pressing and holding the mouse button) often register
as mouse clicks (pressing and immediately releasing the mouse button).  This
happens for approximately 50% of the mouse-downs when playing the game, which
dramatically changes how the game plays, since holding down the mouse button is
used for both moving and attacking continuously in the game.

I'm running wine-staging 2.20 on OpenSuse 42.3 x86_64.

This is for the current version of Diablo 3, version 2.6.1.47919 32-bit.  Note
that Diablo 3 recently dropped support for Windows XP; since this change,
Diablo 3 no longer works in non-staging wine at all.  Also, the 64-bit version
of Diablo 3 has severe performance problems in wine-staging 2.20, so this is
using the 32-bit version of Diablo 3.

I speculate that some bug in wine is causing bogus mouse-up events to sometimes
be generated immediately after mouse-down events.

Note that this is a completely different bug from bug 31262.  Note that user
"pakos" has mistakenly commented about this bug in that bug report, dated
2017-11-13.  He reports that this problem is present in versions of
wine-staging at least back to 2.5.

There has been some discussion of this bug on the application page.  Some users
have reported that changing wine's virtual desktop setting, forcing 32-bit
using setarch, or changing Diablo 3's settings to windowed-fullscreen instead
of fullscreen alleviated the problem.  None of these helped for me.

-- 
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.



More information about the wine-bugs mailing list