Change 2D navigation mesh baking to use floating point coordinates #89929
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
3 tasks
Replaces internal uses of Clipper2 integer structs to their floating point equivalents.
Scony
approved these changes
Apr 23, 2024
AThousandShips
approved these changes
Apr 23, 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.
Replaces internal uses of Clipper2 integer structs to their floating point equivalents.
Resolves #87138.
Note that the float structs are slower because they need to up- and downscale everything to an integer grid.
In turn this avoids baking problems caused by geometry layouts with sloppy float decimal points.