@ortsac so I tried switching with switched off console, same result. Checked the connection three times now. Should be working but it is not.

Maybe the controllers are not working properly. I cleaned them 1 month ago and I noticed that the rubber pads are not the best. There are stripes on the connection pad. I tried to take a picture of that.
rubber pad
I also measured the resistance of these, and it is >60 Ohms. Should be way lower than that right?

@whitehyena to help you we need to take a look at these files from your system:

/opt/retropie/configs/all/retroarch.cfg - be sure to mask your retroachievements account info, if you have it on your .cfg file.

/opt/retropie/configs/all/retroarch-joypads/YOUR_JOYSTICK_NAME.cfg

Paste their content in pastebin or something similar.

@arpiegamer @mediamogul has a tutorial on using the xboxdrvr to program keys to a controller. You need to use something like that or joymap to set escape and enter to your controller.

I'm running into a similar issue as well. Through searching through the moonlight github it seems the move to SDL2 has caused some issues with RetroPie. The developer of Moonlight has stated that they wont bother with fixing the problem as it comes from the way RetroPie handles controllers using SDL2 framework. Something around how the buttons are mapped and what the system sees. I'd love more help trying to track this down as well.

After a lot of investigation, I didn´t found a working key configuration, online.
Also I could not access /dev/input/ to use jstest... Whatever, testing, testing, testing made the deal:
Working xBox360 wired USB Controller:

[Microsoft X-Box 360 pad] plugged = True plugin = 2 mouse = False AnalogDeadzone = 4096,4096 AnalogPeak = 32768,32768 Mempak switch = Rumblepak switch = Start = button(9) DPad U = hat(0 Up) DPad D = hat(0 Down) DPad L = hat(0 Left) DPad R = hat(0 Right) Z Trig = button(6) C Button U = axis(3-) C Button D = axis(3+) C Button L = axis(2-) C Button R = axis(2+) R Trig = button(7) L Trig = button(8) A Button = button(0) B Button = button(1) X Axis = axis(0-,0+) Y Axis = axis(1-,1+)

And to complete it, the iNext USB N64 Controller:

[Generic USB Joystick ] plugged = True plugin = 2 mouse = False AnalogDeadzone = 4096,4096 AnalogPeak = 32768,32768 Mempak switch = Rumblepak switch = C Button D = button(2) C Button L = button(3) L Trig = button(4) Start = button(9) Y Axis = axis(1-,1+) DPad U = hat(0 Up) A Button = button(6) DPad D = hat(0 Down) X Axis = axis(0-,0+) R Trig = button(5) DPad R = hat(0 Right) B Button = button(8) DPad L = hat(0 Left) Z Trig = button(7) C Button U = button(0) C Button R = button(1)

Seems all fine now, except connecting 2 N64, 1 xBox360 USB and 1 xBox Wireless-Adapter. ES displays, that no Controller is connected. They probably suck to much energy or it is related to the NesPi-Case I´m using :(

But that is another Topic :)

I've only recently updated my system to the new moonlight-embedded package yet I am having the same error, different controller ID but the same error. I've followed the steps you outlined and cleared the controller configuration but still no dice. Each time I launch moonlight, it finds the controller, yet never loads the correct configuration. Only falls back to the default configuration at the top, which isn't correct. Any help?

I believe I am.. I've not ventured into 3rd party emulators just yet other than ports.

@Swain224

Unfortunately, the guide I linked to above is about as easy as it gets and there's no GUI. If you have the basics in place, adding a button combination with the 'B' and 'A' set to act as 'start' would look like:

--ui-buttonmap b+a=start

It should be noted that the learning curve for all this is pretty high. However, it does get easier over time if it's something you want to explore. Also, while handy for Emulation Station, this really wouldn't be ideal for game play, as there are plenty of times where any two buttons will need to be pressed to trigger a game event and the game will only ever see your chosen combination as being the 'start' button. Of course, the mapping can be disabled once a game is launched, so there are possible work-arounds, but you're always going to be at a disadvantage with so few buttons.

@DjGamer said in Joystick for MAME,Mapping not working!:

@dankcushions Thank you very much for your help.

I would appreciate if you have an idea how to map the coins button for the NeoGeo or the MAME emulator. because that controller I posted the picture, doesn't look like an NES controller. so a bit hard to map.

sorry if I am very dumb in this geek world. I am just trying to make it work for my kid.

i'm not sure if it helps but there's other examples of other controller types here: https://github.com/retropie/retropie-setup/wiki/RetroArch-Configuration#default-core-controls-for-all-emulators

Sorry for not replying earlier guys, and thanks for the replies!

@TMNTturtlguy I tried pressing TAB when in-game (lr-quicknes). Nothing happens. I can control the game fine from the keys however. I'll try to find Select+Y on the keyboard!

@BuZz I removed the device, switched 8bitdo hack ON and added it back again. Didn't help. Then I realized I need to remap the controls in ES, which worked. Thanks!

@Danorak1981 yes, updating is the best fix! But the Zero gamepads can't be updated I'm afraid.
Funny thing, I have one older Zero gamepad and one slightly newer. The hack is needed for the old one but not the new one (and the Zero can't be updated).

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.

@joaovlg map the c controls to your right analog (-2, +2, -3, +3)

@PECONAUT

That would seem to indicate that it's not registering a joystick event at all, or at least not correctly. If that's the case, I don't think there's much that can be done. It's unfortunate, but third party console controllers are always in danger of limited compatibility outside of their own ecosystem.

@Spiky strange. It works for me on auto.

@AlexMurphy

Sweet! 3.3 was mentioned specifically in the release notes and I figured a couple days was too quick a turnaround. Clearly I underestimated the RetroPie team. Good on 'em!

That's unfortunate.

Does anyone know any workarounds such as using the device as a controller rather than keyboard? Or mapping the keys to a virtual controller?

said in DosBox Mapping problems:

params=(-conf "crystalc1.conf"

"params=(-conf "crystalc1.conf" was supposed it be "params=(-conf "/home/pi/RetroPie/roms/pc/crystalc1.conf""

meh figured it out :)

@edmaul69 Worked. Thank you.

I found a solution in case anyone else has this problem in the future:

I did cat /proc/bus/input/devices to list input devices, which does not give the full ID. But I saw a "Wireless Controller" listed there, so I knew that was my bluetooth controller. I saw it had an H: Handlers set as event0 and I recalled being ale to substitute this for the full ID. So, instead of doing --evdev /dev/input/by-id/*** where the ID is still unknown at this time, I was able to do --evdev /dev/input/event0 instead.

Now whether or not the button mappings I did are accurate is a whole different problem. Time to go test it out.