@sleve_mcdichael said in N64 Controller Input Config:

The autoconfig only works for libretro cores;

Actually, the auto-config works for a few other emulators also, including Mupen64Plus (see here).

@Jay420 Please provide the info requested in https://retropie.org.uk/forum/topic/3/read-this-first, which should include the emulator you're using and what controller type do you have.

@toigo Solution to this problem is at https://retropie.org.uk/forum/topic/29481/controls-randomly-locked-for-1-or-2-secs/11 (switching to HDMI audio in raspi-config).

@ringus said in Changed n64 controller and mapping is busted:

mupen64plus-glideN64-highres

This is the standalone emulator, as @retropieuser555 mentioned, with a different video plugin. In addition to the standalone emulator, there are 2 separate libretro based emulator (lr-mupen64plus and lr-mupen64plus-next) which should be configured automatically based on your Controller configuration with the mapping explained on the same page that was mentioned by @retropieuser555.

@mitu It worked, thank you!

@rip I had the very same issue and could not find any good solution posted already so I will post mine here (Z button was never an issue for me , Z button is also my hotkey)

Once configured as screenshot above and after first launch with n64 emu the following configuration was generated into /opt/retropie/configs/n64/InputAutoCfg.ini

; SWITCH CO.,LTD. Controller (Dinput)_START [SWITCH CO.,LTD. Controller (Dinput)] plugged = True plugin = 2 mouse = False AnalogDeadzone = 4096,4096 AnalogPeak = 32768,32768 Mempak switch = Rumblepak switch = C Button U = button(9) L Trig = button(4) C Button D = button(1) button(0) #C Down gets mapped to button(1) which is really B Button and button(0) is the actual C Down button DPad U = hat(0 Up) DPad L = hat(0 Left) C Button L = button(3) Y Axis = axis(1-,1+) X Axis = axis(0-,0+) DPad R = hat(0 Right) Z Trig = button(6) C Button R = button(8) R Trig = button(5) DPad D = hat(0 Down) Start = button(12) A Button = button(2) # Lack of mapping for button B at all ; SWITCH CO.,LTD. Controller (Dinput)_END

I then used jtest to actually view which button was what hence my conclusions above with jstest /dev/input/js0 then I edited the file nano /opt/retropie/configs/n64/InputAutoCfg.ini with the following

; SWITCH CO.,LTD. Controller (Dinput)_START [SWITCH CO.,LTD. Controller (Dinput)] plugged = True plugin = 2 mouse = False AnalogDeadzone = 4096,4096 AnalogPeak = 32768,32768 Mempak switch = Rumblepak switch = C Button U = button(9) L Trig = button(4) C Button D = button(0) DPad U = hat(0 Up) DPad L = hat(0 Left) C Button L = button(3) Y Axis = axis(1-,1+) X Axis = axis(0-,0+) DPad R = hat(0 Right) Z Trig = button(6) C Button R = button(8) R Trig = button(5) DPad D = hat(0 Down) Start = button(12) A Button = button(1) B Button = button(2) ; SWITCH CO.,LTD. Controller (Dinput)_END

Hope this might help someone else with same setup, cheers

/a

For future reference, I managed to solve my issue by going into the RGUI going to Quick Menu > Controls and playing with those settings. Make sure to save those settings as a game remap file and do not select save on exit as this would break retroarch.cfg files.

@Dr-Nick

Start with this youtube video:

This will help. If you still have questions, come back. I'll keep an eye on the thread.

D

For other folks looking for answers about this, see the following forum:

https://retropie.org.uk/forum/topic/27007/button-mapping-for-a-real-n64-controller?_=1594477474831

@DavidDraper I'm sorry to hear that it is not working for you.

First off, you definitely shouldn't edit the .bak file, stick with only the .cfg file. Sorry if I wasn't clear there. I'm not sure what the .bak even does, or how to revert it.

Second, remember to only overwrite the button mappings. For example, in the .cfg file there are 2 lines above the mappings that I left intact. For me it reads:
input_device = "SealieComputing N64 RetroPort"
input_driver = "udev"

This of course would change depending on what controller you are using.

If you've done all of the above correctly, then the only other thing that I can think of is that it might be because you are using a "Generic USB" controller rather than an original N64 controller with an adapter.
Perhaps this means your buttons are in a different order, or are labeled differently, I'm not really sure as I don't own a Dragon Rise controller to test with.

Still, if you'd like, feel free to copy what your original dragon rise.cfg file was (prior to copy / pasting my info), and I'll see if I can translate it into something that may work for you.

Otherwise, good luck, and I hope that other solution works for you!

Anybody help me?;)

@mitu Thank you!!

@hawkes_84 Thanks will do. The controller should be here in a week.

It appears that in /opt/retropie/configs/n64/InputsAutoCfg.ini that under the relevant controller there was no entry for B button, and A button was incorrect. I edited this manually to correct for this, but I still get the same problem when i run the emulator - e.g., my attempted fix makes no difference to how it actually performs!

Hey bud, we are in the same boat. Run jstest and write down all the inputs and corresponding numbers. Use your Rii to hit f1 while in lr-mupen64plus-next to open the retroarch GUI and scroll down to "controls", then remap everything according to you jstest results. This got me to the point where every button works except for c-up and c-right. Please let me know if you can get any further or if you've already solved the issue.

@chriso205 said in OOT + lr-mupen64plus n64 controller config:

Not sure how to access this retroarch menu?

Hotkey+x will open the retroarch menu while youre in game. Then go to controls and remap as you like and then you can save it as a core remap. Remapping here won't influence your mappings in the standalone emulator because it doesn't use the retroarch controls.

@CobaltEcho The .rmp file doesn't exist by default. That's why you can't see it if you look through SSH. You have to go into your RGUI (in game) to create one manually (select + x to open the rgui).

Alternatively, you could try making hardcoded configuration changes through the various retroarch config files.

I don't know which emulator are you using for N64 and on what system, but what you're looking for is described din the Docs.