@wiggy808 When you have the 2 X-Xarcade Tanksticks connected, exit ES and run from the terminal cat /proc/bus/input/devices then post the output here. If there are 4 joysticks/gamepads detected, then they're correctly functioning. Next, you can check in FBAlpha if the gamepads are assigned correctly to inputs by opening the RGUI (Select + X) and going into Configuration -> Input to check if each player has the gamepad assigned. You can change there the gamepad index for each player to see if all 4 players would work. What ROM are you using to test the 4 players ?

@leitmotiv You can use the same topic, it's up to you if you want to use another forum or not - you might try the AdvanceMAME forums.

@BuZz Yes I did see it in a guide, I can't remember where. I am not enthused by the idea of setting up a fresh image again, but if I don't come right, then I will. @cyperghost The buttons work in the games now, but not on the retroarch menu.

As with the old controller, there's no 1:1 mapping between the cables/wires and the actual buttons - you can't wire it directly to the GPIO and expect it to automatically work, you'll need a driver. When you're talking about the 'new' NES controller, do you mean the one for the NES Classic Mini or the one for the Switch ? The controller for the NES Classic Mini has the same port type as a Wii (U) Classic controller - see here and here for details.

@pengu1n said in GPIO Controls Not Registering After Launching Games: [WARN] Input device ID 3 is unknown to this libretro implementation. Using RETRO _DEVICE_JOYPAD. That's because of the RA's configuration - try resetting the configuration to default by copying the retroarch.cfg.rp-dist files over the retroarch.cfg in the /opt/retropie/configs/all/ folder.

@retropieuser555 I notice in your picture that the User 1 Device Type is set to Sinclair 1 Joystick. I tested this setting and Hen-House Harry moves to the left if I press the B button and to the right if I press the X or Y button even though I have nothing mapped to those buttons. Could you try selecting the User 1 Device Type to the Cursor or Kempston joystick?

@greengrounds but yeah put the power supply into that hub. Then the power supply is giving power to the controller and the pi.

@DreadfulDreamZz You need to change the controller type in both the Quick Menu's Options and the Quick Menu's Controls, then restart for the Quick Menu's Options changes to apply. I use DualShock and RetroPad w/Analog as the Core's default options and controls, while I change to Standard in the options and Retro Pad (alongside mapping the D-Pad to the left analog) on controls for games that are digital-only or don't have analog controls then save the changes for that game specifically. The spreadsheet listed on the wiki is fairly accurate and quick way to see which controller each game used. https://retropie.org.uk/docs/Playstation-1/#game-specific-control-information Only covers USA games though. Go to the PlayStation DataCenter for information on everything else: it's what the spreadsheet above was based on. http://psxdatacenter.com/sitenews.html Might be some inconsistencies between the two as the sheet hasn't been updated much since creation, incorrect info was seen on the site yet not reported (because I was already putting so much time into the spreadsheet), and it's possible something was incorrect on the site when the spreadsheet was made and is now fixed on the site. One of these days I need to make the time to update that PSX documentation since it has so many problems such as directing users to do manual edits when things could be done in RetroArch.

Thanks but I appear to have found the problem. It seems that udev was blocking the new controller. Creating a new udev rule seem to have corrected the issue. For anyone else having this problem, first identify the name of your controller. There are several ways you can do this but the simplest it probably to just look through the system logs. With the controller connected (either via bluetooth of hardwire) cat the messages log. sudo cat /var/log/messages You'll need to look through the messages for the right device name but if you just plugged in the controller or connected it via bluetooth it should be near the bottom. It may even be the last entry in the log. Apr 20 16:31:13 retropie kernel: [ 8.528199] hid-generic 0005:1949:0402.0001: input,hidraw0: BLUETOOTH HID v1.1b Keyboard [Gamepad] on 00:1b:dc:0f:9d:ae Then create a new udev rule in the approprate location. sudo nano /etc/udev/rules.d/99-bluetooth.rules SUBSYSTEM=="input", ATTRS{name}=="Gamepad", MODE="0666", ENV{ID_INPUT_JOYSTICK}="1" Once done simple restart the system and it should now work in EmulationStation. I hope this is helpful for someone! If nothing else I'm sure I'll be back here one day trying to figure out what I need to do again. :-P

AWESOME!!! Just testing it out, when I went into RetroPi configure controller it recognized it as 2 gamepads right away, configured each and was instantly playing some Street Fighter Alpha 3 with my 5 year old. I works great! Thanks for the help, should have notice my mistake, the devil is in the details as they say. I read so much I have developed a tendency to be lays and just speed read without even realizing I'm doing it. I my brain just saw 'add to it's own line' for some reason. Anyways the device should be included by default and hopefully this will be fixed in a new version so folks don't have mess with it manually. Guess my wiring job was spot on, I don't have any issues now. Thanks again.

@cyrusxvi Yes - just follow the docs and use the sixaxis helper for the P3 controllers.

@Zore I don't see any errors in the log file. Can you also post the contents of ~/.emulationstation/es_input.cfg ? Check the permissions on that file also, if your user is able to write to it.

my bad, I did some mistake in following https://www.reddit.com/r/RetroPie/comments/9aswsl/how_to_separate_up_2_controllers_off_1_port/ which has solved my problem

@mitu yes, have uninstalled them all and it seems to have done the trick. Thanks :)

@polygonman244 if you have mapped a keyboard in emulationstation it will never ask again for you to configure a controller.

@BuZz I did

@mitu True, its not too difficult. Maybe I'll just save all my files and redo everything fresh. Its been far too long.

@mitu thanks for the help. It worked great

@Mondo-Gecko I've never tried using Bluetooth controllers, but I'll give it a shot and check what happens. I don't have access to my Raspberry Pi until at least the end of next week though.