@Efriim Thank you! This fixed it. Player 2 is not set up yet as I am waiting for the second dolphinbar to arrive from Amazon which is tomorrow :)

@Zpider33 Sorry for the late response. The text you are meant to copy is in the "es_temporaryinput.cfg" file, NOT the image. I put the image to show visually what you should copy, but your controller configuration may differ. I apologize for the confusion.

I also wrote this once: https://retropie.org.uk/forum/topic/12836/guide-how-to-n64-controller-setup-with-micro-s-n64-pcb-converter-and-mayflash-usb-adapter If you wanted to compare. :)

Thanks for the update, it's interesting to follow your way to a working solution. Yeah, it seems that it is a kind of game of chance to get the right BT controllers for the Pi, may it be that I was lucky or you and @gpmcty were unlucky. And yes, it seems to be either direct connection without the home key, or using an adapter. Ironically, I'm fine with my adapter although I don't use the home key anyway. :)

I figured it out (Wii U), thank you so much!

@sony_simon my compatibility is far better in lr-mupen than the standalone. I get so much lag and many games just black screen in the standalone.

I got mine working as well, the trick, I think was to copy in the ini file (changing the name) and let the config file generate it's own information based on the ini file (device id etc). I did set the number to 0 (full manual) for the controller, but it doesn't seem to matter as it changes back automatically once you launch a mupen64* emulator. The controller will only work in mupen64 emulators though, so I may still return the adapter for something better. N64 is SOOOO much better with a real N64 controller though. Not sure why this failed for me the first time, I think by taking in the cfg file I corrupted something.

@NoOddJob as @polish-potato said. On any mayflash adapters i have used, player 1 and 2 are backward. If that isnt it then re set up your controller. Write down what numbers all the buttons are. Now open up the /opt/retropie/configs/all/retroarch/autoconfig/ folder. Now find the configs for your controllers. Verify if if the numbers match. If they do then run sudo jstest /dev/input/js0 Now push the buttons and verify if the buttons match there. If they dont, then change your config file to match the jstest.

Yeah I got mine as well and besides no random button presses, the controllers are also much more responsive, which made me forget about really needing wired controllers for certain games!

@mitu Hey, thanks, I want to see if I can utilize that. I never knew about that. What an awesome approach! The thing is, I am quite familiar with compiling kernels, not so familiar with how "modular" and dynamic modules can actually be.

Try a different adapter. That MayFlash didn't work on my two 3-button's, and only only a select amount of my 6-button controllers (maybe a little over half of them).

@Furluge yeah i was the reason that raphael learned about the issue which affected a crap ton of controllers. Then he so awesomely found the bug in linux and created the fix for it. But yeah its been fixed for a long ole time. 😊

@mediamogul I would be excited to see this utility opened up to other devices. Hopefully you find the time and motivation to dig into it. Also I hope lightgun support get a little more focus as well... so many awesome games to re-visit.

I've been fighting this same problem today. I have a bunch of different RetroLink controllers (Atari 2600, NES, N64, Genesis) and they all overwrite each other. My workaround was what @meleu said. I had to hardcode the mappings for each specific retroarch.cfg file and then I configured the NES controller through ES. The fact that you can hot-swap controllers makes it not too bad. I just use the NES controller to navigate and once I fire up a ROM, unplug it and plug in the proper controller.