Just a heads-up: removing xpad might break the controller in emulationstation and elsewhere. In my case, the triggers weren't being properly parsed, and as such they couldn't be properly mapped. Hence, I wasn't able to simply remove said driver. That being said, the original solution by @tuxophil DOES work properly, and as such I would still recommend it. Keep in mind, though, that the command at step "8" requires a declaration about which controller you want to map. As such, a correct command might be ./controllermap 0 >> ~/my360.txt, if your X360 gamepad is in slot 0. Running just ./controllermap will show which controllers are connected, so use your gamepad's slot from that list.

@prukogui from what I can tell, SWA on lr-2015 has permanent, broken controls. lr-2016 can be properly configured, but will run slower. lr-mame will run even slower, requires a different ROMset, but has more accurate emulation.

2016 seems to run "okay-ish" up until the trench on the second scene, then there are a bunch of graphic anomalies.

Wish I had better news, but there aren't many good solutions for SWA -- at least none that I could find.

@marconemusic also, lemme add.
That the controller order changes if I use a different emulator…
Currently I’m using the LR -

@cherbakalite @ChaosEffect an alternative if you don't want to bother changing device types for console games (including megadrive) is to use FBNeo : every emulated console game has the "optimal" controller settings hardcoded.

@mitu a huge thank you! It works like a charm!

@X_Splinter said in Unable to use keyboard/controller after rebuild boot partition:

Could this be an issue not related to the boot partition?

Most likely yes. The procedure you performed is not guaranteed to recover another system.

If so is the main partition of retropie a regular EXT3? So I may browse and copy all of my files?

It's an Ext4 partition - should be accessible also as Ext3, but I advise using a Linux installation to try and mount it.

@kdragon_2 RetroPie is just Raspbian Linux underneath, so as long as your setup works with Raspbian and the OS detects your setup as a controller, RetroPie should recognise it and use it. As for the how to communicate with it, that's up to you - Linux/RetroPie already includes a few drivers that interpret GPIO inputs as a controller - look in the Docs.

@europadecas Despite my arcade, electronics, Linux, and coding experience I found Retropie to be a very complex and difficult to manage project. Kudos to the devs for integrating this many emulators into a single environment, and kudos to the support forum here for the help!

I wasn't sure about that line as it looked to do the same thing, however when I pulled the lines from the main retroarch.cfg file, both lines were there so I put them both in "just in case."
Could be that the core looks at one line and retroarch looks at another, or that some lines found else-ware look for the other string.

@mitu said in Diffrent controller map for select emulation?:

@nathan1031982 Looks like a case of https://xkcd.com/979/ - what was the solution ?

The original solution was provided by the reddit user delusion666. I modified it because he was using RetroPie 3 and I am running the latest version as of a week ago.

I configured my controller in EmulationStation. It created a controller config file in:

/opt/retropie/configs/all/retroarch-joypads/

In my case, it was raphnet.net (S)NESAtari_USB.cfg

Next, I created retroarch-joypads dir in the MegaDrive configs dir and copied the raphnet.net (S)NESAtari_USB.cfg to there:

/opt/retropie/configs/megadrive/retroarch-joypads/raphnet.net (S)NESAtari_USB.cfg

Finally, for retroarch to see the file, you need to add or change this line in /opt/retropie/configs/megadrive/retroarch.cfg :

joypad_autoconfig_dir = "/opt/retropie/configs/megadrive/retroarch-joypads/"

I commented out the original line and then added a new line above it for backup/troubleshooting purposes so my file like like this at the line :

joypad_autoconfig_dir = "/opt/retropie/configs/megadrive/retroarch-joypads/"
# Original line - joypad_autoconfig_dir = "/opt/retropie/configs/all/retroarch-joypads/"

I had to do that for the MegaDrive, Sega 32X, and Sega CD. I don't think you need to make the file three times, probaly just need to make sure the path is correct. However the map file is real small so I made one for each system.

Finally, I re-configured the SNES controller so if I load up anything with the SNES controller, it's mapped out correctly.
Now if I load up either the MegaDrive, 32X, or Sega CD RetroArch uses the controller map for the Sega controller.
I was lucky as the buttons for the D-Pad, A, and B didn't change with the SNES mapping so the Sega controller works the exact same in EmulationStation.

Good luck. If you still need help, just ask and I will try to assist.

What is the setting where you go back/exit called? If I push 1 on the logitech pad I exit emulation, which is the B button in nes games.

There has been some discussion on controller localisation settings for ES where you could choose what help icons you want per your controller but that also has similar issues with mappings/integration with libretro's configs

@cerealspiller you could try to manually do it in /opt/retropie/configs/psx/retroarch.cfg

You could try this tutorial (at own risk): http://www.instructables.com/id/RetroPie-Overclocked-Raspberry-Pi-3-for-Video-Game/

@Pdub517 said in BEBONCOOL - Controller button mapping:

Any suggestions?

Yeah, for starters, how about reading this, then provide the details listed. It's hard to give advice when we don't know stuff about your build, which exact emulator you are using and so on and so on. Be specific.