mesh tile original data #38
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
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.
I noticed that in the 'recastnavigation' project, the original 'data' is retained in 'dtMeshTile', but it is not retained in 'go-detour'. In my project, I may need to keep this original 'data' so that I can conveniently remove or rebuild 'MeshTile' at any time. Currently, I am using this to do some dynamic culling of mesh tiles. Regarding 'm.saltBits', when my navmesh construction granularity is very fine and the mesh tile is relatively small, the value of 'm.saltBits' is 8. At this time, the check of 'if m.saltBits < 10' will fail, causing the navmesh to fail to load.