Clarification regarding custom rom key remappings.

Sabercyclone

I'm currently setting up Retropie using a Raspberry Pi 3B+, using this controller/case and GPIOnext, and I'm slightly confused regarding how rom-specific hardcoded configurations work. I've gone through this guide, watched the embedded video entitled "RetroArch: Remapping your controller (I used RetroPie)" and I understand how the theory works, however I'd prefer to simply work in text editors to get the same result, as I find it less of a hassle.

Firstly, I note that this guide says to place the custom config file in the same directory as the ROM. However I note that in the current version of retropie (v4.8), there's 2 subfolders named "cfg" and a "ctrlr".

Is the guide up to date, or shuold I be putting the configs in either the "config" subdirectory or "controller" subdirectory instead?

Both directories seem to be empty, so I'm wondering if that's what 1 or both of them are for.

Also I note that the guide was saying that I need to name the config file after the name of the compressed file carrying the ROM, however I'm wondering if I've missed something.

Based on what I'm seeing and presuming that there was a romfile called "2-button.zip", this is what I understand I'm supposed to include so far, for the filename:

2-button.zip.cfg

This is what I understand the code should be.

# Settings made here will only override settings in the global retroarch.cfg if placed above the #include line

input_remapping_directory = "<rom directory path>"

input_player1_joypad_index = "0"

input_player1_a_btn = "1"

input_player1_b_btn = "0"

input_player1_start_btn = "7"

input_player1_select_btn = "6"

input_player2_joypad_index = "1"

input_player2_a_btn = "1"

input_player2_b_btn = "0"

input_player2_start_btn = "6"

# Axis for RetroArch D-Pad.

# Needs to be either '+' or '-' in the first character signaling either positive or negative direction of the axis, then the axis number.

input_player1_up_axis = "-1"

input_player1_down_axis = "+1"

input_player1_left_axis = "-0"

input_player1_right_axis = "+0"

input_player2_up_axis = "-1"

input_player2_down_axis = "+1"

input_player2_left_axis = "-0"

input_player2_right_axis = "+0"

#Hotkeys- Hotkeys enable you to press a combination of buttons to do such things as exit emulators, save states,
# and load states, as well as any other functionality in an emulator. (In the example below 8 is the select key
# and 9 is the start key so when I hold down select and press start it will exit the emulator.)

input_enable_hotkey_btn = "8"

input_exit_emulator_btn = "7"

#decide on buttons for loading and saving states

input_save_state_btn = "5"

input_load_state_btn = "4"

input_menu_toggle_btn = "0"

input_state_slot_increase_axis = "+0"

input_state_slot_decrease_axis = "-0"

# video_shader = ""

#include "/opt/retropie/configs/all/retroarch.cfg"

# Never save-on-exit after an override config

# or the override will make into the core config.

config_save_on_exit = false```

What, if anything have I gotten wrong here?

dankcushions

@Sabercyclone said in Clarification regarding custom rom key remappings.:

Firstly, I note that this guide says to place the custom config file in the same directory as the ROM. However I note that in the current version of retropie (v4.8), there's 2 subfolders named "cfg" and a "ctrlr".

you didn't fill out https://retropie.org.uk/forum/topic/3/read-this-first so i'm guessing, but are you running a MAME rom? in which case, some MAME emulators create subfolders in the rom directory, like as you've described. these are various configuration folders that are used for MAME's internal configuration.

RetroArch is a front end that sits on top of emulators, providing an abstraction layer for stuff like controller config. to configure controllers via RetroArch (as you're trying to do), you can ignore these folders.

in any case, to remap controllers you should use core-input-remapping. custom override cfgs are not required here, and overcomplicate things. follow this guide: https://retropie.org.uk/docs/RetroArch-Configuration/#core-input-remapping

Sabercyclone

You do realise you're totally gatekeeping right now, right? That's to say nothing of the ableism at play here.

As far as gatekeeping goes, I literally said

@Sabercyclone said in Clarification regarding custom rom key remappings.:

I've gone through this guide, watched the embedded video entitled "RetroArch: Remapping your controller (I used RetroPie)" and I understand how the theory works, however I'd prefer to simply work in text editors to get the same result, as I find it less of a hassle.

In other words, before even asking for help, I'd done a document search, as per point 2 of "read This First". I'd looked at the documentation on configuring controllers in Retroarch - including looking at core input mapping. I'd even brought up the tutorial video on core input mapping that I'd watched. However I said that for certain reasons, which I'll cover later, working on keymapping configs was going to be easier for me to do via text editor. In fact, before this point, I'd already sorted out system-level Hardcoded configurations, for 2 systems, on this rig, before getting into individual MAME ROMS, where game-specific keymaps have now become necessary.

Yet instead of actually trying to be helpful, you just had to accuse me of not reading the Read This First thread, and referred me to something I'd already looked at. If that's not gatekeeping, I don't know what is.

Then there's the ableism. I'd already said

@Sabercyclone said in Clarification regarding custom rom key remappings.:

watched the embedded video entitled "RetroArch: Remapping your controller (I used RetroPie)" and I understand how the theory works, however I'd prefer to simply work in text editors to get the same result, as I find it less of a hassle.

In other words I'd already said that I'd looked into Core Input Mapping and working in text was going to be less of a hassle for me than using that method.

Yet your response was:

@dankcushions said in Clarification regarding custom rom key remappings.:

in any case, to remap controllers you should use core-input-remapping. custom override cfgs are not required here, and overcomplicate things. follow this guide: https://retropie.org.uk/docs/RetroArch-Configuration/#core-input-remapping

Overcomplicated for who though?

Did it ever occur to you that the issue might be that I have fine motor coordination issues due to Autism Spectrum Disorder and that because of that, I'd rather avoid the frustration of accidentally hitting a wrong button during key configs in that method and simply work with text files for the config side of things?

A wrong button press during a game is one thing; a wrong button press when I'm trying to set the system up in the first place is another thing altogether.

I was also hoping to avoid potential issues from my disability being out there, but hey, I guess that bridge has been well and truly crossed now, hasn't it.

So what, should retro gaming be not for those of us who are Neurodiverse when we have fine motor coordination issues, which make the "overcomplicated" method in your eyes, far easier for us?

Surely if you're going to continue to want to offer help, it's not too much to ask for you to meet me where I am, rather than gatekeeping, because I'm not where or how you want me to be.

dankcushions

@Sabercyclone said in Clarification regarding custom rom key remappings.:

Yet instead of actually trying to be helpful, you just had to accuse me of not reading the Read This First thread, and referred me to something I'd already looked at. If that's not gatekeeping, I don't know what is.

well, you didn't read it, otherwise you would have provided the requested information, including the exact game/system/etc, you were trying to configure, so i wouldn't have to guess. i'm sorry you feel this is "gatekeeping" - it's just to help us help you. but hey, my guess was right, and hopefully my info about the MAME folders helped?!

i appreciate using the UI may be more of a hassle than text files for some, but it would at least let you generate a sample .rmp file for you to edit and duplicate as you see fit.

if you want to generate one without the UI entirely, i don't really have a template for the file, but you can find various examples online: https://retrogamecorps.com/2020/10/29/rg351p-arcade-games-guide/

just save the .rmp file as gamename.rmp (your example 2-button.rmp - note you do not include the extension here), in the rom directory of the game in question.

you're welcome

Sabercyclone

@dankcushions You said in Clarification regarding custom rom key remappings.:

well, you didn't read it, otherwise you would have provided the requested information, including the exact game/system/etc

Yet I literally provided the Pi Model or other hardware: (B, B+, 2 B, 3, X86 PC etc..) I was using:

@Sabercyclone said in Clarification regarding custom rom key remappings.:

I'm currently setting up Retropie using a Raspberry Pi 3B+

Controller unit used (which also listed the included PSU btw)::

@Sabercyclone said in Clarification regarding custom rom key remappings.:

using this controller/case

The version of Retropie I was using

@Sabercyclone said in Clarification regarding custom rom key remappings.:

I note that in the current version of retropie (v4.8)

And guide/s I was using:

@Sabercyclone said in Clarification regarding custom rom key remappings.:

I've gone through this guide, watched the embedded video entitled "RetroArch: Remapping your controller (I used RetroPie)" and I understand how the theory works, however I'd prefer to simply work in text editors to get the same result, as I find it less of a hassle.

As for specific ROMs and systems affected, I was asking for clarification on the process, so that was non-applicable to this more generalised question. The file format for system-specific Hardcoded Configurations, isn't going to change with each individual ROM or system. Furthermore, even if the specific system was pertinent information, which it isn't, common sense would suggest that MAME is the only platform where controller mappings are going to be non-standardised on a standard controller.

So yes I did list all of that information. In fact I made sure to provide all that information, specifically because the "Read This First" thread mandated it - on top of the fact that even if it was just a suggestion, it's simply common sense..

So you were actually completely incorrect when you said:

@dankcushions said in Clarification regarding custom rom key remappings.:

my guess was right

And yes, you clearly are gatekeeping, because the only reasonable inference I can draw from your response, is that you're claiming that I didn't provide the information I did, because I provided it conversationally, rather than using this specific table in the Read-This-First thread:

Pi Model or other hardware: (B, B+, 2 B, 3, X86 PC etc..)

Power Supply used: (If using a Pi)

RetroPie Version Used (eg 3.6, 3.8.1, 4.1 - do not write latest):

Built From: (Pre made SD Image on RetroPie website, Berryboot, or on top of existing OS etc.. - please provide the filename of any image used)

USB Devices connected:

Controller used:

Error messages received:

Verbose log (if relevant):

Guide used: (Mention if you followed a guide)

File: (File with issue - with FULL path)

Emulator: (Name of emulator - if applicable)

Attachment of config files: (PLEASE USE PASTEBIN.COM FOR LARGE LOGS)

How to replicate the problem:

You've said:

@dankcushions said in Clarification regarding custom rom key remappings.:

i'm sorry you feel this is "gatekeeping"

There's no "feel" about it - that literally is gatekeeping. It's also passive-aggressive and gaslighting. Like far too many neurotypicals, you're treating me as someone on the Autism Spectrum, like I might as well be a 5 year old, with severe brain damage and an IQ barely above 70, and you probably don't even recognise that you're doing it - like how so many neurotypicals fail to be conscious of that behaviour towards us. You really should read up on the Double Empathy Problem with Autism and how it's very much a 2-way street.

And yes, it is necessary to go there, because this entire exchange it's a textbook example why the final report of the Disability Royal Commission here is expected to be at least 20 volumes long, and why, as I've been led to believe, the Persons with Disabilities community in the UK, are eagerly awaiting the findings of it.

That is to say nothing of the implications of how this behaviour is at odds with the auspices of practically every single set of Safeguarding Vulnerable Persons Guidelines in the British Commonwealth, when this is a forum which, based on the url, I can only presume is located in the UK.

@dankcushions said in Clarification regarding custom rom key remappings.:

If you want to generate one without the UI entirely, i don't really have a template for the file, but you can find various examples online: https://retrogamecorps.com/2020/10/29/rg351p-arcade-games-guide/

just save the .rmp file as gamename.rmp (your example 2-button.rmp - note you do not include the extension here), in the rom directory of the game in question.

And again, having taken a look at the the remap files, they're far more a case of overcomplicating things than working with hardcoded configuration files. Once again, this isn't helping.

Also where you've said:

@dankcushions said in Clarification regarding custom rom key remappings.:

hopefully my info about the MAME folders helped?!

No, again, you were too busy treating me like you viewed me as some 5 year old with severe brain damage and an IQ barely above 70 there, to offer any information that was even remotely helpful, or that I hadn't already figured out myself.

I'd already worked out why the folders might be there. Them being there was enough for me to question whether the information provided in, again, this guide, was still accurate, or whether the location where cfg files had to be located had changed with Retropie 4.8, which again, I did mention I was using here:

@Sabercyclone said in Clarification regarding custom rom key remappings.:

I note that in the current version of retropie (v4.8)

In fact I'd go so far as to describe that part of your response as ablesplaining.

Again, you're gatekeeping rather than helping here, in fact nothing you have offered here has been even remotely helpful; in fact it's been thoroughly ablest. I'd appreciate it if you just stopped interacting with me at this point, while I either wait for someone else to help out or just try and figure this out on my own. Otherwise I'll be contacting the admins about this. I've already taken screenshots of this entire thread to date.

sleve_mcdichael

@Sabercyclone said in Clarification regarding custom rom key remappings.:

question whether the information provided in, again, this guide, was still accurate, or whether the location where cfg files had to be located had changed with Retropie 4.8,

The location has not changed. The additional subdirectories are unrelated, as @dankcushions alluded to in their first response.

Sabercyclone

@sleve_mcdichael Thanks for clarifying that. There was 1 other things I was wondering about as the guide isn't completely clear on it.

The first is the coding line:

input_remapping_directory = /opt/retropie/configs/megadrive/

I just wanted to check that this is self-referential.

For example, if the hardcoded cfg file were located in the ROMs directory, that line of code, in that case would read:

input_remapping_directory = /home/pi/RetroPie/roms/arcade/mame2003/

Am I correct here?

sleve_mcdichael

@Sabercyclone the input_remapping_directory is where the core input remap files (which you're not using) will be stored. There is no need to set it here. If you do use it (because you decide to use core input remapping after all, but want to store the files in a non-standard location), then in that case the emulator core name (e.g. mame2003) will be added automatically, since this config file is core-agnostic (the same .zip.cfg file will be read when you launch the matching .zip rom whether that's with mame2003 or 2015 or fbneo.) So if you want the remaps stored in (a subdirectory of) the roms dir, you would just point this at the roms dir, not the subdir.

Sabercyclone

@sleve_mcdichael Thanks for clearing that up. So far everything is running like a dream. I need to sort out the 6 button layouts, but for the most part, with the exception of looking into how to make roms with CHD files work, the setup is pretty much done - with the exception of figuring out how to spawn multiple coin buttons on a RetroPie rig. However that's starting to shape up to be a potential second uint and housing's problem - presuming RetroPie even supports multiple coin slots at this point..