- Oct 27, 2017
Total latency isn't a good measure, because the base console has latency itself, and different games will have different total latency - I mean, Assassins Creed Odyssey on a local Xbox One X has like 120ms latency between a button press and its visual response! So when that game has like 160ms on Stadia it means quite a different thing, the total number makes it sound horrible and like it's far worse than if you were comparing with Mortal Kombal 11, but the streaming service is only adding 40ms in this example. So if you want to talk about the latency added by the streaming tech, you gotta look at the difference between playing a game on local hardware and the same game on streaming hardware. And in that the three services are quite different.I was looking at the absolute total latency on each service (minus display latency), for Killer Instinct on xCloud, Ultra Street Fighter 4 on PSNow and Mortal Kombat 11 on Stadia. 121ms, 126ms, 122ms respectively. Looking at additional latency in isolation, we might indeed say DF found Stadia to be a bit better than xCloud and PSNow. It would be a good reason to ideally test the same game across all three services - though that still might not perfectly isolate the latency of the rest of the stack in each case, as I've a feeling devs have the opportunity to reduce the base input latency in their Stadia builds that they might not have deploying a game on xCloud or Now, for the moment anyway. (i.e. base input latencies in the stadia version of a game and the xbox version of a game and the ps version of a game may all vary for whatever reason, and we can't compare Stadia against it's 'local' latency alone).