I don't know much about two player, but try pulling the plug, then plugging it back in without controllers. You'll get to the configure screen. Configure your second controller if it is unconfigured then press any button on your player 1 controller to get to Emulation Station. I don't know but theoretically it should work fine.

@Evert said in DualShock controllers with a mind of their own: I would agree that something has changed. I never had this problem when I was running Jessie. Same Pi, same controller. I only changed the SD card and installed the latest nightly. I didn’t update the firmware so maybe kernel. Yes, agreed. After checking a related bug report, it seems that driver changes between kernel 4.14 to 4.19 may have exacerbated the issue. Judging from the replies to that bug report, it looks as though reducing the baud rate even further (to 115200) may fully eliminate the dropped packets on the newer kernel releases.

@Dj-EKI If you'd like that combo to open the menu, then open RetroArch from the RetroPie system in EmulationStation, set the option and then save your configuration. To leave a game, you'll have to use either a Hotkey + Start - which you don't want - or disable the Hotkey and choose another button for the exit hotkey. Pressing that button will automatically exit the game.

@Dj-EKI map z to left trigger I believe

But... if you're trying to just prevent the message from appearing when you don't have a controller available, the easiest solution is to configure a keyboard as input in EmulationStation. When started, even if there's no controller connected, EmulationStation will skip the welcome message and go right into the system list.

@Dinsdale Your screenshot shows an error that happens during pairing in the Bluetooth setup - possibly a timeout during the process. Re-connection is handled by the OS, there's no RetroPie script involved afterwards - so I don't think that's the problem. EDIT: you can try and pair the controller manually - see https://approxeng.github.io/approxeng.input/bluetooth.html, the Pairing with Bluetoothctl section).

Amazing! This did the job!

The PS4 DS controllers show as 2 devices - one for the touchpad and one for the actual gamepad, that's why you have 6 listed. There are some hints on how to disable this in this topic. Also, please add the info detailed in https://retropie.org.uk/forum/topic/3/read-this-first when opening a support topic, it's easier to diagnose things.

@IanDaemon I just changed the line in my cmdline.txt, but I don't really notice anything different.

Ok so a Xbox /Playstation type of control, got it. Thanks guys

If it's a generic USB Xbox clone, then it should be handled by the xpad driver. Can you run - from the command line - cat /proc/bus/input/devices and then post the output ?

@quicksilver Thank you very much and have a great weekend.

@quicksilver I also remember that on original N64 hardware that if the analog stick was pushed while the game was booting up the crosshair/selector would get stuck trying to go one direction. I also remember this, very annoying. But once my N64 joysticks were worn out, I put the analog stick back a bit to not have to press it as much forward to have it react.

I ended up rebinding all the controls through trial and error. Seems like there is no logic behind the labels. But now it works. Also, turns out the erroneous mapping was for player 2 as well, but I could copy the same mapping to player 2 after I had saved settings for the core.

@Pundan I did not really look forward to rebuild the entire Retropie installation with thousands of ROMs (pretty much had every system there is scraped and sorted) just for this I feel your pain. After having to go through that I started storing a big chunk of ROMs on an USB flash drive. It makes rebuilding so much easier! I've also tried storing them on an external USB hard drive (non solid state) and they usually work great with smaller ROMs but with like the larger PSX games, if you're playing a game and the hard drive spins down and then the emulator needs to read the game disc image again, most times it will crash because it times out before the hard drive can spin back up, so in other words, use a solid state drive! Running ROMs from a USB drive: https://retropie.org.uk/docs/Running-ROMs-from-a-USB-drive/ Loading roms from USB harddrive: https://retropie.org.uk/forum/topic/7780/loading-roms-from-usb-harddrive