https://bugs.winehq.org/show_bug.cgi?id=53028
Bug ID: 53028 Summary: gamepad buttons stopped working correctly Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: piotr5@netscape.net Distribution: ---
ever since upgrading to wine-7.0 my gamepad got reduced to having only 10 functioning buttons and just 5 axes are actually doing anything. I now downgraded to wine-6.0.2 and it has all 14 buttons and 6 axes again. (actually now there are 2 devices of the same name detected, both have 8 axes, the second device is spreading the last 2 axes into being horizontal, while the first correctly assigns a 2d-movement analogue to one axis and nothing to the other. so I disabled the 2nd one.)
to be precise, "wine control.exe" has a program for testing my gamepad, and there wine-7.0 is showing me only 10 buttons and 8 axes, of which only 5 are moving. in some game I had assigned one of the missing keys to an action and moving the axis which isn't perceived by wine sometimes triggers that missing button -- cannot see anything like that in this test program.
I'm on gentoo linux, wine-vanilla is the only package providing wine there, and stable versions are just 6.0.2 and 7.0. installing newer versions doesn't work for me since it needs vulkan (winegcc aborts with function vkd3d_* not defined errors in wined3d.spec) which I have not installed. is it worth upgrading, or has that joystick bug not been fixed yet?
https://bugs.winehq.org/show_bug.cgi?id=53028
--- Comment #1 from Rafał Mużyło galtgendo@o2.pl --- Difficult to say, but while there had been slipups (even ones with quite annoying regression crashers), generally speaking, sticking to 'stable' wine doesn't work all that well.
IIRC, there had been a vaguely similar sounding bug fixed lately, but as I pretty much don't use anything besides mouse and keyboard (despite having an old joypad), I can't say anything definite.
https://bugs.winehq.org/show_bug.cgi?id=53028
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, hardware, | |regression, source Status|UNCONFIRMED |NEEDINFO Distribution|--- |Gentoo Ever confirmed|0 |1
--- Comment #2 from Ken Sharp imwellcushtymelike@gmail.com --- The only way to know if something has been fixed is to try the newer version. You can build Wine yourself and install it alongside the one provided by your distribution (configure --prefix=).
A regression test would help a lot too.
https://bugs.winehq.org/show_bug.cgi?id=53028
soredake gi85qht0z@relay.firefox.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gi85qht0z@relay.firefox.com
https://bugs.winehq.org/show_bug.cgi?id=53028
Rémi Bernon rbernon@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rbernon@codeweavers.com
--- Comment #3 from Rémi Bernon rbernon@codeweavers.com --- Having 10 buttons and 5 axes is expected for any gamepad, as we now expose them as XInput-compatible devices.
XInput-compatible devices are now exposed exactly as they do on Windows, to the DInput API through this compatibility, and limited, interface. Through this interface for instance, trigger axes are combined together, and some games expect this to be the case (Jade Empire for instance).
These devices are also now correctly exposed to the XInput API too, and should be more fully featured in that case when it is used by any game.
It is possible to revert that behavior and override the device so that it is exposed fully, but only, through the DInput API. To do that, open the joystick control panel (which can also be used to validate how both APIs are seeing the devices), with `wine control joy.cpl`, then use the "Override" button to override the device for DInput API only.
The "Reset" button can be used to revert that change. Note that it might then be necessary to restart the application for the changes to fully take effect.
If this isn't solving your problem, it would be nice if you could attach a log file when starting some Wine application, with the WINEDEBUG=+hid,+dinput,+xinput,+input,+rawinput environment variable set.
https://bugs.winehq.org/show_bug.cgi?id=53028
Rémi Bernon rbernon@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Resolution|--- |FIXED
--- Comment #4 from Rémi Bernon rbernon@codeweavers.com --- Marking this as fixed as I don't think there is any regression. Please check the described workarounds and re-open if there is indeed something wrong.
https://bugs.winehq.org/show_bug.cgi?id=53028
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #5 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 8.0-rc2.
-
WineHQ Bugzilla