I’ve gathered from the documentation and information on the forum that on screen touch controls, as shown with example below. That’s great, and it makes complete sense - most users need those on screen touch controls.
What I’m noticing though, is that there’s no way to bind actions to android gamepads - I can’t get the example below to work with any android bluetooth gamepads.
It’s obvious that the ‘gamepad triggers’ section of the input/default.input_binding file is for PC controllers - when testing the gamepad_tester example above, it works flawlessly when building for pc. However, when building for android and debugging on a physical device, it fails to register input from a bluetooth gamepad.
Oddly, if I remove all ‘touch-triggers’ and add a ‘key-trigger’ where ‘key-back’ is an action, I can trigger the action with the back button on my android device and the B button of the bluetooth gamepad - which I can see is bound to ‘BUTTON_B’ and ‘keycode 97’ on the device.
It seems like such a tease that I can bind to the B button of the gamepad by a weird coincidence, but can’t bind actions to the rest of the buttons.
Shouldn’t defold support android gamepads with the ‘gamepad triggers’, or at least have ‘key triggers’ which correspond to the rest of Android’s gamepad buttons like these?
KEYCODE_DPAD_UP, KEYCODE_DPAD_DOWN, KEYCODE_DPAD_LEFT, KEYCODE_DPAD_RIGHT etc
I wonder if those keycodes could be added to the possible input choices list for the ‘key triggers’ like the ‘key-back’ was?
Note: I think this other bug highlights that bluetooth android keyboards can’t be bound to either.