This works, but I'll need to test across other games which hopefully will not involve more than sorting out correct button mappings. I noticed that for scummvm, its only backend options are for SDL2 and therefore will not work (as far as I can tell) with xboxdrv.

That's because ScummVM is already a SDL2 application and there's no need for a compatibility shim like sd12-compat.

It's looking to me as if xboxdrv may be a bit of a dead end when it comes to button remappings for non-libretro emulators in RetroPie. Can such remappings be done in SDL2 or is there another option that could be applied system-wide?

Not dead, just not widely used. xboxdrv itself is mostly feature complete and there's little development nowadays, since compatibility with Xbox controllers is offered OOB by Linux kernel modules (xow, xpad, xpadneo).

There are no alternative re-mapping solutions in RetroPit, though anything that works in Linux and without X11/Wayland could work.

100% sure. I bought it directly form Amazon (not marketplace) and the official firmware update tool worked also.

The controller works perfectly with es and Linux. Only libretro seems to ignore the none standard button (xbox).

@jernserval said in More 8BitDo Pro 2 Controller Weirdness:

It appears there's some kind of naming conflict or problem when the 8BitDo tries to "spoof" as an XBox One controller?

No, I don't think so - conflicting with what ?

Xpadneo refers to configuration in it's docs, but there was no configuration after RetroPie-Setup install?

Configuration is optional, RetroPie doesn't add any, but you can add it if you'd like.

hid_xpadneo: loading out-of-tree module taints kernel. - Does this mean I need to install the headers referenced in the xpadneo documentation? Was it not autoinstalled by RetroPie-Setup?

No, that means what it says - it's an out-of-tree module, external to the Linux kernel. Kernel headers are already installed, otherwise the module wouldn't have compiled.

Now in retroarch its saying "8BitDo Controller not configured" why would it say explicitly "not configured"?

Because it's not configured ? This means there was not configuration profile found for the controller.

What is the way forward to get the most reliable experience with X-Input across retroarch and other emulators?

You haven't mentioned the issues you have with other emulators, but for RetroArch it's enough to configure the controller in EmulationStation in order to generate the configuration for it.

@mitu Ah! That makes more sense now. Thank you!

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

Please provide details of set up and a log.

@mikeb said in Retropie does not work on pi4 with xbox one wireless controller:

following all the videos and articles

That could be your problem right there. "All"? You don't need any certification to post a video online.
Without knowing what you did, how can anyone help?

Regardless, it's probably just a driver issue. You may have inadvertently deleted a file which one of the videos told you wasn't important, but actually was. Maybe you bumped the keyboard while editing a config file. I don't know.

https://retropie.org.uk/forum/topic/28094/xbox-one-controller-detected-but-wont-pair/6

Several other users are reporting the same issue on the github for xpadneo:
https://github.com/atar-axis/xpadneo/issues/259

I paired the controller in windows and copied the link key to my raspberry pi as one of the users on github mentioned. Now the pairing works and I can use the controller. Now the Xbox-Button doesn't work as hotkey for both controllers anymore. But this might be an issue because of updating the whole system.

For getting the keys I followed these instructions:
https://bbs.archlinux.org/viewtopic.php?pid=1678405#p1678405

Problem solved! :)

@wholee said in XPADNEO error on Update:

When you have the time, would you be able to update the Retropie Setup script?

It will happen at some point.

Currently a bug in the bluez package. Workaround fixing the issue can be found here.