Fix 2D debug navigation flickering with tile maps #96607
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
Both the tile map layers and the debug navigation canvas items did fight for the same z order causing a lot of flickering in certain situations.
smix8
added
bug
topic:navigation
cherrypick:4.3
akien-mga
approved these changes
Sep 5, 2024
|
Thanks! |
|
Cherry-picked for 4.3.1. |
akien-mga
removed
the
cherrypick:4.3
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.
Both the tile map layers and the debug navigation canvas items did fight for the same z order causing a lot of flickering in certain situations.
Before the debug rendering was changed to server use in #92372 this was kinda hidden due to node order. This change now sets the z index one less the navigation agent debug paths index so the paths can render on top of the navigation mesh debug.