@james-milroy Could be, but the cause is the same - the device is not recognized as a controller, but some other input device. Using evtest instead of jstest would list the input devices present and would let you pick which one to test.

@mitu said in Shanwan usb controller analog/d-pad switch issue:

Which manual ? The one that I found for this gamepad mentions the Home button to switch between XInput/DInput.

I refer to the same manual

@mitu said in Shanwan usb controller analog/d-pad switch issue:

Since most games don't support the analog controls, it's normal. RetroArch has a setting for the controller (Analog to Digital Type) to make the joystick control the D-Pad, without the game supporting it.
Open the RetroArch menu, go to Controls -> Port 1 Controls and set Analog to Digital Type to Left Analog or Right Analog to use the joysticks instead of the D-Pad.

I have also a PS1 controller and I'm able to switch between analog and digital in games, so I thought to do the same with shanwan too

Nevermind, it's solved. Problem was in the connectors...
Topic can be deleted.

I had tried all 3 methods on my pi 3. I used the manual cmake steps, I had tried the wget install.sh method, and I had also tried the GUI option in the retroarch "optional package" menu. I ran into no errors during any method, but nothing worked. Nothing was responsive in jstest. When performing the GUI option pi 2.5, it worked. (I didn't try other 2 methods on the pi 2.5 as my first attempt worked).

I think its my pi. I bought it a few years ago and this was my first time trying to use the GPIO headers. I downloaded a pigpiod GPIO test script and it identified some of my pins as bad. I think I'll grab a pi 4.0 in the near future.

I made a video going over my gamepad design if anyone is curious.

@Clyde Thank you that is good to know.

I have moved my question about the 2nd controller to a new thread so as not to contaminate and confuse there. thank you all.

I know this is old, but this is the only thread that keeps coming up in searches that has fixed this problem for me, and I wanted to say thanks, and also include my controller model in case it helps anyone else.

Controller: GameSir G3s controller in X-input mode.
Left and right triggers were working at one point, and somewhere along the line, remapping the controller broke analog L2/R2. However, manually editing the config, like the user above (rilight) to +2 and +5 (yes, you need the + in there), fixed it for me. Specifically, this problem was plaguing me while playing OutRun on MAME.

Just wanted to say thanks to mitu and rilight. ;-)

@luzer I am in this exact situation, did you manage to solve it?

@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:
alt text

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.