moonlight-qt VS input-leap

I found this https://github.com/moonlight-stream/moonlight-qt/issues/967

You could use sunshine (https://github.com/LizardByte/Sunshine) + moonlight (https://github.com/moonlight-stream/moonlight-qt). To be honest, at least for me, it works better than most of the RDP/VNC stuff.

I discovered the moonlight client and sunshine server a few months ago. These are open source solutions to provide remote gaming/desktop capabilities with built in input and audio passthrough. I tried NoMachine, but I wasn't able to get audio to work. This looks like a known issue on arch. On sunshine, I didn't have to do any extra tweaking! This allowed me to game on my desktop pc without having to sit at my desk. This was especially helpful while watching my 2nd son. I was really impressed by the performance, I could stream my host's display at high resolutions and frame rates with low latency despite my desktop being in the basement using WiFi. I was getting some instability with WiFi, so I wanted to try connecting my desktop to the router via Ethernet. I decided to go with a headless solution because that gives me more flexibility on the placement of the desktop; I ended up moving my desktop upstairs closer to my router. I figured out a way to stream my hosts display headless by using Nvidia TwinView to create the virtual display. This means I don't need to buy any HDMI/DP dummy plugs. I wrote a Linux Guide for sunshine on how to set this up. If you have any feedback on this guide, let me know! I haven't tried this, but wolf is an interesting docker alternative to sunshine.

Releases · moonlight-stream/moonlight-qt (github.com)

and on my Ally: https://github.com/moonlight-stream/moonlight-qt/releases (the windows installer)

There is an actively developed fork https://github.com/input-leap/input-leap, however that fork is still undergoing heavy development and recommends sticking with Barrier until they're able to release v3.0.0 which they expect rather soon.

barrier is basically a dead project now. The active members of the project forked it and are going to release when ready but

https://github.com/input-leap/input-leap

Keep an eye on that for anything new

There's a new fork of barrier called input leap (not to be confused with the leap motion), https://github.com/input-leap/input-leap with work on getting Wayland support in shape. Not sure how far the support is atm, but the gnome 45 release notes mentioned "Wayland support for Input Leap" (https://release.gnome.org/45/)

Wayland tracker issue, https://github.com/input-leap/input-leap/issues/109

I wonder if I would be better off just buying a LG monitor without the Smart KVM, and instead using Barrier (or, Input Leap, which seems to be maintained actively compared to Barrier https://github.com/input-leap/input-leap)

Could also be worth mentioning that Barrier is basically unmaintained at this point so you'll probably never get Wayland support there. The maintainers (apparently the owner of the debauchee/barrier dropped off the face of the earth) of Barrier forked it and migrated to input-leap (issue with details if interested) which is where all development is presently, although they haven't made a release yet.

I'm already using waynergy with input-leap as my main way to control the laptop when it is docked. It is amazing.