Issue configuring PowerA Fusion wired XBox One controller
-
@mitu Got it working
I ran the Update Retropie script, followed by running an update to Retropie & OS.
Reboot
I added my /etc/modprobe.d/bluetooth.conf file to disable the ertm, which worked fine
Ran update from source on the xpad driver package for good measure
Reboot
Controller pairs correctly, emulationstation maps the buttonsWhat I noticed is, I was mapping my triggers and they were coming up as 5- & 4-. This would cause trigger spam in games. I tried remapping them a few times, and noticed I was able to map them in emulationstation as 5+ & 4+. I kind of did a 3/4 trigger press held for a second or two then released.
Playing with this mapping now works fine.
-
I've just run "sudo rpi-update" in order to try standalone KMS, and Emulation Station -> Configure Input is now mapping my Xbox One Elite Controller's Left Trigger as "Axis 2-" and not even detecting my Right Trigger.
My normal Xbox One Controller is working without any problem.
Is the solution above something I should look at (or should I just not try experimental packages when I am such a novice)?
-
@AdamBeGood You should have opened a new topic instead of bumping 2 years old topics.
Your issue is probably caused by the usage ofrpi-update, which overwrote thexpaddriver with the stock Linux kernel version. As explained throughout the topic, RetroPie includes a patched version, which modifies the default driver behavior and maps the triggers as buttons instead of axis.
Don't userpi-updateas a regular update mechanism - it's not intended to be used as such. RetroPie usesdkmsto install additional Linux kernel drivers, so that any normal Linux kernel update (viaapt) will automatically re-install the drivers. When usingrpi-update, this is not possible and causes issues if you rely on a certain driver to be installed and working. -
@mitu said in Issue configuring PowerA Fusion wired XBox One controller:
@AdamBeGood You should have opened a new topic instead of bumping 2 years old topics.
I'm sorry, I should have started a new topic and referenced this thread. Apologies.
Let me know if I am okay to carry on posting here now, or if the best route is to still open a new topic.
Your issue is probably caused by the usage of
rpi-update, which overwrote thexpaddriver with the stock Linux kernel version. As explained throughout the topic, RetroPie includes a patched version, which modifies the default driver behavior and maps the triggers as buttons instead of axis.
Don't userpi-updateas a regular update mechanism - it's not intended to be used as such. RetroPie usesdkmsto install additional Linux kernel drivers, so that any normal Linux kernel update (viaapt) will automatically re-install the drivers. When usingrpi-update, this is not possible and causes issues if you rely on a certain driver to be installed and working.I wouldn't normally use rpi-update but I wanted to try out the KMS change to see how that affected N64 emulation.
Any idea how I resolve this issue now? I looked at amending the line mentioned in the thread but that line doesn't seem to be present in my script, and there is a reference to the trigger issue also so I think the script has been updated since the above was written.
dkms install -m xpad -v 0.4 -k "$kernel"dkms install --force -m xpad -v 0.4 -k "$kernel"I tried re-installing xpad from Source but that hasn't changed anything.
The below line is also present in "xpad.conf"
options xpad triggers_to_buttons=1My controller is connected by a USB lead, I'm not using Bluetooth.
Later Edit: it is especially strange as it is only my Elite Controller that is having this issue. Standard XBox One Controller is perfect.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.