4 ms·

I never had to do it myself, but I have a feeling it will work better with Wayland. The delay of 50-80ms introduced by the network is not terribly much (everyth

by gnull 4y ago

I never had to do it myself, but I have a feeling it will work better with Wayland. The delay of 50-80ms introduced by the network is not terribly much (everything under 110ms is fine for playing Dota), so if your software doesn't lag itself, like X11 did, maybe it will work. You could also use something like Zerotier-one to recover from network being shortly disrupted. This service connects your machines into a virtual network with static IPs, so the IP addresses through which your machines talk will stay the same and TCP connections will recover and ssh will keep working if a device briefly goes offline.

rcoveson 4y ago
> The delay of 50-80ms introduced by the network is not terribly much (everything under 110ms is fine for playing Dota) I don't think you're giving the Dota client enough credit there. Game clients don't wait for network to pretend to respond to user input, because it absolutely is noticeable at 100ms latency. Instead, they predict as much as they can client side and display it as fast as possible. For this reason, the client is not at all thin. It knows how to run the whole program by itself. Not so with remote X11. With remote X programs, the client doesn't know what happens on click for anything, so the user really does get hit with a 100ms delay for every interaction with the program.
- gnull 4y ago
  You're right. I just tested it connecting from laptop in Sweden to a VPS in Sweden through a German VPN server. The total ping was 30-40ms, and running `waypipe ssh remote firefox` was right on the edge of being unusable. Navigating and clicking on links was fine with a bit of delay, but typing when the feedback is delayed is annoying. Although if I connect to something that's 20ms away (within the same country), the experience is really good.
sph 4y ago
50-80ms of non-predicted input lag is not terribly much? Surely you must be joking. Dota is fine because it has network prediction and a finite and well defined set of inputs. And that's also ignoring video compression artefacts which are that you introduce if you send a modern GFX pipeline across the network. Computers screens can no longer be described with just filled rectangles and text.

by gnull 4y ago

rcoveson 4y ago

> The delay of 50-80ms introduced by the network is not terribly much (everything under 110ms is fine for playing Dota) I don't think you're giving the Dota client enough credit there. Game clients don't wait for network to pretend to respond to user input, because it absolutely is noticeable at 100ms latency. Instead, they predict as much as they can client side and display it as fast as possible. For this reason, the client is not at all thin. It knows how to run the whole program by itself. Not so with remote X11. With remote X programs, the client doesn't know what happens on click for anything, so the user really does get hit with a 100ms delay for every interaction with the program.

gnull 4y ago
You're right. I just tested it connecting from laptop in Sweden to a VPS in Sweden through a German VPN server. The total ping was 30-40ms, and running `waypipe ssh remote firefox` was right on the edge of being unusable. Navigating and clicking on links was fine with a bit of delay, but typing when the feedback is delayed is annoying. Although if I connect to something that's 20ms away (within the same country), the experience is really good.

sph 4y ago

50-80ms of non-predicted input lag is not terribly much? Surely you must be joking. Dota is fine because it has network prediction and a finite and well defined set of inputs. And that's also ignoring video compression artefacts which are that you introduce if you send a modern GFX pipeline across the network. Computers screens can no longer be described with just filled rectangles and text.