@00Hugo said in Xpad driver installation issue - not existing commit:

One question regarding that: The controller is paired now in Bluetooth setup, but why it is not visible as device in "Configure Input"?

Maybe it needs another driver (xpadneo) ? As I said, xpad is used only for wired Xbox compatible drivers.

BINGO.... I figured this out and was just coming back to say thanks for the SDL tip again. For the record, I added the env variable to "/etc/environment" to make it a system wide change.

Again, big thanks.

@mitu Whew. It's getting weird now.

I just built the latest version of SDL2 from github.

cmake sees SDL2 as 2.29.0 now instead of the previous 2.0.10.

So then I rebuilt Emulation Station.

The preinstalled Emulation Station was v2.11.2rp. The one I've built identifies as 2.12.0rp-dev.

The good news:

Emulation Station now recognizes my L2/R2 triggers!

The weird news:

When I launch retroarch emulators, they do not recognize my L2/R2 trigger presses. While the bluetooth dialog still reports my controller name as "8Bitdo SN30 Pro" when I pair and connect it, this newly-built version of Emulation Station reports it as "Xbox 360 Controller".

@windg Nice.

@Dochartaigh The xpad devs reverted the change that broke the driver for older controllers, so it's safe to upgrade to the main version of the driver again.

You should re-map your controller(s) in EmulationStation after installing/un-installing a driver, since the mappings are subject to change.

@mitu said in I think the latest xpad driver (Aug 14, 2021) is broken:

@windg said in I think the latest xpad driver (Aug 14, 2021) is broken:

It seems that they have fix the bug, but when I try to install the new version I have an error Failed to install xpad

They fixed the code now, can you try updating to the latest version and see if the controller(s) work ?

Yes everything is working fine now. Thanks!

@mitu That worked! Thanks a million

@mitu said in 2x different 360 Wireless controllers not mapping correct at same time:

so, yes, as far as the input system is concerned, they're the same type of device.

Think I'm going to rewire them - not too hard, the wiring harness has pins I can just pull out and shove into another spot - will just have to figure out what goes where and remember the original layout if I ever want to put it back lol. Thanks for the help though.

@dochartaigh said in 2x different 360 Wireless controllers not mapping correct at same time:

On a related note: is the USB controller device order no longer implemented in RetroPie anymore? Seems like the Xbox wireless adapter is superseding anything physically plugged in on a lower USB port number, or maybe I have to reboot and test that again? (i.e. not hot swappable? - I forget if it ever was TBH).

And yes, I'm quoting myself and looking for confirmation on this. Seems like on the RP3 when all 4x USB's were 2.0, the order was something like left bottom 0, top 1, right side bottom 2, top 3.

On the RP4, I think (NOT positive, would like confirmation if possible), they run separately for the USB 2.0 side and the USB 3.0 side. I had my WIRED fightstick plugged into the left side #1, which should have superceeded the 3x WIRELESS fightsticks which were plugged into #2, but I think because the wireless was on the 3.0 side that superceeded the 2.0 side in controller order. Right now I have the wired fightstick plugged into the right side top, and the wireless 360 dongle on right side bottom and the wired one is player #1, and the wireless are #2/3/4. can anybody confirm this is how it works now on a RP4?

@mitu thanks for all your help!

You can run xboxdrv only for the psp system, if that works for you. I think the Xboxdrv doc page has some examples on how to run it only on specific systems, by using the Runcommand's onstart/onend scripts.

Found the option I was looking for in /etc/modprobe.d/xpad.conf

Changing from options xpad triggers_to_buttons=1 to options xpad triggers_to_buttons=0
solved my issue.

Quick update and some interesting details:

Following

, the controller is immediately recognized, though as a "Generic Xbox Pad". It works, but whenever I shutdown or reboot, I need to do this all over again. But what is strange is that I shouldn't need to be doing this at all: for one thing I never had to go through this workaround with my Pi 3, and second because the Xpad driver already has the device ID configured correctly and recognized as "Hyperkin Duke Xbox One Controller", but it seems that it's refusing to recognize it for me.

So why is this happening?

@quicksilver you're right in Mame2003+ simply open the Retroarch Menu/GUI > Quick menu > Settings (not Controls indeed) and head for the Control Mapping setting. Change the value either to Analog (left stick) or Digital (Dpad). Thanks for the tip as I completely missed that opion!

Is anyone running a Stretch version of Retropie with an Xbox 360 controller?

Can you tell me what your buttons map to, and if the player lights are working?

@mitu Thanks.

I will give this a try and report back tomorrow as it is getting late here.

@dirtyd369 said in Xbox 360 Joystick not working in some emulators, but works on menu:

I assume I can save these settings using “save core remap”? Thank you!

Yes, this is the recommended way to do it.

For the 2nd part, related to Mame and Tapper, I think it is not supported in 'vanilla' Mame2003 (see https://retropie.org.uk/forum/topic/1712/no-tapper-how-will-i-live-controls-not-working/) so you could try to use either advmame or install lr-mame2003-plus (https://retropie.org.uk/forum/topic/17766/mame2003-plus-250-new-games-new-input-system-new-features-new-bugs) and see if you get better results.

@macsgv said in Could not Install Package (s): Linux-headers-Generic:

Solved

How ?

@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.