[kovarex][0.18.37] Desync problems with nested blueprints
-
- Burner Inserter
- Posts: 9
- Joined: Thu Mar 31, 2016 5:21 am
- Contact:
[kovarex][0.18.37] Desync problems with nested blueprints
After shuffling a few Blueprints into nested Books i stumbled upon a problem placing them. If the blueprints are placed via non-direct bp-item(bsp. rails->straight) then the game desyncs and the server places ghost of a completely different blueprint at that position, if the bp is placed after navigating directly to it in the book and taking it from there that problem does not occur.
Last edited by therhodanist on Wed Jul 29, 2020 5:11 pm, edited 1 time in total.
-
- Burner Inserter
- Posts: 9
- Joined: Thu Mar 31, 2016 5:21 am
- Contact:
Re: Desync problems with nested blueprints
To Clarify
if placed via the book, this happens after reconnecting, this is the bp the server placed
but if taken directly from the library the right ghosts are placed without desync
desync report(i think logs are included)
https://mega.nz/file/urRBiKyC#26Uc_DNes ... rPU3N13KzU
if placed via the book, this happens after reconnecting, this is the bp the server placed
but if taken directly from the library the right ghosts are placed without desync
desync report(i think logs are included)
https://mega.nz/file/urRBiKyC#26Uc_DNes ... rPU3N13KzU
Re: [kovarex][0.18.37] Desync problems with nested blueprints
I had to stretch every possible muscle including the ones that moves my eyes to find the cause of this desync and i found it.
When you return to MP server on which you have already been once, activeIndex in book from your shelf is not synced so if you happened to play other games in between and was scrolling your book, this desync will happen.
When you return to MP server on which you have already been once, activeIndex in book from your shelf is not synced so if you happened to play other games in between and was scrolling your book, this desync will happen.
Re: [kovarex][0.18.37] Desync problems with nested blueprints
Thanks for the report. Issue will be fixed in 0.18.39