Gevalt uploaded file logs.zip (141.4 KiB)

P1 = win xp P0 = linux

Gevalt uploaded file desync102_p0.txt (542.5 KiB)

Gevalt uploaded file desync102_p1.txt (542.5 KiB)

Gevalt uploaded file WZlog-1115_133823.txt (1420.9 KiB)

Gevalt commented

P0 = Linux
P1 = Win XP
More logs inside .zip file
if there's any more intel for this bug just ask me, I'm open for debugging

Gevalt uploaded file logs-3.2-master-20150823-211805-11c421d.zip (149.5 KiB)

P1 = win xp P0 = win 7 64bit

Gevalt uploaded file desync102_p0.2.txt (8.3 KiB)

Gevalt uploaded file desync102_p1.2.txt (8.3 KiB)

Gevalt uploaded file WZlog-1115_155434.txt (1756.5 KiB)

Gevalt uploaded file logs-3.2-master-20150823-211805-11c421d----WIN7_SERVER_HOSTER.zip (144.0 KiB)

P1 = win xp P0 = win 7 64bit

Gevalt commented

Added some more logs.
This time a game at 3.2 Master branch, my win xp against win7 host + logs from both machines.

Gevalt uploaded file logs-3.1.2-linux_hoster.zip (133.4 KiB)

P1 = win xp P0 = linux

Gevalt commented

Added above logs of the host from the first game [first attached .zip/logs in this ticket].
Further details - the "desync detection" mechanism "thinks" one player did not get resources, which is untrue, both me and hoster started with proper amount of resources, in both of the played/logged games. So for some reason netcode part of Warzone fails to properly announce what is going on, at least for the starting resources, whenever the game client is being run under Windows XP.
This is clearly WZ2100 netcode code compatibility issue with WinXP, someone should check out what's wrong with it.

Also as a quick observation, despite the desync the game was still playable, me and my opponent could see actions of each other properly and make a quick base fight [the second game's .zip'ped logs, against win7 hoster] so the issue hopefully wont be too hard to address and to fix.

klasskill commented

I don't think they will pirate xp and this is a duplicate of http://developer.wz2100.net/ticket/4271 and there is no 3.1.3

vexed changed status from new to closed

vexed changed resolution from `` to duplicate

vexed changed blocking which not transferred by tractive

vexed changed blockedby which not transferred by tractive

vexed commented

Well, this is a duplicate of #4271 and this is extremely complicated to troubleshoot, especially with a defunct OS, though, as you can see in #4271, the OS don't seem to be the root cause.

(Logs don't help debugging this issue, see #4271 for more info.)
Closing as duplicate of #4271.