@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 the xpad driver 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 use rpi-update as a regular update mechanism - it's not intended to be used as such. RetroPie uses dkms to install additional Linux kernel drivers, so that any normal Linux kernel update (via apt) will automatically re-install the drivers. When using rpi-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=1
My 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.
