[Bug 20395] Mouse / keyboard input not handled (RawInput)

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=20395

--- Comment #132 from voidcastr <cephryx at gmx.net> 2012-09-12 04:42:37 CDT ---
After compiling and testing the latest git version with Guild Wars 2 (in which
the camera is rotated around the character by holding down the left or right
mouse button and then dragging), I made the observations listed below. Please
understand them as a feedback directed to providing viable information for
debugging.

- Basically, the camera can now be turned using the mouse.
- Doing so has a major impact on the game's performance. For me, it drops from
40-50 to ~3 FPS.
- Actually, trying to turn the view with the mouse is not even necessary to
cause the FPS drop: Simply moving the cursor e.g. in a constant circle, not
even pressing a mouse button, leads to the very same result.
- Moving the cursor was already possible before the patch was merged to the
git. Thus, it seems to me like the game only uses the raw input path when
click-dragging the mouse.
- Before the patch was merged, moving the pointer did not cause a performance
drop.
- The previous two points seem to contradict -- I suspect a conflict/bug
somewhere in there.
- Turning the view with the keyboard is perfectly smooth, but it cannot be
considered an option regarding gameplay.
- All in all, the camera angle kind of performs jumps instead of smooth
transitions. This makes the game unplayable.

I'm quite sure to speak for many gamers out there when I say: Thank you for
your efforts, Henri - we greatly appreciate your work! Ofc, this also goes to
anyone else who was involved.

Anyway, we'd love to see further improvements on this - it looks like raw mouse
input is almost done except for performance tweaks.

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.