Mame 2003 unresponsive when 2x PS4 controllers are used.
-
Hi,
Thanks for reading this firstly.
I have just setup a Raspberry Pi 2 with a clean install of Retropie v4.0. I've copied across ROMS to the Mame (2003), NES, SNES, Sega Master System & Mega Drive emulators. I attached my PS4 controller configured it via the GUI within the Retro Pie Menu (within Emulation Station) and have been playing away nicely for a few days.
Until everyone in my house decided they wanted to be involved :) Out came the second PS4 controller which once plugged in worked straight away (no configuration required) and we started playing Final Fight within Mame (2 players via 2x PS4 controllers).
Suddenly, I could no longer insert coins in MAME (select button) and none of my PS4 buttons would work within Mame. If I restarted the Pi all other emulators were working. However, I noticed that when I loaded a ROM in Mame it would say something like 'PS4 controller not configured correctly in yellow down at the bottom' and the controls would not work.
After looking around the internet I found the following fixes:
A. To disable the back / trigger buttons on the PS4 controller. I did this and after reinstalling my build from backup I happily played away in one player mode thinking it was fixed. I plugged in the second controller and as soon as MAME entered into a game none of the buttons worked and the message appeared in yellow at the bottom again saying that the controller was not configured correctly.
B. I found this Youtube video telling you how to fix this problem if you have one controller not working:
However, this seems to be for an older version of RetroPie and the menu options that it advises you to navigate no longer exist.
If you have got this far thanks for reading this. I would really like to get my RetroPie up and running with two controls and have ran out of ways to progress this myself. Any help greatly appreciated!
-
If anyone can find a fix for this I will donate $100 to rstro pie.
-
Please paste this into a terminal over ssh
sudo __nodialog=1 ~/RetroPie-Setup/retropie_packages.sh setup updatescript sudo __nodialog=1 ~/RetroPie-Setup/retropie_packages.sh setup post_update rm /opt/retropie/configs/mame-libretro/retroarch.cfg sudo ~/RetroPie-Setup/retropie_packages.sh lr-mame2003 configure
and see if that helps
-
if not, you can try reconfiguring the controller from inside ES - pressing "Start" then go to the option called "configure input" or similar. Also - have you manually modified any files whilst trying to "fix" this ?
-
@BuZz Hi, thanks for the response I will try those fixes in the morning and see if it helps!
I have not changed anything manually in any .cfg files. I read some articles about setting the driver to udev in retroarch.cfg and controller.cfg would this help also?
-
it should be udev already in RetroPie 4
-
@BuZz Thanks. What does the above commands do that you told me to do... sgould i do this with both controllers plugged in ?
-
they update retropie-setup. remove the mame-2003 retroarch config and reinstall the default, as I suspect the issue could be related to corrupt/broken retroarch.cfg. If it doesn't work I will have to request some of your configs to look at.
-
Hi,
So I ran the commands from SSH. Booted up the Pi and only one controller recognised. I typed in LSUSB and could see that the Pi could only see one controller. After multiple tests I did some testing and it looks like the USB cable is faulty. This would explain why the second controller is not recognised however it did work up until (and after the problems).
I will borrow a controller from a friend and see if I can get this working but to be honest I might just try and get a second controller running with Bluetooth.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.