
- #Retroarch windows gamepad wont configured driver#
- #Retroarch windows gamepad wont configured for android#
This problem is not related with X-Input Software because error happened at HID Gamepad device, not at X-Input. It looks I'm not the only one with this kind of issue:Īnd this is what the gamepad maker told me:
#Retroarch windows gamepad wont configured driver#
Shaks X-input driver detects that situation and doesn't allow the gamepad usage. Kindly note that to change between "Windows" (X-input) and "HID" (Android) modes, I have to forcefully delete old pairing and pair again, so it should discard the "you haven't paired the gamepad in the proper mode" that happens often.
#Retroarch windows gamepad wont configured for android#
I will check with Retroarch for Android when possible. I have just tested that,but on HiD mode, the disconnect message spam still persist. If it works in D-input mode, I believe the culprit would be the wrapper itself. I guess the device would still be recognized as an ordinary D-input controller, so it is just a matter of seeing if there is an autoconfig file readily available and, if that is not the case, you can configure the inputs manually on RA.

Windows into thinking it's an XBOX 360 gamepad for X-input support.

I'm using a bluetooth gamepad (Shaks S2 -> ) that a Window driver that tricks

I think that "Gamepad disconnect" messages should have a counter or something to avoid Since they can't be disconnected or limited, they distract from the game or whatever you are doing at. Retroarch will give "HID gamepad disconnect" messages forever. Forgive me if this is not the right place to post this.
