http://www.generalarcade.com/gamepadtool/
With a fresh install of Fedora 32 and Steam client (from repositories), I also had this issue (PowerA Pro Ex PS3 wired controller and PDP Rock Candy Nintendo Switch wired controller). Running the gamepad tool fixed it for me. I think it has something to do with how Steam is accessing SDL 2 gamepad mappings upon initial installation. The big picture controller configuration just would not detect anything. No udev configuration or xpaddrv is needed.
http://www.generalarcade.com/gamepadtool/
With a fresh install of Fedora 32 and Steam client (from repositories), I also had this issue (PowerA Pro Ex PS3 wired controller and PDP Rock Candy Nintendo Switch wired controller). Running the gamepad tool fixed it for me. I think it has something to do with how Steam is accessing SDL 2 gamepad mappings upon initial installation. The big picture controller configuration just would not detect anything. No udev configuration or xpaddrv is needed.
Thank you, creating a mapping and setting a environmental variable fixed it. Oddly though instead of it pulling the profile in steam, it actually detects the controller itself now rather than pulling the profile name I set.
Nice find, I think that means that SDL hasn't been taught about that controller yet. Can you share the button mapping you're using? Assigning a SDL dev.
This is what the gamepadtool generated
SDL_GAMECONTROLLERCONFIG=03000000c62400003a54000001010000,PowerA XBox One Controller SDL2,a:b0,b:b1,x:b2,y:b3,back:b6,guide:b8,start:b7,leftstick:b9,rightstick:b10,leftshoulder:b4,rightshoulder:b5,dpup:h0.1,dpdown:h0.0,dpleft:h0.8,dpright:h0.2,leftx:a0,lefty:a1,rightx:a3,righty:a4,lefttrigger:a2,righttrigger:a5,platform:Linux,
Dpad down wasn't working with the above one. Here is a working one. I guess steam just doesn't pull the profile name, but still identifies it as a xbox one controller.
SDL_GAMECONTROLLERCONFIG=03000000c62400003a54000001010000,PowerA XBox One Controller SDL2,a:b0,b:b1,x:b2,y:b3,back:b6,guide:b8,start:b7,leftstick:b9,rightstick:b10,leftshoulder:b4,rightshoulder:b5,dpup:h0.1,dpdown:h0.7,dpleft:h0.8,dpright:h0.2,leftx:a0,lefty:a1,rightx:a3,righty:a4,lefttrigger:a2,righttrigger:a5,platform:Linux,
See https://github.com/ValveSoftware/steam-devices/pull/9 - install the latest udev rules in 1.0.0.63 or newer.
See ValveSoftware/steam-devices#9 - install the latest udev rules in 1.0.0.63 or newer.
It didn't make a difference, I still need the SDL line above.
I don't personally get the error above.
I would like to however add that my controller is not in the steam udev list and is also wired.
KERNEL=="hidraw*", ATTRS{idVendor}=="24c6", ATTRS{idProduct}=="543a", MODE="0660", TAG+="uaccess"
This is however unneeded
Hello @Nayr438, are you still experiencing this issue on an up to date system? I'm guessing that you still need a udev line for the controller.
I actually forgot about this, but I do still have that controller.
It's detected by steam and worked for a quick test run on GTA V without any additional configuration.
Your system information
Please describe your issue in as much detail as possible:
Steam is unable to detect my PowerA xbox one Controller, games seem to be unable to see it as well.
lsusb -> Bus 001 Device 014: ID 24c6:543a BDA Xbox ONE Pro Ex controller
Is detected by KDE Input and appears fully functional
I have tried
KERNEL=="hidraw*", ATTRS{idVendor}=="24c6", ATTRS{idProduct}=="543a", MODE="0660", TAG+="uaccess"Detects Microsoft xbox 360 controller just fine.
I have used the PowerA xbox one controller in the past without issue, buts its been awhile.
Steps for reproducing this issue: