# Specifies which joystick is bound to this controller: -1=No joystick, 0 or more= SDL Joystick number # Controller configuration mode: 0=Fully Manual, 1=Auto with named SDL Device, 2=Fully automatic # Mupen64Plus SDL Input Plugin config parameter version number. For each axis, this must be greater than the corresponding AnalogDeadzone value
# Underrun Mode, 0 = Ignore, 1 = Report, 2 = repeat audio when latency = AnalogPeak will saturate the N64 controller axis value (at 80). # Audio Output Frequncy mode (when NATIVE_MODE=false): 0 = Rom Frequency,$ # Number of output samples per Audio callback. # Point OMX to the raw N64 audio data region instead of copying audio int$ # Audio output to go to (0) Analogue jack, (1) HDMI # Frequency which is used if rom doesn't want to change it # Mupen64Plus OMX Audio Plugin config parameter version number # Filename of the disk to load into Disk Drive # This file is automatically read and written by the Mupen64Plus Core library My file looks like this # Mupen64Plus Configuration File You have to edit the /recalbox/share/system/configs/mupen64/ mupen64plus.cfg file, and add in this file your controller config.Īfter you have done this, your Controller should work fine. With the n64.configfile=dummy method i can't use the libretro core's only the standanlone Mupen64plus. I can't simply make the file immutable since it's a fuse filesystem.įeeling rather stuck here. Then I added n64.configfile=dummy to the /recalbox/share/system/nf but that resulted in the controller not being seen at all. This of course resulted in the file being overwritten when the emulator was launched and the buttons were incorrect. I first added the config to the /recalbox/share/system/config/mupen64/InputAutoCfg.ini. Thank you.I have been searching for the answer to this but I just can't seem to get my N64-style generic controllers. (Also, somebody implied this might be important, but User 1 Analog To Digital Type is set to None).Īnyway, any assistance is appreciated. Controller (Dinput).cfg) input_driver = "udev" Here's my config (from ~/joypads/udev/SWITCH CO.,LTD. I mapped the C-buttons to the Right Analog Stick in RetroPad. Navi is notoriously annoying, but C-Up is not working) The part that isn't working is the C-buttons (I'm using OoT because it's obvious what each button is for, for the most part. With your help, I have most of the controller working. I'll be sure to get this added to the GitHub shortly It will make things much easier if you need to remap anything in the quick menu > controls menu, since it will display the actual gamepad button labels instead of using the generic retropad labels (i.e., making you remember a second mapping on top of what you're already doing).ĮDIT - Never .just started working out of the blue. I strongly recommend that you create an autoconfig profile for your own pad if it doesn't exist in the repo and then add the button label lines like in that example.
Here's an example of an autoconfig profile that uses this trick: That can be a little confusing when navigating, but it's better than being locked out altogether. There is a clever solution, though, where you can map both retropad-A and retropad-Y to physical B button and retropad-B to physical A. If you try to match the core inputs, with B to retropad-Y and A to retropad-B, you can't navigate the menus properly because you don't have an 'accept' button! If you map A to retropad-A and B to retropad-B, you can navigate the menus, but the core inputs become weird. So, physical N64 pads are a little tricky. I'll leave step 2 for a later conversation (regarding controller-per-core configuration so that n64 controllers get used for n64 games, SNES contollers get used for SNES games etc) So, that's my step 1, get an n64 controller working properly with Mupen. How do I map the RetroPad to the Emulator? (I'm sure there's a guide for this, if you have a link that would be greatly appreciated) Next, I fired up a game in Mupen, and none of the controls were recognized. R1->R Shoulder, L1-> L Shoulder, Right Analog Stick -> C buttons, and (I think) Select->Zĭoes that make sense? Is there a reason that wouldn't work? What I did was this: Mapped B->B, A->A, Start->Start, D-Pad->D-Pad, Left Analog Stick->Joystick I know the gist is Controller -> RetroPad -> Emulator
The tricky part, for me, is getting it configured. When I plug it in, I can navigate the Retroarch menu as expected, everything works great there. I have Lakka running on a Pi4, and I have a Chinese N64 USB Controller. I'm sure guides exist for this, I just can't seem to find them - shoutout to how absurdly popular RetroPie is, it has completely drowned out any Google results for just about anything else.