Comment by appletrotter
5 years ago
>So, from your human reaction to the resulting frame, at best, it takes from 107ms to react to something on screen and see the results of your reaction.
People can perceive delays smaller than their reaction window. For argument I'll say it's 50ms is the perceivability barrier, since we seem to throwing numbers around here. I can get 50 or 60 ms lag on my wifi often, and I would say that I have a pretty good connection. So therefore, the input lag potential with stadia is significant. 60 > 50.
I think the more important fact is that people can be affected by small amounts of latency, even if they can't react that quickly or perhaps even discern that latency is occurring.
The obvious example here is a precision platformer like Celeste, but you can say the same (with less and less applicability) to other games, starting with FPS.
In Celeste, there are a handful of frame-perfect inputs in the game. This means you have less than a 20 ms window to get your input in, or you're dead (the game's only failure state). How is this possible, if human reaction time is only ~100 ms at best? It's because there's a difference between reaction time and timing. Reaction time measures your time-to-react to an unpredictable stimulus. Timing is your reaction to a predictable stimulus. Most of the time in games you are reacting to a stimulus that is at least somewhat predictable.
So with a little training you can reliably make that frame perfect jump. But if Stadia adds 60 ms of latency, that means your character is over 3 frames ahead of where you think she is. You're going to miss that jump a lot until you can reprogram your brain to account for the latency, as much as possible. And even then you'll probably find it harder. Throw in a little variability to the latency, so you think the character is 3 frames behind but she's actually 4, and you're doomed.
Granted, not every game is a precision platformer, so there are diminishing returns for low latency in other types of game. But if you, say, enable cross-play between Stadia and non-Stadia in a shooter, the local players are probably going to have a huge advantage. Even making it work against an AI opponent would require some significant work to make the AI's reaction time keyed to Stadia's measurement of latency, not whatever you originally hard-coded into the game.
You reacting to something is not the same as reacting + seeing the rendered frame.
There's an entire chain of things that contribute to latency, and network latency is only one part of that chain.
From what I've experienced on a pretty normal, non-optimized wifi connection (meaning I just plugged a cheap TP Link router in and did nothing to its default settings), I don't notice the latency that Stadia contributes making any difference compared to whatever amount of latency I get on my capable PC.
That's not to say network latency doesn't matter. It matters a lot to pro CS:GO players, for example, (who have reaction times in the 130-300ms range, for what it's worth). Those players are will to pay for high poll rate mice to shave off a few milliseconds from input latency, or build $5k+ machines stuff with insanely fast CPUs and GPUs, with $2k+ monitors with 1ms latency.
But Stadia isn't for that kind of game play.
Like I said in another comment, the talk around streaming games is almost identical to people who scoffed at services like Netflix when they first started streaming. You had Laserdisc nerds freaking out about how the streaming would produce compression artifacts, and people like Mark Cuban saying that people were crazy to think streaming video was the way to go, (all while pitching his HD satellite service).
Having used Stadia as a "normal" person might, I'm certain that in the not too distant future, streaming based gaming services will be as mainstream as Netflix is today. Despite whatever compromises it has to make.