[SOLVED] Possible to assign per game turbo buttons?
-
I have a cab with a six button lay-out. I thought the following to be the most versatile way to map a turbo button for a lot of shmups: configure an extra (unused) button as the primary fire weapon and then make that button a turbo button via RGUI --> settings --> input --> turbo (all the way at the bottom)
The problem with this method is that the mapping carries over to other games (I believe it's treated as a core input of sorts), so my turbo button in Twin Cobra also makes a turbo out of Heavy Kick in Marvel vs Capcom...
The above example is with using FBNeo, I haven't tested any other cores.
Is there another/any way to assign turbo buttons on a per-game basis?
-
-
@sleve_mcdichael Well, that worked a treat. Great suggestion, I didn't know there were settings for turbo mapping like that.
I just added
input_turbo_period = 6 input_turbo_duty_cycle = 3 input_player1_turbo_btn = 2 input_player2_turbo_btn = 2
to mine (already have an override config for every game for custom overlays and shaders) and after assigning button 2 in a key remap, everything works like a charm. Thanks!
-
@sleve_mcdichael Something is unclear to me about this turbo functionality, (hoping you know an explanation):
With my above additions to the cfg files, the turbo button still also acts as a modulator for other buttons, is this due to the turbo mode being set to 'classic'?
I experimented with 'single button' as well, but that just makes it so you press the button once and it starts autofiring away without any additional input, is this even the correct behaviour? I can't quite make it out in your linked reddit-post as my settings in RGUI aren't 100% the same as you describe them. (maybe due to some advanced settings toggle I haven't enabled?)
Is there a way to designate one extra button as a turbo equivalent of another button without it also interacting with other buttons?
-
@WeirdH said in [SOLVED] Possible to assign per game turbo buttons?:
Is there a way to designate one extra button as a turbo equivalent of another button without it also interacting with other buttons?
I believe that should be possible with for example:
"Settings" turbo = L2
"Quick menu" turbo default button = B
"Quick menu" turbo mode = hold...in this mode, holding L2 (by itself) will rapid-fire the B-button (you don't have to touch B. Just hold the trigger and it'll machine-gun your B-button). You can long-press B-button while the trigger is held to temporarily interrupt the turbo fire and charge your meter.
-
@sleve_mcdichael Ah, that's what I thought, but my RGUI doesn't have a 'turbo' option under quick menu. I did find entries for default button and mode, however, but they are both in main--settings--input. And the 'turbo mode' there only has two options: classic and single button, so that's where I got confused.
Nowhere is there an option between 'hold' and 'toggle' that I can see.
"Settings" turbo = L2
"Quick menu" turbo default button = B
"Quick menu" turbo mode = holdCould these settings be forced through a cfg file as well, thus bypassing the RGUI?
EDIT: I experimented with 'input_turbo_mode = 'as per this post, but I don't know what values are supported (there's surprisingly sparse documentation on this), so I tried the method mentioned, but it just works as usual, with the turbo button acting as modulator for other buttons as well.
-
@WeirdH said in [SOLVED] Possible to assign per game turbo buttons?:
And the 'turbo mode' there only has two options: classic and single button, so that's where I got confused.
Nowhere is there an option between 'hold' and 'toggle' that I can see.
EDIT: I experimented with 'input_turbo_mode = 'as per this post, but I don't know what values are supported (there's surprisingly sparse documentation on this), so I tried the method mentioned, but it just works as usual, with the turbo button acting as modulator for other buttons as well.
That post says that "Single Button" is the same as "Hold". I'm not sure why it's called 2 different things -- maybe you're using a different menu driver besides RGUI and that calls it something else? Or, maybe it has changed since last I checked it.
The post also says that "Single Button (Hold)" is
input_turbo_mode="2"
, and I see in my default config that the default "classic" mode is"0"
so maybe"1"
is the "toggle" mode?I could test some later but I'm not at my device right now to check it myself.
-
@sleve_mcdichael said in [Semi-SOLVED] Possible to assign per game turbo buttons?:
That post says that "Single Button" is the same as "Hold". I'm not sure why it's called 2 different things -- maybe you're using a different menu driver besides RGUI and that calls it something else? Or, maybe it has changed since last I checked it.
Could be. I'm on a Pi3B+ and as I understand it, Retropie uses an older version of Retroarch on there. Maybe that accounts for some differences...?
-
@WeirdH said in [Semi-SOLVED] Possible to assign per game turbo buttons?:
Could be. I'm on a Pi3B+ and as I understand it, Retropie uses an older version of Retroarch on there. Maybe that accounts for some differences...?
No, the same version of RetroArch (1.10) is installed on all systems supported by RetroPie.
-
@mitu
Is the Retroarch version the number shown in the bottom left corner of RGUI, along with the currently loaded core? If so, mine is on 1.8.8 somehow. If not, where can I check my current RA version?Yeah, so I now updated to RA version 1.10 (d'oh) and I can see the menu entries in the aforementioned places.
Setting turbo mode tosingle button (hold)
and turbo default button toX
(my preferred button) still doesn't make it work as I intend. For instance,1944
still charges up a shot when holding down the button instead of rapid firing.single button (toggle)
does work as I would expect it to, though.What am I doing wrong?EDIT: Okay, got it. After updating RA, if I put
input_turbo_period = "6" input_duty_cycle = "3" input_turbo_mode = "2" input_turbo_default_button = "0" input_player1_turbo_btn = "3"
into my cfg file, button 3 does function as a turbo button, WITHOUT modulating any other buttons, so I guess the previously linked post was correct after all, I was just rocking an older version and didn't realize it.
Thanks to all respondents for bearing with me!
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.