We do often include affiliate links to earn us some pennies. See more here.

If you've read GamingOnLinux regularly, you will likely know how I am a big fan of SC Controller [GitHub]. It's a user-made driver and interface for using and mapping the Steam Controller. It's also now going under some major changes.

After previously noting how they weren't happy with certain issues surrounding Linux (like the Code of Conduct), the previous release was going to be the last for a while. Glad to see them back though, it's an incredibly useful tool.

So what's going on? Well, the developer "kozec" is rewriting large parts of SC Controller from Python to C with an aim to make it "much more portable" including Windows support and eventually Android.

For those interested, you can see the code on GitHub which is in a separate branch. They've also release version 0.4.9.1, which is the first rather experimental build with it using the new code.

Article taken from GamingOnLinux.com.
Tags: Drivers, Hardware
16 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly came back to check on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly. Find me on Mastodon.
See more from me
The comments on this article are closed.
19 comments
Page: «2/2
  Go to:

Klaus Nov 26, 2018
Quoting: mirv,aluminumgriffin
Quoting: GuestFrom a source code perspective, C is actually a very portable language. It might also have fewer dependencies, especially if you stick to POSIX, and quite probably a lower memory footprint once compiled. But I suspect in this case it's more that C can be used to create abstractions over the platform dependent sections, and python bindings will be provided on top of those.

Quoting: aluminumgriffinQuick thing about the C vs Python for being portable.
A python interpreter is a quite hefty penalty, and also there are C-compilers for _far_ more target-systems than there are platforms with python-interpreters.

Also, with C you basically "only" need to port the libs in use (with shims for everything you don't care about) when moving to an esoteric platform (this kinda was the purpose of C to begin with) while with Python you need to port the entire intepreter.

For a bit extreme case that still is easy to imagine - consider the case of an arduino (say, for an homebrew arcade machine). What would you find the easiest to do: port a C-program to fit into a couple of kB of memory, or try to wedge an entire interpreter in those same kB?

And as an aside, when working from another language it is a lot easier to interface with C than with Python (the former is often fairly automated as well as being common, not so about the latter).

Fair points. I actually had to look up Arduino though, but it makes perfect sense that someone might want to couple a commodity control device there.

The reason for my question was that I was under the impression, that C would outright sabotage the portability when targetting mainstream mobile devices, though that impression as apparently wrong.

I'm still confused though, as to whether the GUI portion CAN be portable that way.


Last edited by Klaus on 26 November 2018 at 3:52 pm UTC
Ray54 Nov 26, 2018
View PC info
  • Supporter
Which computer language would I use to write such code really does not matter. I have written specialist USB handling code for Linux and Windows in C and C# respectively, and it was pretty hard to get right. However, I prefer to use languages like Java, Gnome's Vala, Go and Python where practical, and I really like the little Rust coding that I have done. However without knowing the problem area in real detail, I would say that probably the best language for the development is the one that Kozec, who has done it before, chooses. From Liam's text, I assume C for the real-time bit-twiddling and Python for the rest, which sounds sensible to me.

I am not sure when Linux 4.18 will be available with native Steam Controller support, but that must factor in Kozec's decisions.
Shmerl Nov 26, 2018
Quoting: HoriYou all forget that there are waaay more people able to program in C than there are people able to program in Rust. Unless there's a very good improvement from which the application would get a real, noticeable benefit, you'd want to stick with the more popular choice.

That shouldn't be an impediment to use a newer language. Using this logic, everyone should have used FORTRAN forever. The benefit is always noticeable if you choose between C and Rust. The only blocker I can think of, is if the primary developer himself doesn't want to learn Rust.


Last edited by Shmerl on 26 November 2018 at 5:58 pm UTC
sarmad Nov 26, 2018
Is this driver better than valve's own driver? Valve's driver doesn't work out of the box and you have to tinker with udev files to get it to actually behave like a normal controller (for games that has built in controller support).
Shmerl Nov 26, 2018
Quoting: GuestAlso, it makes no sense to use Rust unless you’re in love with it. It’s a complicated language used by very few programmers. It’s much better to use C.

All languages have trade-offs. You pay for C simplicity with its primitivism and a big and painful overhead of code stability and correctness verification (unless you simply don't care about the later and the result can end up being a crashing mess). I'd take language complexity for the price of much higher default code correctness built into the language.


Last edited by Shmerl on 26 November 2018 at 8:19 pm UTC
Shmerl Nov 26, 2018
I'd take Qt over GTK.
Kristian Nov 26, 2018
Quoting: Hori
Quoting: WorMzyHere's hoping the dev moves away from using GTK3.
So that we end up with yet another application that doesn't properly or at all respect the system-wide theme that we want to have?
No thanks.

They could get it to work out fine if they basically imitate the official Steam Controller Configurator. In that case, they would keep consistency with Steam (as opposed to the DE theme) which is fine. Actually, in my personal opinion that would be even better.
Of course, people who don't use Steam might disagree... but then again, how many people (if any) are there who use an SC but not the Steam client?

Quoting: Shmerl
Quoting: GuestAh ok, a personal preference thing rather than a technical one.
On a technical level, C is a better choice here, for ease of cross-platform support on something that is lower level and may require kernel interaction. Pretty much everything is going to have a form of libc, and target platforms will have a lot of support (from compilers and build systems, to additional libraries that might be needed) already in C.

It's both and the reason for preference is technical, not simply one of taste. Rust can interact with kernel all the same by the way. Rust does depend on libc at present.

See https://github.com/rust-lang-nursery/portability-wg/issues/13

And an interesting example here: https://github.com/tsgates/rust.ko

You all forget that there are waaay more people able to program in C than there are people able to program in Rust. Unless there's a very good improvement from which the application would get a real, noticeable benefit, you'd want to stick with the more popular choice.

"Unless there's a very good improvement from which the application would get a real, noticeable benefit, you'd want to stick with the more popular choice."

On a side note, way too many programmers have a similar attitude towards open APIs like OpenGL and Vulkan and sadly they don't consider cross platform support as a considerable benefit.
D34VA_ Nov 26, 2018
Quoting: sarmadIs this driver better than valve's own driver? Valve's driver doesn't work out of the box and you have to tinker with udev files to get it to actually behave like a normal controller (for games that has built in controller support).


I don't know about other distros, but for Ubuntu and derivatives, you can install `steam-devices`, and everything should work just fine.
sarmad Nov 26, 2018
Quoting: aFoxNamedMorris
Quoting: sarmadIs this driver better than valve's own driver? Valve's driver doesn't work out of the box and you have to tinker with udev files to get it to actually behave like a normal controller (for games that has built in controller support).


I don't know about other distros, but for Ubuntu and derivatives, you can install `steam-devices`, and everything should work just fine.
I am on Ubuntu as well, and no, installing `steam-devices` is not enough to get the controller to work for all games. There are still games that require tinkering with udev files.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.