It's been over a year and this issue persists. Any update if a cause or workaround has been found?
Alright, so my issue I reported on Portal 2 was closed and referenced to this one.
Personally I don't think it's the same issue. Controller data is transferred just fine. It's just a matter of the bindings that are wrong.
I also just tried with using Windows as an in-home-streaming host and it shows the same issue:
Using the controller configuration templates works fine, the steam controller overlay works, but using the recommended or community configs that map buttons to actions (X=crouch instead of X=gamepad X) doesn't work.
Tested configs:
Linux host (Steam beta) + Linux client (Steam beta)
Linux host (Steam stable) + Linux client (Steam stable)
Windows host (Steam beta) + Linux client (Steam beta)
Note: This report is very old and seems to be mostly ignored. As my other report was closed referencing to this one, I will be as helpful (and also as annoying) as needed to get this fixed. I bought two Steam controllers to play games in my living room via streaming. For now, that does not work, so the product is completely useless for me right now, which is unacceptable for the > 100€ spent.
Thanks for clarifying @b3nn0. I agree that the symptoms do not match and this should be tracked separately. I've gone ahead and opened #4888 with the discussion thus far.
I'm able to use a controller in L2L. I'm assuming this issue is just a duplicate to #3136
Closing as outdated.
Nothing extracted yet.
I have a strange issue with Inhouse-Streaming Linux-2-Linux. I enter Big Picture Mode (BPM) on the client (with controller) and everything works well. Then I start a game via streaming and the game starts without being able to use the controller.
Obviously, the controller doesn't work in-game (streamed) even if it is still working within BPM (client). When I close the game by using keyboard or mouse actions the controller is back working within client's BPM.
I think, I hadn't that issue 1-2 weeks ago (ArchLinux). A friend of mine has the same behavior with Mint Linux. We changed to a windows host, which let the Linux client work just fine (with controller). So, we assume the Linux client is sending controller data, while the Linux host doesn't take notice.
We tried also with and without Steam Beta versions on client and host side. The result: if the windows host is active, the Linux client is able to control the stream via controller without problems. Using a Linux host shows the behavior as described above (no controller actions).