Repro steps:
Open blueprint book from toolbar, grab blueprint from inventory, try to place into the book anywhere, nothing happens & player char frozen, dropped after a few seconds "players machine could not keep up".
Tried removing a blueprint from the book, worked as expected. Adding it back to the book resulted in the same disconnect error.
Repeated experiment a few times with different books & different blueprints, had exact same results in every case: Dropped when trying to add a BP from inventory into an open book. [log: previous]
I rebooted my game, rejoined again, then asked the host to repeat the same actions. He had same results: When he added a BP to one of his books, I was dropped after a few seconds "server not responding". [log: current]
Logfiles & savegame attached.
[It is a friends world, we use a few mods, but none of those affect blueprints.]
[0.15.26] Desync when adding a blueprint to a book [MP]
- Killcreek2
- Long Handed Inserter
- Posts: 73
- Joined: Sat Dec 10, 2016 8:39 am
- Contact:
[0.15.26] Desync when adding a blueprint to a book [MP]
- Attachments
-
- factorio-current.log
- (205.74 KiB) Downloaded 78 times
-
- factorio-previous.log
- (95.3 KiB) Downloaded 77 times
"Functional simplicity, structural complexity." ~ Appleseed
Re: [0.15.26] Desync when adding a blueprint to a book [MP]
There is no desync in any of your logs.
If a desync did happen then please upload the desync report, see my signature.
If a desync did happen then please upload the desync report, see my signature.
- Killcreek2
- Long Handed Inserter
- Posts: 73
- Joined: Sat Dec 10, 2016 8:39 am
- Contact:
Re: [0.15.26] Desync when adding a blueprint to a book [MP]
Did you even read the repro steps, or just read the title & searched the logs?
There have been a few nearly identical reports, some marked by you as duplicates:
viewtopic.php?f=30&t=50408
viewtopic.php?f=47&t=50440
viewtopic.php?f=47&t=50419
viewtopic.php?f=47&t=50427
It does not have an actual desync report, as it is disconnecting due to a coding error, not due to a fault with the client/host pc.
Anyway, as that first linked thread indicates: "fixed for next version", you can move this from "pending" to where it should belong.
There have been a few nearly identical reports, some marked by you as duplicates:
viewtopic.php?f=30&t=50408
viewtopic.php?f=47&t=50440
viewtopic.php?f=47&t=50419
viewtopic.php?f=47&t=50427
It does not have an actual desync report, as it is disconnecting due to a coding error, not due to a fault with the client/host pc.
Anyway, as that first linked thread indicates: "fixed for next version", you can move this from "pending" to where it should belong.
"Functional simplicity, structural complexity." ~ Appleseed