Connect tile polygons from different layers#1
Open
elsid wants to merge 1 commit into
Open
Conversation
elsid
force-pushed
the
layered_navmesh
branch
7 times, most recently
from
f4f25c6 to
cd35c6e
Compare
If a polygon is located at the top or bottom of a tile there is no indication of border polygon added by recast functions used to generate rcPolyMeshDetail. It is possible to have another tile higher or lower with the same polygon if they were generated from the same geometry which means they should be connected. But since there is no indication this does not happen and paths crossing a tile boundary cannot be found. A spiral stairs is an example used in the added test to demonstrate the problem. To workaround this problem check the centroid proximity of polygons on connecting 2 tiles in NavMesh::addTile. Consider them connected if they are close enough. This has some performance impact but the alternative is to modify recast functions to add indication which is a more complicated solution.
This file contains hidden or 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
1 participant
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 recastnavigation#818.
If a polygon is located at the top or bottom of a tile there is no indication of border polygon added by recast functions used to generate rcPolyMeshDetail. It is possible to have another tile higher or lower with the same polygon if they were generated from the same geometry which means they should be connected. But since there is no indication this does not happen and paths crossing a tile boundary cannot be found. A spiral stairs is an example used in the added test demonstrate the problem.
To workaround this problem check the centroid proximity of polygons on connecting 2 tiles in NavMesh::addTile. Consider them connected if they are close enough. This has some performance impact but the alternative is to modify recast functions to add indication which is a more complicated solution.