![retrolink n64 controller max throw retrolink n64 controller max throw](https://technabob.com/blog/wp-content/uploads/2013/06/nintendo_lamp.jpg)
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)
![retrolink n64 controller max throw retrolink n64 controller max throw](https://i.ebayimg.com/images/g/NaAAAOxy4t1SlFfB/s-l300.jpg)
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.
![retrolink n64 controller max throw retrolink n64 controller max throw](https://retrododo.com/wp-content/uploads/2020/11/How_To_Buy_An_N64_Controller_In_2020.jpg)
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. At this point, the issue still only exists in lr-mupen64plus-next, as far as I can just for curiosity sake I took a Raspberry Pi 3 and loaded the latest 4.5.1 RetroPie image on a fresh SD card. Then I went to go and test with mupen64plus-GLideN64, but I had to modify /opt/retropie/configs/n64/InputAutoCfg.ini because the ES mapping script left it in a dysfunctional state (check out C button D): Generic USB Joystick _STARTĪfter modifying that to match the actual button values (A = button 6, B = button 8, C down = 2), both A and B buttons were functioning as expected in ROM's. Also tested with lr-gambatte on two ROM's and A and B are also working as expected. Just tested with lr-snes9x on two ROMs and both A and B buttons are mapped correctly and working as expected using the Retrolink N64 controller. Input_state_slot_increase_btn = "h0right"Ĭorrect, jtest confirmed that button 8 is the physical B button, as it is mapped in the auto-configuration file. Thanks in advanced! input_device = "Generic USB Joystick " This is driving me crazy, where else should I check to see what is causing the logical B button to get unmapped or disabled? I've included my joystick config file below if anyone would like to review it. I've also tried removing all the hotkeys from the config file and it has no affect. I've also tried mapping the logical B button to various other physical buttons, and pressing every button on the controller, and it just will not work. cfg" causes the physical A button to work as expected, but the physical B button still will not work for the logical B button (can't back out of menus, etc.)
![retrolink n64 controller max throw retrolink n64 controller max throw](https://images.gutefrage.net/media/fragen-antworten/bilder/132394137/0_big.jpg)
RETROLINK N64 CONTROLLER MAX THROW INSTALL
Latest RetroPie setup script with basic install.Fresh, updated Raspbian Lite with Wifi and SSH enabled, stock video settings.This has been driving me crazy for the past few days.