-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to get controllers working in steam? #82
Comments
I will try some day and let you know. Feel free to ping me again if I forget to reply. |
I was able to find a workaround for this. The problem exists with udev not adding the ego user to the device file acl. This may be caused by how the udev rules(the ones that came with the steam package on archlinux) handle pts sessions. |
Here's a NixOS config snippet (for the PS5 controller): # Allow 'ego' to acccess gamepads/controllers, ref.
# https://github.com/intgr/ego/issues/82 ("How to get controllers working in steam?")
# Rules based on "60-steam-input.rules", where MODE= and TAG+= were replaced
# with RUN+=.
services.udev.extraRules = ''
# PS5 DualSense controller over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="0ce6", RUN+="${pkgs.acl}/bin/setfacl -m u:ego:rw /dev/$name"
# PS5 DualSense controller over bluetooth hidraw
KERNEL=="hidraw*", KERNELS=="*054C:0CE6*", RUN+="${pkgs.acl}/bin/setfacl -m u:ego:rw /dev/$name"
''; |
I spend too much time trying to make sense of udev rules but they are too alien to me, basically i was trying a way to add only my controllers, in my case |
@ostoru: If you want a "tighter" udev rule set you can find attributes(?) to put in your rules by running |
How do you get controllers working with steam using ego? Steam doesn't detect the dualshock 4 I am using.
The text was updated successfully, but these errors were encountered: