Companion Drones

by Klonan

Adds friends

Content
1 year, 9 months ago
1.1
75.5K
Blueprints

b Multiplayer Desync with Drones

2 years ago

Playing K2+SE on a dedicated server with Companion Drones.

The drones worked just fine until about hour 20 or so. Now, whenever we pull one out we see a laser attached to our character and immediately everyone on the server desyncs. Then you have an idling drone with 0 fuel, 0 storage. I haven't changed any of the mods since server was created. It occurs even when the drone has no "inventory" items.

The only solution we seem to find is for one player to stand far away from their bugged drone, and have the other player "Pick up" the bugged drone. It has an item attached to it called "Fuel DONT TOUCH" but it doesn't appear in anyone's inventory.

2 years ago
(updated 2 years ago)

My friend and I have a dedicated server and this is happening to us as well. It is only the 2 of us on our server. Although we are not using K2, we are using SE. If the server is up for more than 20hrs, this happens to me since I am not on Local LAN. The only fixes we have been able to do to get around this is to reboot the server, or have my friend pick it up on Local lan when I login after the 20/hr mark. Since my friend is on Local lan this does not happen to him, that we are aware of.

After the 20/hr mark when I am alone on the server, when I desync, I am able to login but cannot get close to the bad robot or try to pick it up. If I do... "desync. If I leave the bad robot alone and try to go elsewhere and play for a bit, I can play for about 5 minutes of moving around before it desync's again. If I login, dont move, and just sit there It wont boot me out. Not much fun to just sit there.

This issue is a bit annoying since I play more than my buddy does and I have to keep having to bug him to reboot the server so I can play in peace for a bit. I have desync reports for you and can give you anything else you may require to help fix this issue.

We do really enjoy this mod, and we enjoy watching these little guys go destroy the mobs for us. Makes it easier. :) Thank you for creating this mod and maintaining it!!

Will be doing more testing and please feel free to let me know if you would like the desync reports or if if you would need anything else to fix this. Thanks!!

UPDATE:
This is what i see in the desync report:

210586.230 Info ClientMultiplayerManager.cpp:610: UpdateTick(28884710) changing state from(ConnectedLoadingMap) to(TryingToCatchUp)
210587.525 Info ClientMultiplayerManager.cpp:610: UpdateTick(28885173) changing state from(TryingToCatchUp) to(WaitingForCommandToStartSendingTickClosures)
210587.625 Info ClientMultiplayerManager.cpp:610: UpdateTick(28885173) changing state from(WaitingForCommandToStartSendingTickClosures) to(InGame)
210587.693 Info GameActionHandler.cpp:5040: UpdateTick (28885177) processed PlayerJoinGame peerID(14) playerIndex(1) mode(connect)
210587.697 Info ConstructionManager.cpp:510: Checking 1 areas.
210597.993 Info ClientSynchronizer.cpp:327: Latency changed to (9)
210602.993 Info ClientSynchronizer.cpp:327: Latency changed to (8)
210627.992 Info ClientSynchronizer.cpp:327: Latency changed to (6)
210632.993 Info ClientSynchronizer.cpp:327: Latency changed to (4)
210682.992 Info ClientSynchronizer.cpp:327: Latency changed to (5)
210788.009 Info ClientSynchronizer.cpp:327: Latency changed to (12)
210808.009 Info ClientSynchronizer.cpp:327: Latency changed to (11)
210812.992 Info ClientSynchronizer.cpp:327: Latency changed to (5)
210938.009 Info ClientSynchronizer.cpp:327: Latency changed to (4)
210987.225 Info ClientSynchronizer.cpp:327: Latency changed to (5)
211084.292 Error GameActionHandler.cpp:3582: Multiplayer desynchronisation: crc test (heuristic) failed for crcTick(28914721) serverCRC(3321409361) localCRC(3614781868)
211084.292 Info ClientMultiplayerManager.cpp:610: UpdateTick(28914722) changing state from(InGame) to(DesyncedWaitingForMap)
211084.359 Info ClientMultiplayerManager.cpp:741: updateTick(28914723) received player (14) desynced
211124.576 Info ClientMultiplayerManager.cpp:747: Received mapReadyForDownload
211124.576 Info ClientMultiplayerManager.cpp:610: UpdateTick(28914723) changing state from(DesyncedWaitingForMap) to(DesyncedCatchingUpWithMapReadyForDownload)
211124.576 Error GameActionHandler.cpp:3582: Multiplayer desynchronisation: crc test (heuristic) failed for crcTick(28914722) serverCRC(2517307495) localCRC(3819866571)
211124.579 Error GameActionHandler.cpp:3582: Multiplayer desynchronisation: crc test (heuristic) failed for crcTick(28914723) serverCRC(3982083637) localCRC(3914402342)
211124.583 Error GameActionHandler.cpp:3582: Multiplayer desynchronisation: crc test (heuristic) failed for crcTick(28914724) serverCRC(580088958) localCRC(3660269142)
211124.592 Error GameActionHandler.cpp:3582: Multiplayer desynchronisation: crc test (heuristic) failed for crcTick(28914725) serverCRC(4284819821) localCRC(2028357929)
211124.609 Error GameActionHandler.cpp:3582: Multiplayer desynchronisation: crc test (heuristic) failed for crcTick(28914726) serverCRC(1697632082) localCRC(4138947836)
211124.630 Info ClientMultiplayerManager.cpp:610: UpdateTick(4294967295) changing state from(DesyncedCatchingUpWithMapReadyForDownload) to(DesyncedSavingLocalVariantOfMap)
211160.574 Downloading file C:\Users\mostw\AppData\Roaming\Factorio\temp\mp-download.zip (235027094 B, auxiliary 210 B, 467252 blocks)
211160.600 Info ClientMultiplayerManager.cpp:610: UpdateTick(4294967295) changing state from(DesyncedSavingLocalVariantOfMap) to(DesyncedDownloadingMap)
211185.926 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ServerToClientHeartbeat) received from IP ADDR:({xxx.xxx.xxx.xxx:34197}): heartbeat sequence number (18334633) outside latency window [18334693, 18335893)
211185.926 Info UnparsedNetworkMessage.cpp:102: Message data: 27 00 a9 c3 17 01

2 years ago

Running K2+SE. I was able to get around the desync issue by completely emptying out my inventory then placing new drones. Once the drones are placed, give them some coal and you can pick your inventory back up.

New response