@mitu Sorry for failing to mention those details, yes other games work in two player, I just tried another two player game by pressing start on controller 2 at the title screen and it started a two player game. The controllers are both 8bitdo SN30 Pro+ using bluetooth.

@Crush Thank you so much! That worked perfectly

@CH their product page on amazon says to go to https://retropie.org.uk/docs/Xin-Mo-Controller/ for retropie configuration. basically it seems you need to add usbhid.quirks=0x16c0:0x05e1:0x040 to your kernel parameters, i don't know the specifics for linux mint but i'm sure google will tell you how to do that.

@Oxopi said in Controller with retropie: The left analog up, down, left and right says already taken if i hold against the setting it then says not defined The same goes for the right analog That indicates the analog sticks might emit the same input data as the D-Pad. I notice there's an Analog button on the controller - what is the function of it ? You can exit EmulationStation (via the menu or just pressing F4) and test the gamepad's buttons with the jstest command by running jstest /dev/input/js0 and pushing the buttons and operating the analog sticks - see if the analog sticks are overlapping with other buttons/D-Pad. Exit the test by pressing Ctrl+C. Also what should the hotkey be set to You can leave it as default - don't set one and you'll be asked to use Select - or try to use the raspberry button at the top.

@MeltedPineapple I would appreciate if you wouldn't tag me directly, I find it rude. I'm trying to contribute as much as my free times allows in the forum, but that doesn't mean I need to respond to every topic and every user. Please provide the info requested in https://retropie.org.uk/forum/topic/3/read-this-first when opening a support topic. If you have trouble with your controller, try re-setting the gamepad configuration and re-map it again in EmulationStation.

@stevedee78 said in Retroarch Input Bind Config: when I looked in there it was very light, couple of lines, mostly comments Yes, this is the default configuration - it's normal. Then I noticed that it had generated a new tetrarch.cfg in that snes directory, much bigger than the previous one and full of config goodness We don't recommend using 'Save Configuration', core remapping is the preferred method.

Apparently this is an issue with the SN30 Pro itself. I got it working. Here's what I did: Deleted /etc/udev/rules.d/99-bluetooth.rules Deleted SN30 Pro from registered Bluetooth devices Powered on SN30 Pro with Start+B (Android mode) and held Pair button (top of controller) for 3 secs to immediately go into pairing mode. While in pairing mode selected Register and Connect Bluetooth Devices in RetroPie-Setup Script >> Setup >> Configure Bluetooth Devices Selected 8Bitdo SN 30 Pro from list and finished config Did NOT set up udev rule Now the controller is working perfectly; I'm able to open Launch Menu or go straight into games ... no sitting at black screen for ~40 secs. Also no waiting required to navigate script menus either. I did have to reconfigure controller layout ... and the L/R triggers are actually recognized now as well.

@DavidDraper Ah ok will do. Thanks for your response.

@simpleethat I second the Retroflag Snes controller's. But for Mega Drive/Genesis i use the official licensed from Retrobit.

@DavidDraper said in Issue with multiple "USB Controller " controllers...: /opt/retropie/configs/all/retroarch/autoconfig I thought whatever is in there is automatically copied into /opt/retropie/configs/all/retroarch-joypads; It's the same folder, the latter is a symlink to the former. pi@retropie $ file /opt/retropie/configs/all/retroarch-joypads /opt/retropie/configs/all/retroarch-joypads: symbolic link to /opt/retropie/configs/all/retroarch/autoconfig

Just to give a conclusion to the thread, I tried a whole bunch of stuff. I tried jscal, evdev-joystick, updating the kernel, downloading some different files... but ultimately, this is what worked: https://retropie.org.uk/forum/post/227102 I installed hid-nintendo as described in the post and everything just worked like it was supposed to after rebooting the machine. It makes you reconfigure the controller, but after that, it just works.

@mitu thanks for the reply! I don't think there's any way to change the pairing setting on the wired controller. The manual is pretty sparse. The button below the B button is actually the Home button and I have it set to the hotkey currently it's just awkward to use with some of the combinations. I'll have to give the xpad a whirl. I think I managed a work to make it work by manually editing the appropriate .cfg in the retroarch-joypads folder (the same way I set the toggle fast forward to work across all of the retroarch emulators). But I haven't yet added any games to see if it works. I'll report back with my findings. I added these two lines: input_l2_axis = "+2" input_r2_axis = "+5" adding this line: input_toggle_fast_forward_axis = "+5" works to toggle fast forward so I think it will work to make the triggers function. I've got to track down a PS1 game that uses L2/R2 to see if my solution worked. I'll try the driver on another build as it's always good to have multiple working solutions.

Awesome! This worked like a charm. Thank you!

So I just wiped InputAutoConfig.ini and started again. When it's this: ; Keyboard_START [Keyboard] plugged = True plugin = 2 mouse = False DPad R = key(100) DPad L = key(97) DPad D = key(115) DPad U = key(119) Start = key(13) Z Trig = key(122) B Button = key(306) A Button = key(304) C Button R = key(108) C Button L = key(106) C Button D = key(107) C Button U = key(105) R Trig = key(99) L Trig = key(120) Mempak switch = key(44) Rumblepak switch = key(46) X Axis = key(276,275) Y Axis = key(273,274) ; Keyboard_END the game works perfectly, but keyboard only - WASD and cursors and a few others. When I add this: ; usb gamepad _START [usb gamepad ] plugged = True Start = button(6) A Button = button(1) B Button = button(2) X Axis = "hat(0 Left Right)" Y Axis = "hat(0 Up Down)" ; usb gamepad _END the keyboard stops working and the Start, A and B buttons all map to the proper buttons on the arcade joystick, (and button 5 quits back to EmulationStation) but the stick itself does absolutely nothing. Those X and Y axis lines are taken from some semi-gibberish here: https://retropie.org.uk/docs/Nintendo-64/ where it says *"Note for configuring Arcade Joystick or non analogue controller to use N64 correctly. Changing the below inside /opt/retropie/configs/n64/InputAutoCfg.ini From X Axis = "hat(0 Left, 0 Right)" Y Axis = "hat(0 Up, 0 Down)" To X Axis = "hat(0 Left Right)" Y Axis = "hat(0 Up Down)""* But none of those lines, with or without quote marks, make the joystick do anything at all. If I change it to: ; usb gamepad _START [usb gamepad ] plugged = True Start = button(6) A Button = button(1) B Button = button(2) DPad D = hat(0 Down) DPad U = hat(0 Up) DPad L = hat(0 Left) DPad R = hat(0 Right) ; usb gamepad _END nothing changes. The stick still does nothing, whether I put quotes round the hat commands or not. What in blazes do I need to do to make the dumb emulator recognise the stick?

@mitu This was it! I have a script that controls an LED light/Power button on my case, (as well as shows heat/fan speed, etc) and it seems that the new update doesn't like it. If I delete the python line, the retropie command line and the RetroPie UI work as expected. Not sure what the conflict is, but it's clearly to do with the script on my end. Below is the autostart.sh if you're curios. Thanks so much for your help! python /home/pi/scripts/picontrol/picontrol.py& emulationstation

Maybe a config override for that core?

4.2 is very old release, you should update to a more recent RetroPie version, as we cannot continue supporting such old version.