Glad it helped you. My buttons on the 360 controller do the same thing. I just know not to touch them. You may be able to modify the config file in the /nes/retroarch-joypads folder and set the Y and B buttons on the controller to blank (“”). You wouldn’t want to do this for any of the hotkey buttons though. SO right elbow/left elbow which are used to “save” and “load” states. Don’t wipe those out.

side note: I just bought some nes usb controllers off ebay. I configured one and it created a usbgamepad.cfg file. I only set the up/down/left/right/a/b/select/start buttons and left the rest blank (by holding a button to skip the button assignment). The nes controllers work great now that I copied the usbgamepad.cfg into /nes/retroarch-joypads folder. So now that the nes controllers work I probably won’t be using the xbox one for nes games. The controllers do feel too light though. I’m going to open them up and hot glue some washers inside to make them feel more like original.

no mate usb’s auto mount, in RetroPie

I’d like just to point out, I’m not saying this is the way this should be done, this is the way I have done it & it works well for me

ok, here goes,

firstly I edited /boot/config.txt on a fresh RetroPie image.

sudo nano /boot/config.txt

adding right at the bottom

max_usb_current=1

next I format the drive to ext4 via a spare rPi running Raspbian, using gparted

sudo apt-get install gparted

next boot the RetroPie image I prepared earlier, with the drive in.
once set up RetroPie, I set permissions on the drive with, this will allow to add files as & when needed via ftp

sudo chown -R pi:pi /media/usb0

now I don’t use any uuid’s as I don’t plan on using any other drives, (I use a 128gb USB drive)

then i can create folders & add roms…

then edit the es_systems.cfg

pointing directories to

/media/usb0/

well I used to run my system from my USB, but now I’ve changed my setup to using USB only for roms and sd for system files,

ok here’s what I did and all works perfect,

since you’ve done a lot of work already I’d suggest trying this as your addressing your es_systems.cfg

/media/usb0/PSX

if no good I’ll go through my step by step set up

2.5 is more than enough to power the PI at overclock. If you add in peripherals, it’s still enough to power most external (usb powered) hard drives, with a port adjustment in the config.

If you are just worried about controllers and things, you have more than enough power there. My setup is 2amp, and it powers PI at overclock, two controllers, a keyboard, a usb wifi stick, and an external hard disk.

Hi! hapy new year to everybody and thx for this thread. I’m sure it has saved a lot of time to many people!. I’m building my cabinet based on retropie and y have a PCB that is USB-Jamma . I had al the issues described and i solved it with the USB quirks and i even installed the kernel hack, but in Emulation Station , ( only, in mame works fine and i have two devices working in jstest) stil sends multiple signals like in https://www.petrockblock.com/forums/topic/joystick-sending-multiple-actions-with-a-single-click-2-4-2/
Any ideas?

It’s a bios and has the same legal standing as roms I.e. you’re on your own in finding it.

But If there are no roms in the folder they wont show up in emulationstation. You may need to use the cp command if they aren’t transferring from your usb. Or just use samba shares.

https://github.com/RetroPie/RetroPie-Setup/wiki/First-Installation#transferring-roms

Hy, I read the whole thread and all the other ones on the forum, but i don’t manage to make my XBox 360 wired controller work.
I have the same problem of being stuck not being able to press the “select” button to validate the date.

I copied the Hex values in my controller_XboxGamepad(userspacedriver).cfg:

[emulator]
mapping_name = Xbox 360 Controller (xboxdrv userspace driver)
btn_escape = 0x13a

[dreamcast]
btn_a = 0x130
btn_b = 0x131
btn_c = 0x136
btn_d = 0x137
btn_x = 0x133
btn_y = 0x134
btn_z = 0x13d
btn_start = 0x13b
axis_x = 0x00
axis_y = 0x01
axis_trigger_left = 0x0a
axis_trigger_right = 0x09

[compat]
axis_dpad1_x = 0x10
axis_dpad1_y = 0x11

And here is my emu.cfg:

[audio]
backend = oss
disable = 0

[config]
Debug.SerialConsoleEnabled = 0
Dreamcast.Broadcast = 4
Dreamcast.Cable = 3
Dreamcast.RTC = 2082730217
Dreamcast.Region = 3
Dynarec.Enabled = 1
Dynarec.idleskip = 1
Dynarec.unstable-opt = 0
aica.LimitFPS = 1
aica.NoBatch = 0
aica.NoSound = 0
axis.0 = Axis_X
axis.1 = Axis_Y
bios.UseReios = 0
pvr.MaxThreads = 3
pvr.Subdivide = 0
pvr.SynchronousRendering = 0
pvr.rend = 0
rend.UseMipmaps = 1
rend.WideScreen = 0
ta.skip = 0

[input]
evdev_device_id_1 = 0
evdev_device_id_2 = -1
evdev_device_id_3 = -1
evdev_device_id_4 = -1
evdev_mapping_1 = /opt/retropie/configs/dreamcast/mappings/controller_XboxGamepad(userspacedriver).cfg
joystick_device_id = -1

[reios]
ElfFile = 

[validate]
OpenGlChecks = 0[input]

I also tried to add this to my emu.cfg:

[Xbox 360 Controller (xboxdrv userspace driver)]
button.0=DPad_Up
button.1=DPad_Down
button.2=DPad_Left
button.3=DPad_Right
button.4=Btn_A
button.5=Btn_B
button.6=Btn_X
button.7=Btn_Y
button.10=Axis_LT
button.11=Axis_RT
button.12=Quit
button.13=Btn_Start
axis.0=Axis_X
axis.1=Axis_Y

But it does nothing more, i was wondering if the evdev_device_id was correct set to 0 ? I have tagged my usb XBox controller on the top-left usb port on my Raspbery 2.

Thanks in advance for your help, i think i missed something or didn’t understand something !

I have started to build my first Arcade machine based on retropie over the last few days. I was experiencing some issues with the Xin-mo controller but thanks to the efforts of people like “feederchain” in this thread I have everything up an running.

My setup consists of the following;
– Raspberry Pi B
– Xin-mo dual arcade controller
– 2 x joysticks and 16 buttons (Street Fighter II setup)
– Retropie 3.2.1
– Mame4All

My config was working fine using a keyboard and Logitech F310 gamepad but when I added the Xin-mo and my custom joystick I couldn’t see it – this was resolved by installing custom_kernel_1.20150818-1.tar.gz referenced earlier in this thread.

Next issue was not being able to use the 2nd joystick and button setup, this was resolved by modifying /boot/cmdline.txt by adding the following content after a space at the end of the first line “usbhid.quirks=0x16c0:0x05e1:0x040”

I was then able to see two distinct controllers in jstest, configure 2 gamepads in emulationstation, and setup buttons for SFII in Mame.

that is all my technical issues resolved, arcade cabinet is mostly assembled so I am doing some undercoating tomorrow.

Again many thanks to the forum members and particularly contributors to this thread, without your efforts I would still be wondering why I couldn’t see my joystick.

The video tutorial is a little bit outdated. Just install ps3 driver “once” and connect your controller over usb afterwards. Everything should be setup now. Remove usb cable and press PS button. Your controller should pair (one LED should light up). Start controller config in emulationstation (Start button + Input configuration) and configure your controller.

Hi Guistino,

did the pairing from the terminal work as per the tutorial?

For step 2: did you remove the USB cable after the pairing as per instructions? What I found is I press the PS button once, it starts vibrating/cycling lights and I press it a second time (both times a short press) and it works. Let me know if this works for you!

I’ll start by saying I’m new to this, but I have been reading everything I can to try and figure out where I am going wrong.
I am using Jessie with the latest retropie (must be 3.3?), and a rumble pad 2
My problem sounds just like everyone else’s. I can use the joystick and configure it in the GUI (emulation station). However, once I launch a game, it doesn’t respond, saying ‘rumble pad 2 USB controller not configured (it seems like it’s detecting it quite well for the recognition of the controller in the message!). I’m back to the keyboard only.

Some people have mentioned pushing f1 in-game can get to the controller setup and it works from there. But, I can’t seem to launch a menu by pushing F1.

I have a suspicion that there is nothing at all under:
/opt/retropie/configs/all/retroarch-joypads/
And from all my reading it seems like something should be there. I feel like that’s why the ROM’s are telling me my joystick is not configured.

I’ve tried changing the drivers to Udev and rebooting, but that didn’t help.
Am I right in my suspicion about the missing file? Is there anyway to generate it?

Thanks for any help.

Marc

The problem is a lot of the information and youtube videos on controller configs are dated. Everything seems to work differently in 3.3. This is the best thing you can do for setting up a pi…

1. grab the 3.3 flash and start with that
2. On first startup don’t have your controller plugged in, just use a keyboard. emulstation will want you to configure it which is fine. You really only need to input the up/down/left/right a and b buttons. skip the rest
3. Then go the retroarch emulator and into the settings. Here you can enable the xbox 360 driver. Now shut it down and plug in the controller
4. When it restarts all the xbox lights in the center should be blinking until ES loads. Then it will show one light. Go into the controller config from the start menu and go through the button presses.
5. At this point the controller should be usable but you should take it a step further…

6. Using winscp go to /opt/retropie/configs/all/retroarch-joypads. You should see an XboxGamepad(userspacedriver).cfg file. This was created when you installed the 360 driver. The buttons in this file were programmed in step 4. You can see what they are mapped to. But it’s not going to be obvious to you that input_r3_btn = “12” is the right joystick being pressed down or that input_r_btn = “5” is the right elbow button above the trigger. So let’s fix that.

7. Keep the config file open in winscp. On the keyboard plugged into the pi press f4 and then any key to go to the command prompt. go to root directory and into /dev/input. You should see a js0 or js1 or js2 or js3 depending on where your controller is plugged into. Type in: jstest js1
Now press some buttons on the controller. Do you see anything going from off to on? If not ctrl+c and try a different joypad (ex jstest js2). You are trying to find the right js number for your pad. Once you find it you can go through the mappings. For instance you press the right elbow button on the controller and you see 5: off go to 5: on. Now in your config file you can put a comment next to that line.

input_r_btn = “5” #Right elbow button

For the analog thumbsticks those are a little confusing at first. For instance the right thumbstick, move it to the right. You will see a big number on the screen like 2: 32342343. Now move it to the left and you’ll see a big negative number like 2:-34324322 This means that +2 is the right thumb stick moved to the right and that -2 is the right thumbstick moved to the left. Now go put the comments in your config file. You can re-arrange the buttons in the config file to so that they are grouped together to make more sense. As you comment the file, you’ll end up with stuff you don’t have a button for. These are hotkeys. You can put these at the bottom. Here is my config file all commented and organized:

input_device = “Xbox Gamepad (userspace driver)”
input_driver = “udev”
input_r_x_plus_axis = “+2” #Right Thumb Right
input_r_x_minus_axis = “-2” #Right Thumb left
input_r_y_minus_axis = “-3” #Right Thumb down
input_r_y_plus_axis = “+3” #Right Thumb up

input_l_y_plus_axis = “+1” #Left Thumb up
input_l_y_minus_axis = “-1” #Left Thumb down
input_l_x_minus_axis = “-0” #Left Thumb Left
input_l_x_plus_axis = “+0” #Left Thumb right

input_up_btn = “h0up” #Dpad up
input_left_btn = “h0left”#Dpad left
input_down_btn = “h0down” #Dpad down
input_right_btn = “h0right” #Dpad right
input_l2_btn = “6” #Left Trigger
input_r2_btn = “7” #Right Trigger
input_r3_btn = “12” #Right Thumb down
input_l3_btn = “11” #Left Thumb down
input_r_btn = “5” #Right elbow button
input_l_btn = “4” #Left elbow button
input_select_btn = “8” #select button
input_start_btn = “9” #Start button
input_a_btn = “0” #A button on controller
input_b_btn = “1” #B button on controller
input_y_btn = “3” #Y button on controller
input_x_btn = “2” #X button on controller

#hotkey stuff
input_enable_hotkey_btn = “8”
input_save_state_btn = “5”
input_exit_emulator_btn = “9”
input_load_state_btn = “4”
input_reset_btn = “0”
input_menu_toggle_btn = “3”
input_state_slot_decrease_btn = “h0left”
input_state_slot_increase_btn = “h0right”

8. So now this works great. But in the nes emulator you are trying to play mario and the A/B button seems reversed because on the nes controller B is to the left of the A button, but on the 360 controller B is to the right of the A button. It would be better if these could be reversed for just the nes emulator. Even better the X button seems more natural to push as B. So let’s make the X button on the 360 controller equivalent to the B button on the nes controller. The A button can stay the same.

You would think you just have to copy/paste/change the button config into /opt/retropie/configs/nes/retroarch.cfg. But that would be wrong. You have to mimic how it works in the configs/all directory.

So go to /opt/retropie/configs/nes and create a “retroarch-joypads” folder. Now copy the “XboxGamepad(userspacedriver).cfg file from /opt/retropie/configs/all/retroarch-joypads and place it into the folder you just created. Now open the file and swap the number values between B and X. This will be easy as you’ve already commented every button and know exactly what they are. I like to expand on the comment if it’s custom so that if I open it up later I’ll know what I did).

input_a_btn = “0” #A button on controller
input_b_btn = “2” #B button on controller (Swapped with x button)
input_y_btn = “3” #Y button on controller
input_x_btn = “1” #X button on controller (swapped with b button)

Now save this config file. Now we need to tell the nes emulator to use this file instead of the one in the all directory. Open up /opt/retropie/configs/nes/retroarch.cfg. Add this line above the bottom #include. When the nes emulator starts it will look at joypads specifically configured for the nes before checking the all directory. Since it’s a first fine/first use logic, it will use the config you just customized.

joypad_autoconfig_dir = /opt/retropie/configs/nes/retroarch-joypads/

9. Go enjoy mario. You may also need to repeat this process for other nintendo systems like super nintendo or gameboy.

This is as far as I’ve got so far. I haven’t dealt with multiple controllers yet. I have some usb nes and usb snes controllers coming next week that I’ll be playing with. I’m hoping I can get it so that I can unplug/plug in new controllers for different emulators and it will just work. In an ideal world I could have 20 controllers plugged in and the emulator would just know what ones to use based on what one I opened the game with. Or have a little screen that says “press any key on the controller you want to use”