coming soon to retroarch - new input mapping system - old remap files don't work

markwkidd

For those who are compiling the absolute latest RetroArch, be aware that a major update to the input (re)mapping code was just merged. This brings notable usability and functionality improvements and has been in the works for weeks.

Presently this is documented here: https://github.com/libretro/RetroArch/pull/6485

Because there is a new paradigm for mapping, old retroarch input remap files will not work starting with the current build in github and in stable RetroArch 1.7.2, which is the release that is targeting this feature.

Exciting times!

dankcushions

point of order: if you update via the setup script, even via source, you won't get the latest retroarch, only the last 1.7.1 version, which doesn't contain any of this stuff.

markwkidd

@dankcushions said in bleeding edge retroarch - new input mapping system - old remap files don't work:

point of order: if you update via the setup script, even via source, you won't get the latest retroarch, only the last 1.7.1 version, which doesn't contain any of this stuff.

Thanks. Consider this to be a warning from the future!

RedBatman

So does this mean that we have to exit out of emulation station to update. Or would it even be worth it if 1.7.2 will cause problems?

mediamogul

@redbatman

It just means that the current script module will only install version 1.7.1 no matter under what circumstance you launch the RetroPie-Setup script.

RedBatman

@mediamogul Thanks for the clarification

lostless

im trying the new 1.7.3 on a pi. anyone figure out how to remap controls? seems the new way has no real logic behind it.

hooperre

@lostless said in coming soon to retroarch - new input mapping system - old remap files don't work:

im trying the new 1.7.3 on a pi. anyone figure out how to remap controls? seems the new way has no real logic behind it.

Same here. My N64 controls seem to be all out of wack..

@mediamogul Any advice as to what to do for now? Thanks. (Specifying further, do you anticipate a workaround for this to be released? Or should I go ahead and totally reconfigure my controls as this is how things will be for the foreseeable future?)

mediamogul

@hooperre said in coming soon to retroarch - new input mapping system - old remap files don't work:

Or should I go ahead and totally reconfigure my controls as this is how things will be for the foreseeable future?

For better or worse, it's probably the best idea to tilt toward this new scheme instead of trying to fight against it with a work around. That said, I'm not completely sold on it myself. I had an idea in my head of what they were trying to achieve, but the actual result has me scratching my head too. It really seems like a lateral change rather than a straightforward improvement, but that's just my opinion.

hooperre

@mediamogul Great thanks for the reply. Gives me something to work on on my day off! ... The latency feature is awesome.

hooperre

@mediamogul Sorry to piggyback off of this, but maybe it will help someone else. How do I delete/clear an input completely? N64 for example always defaults to having A and C Down being the same input.

mediamogul

@hooperre

I believe, aside from saving over a previous map, you'd need to delete them manually from /opt/retropie/configs/all/retroarch/config/remaps/.

hooperre

@mediamogul said in coming soon to retroarch - new input mapping system - old remap files don't work:

@hooperre

I believe, aside from saving over a previous map, you'd need to delete them manually from /opt/retropie/configs/all/retroarch/config/remaps/.

I oddly have no files here. I've saved my autoconfigs. Should I only be using the Options > Controls sections, and not the Settings > Inputs section?

Edit to Add:

As I understand it Settings > Inputs > Autoconfig will be the same among every core. I would like my standard autoconfig layount to represent a PSX controller. So if I go into lr-pcsx-rearmed and save my autoconfig to match that controller layout I should be good. Then, I need to go into each core and map them out under the Options > Controls section. This would make sense to me. Correct?

mediamogul

@hooperre

I may not be understanding you exactly, but you'd always want your auto-config to cover as many systems as possible, thereby limiting the number of remaps you'd need to make.

thelostsoul

@markwkidd Does this only affect for those who compile from source? I mean, will this be any time updated to binary versions or don't I need to worry if I only update through binary? Will the emulators get a new version or is this default on future RetroArch versions? I ask, because I don't want break current settings with an update. I find the new scheme interesting and good (I read that thread from time to time). I just fear it, because setting up my Arcade Stick was a bit of hassle.

markwkidd

@thelostsoul said in coming soon to retroarch - new input mapping system - old remap files don't work:

Everything described in this thread is contingent on the version of RetroArch you're running -- the version of the individual cores does not affect this feature.

mitu

@markwkidd The RA version in RetroPie right now it's 1.7.3, which is the latest (official) release upstream. It has only a local patch for disabling the automatic gamepad re-ordering (introduced in 1.7.1 I think), otherwise it should be identical to upstream.

youxia

@mediamogul said in coming soon to retroarch - new input mapping system - old remap files don't work:

For better or worse, it's probably the best idea to tilt toward this new scheme instead of trying to fight against it with a work around.

That may be so, definitely inevitable in the long run. The problem is, there does not seem to be any solid guide regarding this - rather convoluted - subject. Unless somebody can point me towards one, I'll definitely delay upgrading for as long as possible.

lostless

@youxia if you update, your old remap configs will not work. The way it works now is that instead of mapping a game button to a physical, it’s the opposite. You map a real button to a game button. Basically you can map multiple buttons to do the same thing or disable a game button altogether. Better in my opinion as you can disable turbo buttons, etc if you want. Problem is that the Rugi doesn’t show what player you are remapping, and also, currently, retro arch is only showing the auto configs button numbers and not the typical Y B X A dpad etc. so it’s a pain unless you know the order of the buttons in retro arch. You can solve the player number issue by switching to the Xmb interface, but may not run well if your using a pi zero or 2.

markwkidd

I think it's just an oversight that RGUI doesn't have user # labels in the remapping interface. I have not done any work with the RetroArch UIs and I'm pretty backlogged with mame2003-plus coding. If no one has addressed this in a few weeks a month or two I will be more tempted myself.

I did start an issue here requesting it: https://github.com/libretro/RetroArch/issues/6843

It's probably not hard to add a new row that just says something like "User 1 Controls----" between each section but then again, maybe it is hard. :shrug: