You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've seen the scc-daemon specification and saw that it uses UNIX sockets in the filesystem instead of TCP/IP Sockets. Would it be too difficult to adapt to use that? USE CASE: I have a spare Steam Deck that I want to use as a wireless controller for my Gamer PC, so I would run scc-daemon on the deck (which would get the devices, mouse etc.) and connect sc-controller from my PC Gamer to the Steam Deck, having the outputs there.
I know that since the Steam Controller is long gone this project has had not much activity, but I think new opportunities for it to shine are appearing. Not only via the steam deck functionality (and it works great already with that), but replacing Steam Input in wayland since Steam Input still can't handle mouse control properly in Wayland via the steam controller / deck.
The text was updated successfully, but these errors were encountered:
I've seen the scc-daemon specification and saw that it uses UNIX sockets in the filesystem instead of TCP/IP Sockets. Would it be too difficult to adapt to use that? USE CASE: I have a spare Steam Deck that I want to use as a wireless controller for my Gamer PC, so I would run scc-daemon on the deck (which would get the devices, mouse etc.) and connect sc-controller from my PC Gamer to the Steam Deck, having the outputs there.
I know that since the Steam Controller is long gone this project has had not much activity, but I think new opportunities for it to shine are appearing. Not only via the steam deck functionality (and it works great already with that), but replacing Steam Input in wayland since Steam Input still can't handle mouse control properly in Wayland via the steam controller / deck.
The text was updated successfully, but these errors were encountered: