This one might be more of an incompatibility between the device I'm using, the controller I'm using, the OS im running etc.
HOWEVER. In every build past 5.0-5684, it's impossible to bind controls. Everything automatically gets bound to "Moga Pro 2 HID: Axis 32+". If I bind my controls in an old version of dolphin, then i can still use the controls properly in the latest commits. It's strictly a binding problem.
In 5.0-5681, this doesn't happen.
Uh, hackbar I don't hate you or anything lol. I just happened to find two problems in this build.
That's because your controller is missing mappings in the Android. I'll publish my debug app this weekend and have you send me the debugging info for your controller.
Vendor ID: 0x20d6
Product ID: 0x6271
Name: Moga Pro 2 HID
OS version: 7.1.1
SDK version: 25
Manufacturer: OnePlus
Model: ONEPLUS A5000
AXIS_X: Center: 0.00, Min: -1.00, Max: 1.00, Flat: 0.12
AXIS_Y: Center: -0.04, Min: -1.00, Max: 1.00, Flat: 0.12
AXIS_Z: Center: 0.00, Min: -1.00, Max: 1.00, Flat: 0.12
AXIS_RZ: Center: -0.00, Min: -1.00, Max: 1.00, Flat: 0.12
AXIS_HAT_X: Center: 0.00, Min: -1.00, Max: 1.00, Flat: 0.00
AXIS_HAT_Y: Center: 0.00, Min: -1.00, Max: 1.00, Flat: 0.00
AXIS_GAS: Center: 0.00, Min: 0.00, Max: 1.00, Flat: 0.06
AXIS_BRAKE: Center: 0.00, Min: 0.00, Max: 1.00, Flat: 0.06
AXIS_GENERIC_1: Center: 1.00, Min: nu, Max: 1.00, Flat: 0.06
I'm also having this issue with my new xbox one x controller.
Vendor ID: 0x45e
Product ID: 0x2e0
Name: Xbox Wireless Controller
OS version: 7.0
SDK version: 24
Manufacturer: samsung
Model: SM-G955U
AXIS_X: Center: 0.04, Min: -1.00, Max: 1.00, Flat: 0.12
AXIS_Y: Center: -0.03, Min: -1.00, Max: 1.00, Flat: 0.12
AXIS_Z: Center: 0.01, Min: -1.00, Max: 1.00, Flat: 0.12
AXIS_RZ: Center: -0.01, Min: -1.00, Max: 1.00, Flat: 0.12
AXIS_HAT_X: Center: 0.00, Min: -1.00, Max: 1.00, Flat: 0.00
AXIS_HAT_Y: Center: 0.00, Min: -1.00, Max: 1.00, Flat: 0.00
AXIS_GAS: Center: 0.00, Min: 0.00, Max: 1.00, Flat: 0.06
AXIS_BRAKE: Center: 0.00, Min: 0.00, Max: 1.00, Flat: 0.06
AXIS_GENERIC_1: Center: 0.53, Min: 0.53, Max: 0.53, Flat: 0.06
If you connect the Xbox One S/X controller to a PC, and get the Xbox Accessories application.
https://www.microsoft.com/en-us/store/p/xbox-accessories/9nblggh30xj3
This will update the firmware(might take a few minutes for the application to see that there is an update available). This will fix the issue with the controller mapping improperly in Android.
(11-16-2017, 01:38 PM)Sonicadvance1 Wrote: [ -> ]If you connect the Xbox One S/X controller to a PC, and get the Xbox Accessories application. https://www.microsoft.com/en-us/store/p/xbox-accessories/9nblggh30xj3
This will update the firmware(might take a few minutes for the application to see that there is an update available). This will fix the issue with the controller mapping improperly in Android.
I've tried this and it doesn't seem to fix the issue. it randomly stopped having the issue but wouldn't map the L/R buttons so I restarted the app and after that is started the axis 32+ issue again.
Sorry for the delay.
buffsee, this should be fixed in pr6224. Can you test at
https://dl.dolphin-emu.org/prs/pr-6224-dolphin-latest.apk ?
CallMeCody, I'm not sure what to tell you, the firmware update should fix the mappings. I have the same controller and it seems to work. I'm not sure how to get the firmware version, though.
(11-29-2017, 02:15 PM)hackbar Wrote: [ -> ]Sorry for the delay.
buffsee, this should be fixed in pr6224. Can you test at https://dl.dolphin-emu.org/prs/pr-6224-dolphin-latest.apk ?
CallMeCody, I'm not sure what to tell you, the firmware update should fix the mappings. I have the same controller and it seems to work. I'm not sure how to get the firmware version, though.
I am having the same error as Buffsee, the download you posted did not solve the problem.
roforce please follow the instructions in #3.