hi, i would like to set a joypad combination buttons to quit from RetroArch. i have tried to set this on retroarch.cfg but doesn’t work, why?
input_exit_emulator_btn = "8+9"
hi, i would like to set a joypad combination buttons to quit from RetroArch. i have tried to set this on retroarch.cfg but doesn’t work, why?
input_exit_emulator_btn = "8+9"
RetroArch doesn’t support arbitrary button combo mapping, only single buttons. There is a “hotkey enable” button you can map that, when mapped, will force RetroArch to stop listening for hotkeys unless it is pressed. You could map that to, say, button 8 and then map exit_emulator to button 9 and it would give you the effect you’re looking for. However, any other hotkeys (such as menu_toggle) would not work unless you were holding button 8, as well.
thanks for reply.
RetroArch doesn’t support arbitrary button combo mapping, only single buttons.
why this strange decision? who uses a gamepad with few buttons is screwed
It’s not really an active decision, just the way the input system was originally implemented and changing it now would be a very big deal. It definitely needs to be done eventually, but it’s a major task that touches pretty much everything in the program so we keep putting it off.
We do have some menu hotkey combos that are hardcoded that you can choose among, and then you can do whatever you want, like closing the program, from the menu.
I know this is an old post, but is this still true? I really with I could quit RetroArch with start+select, but it doesn’t seem to work from the hotkeys menu.
Still true, yep. Start+select will get you in the menu and then you can quit from there, or else you can use something external, like antimicro, to make start+select trigger some random single-button event that you map “quit retroarch” to.
I figure if I set the hotkey enabler command to start and then the quit command to select, it works. I just don’t really know if this will affect anything while playing. Do you know if that will be the case? Anyway, thanks for helping me every time.
That’ll work, yeah. The only thing to remember is that the hotkey-enabler blocks all hotkey events unless it’s held, so if you have any other functions you want to do, you’ll need to hold select to do them.
Also, the way the hotkey enabler works, it blocks out retropad inputs once it’s in “hotkey mode”, so to speak, so things that require you to hold retropad-select won’t work. Note: we added a little hack that delays the hotkey-enabler retropad lockout for a few frames, so the retropad-select function (for example, ‘coin’ in FBNeo) will still fire, you just can’t hold it down.
Does that make sense?
I think I get what you said, but I just tested using the same select button I’ve set as the hotkey-enabler as the coin button (but it was the mame core instead of FBNeo), and it worked just fine without setting the delay. If I’m not mistaken, you just said it should’ve blocket that input, right?
It should work. We added the delay by default. Previously, some cores (not all) would fail to fire any retropad events from the hotkey-enabler-mapped button.
Oh, now I get it! I though I was supposed to configure the delay manually first. That’s perfect, then. Thank you so much!