Page 1 of 1

[Twinsen] [0.16.36] Desync, perhaps related to blueprints and trains

Posted: Mon Apr 09, 2018 10:09 pm
by thuejk
We had a desync in AntiElitz's multiplayer stream. Multiple people (but not everybody) desynced. The desync happened around 7:45:00 in the video https://www.twitch.tv/videos/248419397 .

The desynced people could not rejoin.

We have 2 guesses as to what caused it. Either copy-pasting train stations, or trying to make a circuit clock.

The desync report is here: http://thuejk.dk/desync-report-2018-04-09_23-57-49.zip

Restarting the server seemed to fix the problem.

Re: [0.16.36] Desync, perhaps related to blueprints and trains

Posted: Mon Apr 09, 2018 10:47 pm
by POzilGeR
i was on the server as well, and the desync happend to me too. heres the report:
https://www.dropbox.com/s/vxurbgek7dgus ... 5.zip?dl=0

Re: [kovarex] [0.16.36] Desync, perhaps related to blueprints and trains

Posted: Thu May 17, 2018 3:59 pm
by kovarex
Hello, I investigated the desync report a bit, and there were too many accumulated changes to let me make any sense out of it.
I also tried to run the save in a heavy mode, but it ran fine (the same effect as when you restart the server, it gets to be fine).
It might be related to some circuit logic desync problem being investigated by twinsen (60245)

As always, getting way to reproduce the desync would be very helpful.

Re: [Twinsen] [0.16.36] Desync, perhaps related to blueprints and trains

Posted: Thu May 24, 2018 4:47 pm
by Twinsen
Was anyone making anything around position 148.5, 579 at the time of the desync? (the circuit contraption next to "totally not afk")


The desync was caused by the arithmetic-combinator at position 158.5000000000, 579.0000000000 outputting "8 white" instead of "2 white", even though it's input was 3422. I fail to see what could have possibly caused that.

Re: [Twinsen] [0.16.36] Desync, perhaps related to blueprints and trains

Posted: Tue May 29, 2018 12:23 pm
by Twinsen
I was unable to find what could have caused this. And the other desync I fixed is unrelated.

We added some extra logging in desync reports so if this happens again report it after Version 0.16.46