I'll try that config file from the database on both setups and see if that yields any different resetting RetroArch's main configuration yielded the same results. opt/retropie/supplementary/emulationstation/scripts/inputconfiguration.sh Īnd the mappings you had me check in es_input.cfg are exactly as they should be: The game's B button was mapped to some "Y button (left)", and the physical A button on the controller was mapped to (C1), whatever that is. Once I fix those, native mupen64 works fine, but altering the libretro mapping doesn't.Īt this point, is it possible there is some bug in the mapping of controls for lr-mupen64plus? Or a possible incompatibility with this controller? Really appreciate any thoughts you may here's what the RetroArch RGUI had for controller mappings.
And the joystick configuration in /configs/n64/ is incorrect as in my previous test, specifically for the A, B, and C down buttons: C Button D = button(6) button(2) The joystick configuration in /configs/retroarch/autoconfig/ is 100% correct however in lr-mupen64plus the B button controls the A button, and the A button does nothing. cfg and /opt/retropie/configs/n64/InputAutoCfg.ini my results are identical to my previous test. I followed the same procedure in my original test, only enabled ssh and wifi, and configured the Retrolink N64 controller using the ES mapping prompt and recommended mappings for lr-mupen64plus.Īfter checking /opt/retropie/configs/all/retroarch/autoconfig/Generic USB Joystick. Just for curiosity sake I took a Raspberry Pi 3 and loaded the latest 4.5.1 RetroPie image on a fresh SD card.