SYNC!!
Issue #100
resolved
I just played someone who captured my construction yard. The problem is it never showed up on my screen so I never saw it. I even watched the replay twice and no engineer ever came over. So clearly things are not synced up. And in another game, the other player was able to continue building near where I destroyed his buildings. In my view, his buildings were destroyed and he shouldn't be able to continue building. In his view, he still had buildings there. Is there anything that can be done for this? We were both playing in Chrome and I had no other applications opened, yet he was seeing things long before I ever did.Thanks.
Comments (6)
-
repo owner
-
repo owner
You can see a detailed description of what to do to report a sync error on the forum here...
Reporting multiplayer sync errors in Command & Conquer HTML5
-
repo owner
Issue
#99was marked as a duplicate of this issue. -
repo owner
- changed status to resolved
This should have been fixed by now... Please report if the problem occurs again.. Send the replay as attachments or via FB page
-
reporter
i tried to send an unsynced game. But it wouldn't let me abort. Instead 3 white squares appeared on my screen and i had to x out of the whole thing
-
repo owner
That sounds a little weird... Did you notice any error messages in the console?
Maybe next time... I assume the sync error happens less often now, and not all the time?
- Log in to comment
Multiplayer games going out of sync is a high priority bug that I have been trying to trace/fix for a while now....
It is definitely fixable once I figure out where the problem is occurring... Lots of games work fine and only some seem to have the bug....
I need the help of testers to locate the problem.
Anytime a game ends, both players end up saving the game as a multiplayer replay.
In my next release, I will add a button to export saved replays....
Once I do, please send me both the players versions of the saved replays (whenever a de-sync occurs) so I can compare and see where the problem is occurring....
With your help, I know we can fix this problem soon :)