-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Description
Is there an existing issue for this?
- This is a bug in RetroArch frontend
- I have searched the existing issues — I saw [Android] Not possible to map touch inputs. #11021 but I can’t tell if the underlying issue is the same as mine.
Description
I am trying to map taking a screenshot to an on-screen button on Android. I am playing a Nintendo DS game, so I won’t need L2, R2, L3, or R3. R3 was mapped to “joystick touchscreen” in the core settings, but since I’m playing on smartphone, I decided I didn’t need it and unmapped it.
However, when I plugged in at external controller and mapped the “Screenshot” shortcut to R3, the on-screen R3 button did not do the same thing as the external controller’s R3.
And when I try to remap the shortcuts by setting the on-screen controller overlay to not disappear in the menu, the controller mapping dialog does not respond to any of the on-screen controller buttons, not just R3.
Video: https://streamable.com/t2shyw
Expected behavior
I should either be able to:
- map “Screenshot” to R3, then have the on-screen R3 button take a screenshot, or:
- map specifically the on-screen R3 button to taking a screenshot
Steps to reproduce the bug
Seen in the video:
- While the on-screen controller overlay is set to not hide in the menu...
- Go to hotkey mapping
- Try to map R3 to “Screenshot” using the Overlay
Version/Commit
1.20.0, Git 7a5fcd4
Bisect Results
No response
Present in the nightly version
I don't know
Platform & operating system
Android 15 (Motorola Moto g64)
Affected Cores
melonDS, possibly all others?
Environment information
No response