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
I tried to set up key mappings for a gamepad on Android. The triggers are recognized when they function as buttons, but not when they are analog. Is it possible to update it to recognize analog triggers?
The text was updated successfully, but these errors were encountered:
Hi! The gamepad handling code Pegasus is built on doesn't seem to handle triggers as axes, only as buttons. I assume you can't do both a the same time, so they went with buttons. What would be your use case here?
I'm using it to scroll through the game list pages.
However, when both the button and analog inputs are enabled, continuous input doesn't work, so I have to flip through one page at a time.
If I enable only the buttons, many games become incompatible, so I usually keep only the analog input enabled—but in that case, I can't scroll through the game list pages at all.
Would it be possible to add support for assigning analog input to this function in a future update?
Not sure if possible, but I'll keep this in mind. The gamepad support on Android is based on an external module, which got somewhat outdated. I'd need to rewrite it from scratch, but that's a big larger task, so might take a while.
I tried to set up key mappings for a gamepad on Android. The triggers are recognized when they function as buttons, but not when they are analog. Is it possible to update it to recognize analog triggers?
The text was updated successfully, but these errors were encountered: