[Solved] Desync with 1 human player, not with other human player

[x4000]

How's it going, fellas?  I'm not seeing anything in the code thus far -- did the .NET update fix it?

[x4000]

Update:  based on further email correspondence, it looks like the .NET update was the cause of the desync.  So if this happens for anyone else, please make sure everyone has all of the .NET updates installed.  Further play from Arcane, Daemon, and Bridger will be needed before we will be 100% certain that is what the issue is, but so far so good after the MS patch.

[x4000]

Further update:  Turns out that the desync was caused by having the .NET Framework 3.5 SP1 on two of the machines, but just plain old .NET Framework 3.5 on the one that was getting out of sync.  You can play the game with .NET 3.5 or .NET 3.5 SP1, in single or multiplayer, but in multiplayer all of the players must be on the same version (SP1 installed or not).


Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 3.5 Family Update (KB951847)

Update type: Important

The Microsoft .NET Framework 3.5 Service Pack 1 is a full cumulative update that contains many new features building incrementally upon .NET Framework 2.0, 3.0, 3.5, and includes cumulative servicing updates to the .NET Framework 2.0 and the .NET Framework 3.0 subcomponents. The .NET Framework 3.5 Family Update provides important application compatibility updates. This update is provided to you and licensed under the Windows Vista and Windows Server 2008

[Daemon]

Yes I can confirm that the .NET patch was needed to cure the problem. After this patch gameplay was fine last night.

Will keep you posted and thanks for your speedy responses and great help.

[Bridger]

/signed.  Trouble free play on 1.004 for several hours last night.  Will upgrade again to 1.005C and 3 player tonight.

Just as a further info, the first desync came after the first wave of enemy were destroyed/being destroyed.

[x4000]

No problem, guys!  And thanks for your help in hunting that down.  You should be able to use any of the more recent 1.005 prerelease versions without any issues, since the problem was the .NET versions.  Glad that's all it was!