I watch this video and I done everything as shown, still same problem. I successfully connected Xbox controller but ES does NOT detect it. I still can't configure buttons and jstest is still same, nothing changes.

@Riverstorm no worries. 😊

@gogangdong said in RPI4+GPIO acting strange: 4.5.13 The hardware was wired to the GPIO for the wiring of the mk_arcade_joystick_rpi and the mountains and joysticks, Sanwabuttons a,b,x,y,l,r,start, and select buttons to fit the GPIO and install 4.5.13 (https://files.retropie.org.uk/images/weekly/).B,Y,Other buttons on joystick did not work. mkarcadejoyystick 0.1.7 version(https://github.com/RetroPie/RetroPie-Setup/blob/master/scriptmodules/supplementary/mkarcadejoystick.shSetup/blob/master/scriptmodules/supplementary/mkarcadejoystick.sh In the input setting of the retropie, say you found the GPIO controller and enter the keystroke (if you press Y, GPIO).They say they found the controller and enter the keystrokes. The joystick and other buttons do not work and the key setting sets the joystick to the top and B buttons, and the other buttons do not work.)

Take a look at this recent topic - https://retropie.org.uk/forum/topic/22337/gamepad-calibration-problem/3. If the emulator is using the new evdev api to read/access the gamepad, then jscal doesn't have any effect.

Turns out it was underlying OS issue. For whatever reason, the update broke the gamecon driver for SNES controller input. After uninstalling the db9 and gamecon drivers, rebooting, reinstalling then rebooting, my pad now works as one would expect! What cued me into it was while reviewing logs after an update failure I found a gamecon update failed message. Researched it and found this info at the link below. https://retropie.org.uk/forum/topic/3875/solved-gamecon-installation-fails/10 @Efriim, really appreciate all your help and insight onto this issue. You helped direct me to look more into the software side and that's where it was.

@mitu Yes

im having the same issues, retropie 4.4 installed, 360 controllers working perfectly, then update and bam, broken. all advice says: don't update. so ill roll back to new, and wont update, not updating bothers me a bit, that feeling that newer is always better is hard to break sometimes

@deeobat the manufacturer confirmed that the cable is not compatible with Retropie. Oh well.

@nsuk ok so you made me look like a jackass thanks.

@com_gunner said in Conflicting joysticks?: https://k60.kn3.net/taringa/C/7/6/C/F/8/comgunner/08F.jpg Hi every one. I used command line in Terminal lsusb and I got this information: Bus 001 Device 004: ID 0810:e001 Personal Communication Systems, Inc. Bus 001 Device 005: ID 0424:7800 Standard Microsystems Corp. Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub How to know where is mine? I use this one oncoder:

I set it directly in /opt/retropie/configs/all/retroarch-joypads/THTTHTArcadeconsole2PUSBPlayer.cfg input_enable_hotkey_btn = "8" If I use the Retroarch menu (Settings/Input/Input Hotkey Binds/Enable Hotkeys), I can't set it to 11 because is on js1. I can only set button from js0.

@pnoeric you press it once then start pressing other keyboard keys. You will see a key number appear in the upper corner everytime you press a key.

@columboscoat school boy error on my part the joystick cable from the board was plugged in upside down, Its now registering all axes 8-)

@g0nz0uk some bluetooth controllers has different numbers than those returned by jstest. But it still is the best tool I know to get the numbers...

Fixed my problem. Figured I'd post the resolution in the event that somebody else inevitably has the same issue. gunnarh's posted solution was right. It's not an issue of the multiple joysticks. It's actually the sketch. You need to use the bounce library, like was used in gunnarh's link. Without it, the buttons don't get recognized properly within retropie. I went as far as to edit the usb_desc.h for the teensyduino libary to only have it expose the joystick, and nothing more. That worked for only having a single joystick show up, but the button issue remained. It wasn't until I utilized the Bounce library, that my button presses behaved as I expected.

I am using Asciinema for that for some time now.