Page 1 of 1

98 OS compatibility ?

Posted: 08 Nov 2014, 22:53
by albator
I tried to watch this: http://replays.springrts.com/replay/8a8 ... 668e74b03/

I tried both linux static 32 and 64 and I end up with the same exact error and a broken replay:

Code: Select all

Error: [DESYNC_WARNING] checksum 2ac17a27 from player 17 (ktalog) does not match our checksum 7217fbdf for frame-number 4380
Does that mean the synchonization is broken between windows (host that run the demo) and linux (me)

Re: 98 OS compatibility ?

Posted: 08 Nov 2014, 23:26
by jK

Re: 98 OS compatibility ?

Posted: 08 Nov 2014, 23:38
by albator
Here are the full logs of the run: I stopped after a lot of error messages

32:

http://s000.tinyupload.com/?file_id=099 ... 6373957794

64:

http://s000.tinyupload.com/?file_id=966 ... 3429411521

Everything look normal until the "checksum" warning.

I use linux mint 17.1 cinnamon 64 bits

The weird thing is that I actaully played that game with the exact same spring (64) I am trying to watch the replay with

Re: 98 OS compatibility ?

Posted: 08 Nov 2014, 23:47
by jK
no filehosters, there are pastebins for that

tip: I assume the autohost doesn't run 98.0

Re: 98 OS compatibility ?

Posted: 09 Nov 2014, 00:04
by albator
32
http://pastebin.com/MMbhcNat
64
http://pastebin.com/uYgUpp7S



SL201 say blackholehost1 runs 98.

Re: 98 OS compatibility ?

Posted: 09 Nov 2014, 12:41
by Silentwings
Does that mean the synchonization is broken between windows (host that run the demo) and linux (me)
Not at home so haven't looked at the logs at all, but the BlackHoleHosts run linux (64 bit iirc) and all except the engine testing one currently run 98.0.

I have watched several demos from them (on my own machines, which are all windows), all without desyncs. Imo check other demos to see if this always happens to you or if it is specific to that demo.

Re: 98 OS compatibility ?

Posted: 09 Nov 2014, 14:12
by albator
Humm, it looks like specific to that demo. Some other I tried work fine.
The point is that it is also a game that was not able to end correclty on linux (at least on my machine) and I had to kill the job, so maybe that is correlated and happens server side as well.