@Bravenstein Does the controller work in Emulationstation, browsing the games and launching them ? Please add more info about your setup as requested in https://retropie.org.uk/forum/topic/3/read-this-first.

@theretroprince I solved the problem of Hotkeys not saving. All I had to do was cp the retroarch.cfg from configs/all to configs/snes. It looks like there was a problem individual core configs.

@mitu Ohh man i wasted so many hours and now it works! Big THX

@mitu thanks it worked

@aditkrator said in Changing Xbox driver based off game: Parsec for Raspberry Pi I hadn't heard of Parsec, but it looks like something similar to Moonlight, which I use (or did use, but ever since I updated to RetroPie 4.4 I can't seem to get it to work). I have quite a few individual bash scripts that invoke xboxdrv and then start moonlight and then individual games, so it can be done: sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv > /dev/null 2>&1 \ --silent \ --detach-kernel-driver \ --deadzone=4000 \ --deadzone-trigger 15% \ --force-feedback \ --mimic-xpad \ --trigger-as-button \ --ui-buttonmap lb=void,rb=void,tl=void,tr=void,guide=void,lt=void,rt=void \ --evdev /dev/input/by-path/platform-3f980000.usb-usb-0:1.3.2:1.0-event-joystick \ --device-name "Player_1" \ --evdev-absmap ABS_X=x1,ABS_Y=y1 \ --evdev-keymap BTN_THUMB=a,BTN_TOP=b,BTN_PINKIE=x,BTN_TRIGGER=y,BTN_THUMB2=back,BTN_TOP2=start \ --ui-axismap X1=KEY_DOWN:KEY_UP,Y1=KEY_RIGHT:KEY_LEFT \ --ui-buttonmap a=KEY_Z,b=KEY_E,x=KEY_X,y=KEY_Q,back=KEY_SPACE,start=KEY_ENTER \ --ui-buttonmap back+start=cycle-key:KEY_ESC:KEY_LEFTCTRL+KEY_LEFTSHIFT+KEY_LEFTALT+KEY_Q \ & sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv > /dev/null 2>&1 \ --silent \ --detach-kernel-driver \ --deadzone=4000 \ --deadzone-trigger 15% \ --force-feedback \ --mimic-xpad \ --trigger-as-button \ --ui-buttonmap rb=void,tl=void,tr=void,guide=void,lt=void,rt=void \ --evdev /dev/input/by-path/platform-3f980000.usb-usb-0:1.3.4:1.0-event-joystick \ --device-name "Player_2" \ --evdev-absmap ABS_X=x1,ABS_Y=y1 \ --evdev-keymap BTN_THUMB=a,BTN_TOP=b,BTN_PINKIE=x,BTN_TRIGGER=y,BTN_BASE=lb,BTN_THUMB2=back,BTN_TOP2=start \ --ui-axismap X1=KEY_F:KEY_R,Y1=KEY_G:KEY_D \ --ui-buttonmap a=KEY_S,b=KEY_P,x=KEY_A,y=KEY_W,back=KEY_J,start=KEY_H \ --ui-buttonmap back+start=cycle-key:KEY_ESC:KEY_LEFTCTRL+KEY_LEFTSHIFT+KEY_LEFTALT+KEY_Q \ & sudo /opt/retropie/emulators/moonlight/moonlight stream -bitrate 5000 -audio local -720 -fps 30 192.168.0.5 -app "UnderDefeat" moonlight quit 192.168.0.5 sudo killall > /dev/null 2>&1 xboxdrv The above script invokes xboxdrv, maps out 2 of my joysticks as against keyboard inputs and then starts moonlight and, ultimately, the game Under Defeat via an emulator on my Windows 7 based PC.

@aditkrator Can you check my update in the other topic to see if the workaround I posted there works for you also ?

@fuzzybat23 On first install, you will need a keyboard to configure your controller. You can do this by navigating to Options -> Control setup -> Joystick Setup -> Edit Buttons. Once you have mapped your buttons, the axis mapped to turning will navigate a menu (this has probably already been mapped) and the button mapped to fire will select an item in a menu. I have not found a way to map Escape to a button so a keyboard will be needed to bring up the menu in-game.

im having the same issues, retropie 4.4 installed, 360 controllers working perfectly, then update and bam, broken. all advice says: don't update. so ill roll back to new, and wont update, not updating bothers me a bit, that feeling that newer is always better is hard to break sometimes

So... doesnt matter. i use now my gaming latop and emulationstation...

Hi, if I use a regular snes controller usb design I can back out of Dreamcast the usual way start and select but when I use a wireless Xbox I have to use the center button? How can I change this, the pad is also the start button so if I’m playin I keep pausing by accident...how can I remap these?

Perhaps it would be a good idea to include a documentation for the Xbox One controller. For me this thread made the difference from giving up on RetroPi and finding the perfect setup!

Can please anybody share his/her experience?

@reginaldsharma said in Unable to use hotkeys with xbox360 controller on retro4.3: but next time around i made it the xbox button. still was having issues. See what @BobHarris also said. If you mapped the now 'xbox' button as Hotkey, then it will replace what you previously used (Select) in the button combinations you're trying now. If you left the Hotky button unmapped, then the input dialog will ask you if you want to use Select and then it should work as in ver. 4.1.

@megahertz Nice!

@jocaedu Are you sure your controller/usb cable are OK ? 1 gamepad detected implies the keyboard is detected, but not the controller. As for the image, I don't think there is such a thing as Windows User-Friendly drivers on the Linux, but over USB the controller should be detected ok. Please give more details about your setup - https://retropie.org.uk/forum/topic/3/read-this-first - especially about your controller model and version. tags: this is not twitter.

I had no trouble to connect both x-Box one s controller via Bluetooth (pi 3b - disable ertm and updated retropie and the both controllers via my Xbox one). I conectet the first one and after it was done I connected the other one. But I have trouble to configure them in the retroarch GUI. Does the controllers work in retroarch gui for you?

@ogaspard https://retropie.org.uk/forum/topic/3/read-this-first Power supply?

@mnmagri I'm not sure how far you got when setting up Moonlight but you need to find your controller's ID number and the correct corresponding button numbers by using jstest /dev/input/js0 Then you add this information into /usr/share/moonlight/gamecontrollerdb.txt This is because Moonlight decided to use an SDL gamecontrollerdb.txt format to be able to make common game controllers work out-of-the-box. Here's the official template file: https://github.com/irtimmer/moonlight-embedded/blob/master/gamecontrollerdb.txt Here is the information for my wireless Xbox 360 controller. Warning: my d-pad settings are not correct and I've been meaning to fix this but I'm too lazy to do it right now!. They differ a little depending if you're using the Xpad driver or the Xboxdrv driver. Xpad version: 030000005e040000a102000007010000,X360 Wireless Controller,a:b0,b:b1,x:b2,y:b3,leftshoulder:b4,rightshoulder:b5,lefttrigger:b6,righttrigger:b7,back:b8,start:b9,guide:b10,leftstick:b11,rightstick:b12,dpleft:b13,dpright:b14,dpup:b15,dpdown:b16,leftx:a0,lefty:a1,rightx:a2,righty:a3,platform:Linux, Xboxdrv version: 030000005e040000a102000007010000,X360 Wireless Controller,a:b0,b:b1,back:b6,dpdown:b14,dpleft:b11,dpright:b12,dpup:b13,guide:b8,leftshoulder:b4,leftstick:b9,lefttrigger:a2,leftx:a0,lefty:a1,rightshoulder:b5,rightstick:b10,righttrigger:a5,rightx:a3,righty:a4,start:b7,x:b2,y:b3,platform:Linux, More information here (Xbox 360 Wireless Receiver mapping chart): https://github.com/irtimmer/moonlight-embedded/issues/514#issuecomment-310163270

Replying to this old topic with the solution that worked for me, after finding this question via google with no reply. It's likely your left/right triggers were configured incorrectly. If they're configured for minus axis, retroarch believes they are held down when the game launches and everything acts weird. It's likely the retroarch menus are un-navigable as well. To fix the problem, go to "configure input" again and make sure left trigger is "Axis 5+" and right trigger is "Axis 4+". If they're negative the emulator thinks they're held down and that's causing the problems. Hope this helps anyone else coming across this problem via google.