View Steam Controller Support and Troubleshooting here:
https://support.steampowered.com/kb_article.php?ref=2754-YPKV-8614Linux-specific notes and known issues
Rules updated; update necessary for compatibility with Steam builds newer than 11/22!The controller is fully supported on Linux without needing a kernel driver, but Steam needs proper read-write access to the HID device nodes it exposes in order to program it. We are working with distributions to make sure the necessary access is provided out of the box, but this might not currently be the case depending on your distribution of choice. Here are the rules needed for proper use of the controller:
# This rule is needed for basic functionality of the controller in Steam and keyboard/mouse emulation
SUBSYSTEM=="usb", ATTRS{idVendor}=="28de", MODE="0666"
# This rule is necessary for gamepad emulation; make sure you replace 'pgriffais' with a group that the user that runs Steam belongs to
KERNEL=="uinput", MODE="0660", GROUP="pgriffais", OPTIONS+="static_node=uinput"
# Valve HID devices over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="28de", MODE="0666"
# Valve HID devices over bluetooth hidraw
KERNEL=="hidraw*", KERNELS=="*28DE:*", MODE="0666"
# DualShock 4 over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="05c4", MODE="0666"
# DualShock 4 wireless adapter over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="0ba0", MODE="0666"
# DualShock 4 Slim over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="09cc", MODE="0666"
# DualShock 4 over bluetooth hidraw
KERNEL=="hidraw*", KERNELS=="*054C:05C4*", MODE="0666"
# DualShock 4 Slim over bluetooth hidraw
KERNEL=="hidraw*", KERNELS=="*054C:09CC*", MODE="0666"
# Nintendo Switch Pro Controller over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="057e", ATTRS{idProduct}=="2009", MODE="0666"
# Nintendo Switch Pro Controller over bluetooth hidraw
KERNEL=="hidraw*", KERNELS=="*057E:2009*", MODE="0666"
Please note: Make sure you don’t have older rules that are taking priority. If there are both /lib/udev/rules.d/60-steam-controller-perms.rules AND /etc/udev/rules.d/60-steam-controller-perms.rules, one of the two will take priority and the edits will be ignored. Check that you only have one before putting the content of the rules file in and fixing the group name.
Bootloader firmware updatesRegular firmware updates will go through regular USB hid reports and can be performed wired or wirelessly. We'll also sometimes be releasing infrequent bootloader updates; these updates are different and can only work when wired. When Steam asks you to plug in the controller to start the update, the controller will change from a HID device to a mass storage device with an identifier of 'CRP DISABLED'. Steam will then wait for that device to become mounted somewhere so that it can copy the firmware file into the controller. A lot of distributions don't auto-mount mass storage devices by default, meaning you'll most likely have to go click on the volume in your file manager of choice when Steam is waiting for the volume to get mounted, or mount it manually where Steam can write to it.
Endless firmware update loop
If you're experiencing an issue with the firmware update window endlessly coming back up during a firmware update, this is most likely due to poor signal integrity causing the firmware update process to fail and retry. Try the following:
- Move the controller closer to its wireless receiver
- Connect the controller directly to the computer using the included USB cable
Mac-specific notes and known issues
- You'll need to restart the Steam client after being prompted to install the driver
- Note that some Mac games don't actually support any kind of controllers; you will have to use mouse/keyboard emulation in this case
- If a given game is not compatible with the Steam Overlay, input emulation will not currently work
I'm a linux user comfortable with my OS but I'm not the most in-depth of my knowledge with it. Is this a command that you put into the terminal? Because if so, my terminal returns "command not found." Appreciate all you guys are doing ^_^
Each time a new device is detected, these files will be read in alphabetical order and scanned from top to bottom for matches. It's usually best for user-made custom rules to be last, so probably call the file you create "99-steam-controller" or something similar.
Googling "udev rules" will get you a lot of detailed information about writing these files, in case you want to understand how the individual rules are working.
Thank you so much! Controller works flawlessly now!
some games outright don't support both at the same time and will break the space time continuum of the engine if you try
I do like the controller so far, though. (Even though I can't play games.)
I can't say I have recieved any of these free copies you are talking about, but I wouldn't mind if it happened. ;)
EDIT: Hey, hey! Logged in this morning and found myself a Valve Complete Pack. Noice!
Is gyroscope disabled by default? Should I activate something before being able to use it?
Regards,
OLI
EDIT: Now I can use the gyroscope! I seems that many SC issues are solved just by activating "steam overlay" in big picture mode. Also, I activated the "beta" for big picture as I read about a fix related to the SC.
Hope that helps.
Best,
OLI
Not too sure. I got mine through Steam, if that helps.
After contacting steam support about it, they added the Valve Complete Pack to my account too! It did take a few days for them to get back to me, but in the end handled it well.