Desyncs and minidumps

I played a 4v4 with some friends today, and everyone except me (the host) repeatedly minidumped at a certain point in the game, even after reloads from saved games.  We fixed it by restarting our computers, but then we discovered that we were desync'ed.  This was about 2 hrs into the game.  What does it take for you guys to diagnose the problem?  Will my own save game be enough, or will everyone have to submit theirs?

 

Also, why is it that when the game detects a desync from checksums or whatever, it doesn't let the players know?  Why doesn't it pause the game and re-sync states?  IIRC when Supreme Commander caught itself desync'ing it will attempt to re-sync.

1,453 views 1 replies
Reply #1 Top

Everyone should submit the save game, minidump, and anything else they generate (e. g. I believe there is a desync log generated).

 

And it does let the player know when it detects a desync; the problem is it doesn't always do so unless you fiddle with some settings (I think they increase the 'strictness' of the checksum system, I don't know the details).  As far as attempting to resync...  that's over my head; I don't know how supreme commander does it (they've probably had more opportunity to think about it than I have :D) but it seems like it would require having a 'host' computer upload the 'correct' stats to all other computers (violating the P2P design of the multiplayer architechture).  If SC catches it right away, it might be relatively easy by just detecting the 'improper' orders but...  I really don't see how that could happen short of a full 'resynch' involving the transfer of the entire game state.

I wonder if what you're talking about is a desync in time -- game Y is at frame XYZ, and game Z is at frame XYZ+30, and you need to get the time resynched... that hsould be doable...