3 ms·
However, since the game state has to be rendered on the server, there would still be at least 120ms input latency.
by Retr0spectrum 11y ago
However, since the game state has to be rendered on the server, there would still be at least 120ms input latency.
- angersock 11y agoCorrect. Strictly speaking, 240ms--120 there, 120 back once rendered.
- pests 11y agoThere is a post sometime in the last year here about a Microsoft Research tech demo which abused bandwidth to send all possible futures as well as the current screen, enabling client-side prediction to again eat one way of the trip. Anyone remember this? e: Found it! http://www.pcmag.com/article2/0,2817,2464341,00.asp http://www.pcmag.com/article2/0,2817,2464341,00.asp https://news.ycombinator.com/item?id=8210957 https://news.ycombinator.com/item?id=8210957 (comments on actual paper) This is the relevant technical details from the pcmag article: Microsoft's DeLorean system takes a look at what a player is doing at any given point and extrapolates all the possible movements. It streams a rendering of these from a server to a player's console. Thus, when a player decides what he or she plans to do, that scene—for a lack of a better way to phrase it—is already ready to go.