Add get_bounds() function to NavigationMeshSourceGeometryData
#95137
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
smix8
added
enhancement
topic:navigation
cherrypick:4.3
smix8
force-pushed
the
source_geo_bounds
branch
from
fdccb61 to
4197879
Compare
AThousandShips
approved these changes
Aug 18, 2024
Adds get_bounds() function to NavigationMeshSourceGeometryData2D/3D to get a bounding box that covers all the geometry.
smix8
force-pushed
the
source_geo_bounds
branch
from
4197879 to
2e1f6b5
Compare
|
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.
Adds
get_bounds()function to NavigationMeshSourceGeometryData2D/3D to get a global bounding box Rect2/AABB that covers all the geometry.Knowing the bounding box of the source geometry is valuable information. Very important for certain systems like calculating the affected grid cells that require updates or the required bounding boxes for chunk navigation mesh baking.
Calculating the bounding box manually in scripts is very, very slow for larger geometry and also not that straight forward as the different arrays and objects stored inside source geometry data need to be converted to actual vertex positions.