Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

scc-daemon and sc-controller as TCP/IP server-client #736

Open
Patola opened this issue May 10, 2024 · 0 comments
Open

scc-daemon and sc-controller as TCP/IP server-client #736

Patola opened this issue May 10, 2024 · 0 comments

Comments

@Patola
Copy link
Contributor

Patola commented May 10, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant