@mitu Oh, yes that file. I tried that but no luck. I remapped and got the same result. Although up and down are reversed, they work just fine but it won't read left and right. Daphne is such a pain to get going. I've done the jstest and see the stick is axis 0 and axis 1 and return a pos/neg 32767 on each axis. I don't have any issues with any other emulator I have games for (Fba, Mame, PS1, Sega Genesis, Nes, SNES ,PC Engine). I can't understand what the issue is with Daphne and the axis mapping.

@Rookerman Swap the controller ports on the actual pie.

Please add more info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

@MaMikee Just had a thought, if you followed the manual install instructions, it may have changed your version of GCC to an old version which may affect your ability to compile. I can't remember what it was but it definitely happened to me at some point. Edit: It was this line, forced an earlier version of cpp and GCC to be linked as current version: sudo apt-get install -y --force-yes dkms cpp-4.7 gcc-4.7 git I think I had to force reinstall the current builds of gcc and cpp back on over the top. Si

I have managed to get it operating correctly. I just need to configure the buttons now. Thank you.

@funkotron77 While there might be a way to get it to work as-is, turning your tanksticks keyboard into dual controllers would be more beneficial, did you install and ran Xarcade2Jstick as mentioned in the X-Arcade guide ?

@SpudsMcToole Very true.

@vsilvalopes I know the Dualshock4 new driver (well, it's the same driver for both DS3 and DS4) also adds a device for the touchpad present on the controller (which appears as a mouse), but I don't remember the DS3 controllers having the same touchpads. Can you pair one DS3 controller, then run the following 2 commands lsusb cat /proc/bus/input/devices and post the output ? Have you installed the customhidsonly driver from the RetroPie-Setup drivers section before pairing the controllers ?

Regarding your question about the coin door. could be a bad microswitch. do you have access to a multimeter? you could check the resistance from open to close. Any pics on how you have the coin door wired? Are you sure that you wired correctly to the button. Needs to be wired to the open close. On your buttons it should be the posts that are offset from one another and are on risers

@Tigry Thanks for sharing your solution, glad you found it. Just for completeness, I was going to suggest that you could use @meleu's joystick-selection tool to see if your sticks are configured as player 1 +2. If not, that could've been the reason why they didn't work in RetroArch.

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.

@rsn8887 RetroPie doesn't automatically maps the keyboard as a controller - it only saves the gamepad configuration from the configuration you made in Emulationstation. Unless you explicitely map the keyboard in ES, it shouldn't generate any configuration for it. You can find the saved configurations - one per gamepad configured - in the /opt/retropie/configs/all/retroarch-joypads folder. Must be a new RA thing, does it do the same without the keyboard plugged in ?

@mediamogul Exactly what I needed. Many thanks :)

@spudsmctoole mame4all is not a libretro emulator.

Well, I don't have an IPAC, but maybe some forum members can chime in with their experience, but IMHO shouldn't be an issue as long as all controllers are detected by the system.

Nevermind.... it doesn't work. I tried redoing my configs because the switch pro controller would get recognized 1/4 of the time. Ended up with the Pi detecting the pro controller but not the switch pro controller.... I don't get with this is so difficult with the switch...