You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 19, 2021. It is now read-only.
What platform does your feature request apply to?
Android
Is your feature request related to a problem? Please describe.
Yes, for the time being I've remapped my right stick to be a hat as the game I am playing does not use the right stick, however long term not a tenable solution.
Describe the solution you'd like
Modify the Android version to consider both HAT_ inputs and DPAD_ inputs when looking for input from the D-pad or allow users to rebind keys on Android.
Describe alternatives you've considered
Only alternative I've considered is what I'm doing now, and it's less than ideal. This is a system with controls and no touchscreen, so on-screen keys are a real pain to use, I'm sure that's not a completely uncommon situation.
Additional context
In terms of Android keylayout files, the mapping HAT_X and HAT_Y will work when bound to an axis, however any DPAD_ controls don't work. It's also seemingly not possible to bind individual keys to HAT directions in Android. I believe the setup of DPAD_ controls for the D-pad is standard for PS3 controllers connected to Android, users shouldn't be expected to root and modify their files to get working controls imo.
The text was updated successfully, but these errors were encountered:
What platform does your feature request apply to?
Android
Is your feature request related to a problem? Please describe.
Yes, for the time being I've remapped my right stick to be a hat as the game I am playing does not use the right stick, however long term not a tenable solution.
Describe the solution you'd like
Modify the Android version to consider both HAT_ inputs and DPAD_ inputs when looking for input from the D-pad or allow users to rebind keys on Android.
Describe alternatives you've considered
Only alternative I've considered is what I'm doing now, and it's less than ideal. This is a system with controls and no touchscreen, so on-screen keys are a real pain to use, I'm sure that's not a completely uncommon situation.
Additional context
In terms of Android keylayout files, the mapping HAT_X and HAT_Y will work when bound to an axis, however any DPAD_ controls don't work. It's also seemingly not possible to bind individual keys to HAT directions in Android. I believe the setup of DPAD_ controls for the D-pad is standard for PS3 controllers connected to Android, users shouldn't be expected to root and modify their files to get working controls imo.
The text was updated successfully, but these errors were encountered: