Core overrides and input modifications from the main menu (not quick)

General
#1

Is there still no way to save core overrides with controller input mappings?

I still can’t get on board with this new RetroArch, unless I’m missing something. When R. Danbrook implemented the turbo keys for Nestopia, he didn’t provide a way to turn them off, so my workaround for this in the old RetroArch was to use per core configs, and leave buttons unmapped, then from there, simply change the ‘turbo’ buttons to an unmapped button in the quick menu. Not ideal, but it works.

With N64, I use a real N64 controller, and I have to alter the main controller settings so that the right analog is mapped to the C buttons on the N64 controller. This wouldn’t be an issue if the quick menu would allow me to map an analog direction to a button, but it does not. So again, a 2nd instance where I need to alter the main controller input.

I’ve played around with manually entering in changed settings on a core override file, and that works, but if I then try to save a new setting in the menu, RetroArch will delete all of that.

Edit: figured out this part of the problem on my own.

Is a fix for this on the horizon? Or, am I doing something wrong possibly?

#2

Not ideal, but you can use the core input remapping to move the turbos over to R3/L3.

For N64, you should be using an autoconfig for that controller+adapter. We already have a handful of them in the autoconfig profiles but if yours isn’t covered, create one and submit it to the repo and I’ll merge it in.

#3

Thanks for the reply. The issue with N64 is, the Mupen64 core maps the ‘C’ buttons to the right analog stick of a typical Xbox 360 controller.

They did what they had to do to make it work for most people, I understand that.

But that doesn’t work for me, because my controller doesn’t have a right analog stick. So I have to go into the main settings and change the non-existent right analog mapping to the C-buttons on my N64 controller to make it work.

But the problem there is, RetroArch still doesn’t have controller overrides working yet. I can make it work by manually creating an override file with the necessary settings, but there’s no way to do it from the UI.

Of course a much better solution would be to just allow users to re-map the directions of analogs, as well as buttons, in the quick menu controls…

I don’t understand why that option doesn’t exist already. The issue comes up more often than you’d think, and I’ve had to come up with creative workarounds.

#4

The analogs and digital buttons aren’t the same under the hood, so they aren’t interchangeable. That is, analogs give an axis value of +/- whatever, while the digital buttons return 1 or 0. To be able to remap them, they would need to all produce the same sort of value. That is, either analogs would need to return digital values, which would defeat the purpose of having analogs, or all digital buttons would need to return analog values, which would be a lot of work to implement and significantly increase the complexity of many things.

With the autoconfig profile, you can have the right analog values mapped to your C-buttons. That’s how we have all of the other N64 pads set up right now.

#5

I will certainly do that, but again, how exactly am I supposed to make this happen? Core overrides do not save changes from the main input mapping, nor changes to the hotkeys. I can manually make a core override file (e.g. create a new config file in notepad, and save it to the necessary location) with the necessary changes, and that will work, but if I didn’t know to do this, and if I didn’t know exactly what to put in it, I’d be lost. In fact, doing a simple task like this is actually quite a hassle. I pretty much have to create a new config, and see what RetroArch calls the ‘c’ buttons on my n64 adaptor, then copy them to a new core override file.

Also, if I actually took the time to manually enter in the data necessary to override controls, if I then change something else in the menu, and try to save a core override, RetroArch will delete anything pertaining to controls, meaning once I decide to manually edit controls with overrides,I’m stuck manually editing everything from then on.

Is the ability to save changes to controls/hotkeys from the UI using the ‘save core overrides’ command going to be implemented at some point in the future?

Edit: It is not possible to utilize core overrides in any way to disable an auto-configured entry, if the main profile has autoconfig enabled. This further complicates the issue, because now I’ve got controls being mapped to multiple things.

#6

Ah, if you have autoconfig disabled for some other reason, it’s not going to be a good solution for you. You’ve fallen into what’s known as an “edge case”.

Not that I know of. Your best bet in this case may be to add an external launcher into the mix that you can use to pass complete configs at launch-time.

#7

Oh, I think I get what you were saying before. To map the right analog to the C-Buttons, then save that as the auto-config.

That solution wouldn’t work for me because I use my N64 pad for 6 button controller systems like Sega Genesis.

I just don’t understand why core overrides in the menu don’t save changed controls, yet I can do it manually and get it to do what I need it to do (even though it’s 10x the hassle). And again, using the UI to try to save additional overrides deletes all the controller entries I manually entered.

#8

Would it be possible for me to turn this issue into a bounty? I’d personally put up $50 to see core overrides affect every possible change in the menu, especially controls and hotkeys.