https://bugs.winehq.org/show_bug.cgi?id=52835
Bug ID: 52835 Summary: Controller device gets permanently assigned as xinput ONLY or dinput ONLY on prefix creation, depending how the prefix was created. Product: Wine Version: 7.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: xinput Assignee: wine-bugs@winehq.org Reporter: twilight312+winebugzilla@gmail.com Distribution: ---
Created attachment 72227 --> https://bugs.winehq.org/attachment.cgi?id=72227 winecfg-dinput.log
Dear wine developers, Depending on if the prefix was first created by running ``wine control`` or ``winecfg``, my controller device gets permanently (for that prefix) assigned as either ``dinput`` ONLY device (being not visible for application that accepts only ``xinput`` devices), or as ``xinput`` device, allowing to be used by said application. Once the prefix is created, there is no way to change how the device will be seen on wine's side.
Specifically: If prefix is first created by running ``wine control``, the device will be ``xinput`` (see log ``wine-control-xinput.log`` from creating the prefix and ''xinput.png`` screenshot for ``wine control`` joyapplet content).
If prefix is first created by running ``winecfg``, the device will be ``dinput`` (see logs ``winecfg-dinput.log`` from creating the prefix and ``wine-control-dinput.log`` from running ``wine control`` there, also ''dinput.png`` screenshot for ``wine control`` joyapplet content).
All logs are made with: WINEDEBUG="+plugplay,+hid,+xinput"
It is worth adding, that any prefix affected by the bug (as in - controller device not usable by application expecting ``xinput``) will have the controller WORKING as ``xinput`` if the prefix will be run with Wine 6.16 or earlier. The bug is present in Wine 6.17 already (despite no separate ``dinput`` and ``xinput`` fields in ``wine controll`` joyapplets, those appeared in Wine 6.18).
Cheers, /CatLady