Also, I find it hard to believe that the refresh latency of a TV is greater than Internet network latency. Do you have a source for that? And even if it’s true, wouldn’t that only exacerbate the problem if you’re playing a cloud game streamed to your TV?
Not me really, but my kid likes to play latency sensitive stuff. Platformers and some FPS style.
> Also, I find it hard to believe that the refresh latency of a TV is greater than Internet network latency.
2017 TV models have input latency between 12 and 69 ms in "game mode" according to [0].
The situation seems to have improved considerably, some older models I've tested were up to 100-140 ms.
When I tried to ping google.com, I generally got about 16 ms avg.
$ ping google.com
PING google.com (172.217.21.174): 56 data bytes
64 bytes from 172.217.21.174: icmp_seq=0 ttl=54 time=16.403 ms
64 bytes from 172.217.21.174: icmp_seq=1 ttl=54 time=15.492 ms
64 bytes from 172.217.21.174: icmp_seq=2 ttl=54 time=16.880 ms
64 bytes from 172.217.21.174: icmp_seq=3 ttl=54 time=16.249 ms
> And even if it’s true, wouldn’t that only exacerbate the problem if you’re playing a cloud game streamed to your TV?Well, in this particular case I was using a laptop instead when playing remotely. So it kind of offsets it.
Disclaimer: I don't play much, but my kid sometimes do on the go. Perfectly happy with it.
So why would Google need to be any worse?
There's less latency on the network than in many TVs because of their crazy image high latency processing pipelines.