@JKimRX Is it a keyboard with a Fn key? Make sure capslock and numlock are off, some of them have a Fn lock ya know. Also retropie uses UK default so it is a good idea to change now to US using raspi-config if you use that layout.

@bengalsfan88 said in Help with mapping 4 start buttons for Galaga/Ms. PacMan: I'll be sure to make a post when the project is complete and the cabinet is restored to her former glory! I'd like to see that, thank you !

I'm starting to think that the issue is with the mame2010 driver in libretro. The inputs in other libretto emulators are not problematic (e.g. street fighter in Super Nintendo works fine with all buttons)... but many of the street fighter II sets in mame2010 have issues with second player buttons. Something for the libretro people to fix I think.

I have an old model IPAC4 that I used back in 2008 running Win98, XP, etc. and I eventually rebuilt my system around the PI (you can see details linked in my profile or signature below). Anyway, my IPAC has the PS2 connector but works with a USB adapter cable. Here is the thing--the IPAC is a keyboard. Or at least it looks like one to the computer to which it is connected. Your joysticks, assuming they are microswitch-based, could be pushbuttons. There is nothing about the fact that it is a stick vs. a button--it is simply shorting the input on the IPAC to ground. So, what happens if you wired a joystick to BUTTON1,2,3,4 on the IPAC? I would think this would let you trigger those buttons when you move the stick to short the respective inputs. If true, you should conversely be able to wire a button to one of the joystick inputs and pressing the button should trigger that key. And this brings me to my point. . . Do you know what keyboard keys are getting sent by each directional trigger? How are you testing on the Pi? Are you opening a text file in Pixel for example? My player 1 joystick maps to the arrow keys I think. So, if I open a text fine on the Pi, I can move the cursor around just like I am typing arrow keys. I know I am not offering an answer but more of a testing method. Mapping keys can get really confusing once you launch an emulator, so my approach is to verify the raw inputs are getting out of the IPAC and into the Pi. One approach to testing keyboard inputs is to launch the keyboard testing executable from AdvanceMAME at commandline. This will let you watch on screen what the PI is receiving when you pound on buttons or move your sticks. I don't remember the test command off-hand, but if you dig into the Docs here on the RetroPie and look for the Spinners/Trackball page, there is a similar test you can run for Mouse input. I know, we are not testing a mouse, but there are three executables in there for AdvanceMAME that let you test each Mouse, Joy and keyboard inputs. Might be worth a little time looking that up. Sorry , don't have my Pi handy to check. My thought is that once you know the inputs are getting sent, you are no longer troubleshooting the IPAC, but rather the mapping. Knowing that much can go a long way to figuring out the next step.

was this ever solved?

@rolandpibb Joystick numbers, jsX, are assigned in the order they are recognised by the Pi as it boots. I believe the XBox controller needs to come out of a stale state so, when the Pi boots, the USB controller is recognised straightaway and assigned js0 with the Xbox controller assigned js1. My PS3 controller needs to come out of a stale state which can be seen by the LEDs blinking for a second or two as the Pi boots before the player 1 LED becomes solid. My fix is to plug in the PS3 controller before the Pi boots and then plug in my generic USB gamepad once EmulationStation has loaded.

Its a mess... after trying numours installations i cant fix it. The issue is too annoying too look over. Im done.

Never mind. Found out it's the recent update to RetroArch causing the issue. Re-installing the image without updating fixes the issue.

@barbudreadmon Evo 2014: https://kotaku.com/the-2014-evo-champ-just-won-using-a-ps1-controller-1604535870

I had all sorts of issues with the ds4 using ds4drv, it caused the pi to overheat, but I didnt have any lag, either way, I purchased the usb dongle for the ds4 and the problem was instantly gone. for 20USD i would reccomend you dont waste your time, and just buy the dongle.

@bengdahl Did you ever find a solution for this? I'm having the exact same problem.

@WetpantsMcGee Good to hear. Welcome to the forums btw.

@lensdrifter Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first Anyways: Which emulators are you using to emulate "arcade-classics"? Which roms/"arcade-classics" you tested it with? Which 8bitdo controller do you use?

@wack26 Pleas update RetroPie-Setup and install mupen64plus again. Keyboard should work now.

This seems the most similar to my issue I've found. What is that editor you are using for the .cfg file? Also, this wouldn't happen to be with DragonRise controllers would it?

@edmaul69 i don't have money for that and i use it in pc games fine. It's just i need an fix for the b button bug