4 ms·

> Unless it does something smart like trying to compensate for the latency on the client end This is actually already done in many AAA titles. The idea is to b

> Unless it does something smart like trying to compensate for the latency on the client end This is actually already done in many AAA titles. The idea is to basically always be showing a prediction of what will have happened in ~70 ms, and update your state model accordingly. Given a datacenter to run the games on and all of the announcements about being able to take a snapshot of the state, this doesn't sound super far-fetched.

manfredo 7y ago
But stadia can't use these techniques. The game engine and rendering isn't done on the client side. Normally a network game the client displays the user's actions immediately, and the lag is only seen from other player's perspectives. On a streamed game, all interactions need a round trip before the user sees any response.
- loop0 7y ago
  Didn’t Google say something about using AI for this kind of game state prediction at Stadia presentation?
  - meheleventyone 7y ago
    Doing anything where mispredictions result in a few frames of doing the wrong thing escape to the user is going to make games feel really inconsistent. If the game is running at 60fps and you have a system that can predict with 99% accuracy (which seems wildly optimistic) you’re still going to have mispredictions at a pretty high rate. Not to mention that the game will have to be written especially to allow for the simulation to be rolled back and forth. For example a misprediction triggers a sword swing it turns out you didn’t make that traps the player in a state for a second. You end up giving the player a horrible experience where the game seemingly has a mind of its own. Or you can roll back and interpolate from the bad state back to a good one which would be ideal. Then the middle ground is to rollback and have a cut in the action back from misprediction. Then you realise this is happening every second or two.
  - manfredo 7y ago
    Game state prediction doesn't cut it, or rather there's no point to it. The rendering is done server-side - remember they're streaming HD AAA games to televisions and tablets. There's always going to be a round trip between pushing a button and something happening onscreen. Google did say something about device inputs being sent straight from the controller to the server. Maybe this means they will cut down on latency between the input and the server, but it's still a trip back down from the server to the display on top of that.

manfredo 7y ago

But stadia can't use these techniques. The game engine and rendering isn't done on the client side. Normally a network game the client displays the user's actions immediately, and the lag is only seen from other player's perspectives. On a streamed game, all interactions need a round trip before the user sees any response.

loop0 7y ago
Didn’t Google say something about using AI for this kind of game state prediction at Stadia presentation?
- meheleventyone 7y ago
  Doing anything where mispredictions result in a few frames of doing the wrong thing escape to the user is going to make games feel really inconsistent. If the game is running at 60fps and you have a system that can predict with 99% accuracy (which seems wildly optimistic) you’re still going to have mispredictions at a pretty high rate. Not to mention that the game will have to be written especially to allow for the simulation to be rolled back and forth. For example a misprediction triggers a sword swing it turns out you didn’t make that traps the player in a state for a second. You end up giving the player a horrible experience where the game seemingly has a mind of its own. Or you can roll back and interpolate from the bad state back to a good one which would be ideal. Then the middle ground is to rollback and have a cut in the action back from misprediction. Then you realise this is happening every second or two.
- manfredo 7y ago
  Game state prediction doesn't cut it, or rather there's no point to it. The rendering is done server-side - remember they're streaming HD AAA games to televisions and tablets. There's always going to be a round trip between pushing a button and something happening onscreen. Google did say something about device inputs being sent straight from the controller to the server. Maybe this means they will cut down on latency between the input and the server, but it's still a trip back down from the server to the display on top of that.