hi
i did 2 cabinets out of this dragonrise usb controller (2 for each player).
i had same misconfiguration problems in all lr-* emus : wrong assignment of buttons, not working buttons, 2 buttons assigned to the same phisical button.
i notice that the config made in setup panel of emulation station is correct but it gaves a interface name with spaces in it (i will post log later). i don't know if this leads to errors o bugs.
all controls in emulationstation are ok but not in lr-* emus.

i managed to resolve this only the hard way: hardcode every control lines directly in config/all/retroarch.cfg without let it pick control config from original control file.
this has done the job but don't let you use other controllers beside dragonrise because config is hardcoded.

Here's a video...

@Coax88 Mine worked fine once I put in the kernel hack to have it detect properly as a 2 player controller. Then I just press P1 select / P1 start and I get sent back to the main menu. (or P2 select / P2 start)

EDIT!!!!! i uninstalled this because it made my wifi no longer work. once i removed it my wifi worked again. so i guess i cant use the wiimotes

sudo apt-get install bluetooth vorbis-tools python-cwiid wminput

Hi, I tried both ubuntu 16.04 BT drivers and also installed qtsixa. When connected with usb cable PS3 controller works fine, but when I connect with bluetooth only left analog stick works. Can anyone help me with that?
Ps. How can I uninstall qtsixa after I installed it with that method?

Thank You in advance ;)

I too get the same error. I'm assuming the content here is stale since Option 310 is no longer available. https://github.com/retropie/retropie-setup/wiki/Setting-up-a-PS3-controller

310 Install PS3 controller driver

@Riceman97 If you genuinely want help, you must provide a lot more information rather than asking, it doesn't work for me, why? The only honest answer that I can give you is that I read this and it worked perfectly. You don't even reveal which scraping method you are using!

Here are some questions for you to consider before you compile a response post:

Are you actually connected to the internet? Are your rom files in the correct place? Are you using the command line to scrape correctly? What are the "multiple ways" that you describe? Have you checked that the database is not down? Have you read: https://retropie.org.uk/forum/topic/3/read-this-first ?

@epicrean You should turn off Save Metadata on Exit as described here:
https://github.com/RetroPie/RetroPie-Setup/wiki/FAQ#why-does-shut-down-and-reboot-take-ages

@dankcushions Thanks for the tip, I changed the setting to 5:4via the Configuration Editor, that then made the changes to the retroarch.cfg file and that's now the default when I load games. Interesting that by changing it manually it did not work. Anyway, thanks again for all the help over the past few days. I hope this thread is useful for someone else one day who also wants to use a CRT and really wants fullscreen :)

Hi,
I found a work around, set up the controller in RetroArch, or change the 小米蓝牙手柄.cfg to the following:

input_device = "小米蓝牙手柄"
input_driver = "udev"
input_r_y_plus_axis = "+5"
input_l3_btn = "17"
input_r_x_minus_axis = "-2"
input_start_btn = "15"
input_exit_emulator_btn = "11"
input_l_y_minus_axis = "-1"
input_up_btn = "h0up"
input_r_y_minus_axis = "-5"
input_a_btn = "4"
input_b_btn = "5"
input_reset_btn = "1"
input_down_btn = "h0down"
input_l_x_plus_axis = "+0"
input_l_y_plus_axis = "+1"
input_r3_btn = "18"
input_right_btn = "h0right"
input_state_slot_increase_btn = "h0right"
input_x_btn = "7"
input_menu_toggle_btn = "3"
input_select_btn = "14"
input_enable_hotkey_btn = "10"
input_l_x_minus_axis = "-0"
input_y_btn = "8"
input_left_btn = "h0left"
input_state_slot_decrease_btn = "h0left"
input_r_x_plus_axis = "+2"
input_l_btn = "10"
input_r_btn = "11"
input_l2_btn = "12"
input_r2_btn = "13"

second video

OK, so after reading a little more, I did the RetroAch setup and compared the ES to the RA generated configs,

So using ES setup :

input_device = "小米蓝牙手柄"
input_driver = "udev"
input_r_y_plus_axis = "+5"
input_l3_btn = "13"
input_r_x_minus_axis = "-2"
input_start_btn = "11"
input_exit_emulator_btn = "11"
input_l_y_minus_axis = "-1"
input_up_btn = "h0up"
input_r_y_minus_axis = "-5"
input_a_btn = "0"
input_b_btn = "1"
input_reset_btn = "1"
input_down_btn = "h0down"
input_l_x_plus_axis = "+0"
input_l_y_plus_axis = "+1"
input_r3_btn = "14"
input_right_btn = "h0right"
input_state_slot_increase_btn = "h0right"
input_x_btn = "3"
input_menu_toggle_btn = "3"
input_select_btn = "10"
input_enable_hotkey_btn = "10"
input_l_x_minus_axis = "-0"
input_y_btn = "4"
input_left_btn = "h0left"
input_state_slot_decrease_btn = "h0left"
input_r_x_plus_axis = "+2"

And then using the RetroArch:

input_device = "小米蓝牙手柄"
input_driver = "udev"
input_r_y_plus_axis = "+5"
input_l3_btn = "17"
input_r_x_minus_axis = "-2"
input_start_btn = "15"
input_exit_emulator_btn = "11"
input_l_y_minus_axis = "-1"
input_up_btn = "h0up"
input_r_y_minus_axis = "-5"
input_a_btn = "4"
input_b_btn = "5"
input_reset_btn = "1"
input_down_btn = "h0down"
input_l_x_plus_axis = "+0"
input_l_y_plus_axis = "+1"
input_r3_btn = "18"
input_right_btn = "h0right"
input_state_slot_increase_btn = "h0right"
input_x_btn = "7"
input_menu_toggle_btn = "3"
input_select_btn = "14"
input_enable_hotkey_btn = "10"
input_l_x_minus_axis = "-0"
input_y_btn = "8"
input_left_btn = "h0left"
input_state_slot_decrease_btn = "h0left"
input_r_x_plus_axis = "+2"
input_l_btn = "10"
input_r_btn = "11"
input_l2_btn = "12"
input_r2_btn = "13"

It seems the 小米蓝牙手柄.cfg file changes, its like RetroArch reads a different key to what ES reads.
I will do as mentioned above and just restore this config after updating each time.

Thanks. Tried turning off the overclock and it didn't help. Power supply is supposedly 2.5A but I will source another one and try it.

Thanks, it's working great now :)

@BuZz I want a more clear image.

You only have to configure it once though. Doesn't take long.

@Richyeah

From the home/root menu of Kodi, move right and select 'System'. The resulting menu will have another listing for 'System'. Select that and go to 'Audio Output'. By selecting the 'Audio Output Device' menu listing, you'll be given a few options. Based on your initial post, I'm a little unsure if you're using HDMI or the 3.5mm jack, so pick whichever one applies to you and see if that does the trick.