[0.11.3] Irrecoverable Desync Loop

[lux]

After 25 hours of 3-player multiplayer, our save has become unstable and we cannot continue.

The following link contains the map save, the full crash logs from the server machine, and from client machine:
https://www.dropbox.com/s/0ty6x5kdsah5y ... 3.zip?dl=0

The crash is reproducible between two people on LAN both with windows 7 64bit:
- server (player 1) hosts with 99ms latency setting
- client (player 2) connects over LAN
- map loads, after a few seconds, the client desync occurs and client disconnects
- client automatically reconnects, but desyncs after rejoining, only to desync and disconnect again
- this process is repeatedly forever

The majority of the save was played with three people, and we tested all possible combinations of different hosts, 2 or 3 players, the same outcome seems to occur. The save started on 0.11.1, where the same issue occurred. We stopped playing, hoping that a future patch might fix it. We then tried to pick it back up in 0.11.3, however the same desync issue seems to occur.

[Adamo]

We've experienced errors like this. One temporary fix has been to change usernames. Yes, this means you will lose your inventory.

[lux]

We've experienced errors like this. One temporary fix has been to change usernames. Yes, this means you will lose your inventory.

Interesting, will try it out.

[xiphias]

I have experienced the same thing with games that have been going on for some time, and I wrote a thread about it yesterday, read it and try and see if what I suggests solves the problem!

https://forums.factorio.com/forum/vie ... f=7&t=6924

[lux]

I have confirmed that neither of these tricks worked on the save that I posted:
- renaming character before connecting
- disconnecting all source of power draw (lights, laser turrets, accumulators, inserters, etc)

Happy to try any other ideas

[kovarex]

Hello, we tested the savegame, and we found one bug (maybe unrelated) that crashed the game, but when we fixed it, it was working quite fine, so I'm moving this to resolved for next release.