moonlight-android VS sc-controller

I could however play it through Moonlight Deskstop Stream using the mstmc.exe. This way I could just open Steam in Big Picture Mode then launch the game as always. However, once ing game, it has some weird visual glitch when walking in the streets of the city causing some stroboscopic effect in the textures which switch to a whitish washed-off color, and then back to normal darker colors, and then half a second later back to whitish colors, etc.

Just a guess since I don't have any Android devices but it sounds like it could be related to this bug: https://github.com/moonlight-stream/moonlight-android/issues/1108

Seems like you're not alone https://github.com/moonlight-stream/moonlight-android/issues/1161

Moonlight Game Streaming (version 11.0): Play games from your PC on Android

Finished the native Android client of my desktop streamer and latency still sucks. I looked over at Moonlight's code and they have lots of vendor-specific hacks for lowering latency. But I can't just copy that because: 1) it's GPL, 2) I'm doing the decoder initialization purely in Rust so I don't have convenient access to the Java methods.

And the "Moonlight" app on your phone to access your PC: https://github.com/moonlight-stream/moonlight-android

I know little about this, but from reading the description this sounds like a replacement for the "server" side of it (running on the machine where the game is running), but the article is talking about ending support for the client side of it on the Shield (please correct me if I am wrong)

In which case, perhaps a better replacement is something like this: https://github.com/moonlight-stream/moonlight-android

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.