Rewrote the image, and everything was nice and fresh. I can register each controller through the menu prompt but they won't connect or be recognized at all now

Thanks. When my new controller comes in the mail. I will retry it though the retro arch menu. If that doesn't work. I'll just manually​ edit the config file.

@rbaker thanks, but we've already ruled out the power issue (see my replies above on the progress). It detects in the command line thing, but won't detect in emulation station. Everything works fine in Windows, so i know nothing is broken. This is really for linux masters only.

@duggeryskull this solution works for me although the Cdown remains unassigned. Do you leave RIGHT ANALOG DOWN (which is Cdown) -NOT DEFINED-? That's an issue I have not been able to find a solution for so far... Cheers

How did you solve this? I have the same problem with C down unassigned. Any help would be highly appreciated, thank you. :-)

I figured it out, at least for Nintendo.
I had been testing in Atari 2600, attempting to tweak both the retroarch.cfg file under /opt/configs/atari2600, in addition to the file under /opt/configs/all/retroarch-joypads/Microchip Technology Inc. Ultimate 2.cfg

I was doing some testing on Nintendo, and ended up doing the final modifications under the Microchip file referenced above.

Here are my settings, and "Enter" (19) is my new hotkey, and "6" (13) works to exit!

input_device = "Microchip Technology Inc. Ultimate 2"
input_driver = "udev"
input_l_btn = "14"
input_load_state_btn = "14"
input_start_btn = "12"
input_exit_emulator_btn = "13"
input_down_axis = "+1"
input_r_btn = "17"
input_save_state_btn = "17"
input_right_axis = "+0"
input_state_slot_increase_axis = "+0"
input_select_btn = "11"
input_left_axis = "-0"
input_state_slot_decrease_axis = "-0"
input_up_axis = "-1"
input_a_btn = "0"
input_b_btn = "1"
input_reset_btn = "1"
input_enable_hotkey_btn = "19"

Hope this helps someone.

Thank you for doing what you do.

Thanks for the advice everyone. I will pick up a cheap keyboard after work. Hopefully that works. Otherwise I will just have to start from scratch.

@Joface , did you ever find a solution to this? I'd like to know if you did. Thank you

@z3r0d4y

For the RetroArch cores, a good place to start is here:

https://github.com/RetroPie/RetroPie-Setup/wiki/RetroArch-Configuration#custom-retroarch-override-examples

As for everything else, the individual pages for each system details controller mapping.

https://github.com/RetroPie/RetroPie-Setup/wiki/Supported-Systems

You can also use external mapping software if you find any of the default methods lacking. Linux Joystick Mapper is one to consider as well as xboxdrv. Below is a guide to setting up xboxdrv on a per-emulator basis that deals directly with RetroPie:

https://github.com/RetroPie/RetroPie-Setup/wiki/Universal-Controller-Calibration-&-Mapping-Using-xboxdrv

I have the same issue. I am sending this gamepad back and going back to my first gen Amazon Fire TV game controller which surprisingly works great with retropie.

@SNES30help Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first (which you agreed to read when registering)

@Jeremy Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

Thanks for the replies! ill check it out when I get home later.

@meleu no this will not even work I'm not sure whats causing this but i wanna fix it asap

@gnome73 basically it's like a little GPIO board that plugs into a USB port on the Pi. Mapping isn't a problem, it took me a long time to work out how to do it, but thank you for your response. I'll give it a go once it's all up and running. Much appreciated guys.