Trying to get my head around control binds

JimmyFromTheBay

@YFZdude said in Trying to get my head around control binds:

@JimmyFromTheBay said in Trying to get my head around control binds:

So now I have the control remap saved, how do I save the Port 2 bind (Gamepad#2 to Gamepad#1) so that it only applies to PMMM and doesn't mess up every other FBNeo game?

I thought saving a per-game remap file would do that. If it doesn't then I'm not sure what other option would.

No, saving a game remap file saves the changes you made in Controls (eg changing the jump command from P2 Right to P2 Button A), but it doesn't save the ones you made in Settings>Input to switch that to P1 Button A. Save Game Overrides in the Quick Menu doesn't do it either.

So at the moment, every time I load the game I have to go into the latter and switch the Settings>Input>Port 2 Binds setting manually from Gamepad#2 to Gamepad#1.

The Settings>Input>Port 2 Binds menu has a Save Autoconfig option, but nobody seems to know what that actually means.

sleve_mcdichael

@JimmyFromTheBay said in Trying to get my head around control binds:

at the moment, every time I load the game I have to go into the latter and switch the Settings>Input>Port 2 Binds setting manually from Gamepad#2 to Gamepad#1.

Try input_player2_joypad_index = "0". Default is player 1 index =0, player 2 index =1, etc.; this binds player 2 to the same index (0) as player 1.

Put this in a game override config at ~/RetroPie/roms/[system]/[romname.ext].cfg e.g.:

~/RetroPie/roms/arcade/pmmm.zip.cfg

JimmyFromTheBay

@sleve_mcdichael Sorted! Many thanks!

(Any idea whether Case 2 is solvable?)

sleve_mcdichael

@JimmyFromTheBay said in Trying to get my head around control binds:

(Any idea whether Case 2 is solvable?)

Case 2 should be a simple core-input remap. quick menu > controls > port 2 controls:

1: "mapped port: port 1"
2: map D-pad to face buttons
3: save game remap.

JimmyFromTheBay

@sleve_mcdichael So, absolutely nothing is working here. There is no "mapped port: port 1" option, so I assume by that you mean the CFG file line mentioned earlier.

Here's what I now have in Port 2 Controls:

I've swapped all the d-pad controls for buttons, and vice versa to avoid conflicts. This did nothing.

Here's what I now have in Port 2 Binds:

Basically the same again - buttons swapped for d-pad and vice versa, and Device Index switched from #2 to #1.

I've tried each of these steps on their own, and worked up to having them all present at once. But none of them changes anything. Whatever I do, movement is still on P1 joystick, and firing is still on P1 buttons.

sleve_mcdichael

@JimmyFromTheBay said in Trying to get my head around control binds:

There is no "mapped port: port 1" option, so I assume by that you mean the CFG file line mentioned earlier.

No I meant in the RGUI menu. What version is your RetroArch?

JimmyFromTheBay

@sleve_mcdichael said in Trying to get my head around control binds:

@JimmyFromTheBay said in Trying to get my head around control binds:

There is no "mapped port: port 1" option, so I assume by that you mean the CFG file line mentioned earlier.

No I meant in the RGUI menu. What version is your RetroArch?

God knows. Where is that even displayed?

sleve_mcdichael

@JimmyFromTheBay said in Trying to get my head around control binds:

Where is that even displayed?

You can run /opt/retropie/emulators/retroarch/bin/retroarch --version or it's shown in the RGUI menu on the bottom banner on some items that don't have any other item-specific info there -- like in your images where it says bsnes 1.8.8; if you browse around the menus, sometimes that will say the RetroArch version (or there's probably an "info" page somewhere in the menu itself but I'm not at my screen right now to check.)

JimmyFromTheBay

@sleve_mcdichael Hmmm, nothing like that anywhere but it seems like it was built in November 2020 so I guess it's pretty out of date. I'm INCREDIBLY wary of updating core features because they invariably break something that necessitates me repairing 2,500 individual config files because they decided to change the aspect ratio numbering or something for a laugh. I might just stick to the arcade Smash TV...

sleve_mcdichael

@JimmyFromTheBay said in Trying to get my head around control binds:

nothing like that anywhere but it seems like it was built in November 2020 so I guess it's pretty out of date.

Yeah, it looks like the "mapped port" feature was added about a year ago.

JimmyFromTheBay

@sleve_mcdichael Ah. That's annoying, looks like a really useful feature but the stakes are just so high on the gamble :(

sleve_mcdichael

@JimmyFromTheBay said in Trying to get my head around control binds:

but the stakes are just so high on the gamble

It looks like the aspect-ratio-index fiasco happened in 1.7.4 in 2018; I'm not aware of anything else like that that's happened since, but, you do have a backup...right?

Do you really have 2500 custom override configs? What do you use them all for? Are a lot of them duplicates? For example, I usually use integer scaling and a scanline shader, but for vertical (rotated) arcade titles, I turn integer scaling off and use a different shader. I have one config that sets these overrides, and then in my various different game configs, I just have:

#include "/opt/retropie/configs/arcade/arcade-vertical.cfg"

That way, if anything does change (or I just want to use a different setting), I can just change that "arcade-vertical.cfg" and I don't have to do it in 52 individual game-overrides.

JimmyFromTheBay

@sleve_mcdichael said in Trying to get my head around control binds:

Do you really have 2500 custom override configs?

Rather more than that, it turns out :D

Obviously not all of those would be potentially affected by a Retroarch change, but goodness knows how many might be, and I never want to go through AspectRatioGate again. Even now, years later, I'm still finding games with the screen all wrong.

(I have CFGs for all sorts of reasons, in many cases it's as simple as a bezel but even those often need custom tweaks.)

And yeah, I have a backup but at 256GB it takes two days just to write the memory card. (And it's not really practical for a case like this, because if a new Retroarch broke everything the only suitable backup is a complete image file. What I actually have as a day-to-day backup are copies of the ROMS and CONFIGS folders, which can be updated in seconds, but that would be no use for a Retroarch meltdown. You can't save a 256GB image file every night.)

Anyway, that's my hangup to deal with, I'd really like the new feature but since it's basically only for two SNES ports that already run fine in MAME I'll have to weigh up the risk, and the terror of possibly having to go through the infinite pain of configuring WonderSwan games again. Thanks for the help :)