Make NavMeshSourceTag component support having different area types#161
Open
azb wants to merge 1 commit intoUnity-Technologies:masterfrom
Open
Conversation
|
I'm interrested by this but it seems like the area are then overlapping? |
|
Remember to remove in OnDisable or it will not retrace the path if it is disabled and enabled for some reason. |
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
3 participants
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.
Before NavMeshSourceTag didn't support having different area types, and so all nav mesh created using this component was marked as the "Walkable" area by default.
Now the NavMeshSourceTag has an inspector field for entering a different navigation area type. This allows for having different navigation areas which different types of agents can travel on (for example, boats on water, humans on land). The default area type will still be Walkable as it was before so upgrading to this new component won't change the behavior in existing projects.