https://bugs.winehq.org/show_bug.cgi?id=51745
Bug ID: 51745 Summary: Xbox Controller no longer recognised Product: Wine Version: 6.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: xinput Assignee: wine-bugs@winehq.org Reporter: lemonzest@gmail.com Distribution: ---
Created attachment 70631 --> https://bugs.winehq.org/attachment.cgi?id=70631 XinputTest.exe Test Program for Xinput Controllers
Hi
I just updated to WineHQ-Devel 6.17 and Xinput/Xbox controllers (Not sure about others as don't own any) are no longer detected in games
I have tried Dragon's Dogma, Dead Cells and a couple of others and they no longer react to Gamepad inputs and XinputTest.exe says its disconnected. rolling back to WineHQ-Devel 6.16 all is working.
I am on Fedora 34 with a PDP Afterglow XBox One Controller which in many previous versions worked correctly.
https://bugs.winehq.org/show_bug.cgi?id=51745
Lemonzest lemonzest@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|xinput |-unknown
https://bugs.winehq.org/show_bug.cgi?id=51745
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rbernon@codeweavers.com
https://bugs.winehq.org/show_bug.cgi?id=51745
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
https://bugs.winehq.org/show_bug.cgi?id=51745
--- Comment #1 from Rémi Bernon rbernon@codeweavers.com --- It's likely to be caused by the device driver being cached in the registry, and as a new driver has been introduced, the old driver is not recognized by XInput anymore.
I think this can be solved by re-creating the prefixes, or as a ligther operation, it should also be possible to fix it by removing the registry entries starting with "System\CurrentControlSet\Enum\SDLJOY" (or HIDRAW / LNXEV instead of SDLJOY) in the prefix' system.reg.
I intended to change the device id prefixes (the SDLJOY / HIDRAW / LNXEV part), and that should have also fixed the problem with prefix upgrades, but the patch didn't get accepted (yet).
https://bugs.winehq.org/show_bug.cgi?id=51745
--- Comment #2 from Lemonzest lemonzest@gmail.com --- Deleting those keys under the SDLJOY path you mentioned has fixed my XBox controller
It now works again in those games mentioned and XinputText.exe as before
so thanks for the help, now to update my prefixes!
https://bugs.winehq.org/show_bug.cgi?id=51745
Michael Psyllides spanky_12inch@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |spanky_12inch@hotmail.com
--- Comment #3 from Michael Psyllides spanky_12inch@hotmail.com --- (In reply to Rémi Bernon from comment #1)
It's likely to be caused by the device driver being cached in the registry, and as a new driver has been introduced, the old driver is not recognized by XInput anymore.
I think this can be solved by re-creating the prefixes, or as a ligther operation, it should also be possible to fix it by removing the registry entries starting with "System\CurrentControlSet\Enum\SDLJOY" (or HIDRAW / LNXEV instead of SDLJOY) in the prefix' system.reg.
I intended to change the device id prefixes (the SDLJOY / HIDRAW / LNXEV part), and that should have also fixed the problem with prefix upgrades, but the patch didn't get accepted (yet).
I have the exact same problem and deleting prefix and creating a new did not fix it strangly. However deleting the keys from reg even after creating new prefix worked. (No idea how) BUT I had to delete the keys at least twice.
1) After first delete, loaded a game and no controller input. 2) Loaded reg and deleted key again and started game. This time controller detected.
If it matters. I'm also using xbox controller.
https://bugs.winehq.org/show_bug.cgi?id=51745
--- Comment #4 from Rémi Bernon rbernon@codeweavers.com --- I believe that f37ae29b49089dbb97fe95070aad4444050594e5 force the devices driver association to be invalidated, so the controllers should be working after a prefix upgrade.
https://bugs.winehq.org/show_bug.cgi?id=51745
--- Comment #5 from Michael Psyllides spanky_12inch@hotmail.com --- (In reply to Rémi Bernon from comment #4)
I believe that f37ae29b49089dbb97fe95070aad4444050594e5 force the devices driver association to be invalidated, so the controllers should be working after a prefix upgrade.
Would this have an affect on the controller getting disconnected randomly now?
After we fixed the controller detection issue the controller just disconnects randomly now. Seems to happen around 10 to 30 minutes. Tested on xbox controller ( wired ) and PS4 controller ( bluetooth & wired )
Again this is not happening on v6.16
https://bugs.winehq.org/show_bug.cgi?id=51745
--- Comment #6 from Rémi Bernon rbernon@codeweavers.com --- I don't know about this disconnection issue, it may be another regression.
https://bugs.winehq.org/show_bug.cgi?id=51745
--- Comment #7 from Rémi Bernon rbernon@codeweavers.com --- I've left some XInput test running for a while with a PS4 controller and didn't see any disconnection.
Although I found a few other issues that I intend to send patches for before next release, I think this specific problem should be fixed now and if there's something more another bug could be opened.
https://bugs.winehq.org/show_bug.cgi?id=51745
--- Comment #8 from Michael Psyllides spanky_12inch@hotmail.com --- (In reply to Rémi Bernon from comment #7)
I've left some XInput test running for a while with a PS4 controller and didn't see any disconnection.
Although I found a few other issues that I intend to send patches for before next release, I think this specific problem should be fixed now and if there's something more another bug could be opened.
Thank you. I did more testing today after building the latest copy and the controller seems to be functioning normally now.
https://bugs.winehq.org/show_bug.cgi?id=51745
--- Comment #9 from Hans Leidekker hans@meelstraat.net --- (In reply to Michael Psyllides from comment #8)
(In reply to Rémi Bernon from comment #7)
I've left some XInput test running for a while with a PS4 controller and didn't see any disconnection.
Although I found a few other issues that I intend to send patches for before next release, I think this specific problem should be fixed now and if there's something more another bug could be opened.
Thank you. I did more testing today after building the latest copy and the controller seems to be functioning normally now.
Can we close this bug?
https://bugs.winehq.org/show_bug.cgi?id=51745
--- Comment #10 from Michael Psyllides spanky_12inch@hotmail.com --- (In reply to Hans Leidekker from comment #9)
(In reply to Michael Psyllides from comment #8)
(In reply to Rémi Bernon from comment #7)
I've left some XInput test running for a while with a PS4 controller and didn't see any disconnection.
Although I found a few other issues that I intend to send patches for before next release, I think this specific problem should be fixed now and if there's something more another bug could be opened.
Thank you. I did more testing today after building the latest copy and the controller seems to be functioning normally now.
Can we close this bug?
Yes
https://bugs.winehq.org/show_bug.cgi?id=51745
Rémi Bernon rbernon@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
--- Comment #11 from Rémi Bernon rbernon@codeweavers.com --- Marking as fixed as of 7.0-rc1
https://bugs.winehq.org/show_bug.cgi?id=51745
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #12 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 7.0-rc2.
-
WineHQ Bugzilla