Fix avoidance dirty flag regression #100105
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The dirty flag can also still be set by some legacy functions triggered by the agents and obstacles.
adamscott
approved these changes
Dec 6, 2024
clayjohn
approved these changes
Dec 6, 2024
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #100085
The dirty flag can also still be set by some legacy functions triggered by the agents and obstacles.
So what happened is that those would set the dirty flag to
trueat random moments expecting that the next sync would pick it up at some point. Meanwhile the actual agent or obstacle sync queue was empty turning it back tofalse, and without the dirty sync the arrays for the avoidance would be broken causing the crash.