Hello @SerraLanao, it might be interesting to check what usbid your controller has with lsusb, then add a udev rule to /lib/udev/rules.d/60-steam-input.rules that is similar to https://github.com/ValveSoftware/steam-devices/commit/4aa93a54d237f7de2428068e7dd955a462bc1754, but adjusted for your board's usbid and see if that has an effect.
Hello @SerraLanao, it might be interesting to check what usbid your controller has with
lsusb, then add a udev rule to/lib/udev/rules.d/60-steam-input.rulesthat is similar to ValveSoftware/steam-devices@4aa93a5, but adjusted for your board's usbid and see if that has an effect.
So that really did the trick!! Is detecting the divice as an Nintendo Switch controller but it really works!!
Why and how is my biggest question?
So what I did, if anyone else has the same problem is run the lsusb command, in the console, as @kisak-valve sugested, and this is the output presented:
Bus 001 Device 036: ID 0f0d:00aa Hori Co., Ltd Audio Fighting Board
Then I create and edit the file /lib/udev/rules.d/60-steam-input.rules and add the following lines:
# Brooks PS4+ Audio Fighting Board
KERNEL=="hidraw*", ATTRS{idVendor}=="0f0d", ATTRS{idProduct}=="00aa", MODE="0660", TAG+="uaccess"
See that the idVendor and the idProduct values had to match with the ones extracted using the lsusb command.
Nothing extracted yet.
Please excuse me if I create the wrong issue or if everyting sounds confusing...
As I installed proton and test a custom build controller using a Brook PS+ audio, I see that some of the action buttons (not the directional inputs, but the
ABXYbuttons, shoulder buttons, and trigger buttons) are not recognized by the game.In the other hand, I can see that the system is recognizing the controller without any issue and detects all inputs without any problem.
Is this an errror form my configuration or is Proton/wine not detecting my controller correctly?
System specifications