![]() ![]() ![]() ChoquePumper found the master list of these binds, and that's how I got my exit button working. Thinking that touchscreen buttons are only passing to the game input and not the program itself, I went to work finding the correct command bind. (Having two touchscreen buttons, one select and the other start, would not exit the app.) For testing purposes I set the touchscreen button to Select, and that still won't work, regardless if the button I am using it with is the physical gamepad of the Retroid or the other touchscreen button. I first tried using keyboard keys to trigger set the button to shift, and then map shift as the hotkey in config. However, I still can't get a touchscreen overlay button to work as a hotkey. ![]() I need to quit out of the app to reliably put my device to sleep.)Īfter a lot of struggling, thanks to ChoquePumper in the Discord, I managed to get the top button working to quit the app. (This is important since, for whatever reason, RetroArch doesn't work with Android sleep commands. Tap the top half of the screen to exit Retroarch. Hold on the bottom half of the screen to trigger the hotkey. The idea is that I would have two buttons (no visible UI), one the top half of screen, the other bottom half. This problem has me trying to think of a better way to use hotkeys, and I had the idea of using an overlay on the touchscreen. So if I do a hotkey to save a save state, the game is going to spit out the mushroom I have stored away. Select is used at all times in this game, to release your stored power-up. I'm playing through Super Mario World, and it is really problematic here. I currently have Select set as the hotkey, which works for a majority of games, but it can cause issues in a few. I'm trying to optimize how Retroarch is configured for use with hotkey commands. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |