I've attached the output of Steam with Solus integration enabled and LSI_DEBUG on. So it seems to be somewhere else in the recent updates. I tested an older unstable test build (linux-steam-integration-0.5-18-1-x86_64.eopkg) which had worked previously with the controller (at least as I recall over the Steam Link) to no avail. I also disabled all Solus Steam Linux integration to no affect and I opted into the Steam beta to see if changes there made a difference but unfortunately not. I've tested SC-Controller and it works just fine there. It is when I launch a game that input stops working. On launching Steam the controller will act in its desktop mode when Steam is in desktop mode and when in Big Picture it still works as expected. To make sure I also sudo chmod 666 /dev/uinput but this had no affect.
Getfacl: Removing leading '/' from absolute path names So it might be worth updating the steam package to do that.Īnyway I have confirmed that my user has access to write to uinput: I picked up somewhere on the inter-webs at some point that some changes in udev rule processing had adjusted where the processing of devices tagged uaccess was done and thus the steam controller rules needed to be defined sooner. It did not work quite out of the box as /dev/uinput was not having correct ACL set. Original postįirstly sorry I did not report this bit earlier. On Ubuntu 16.04 and testing Rocket League the controllers continue to function with the Gamepad Configuration enabled.
#Hollow knight pc controller not pro#
Disabling this feature allows the Steam Controller and my Xeox Pro Wireless controller to function in all games. Turns out the issue started because I enabled Steam's Generic Gamepad Configuration Support. Previously I had a working Steam controller that adjusted as designed for each game.
0 kommentar(er)
