Closed thetargos closed 6 years ago
Second update, as a new comment to avoid overcrouding the first one, I did an experiment and connected the controller through BT, and SCC does recognize the controller, alas, the input feels sluggish and lagging in most games, but the Desktop profile seems to be much snappier. I feel no difference in regards to the dongle... So bottom line, it seems to be a conflict with the dongle, and maybe the new firmware or some other interaction with HID/evdev.
Two problems here:
But since there was new kernel-mode driver for Steam Controller added recently, my first question is which kernel are you using? Can you post output of uname -a
?
I knew I was forgetting something, 4.17.2, the kernel side driver I thought was slated for 4.18?
Follow up, so I did end up deleting my .config/scc directory and try running the scc gui and daemon, voilà... There seems to be an issue of USB conflict, there is an error on top of the SCC window: "There as an error with enabling emulation: Failed to claim USB device: LIBUSB_ERROR_BUSY [-6] Another application (most likely Steam) is using the controller".
Steam is not running, so this leaves an issue open, I remember back in the day that MS XBox 360 Wireless receiver could interfere, maybe I having such an issue... testing...
In fact typing this with the on-screen keyboard...
So in the end, the issue was on my end.
Thanks.
That's good to hear.
Sorry for late answer, I had to reinstall my "guinea-pig" machine before switching it to right kernel version and then was unable to replicate the problem. But at least I can confirm that there is no kernel-mode driver in it yet.
4.18-rc2 added the kernel mode driver behind a config flag (HID_STEAM)
Hello. First up, a BIG thank you for this amazing app!! The issue I currently have is as follows: I can't seem to be able to use sc-controller with my Steam Controller in its current state, might be a distribution update (I currently use Fedora 28), or something else entirely. The thing is that if I turn on the controller and start SC-Controller, the controller is not found/useable, and if I cycle the emulation, the SC shuts itself down... And I can't power it up again using the Steam button. In order to power the controller back up, I have to open the back, remove one of the batteries, and then power up, with the same result of SC-Controller not using it, cycling emulation shuts the controller down, etc, etc.
I don't seem able to find any useful entries in dmesg or the logs, and I have made sure all pertinent perms are set.
I see the following when I start scc gui and upon controller shutdown, and if I disconnect the dongle, reattach it and restart the emulation, it may be worth mentioning that upon closer inspection, the controller shuts down UNTIL I either press a button or touch a trackpad.
PS: I am using the latest firmware with the bluetooth low energy profile added to the SC installed from the Beta client of Steam, needless to say I am able to use the controller in Steam without issues.
What additional info would you need in order to try and attempt to fix this? I am assuming the issue is on my end, and I should mention that upon the firmware update, I did connect the controller in BT and then unpaired it and repaired it to the dongle, could this process have caused this behaviour?
Update: Just tried wired, deattached the range extender for the dongle from the cable, and attached the SC and the behaviour was odd: It appeared that a race condition was set in that the SC seemed to shutdown/up several times (while I was able to use it as a regular mouse, as it usually is the case when plugged in with cable) and then the fifth time or so, it registered the inputs in scc gui. From this it is apparent that the issue might be a conflict somwhere, as to what or where... I'm still lost. At the console from which I started scc gui there is no output... Back to square one.
TIA!