Skip to content

Can't recognize analog triggers #1154

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kimdonga99 opened this issue Apr 30, 2025 · 3 comments
Open

Can't recognize analog triggers #1154

kimdonga99 opened this issue Apr 30, 2025 · 3 comments

Comments

@kimdonga99
Copy link

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?

@mmatyas
Copy link
Owner

mmatyas commented Apr 30, 2025

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?

@kimdonga99
Copy link
Author

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?

@mmatyas
Copy link
Owner

mmatyas commented May 5, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants