https://bugs.winehq.org/show_bug.cgi?id=51745 Michael Psyllides <spanky_12inch(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |spanky_12inch(a)hotmail.com --- Comment #3 from Michael Psyllides <spanky_12inch(a)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. -- 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.