Desync error (likely caused by layer sorting)
Starkku opened this issue · 0 comments
Description
There is a recurring desync error caused by Phobos, cause of which dates back to changes introduced between development builds 33 and 34.
Through testing this cause has been narrowed down (assuming these results have not been severely skewed by RNG) to having been introduced in either commit d89ea77 or 86c0c2b.
Based on the circumstances in testing as well as my other knowledge, I strongly suspect it is the layer sorting being the culprit, although the actual mechanism through which this leads to desyncs eludes me.
Whether or not #1070 is related is undetermined as of current.
Phobos Version
b34
Conditions to reproduce
No response
INI code
No response
Steps to reproduce
Due to the nature of the problem, exact reproduction steps are not available. During testing it has most often occured in busy multiplayer games with multiple human players, however.
Expected behaviour
There should not be any desync errors caused by Phobos, period.
Actual behaviour
There's a desync error that sometimes occurs in multiplayer games.
Additional context
No response
Checklist
- The issue happens on the latest official version of Phobos and wasn't fixed yet.
- I agree to elaborate the details if requested and provide thorough testing if the bugfix is implemented.
- I added a very descriptive title to this issue.
- I used the GitHub search and read the issue list to find a similar issue and didn't find it.
- I have attached as much information as possible (screenshots, gifs, videos, debug and exception logs, etc).