@YFZdude I see. Thanks for the info and the tip. But the issue I have, and the reason I wanted for every button to work on d-input, is the fact that both controllers have the same name in switch mode, which is a problem with their wildly different layouts.

@nemo93 Ok thanks anyway.
I opened a topic on GitHub.
https://github.com/BlitterStudio/amiberry/issues/1022#issue-1405758532

Assuming you're referring to the pairing info saved by Linux, you may try copying over the /var/lib/bluetooth/ folder. It's only accessible by the root user and you'll need to use the command line to copy it somewhere to back-it up.

@windg Not (yet). On the RPI (and probably other embedded) platforms we install a patched SDL2 library, but not on PC - where we use the distro's version of SDL2.
When the SDL2 library shipped by RetroPie will be upgraded we'll make sure to accomodate the changes done in upstream SDL2. For reference, see the discussions on this RetroPie issue.

One point to note. On my GPi it looks like I could probably have hard-coded the value to unbind/bind the built in controller. But I felt it was taking a risk it wouldn't work right. So, instead, I use a temp file to pass the value between scripts.

@hawkes_84 I'd like them to do an M30 Pro with dual analogues, hard to fit on the 6 button layout though. There's a cheapo Chinese one that sort of does it, they've tilted the buttons the other way to make room for the right analogue. From what I could work out though it's not a proper 6 button layout, one of them is for turning on autofire.

Got a 2.4G M30 on the way for my real Mega Drive, can't wait!

Update for anyone who is curious, I ended up buying an "8BitDo Adapter 2". After updating the adapter's firmware using 8BitDo's firmware updater, the adapter makes it pretty easy to connect a Nintendo Switch SNES controller to a Retropie.

@Grasscastle please give more information about your setup as requested in https://retropie.org.uk/forum/topic/3/read-this-first

@Dr_Goggles

I'm about to try the same thing you went through. I tried to update a pi which hasn't seen any updates for the better part of like 5 years, and got errors saying I need to update from stretch. The update finished (with failures) and now the pi boots up the retropie screen, then powers down. So I have to update or else I can't even use the pi.

I have another pi in the house which is basically identical, so I'll be attempting a clean install of buster with the hopes that I don't lose functionality of my very- simplistic use of it. Mostly just watching video files in kodi from an external hdd, and a bunch of roms I can copy from the other pi.

I'll probably make copies of the config and rom folders before I download and flash the new retropie software. But I haven't done this for a few years and I hope it's as easy as it used to be. Any roadblocks you overcame that might help me would be appreciated. I didn't see you make a 'success!' post so I can only assume you got it figured out and are back in business.

@mitu WELL after I did the jtest my original controller didn't work anymore in the GUI so I did a sudo reboot. While it was rebooting I removed the dongle in sadness and saw "xbox controller disconnected" small info tag in the corner, and BOOM now xbox 360 controller is working!! I have no idea after countless reboots it worked.

Thank you

BTW it's like I'm hitting F12 using the right dpad button. :/

Does wireless mean the controllers are connected via Bluetooth ? Is the disconnect happening if you use just one controller (and not 2) ?

@paulfecht Why don't you open a separate topic and describe your setup (see https://retropie.org.uk/forum/topic/3/read-this-first) and your problem ?
You may get a response from other forum users as-well - the original topic poster hasn't logged in since they responded to this topic.

@barbudreadmon thank you, I did end up remapping the controllers.

@rasp_renegade Hello, it happened to me too. But after loading a new firmware ( IPAC2_155c.ufw ) under the WinIPAC, I also loaded the Default Ipac2.ipc ( you can find it under C:\Program Files (x86)\WinIPAC V2\Defaults\ folder. Somehow before this there was no keys are mapped. The default Ipac2.ipc solving such a problem easily.
Kind Regards
Niyazi