Skip to content
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

RG405V (aarch64) | Binding "Home/Back" button to "Hotkey Enable" allows brief in-game input #17016

Closed
tyeg98 opened this issue Sep 19, 2024 · 1 comment

Comments

@tyeg98
Copy link

tyeg98 commented Sep 19, 2024

Per the title, I am using RetroArch on an Anbernic RG405V. In my hotkey settings, I am binding the center home/back (Button 110) button to "Hotkey Enable", and setting other hotkeys to other buttons (i.e. Start = quick save).

I am able to bind the controls without issues. The problem lies in the in-game behavior. When I hold the home/back button to activate a hotkey, there is a brief delay where I still have in-game input. This causes in-game buttons to trigger at the same time as hotkeys (i.e. if I were to press home/back + start to quick save, the in-game pause menu would also trigger). The duration of the delay is inconsistent. It happens across all cores, so it seems to be within RetroArch.

I have "Hotkey Enable Delay (Frames)" set to 0 in my config but the behavior still persists. The problem does not happen when setting anything else on the RG405V as hotkey enable. The issue is reproducible in latest stable and nightly release (aarch64) for me. I'm not able to test on another copy of the device.

Please let me know if any additional info is needed!

P.S. If someone happens to have the RG406V and tests this, could you let me know if it has the same issue?

@tyeg98
Copy link
Author

tyeg98 commented Nov 4, 2024

Just wanted to make a note, I did end up getting the RG406V, and thankfully this problem doesn't happen on it. I did have GammaOS on the RG405V, so might have been something from that. 406V is running on stock.

Either way, it seems the controls are bound differently compared to my previous device and they come up differently (i.e. 405V = xbox input, 406V = retropad input). This could also have something to do with it. Just wanted to share for the 0.1% of people who run into the same problem I did.

@tyeg98 tyeg98 closed this as completed Nov 4, 2024
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

1 participant