In addition to an update to the excellent SC Controller software, it seems there's also work towards getting full Steam Controller support in the Linux Kernel.
Currently, to get proper use out of the Steam Controller you either need the Steam client open, or to use something like SC Controller. However, this could change due to the reverse engineering effort from one hacker. This is actually the second revision to their patches, which cleans it up and implements a few more features.
Part of the problem, is that currently it will show up as multiple different types of devices like a virtual keyboard, a virtual mouse and so on. Here's what the developer of the patch said:
This driver was reverse engineered to provide direct kernel support in case you cannot, or do not want to, use Valve Steam Client. It disables the virtual keyboard and mouse, as they are not so useful when you have a working gamepad.
Working: buttons, axes, pads, wireless connect/disconnect.
TO-DO: Battery, force-feedback, accelerometer/gyro, led, beeper...
They said they are working on a third revision to the patches and there will likely be more work to be done if it is to be accepted. Valve developer Pierre-Loup A. Griffais has been commenting on the mailing list as well to provide some help and ask questions. Part of the issue, is this needs to not break support for the Steam Controller with the Steam Client or other software like SC Controller. Nothing seems set in stone right now in regards to this particular code, so it will be interesting to see what happens.
You can find the information here on the mailing list.
Article taken from GamingOnLinux.com.
Quoting: GuestBecause Valve want/need you to use their Steam client.
Tying hardware to clients is obnoxious.
Quoting: meggermanAlthough the profile management on sc-controller for instance is nice, id imagine it could benefit from this too.
The GUI for the controller can just use the driver, instead of hacking access to it through USB python APIs.
Kimyrielle Feb 28, 2018
Quoting: ShmerlQuoting: GuestBecause Valve want/need you to use their Steam client.
Tying hardware to clients is obnoxious.
*looks at Apple*
Yes...yes, it is.
Quoting: ShmerlQuoting: meggermanAlthough the profile management on sc-controller for instance is nice, id imagine it could benefit from this too.
The GUI for the controller can just use the driver, instead of hacking access to it through USB python APIs.
Yes, i should of stated that. i only imagined it would ;)
hardpenguin Feb 28, 2018
Quoting: ShmerlWhy can't Valve make such driver and use it directly after that?My guess is that their daemon-based approach was initially less work, since they could reuse a lot of code to provide identical support on Windows and macOS, not just SteamOS/Linux.
BloodaxeNOR Feb 28, 2018
Quoting: ShmerlWhy can't Valve make such driver and use it directly after that?
First thing I can think of because otherwise they would then depend from linux kernel release process for steam controller updates and features. And linux kernel guys have comprehensively other priorities. So it makes sense for them to leverage steam client to deliver their software since it's already good at doing that.
Patreon
PayPal
See more from me