ssh-rdp VS sc-controller

i use a bash script for that - lower latency than steam link https://github.com/kokoko3k/ssh-rdp

Can't believe nobody has mentioned this one https://github.com/kokoko3k/ssh-rdp

Well, there's netevent for that; there's this project that implements it: https://github.com/kokoko3k/ssh-rdp

https://github.com/kozec/sc-controller has been my best friend in getting controllers working properly

I haven't figure out how to intall sc-controller on latest fedora. I reported a bug on the github but I wanted to ask in this subreddit too, just in case anyone here has a solution.

third - sc controller

you appear to be missing some dependencies. Make sure that you have all of the build dependencies installed to build this program. They are listed here.

So with drivers it's easy to give gryo data to Linux, and Linux to expose it to games, but games don't always know what to do with it. The current workaround has always been a tool like Steam Input, or the open source sc-controller, that takes the gyro data, combines it with the old school gamepad data, and emulates an Xbox 360 controller with it.

The only thing I can think of, left to try is: https://github.com/kozec/sc-controller

But in the end I ended up buying PS4 pad. * A big selling point for me was that it has gyro. You can set it up as mouse input (in Steam controller settings for the game or something like sc-controller. I'm sure there is something similar for Windows too) and that way use for precise movements * The mouse pad in the middle is nice too * I'm not sure if these measurements are still true after 4 years but it seems it has the lowest input lag when used via BT

I don't know about the state of Windows support, but for Linux users the fork at https://github.com/Ryochan7/sc-controller is preferable. Ported to Python 3 (upstream is still sitting on EOL'd Python 2 due to kozec preferring a C port) as well as some bugfixes. I use it for any non-Steam games (Epic, Uplay, Origin, GOG).

SC-Controller should fit your use-case.