More autocfg pads #23
Conversation
Reported by [email protected] in google code issue tracker (601). Note: user reports that Start button "is not running correct" and in that case button(7) [ie Right Axis button] could be used as a workaround.
Reported by [email protected] in google code issue tracker (629). [email protected] also reported that Huija prefix was not necessary for him, that's why I added both descriptors.
Reported [email protected] in google code issue tracker (426).
Reported by [email protected] in ControllerSetup page comments.
Reported by [email protected] in ControllerSetup page comments.
Reported by [email protected] in ControllerSetup page comments.
|
The way that the joystick name matching code works, is that it subdivides the name into words separated by spaces, and then it searches for each word in each candidate section of the InputAutoCfg.ini file. A couple of artifacts of this process are that all of the extra spaces in a joystick name like this are unnecessary: [Honey Bee AIRFLO ] Also, these 2 sections are effectively the same: [USB Gamepad] In this case, the second section will never be used because anything that would match this would also match the first section. |
|
I didn't know about that subtlety.
|
|
I tend to think that it's a defect in SDL (or the USB device drivers) to have such generic device names. I would recommend just picking one of the configurations for the USB Gamepad joystick. |
|
Hello I am new to git but i would like to contribute I am using a [Xbox Wireless Adapter for Windows] Mupen (M64py) dosnt recognise and save my controler |
Xbox One wireless controllers (at least on Win 10) are recognized as [Controller (Xbox One For Windows)]. Autoconfig.ini is already patched on current master branch for those controllers and is working ok. |
4 participants
I went through the google code issue tracker and ControllerSetup comment section to upstream user-provided gamepad configurations. As I don't own any of the device mentioned, I cannot test if those settings are correct or not.
If this PR gets merged, issues 426, 601 and 629 from the google code issue tracker can be closed.