Re:Synchronous RTS Engines and a Tale of Desyncs
by nopassrecover on Sunday July 10, 2011 @12:04PM
(#2747966)
I think the point was that resyncs (exchanging game state) are too intensive (hence the prohibition on "join in game") - as you say if people are prepared to wait a few minutes it's less of an issue. Having said that, this explains load screens on joining multiplayer games much better for me (first load is a state sync, but subsequently input-sync could be sufficient).
Re:Synchronous RTS Engines and a Tale of Desyncs
by algorias on Sunday July 10, 2011 @05:43PM
(#2748694)
I think we'd be talking about seconds here, not minutes. 1K units might be a lot to update in real time while doing a bunch of rendering etc, but a dedicated sync pause shouldn't really take very long in isolation.
I think this would essentially amount to having save/load game for multiplayer, and how often have you seen games have one of those?
Still, desync errors are pretty common in early versions of RTS, I remember pulling my hair out while playing Starcraft and getting desynced non-stop. Or maybe it was the cheaters!
Re:Synchronous RTS Engines and a Tale of Desyncs
by seabee on Sunday July 10, 2011 @02:01PM
(#2748204)
Multiplayer save/load is not prevented by technical issues as much as it is by development time constraints and the ideal that such a situation is unnecessary. A scenario editor is not that far removed from dumping the current game state.
Robustness is no incentive either, since people will put up with a lot of bugs from games.
You would choose a player to be considered to have the master copy by who is least likely to be cheating. In the case of a tie in votes, the player with the master copy could be chosen with a deterministic random number generator instead.