High Level API Components for Runtime NavMesh Building

Перейти к файлу

Adrian T c2c7597cbf New branch that might require features only available starting with Unity 2017.2.		2017-05-31 16:02:10 +02:00
Assets	Make playmode tests available only in editor and standalone.	2017-05-11 22:31:05 +02:00
Documentation	Add missing spaces to # in md files.	2017-04-07 15:01:29 +02:00
ProjectSettings	Update the version file to match 5.6x	2017-04-07 14:52:34 +02:00
.gitignore	add ignore file	2016-11-16 13:24:28 +01:00
LICENSE	Bump year to match actual	2016-10-14 08:22:31 +02:00
README.md	New branch that might require features only available starting with Unity 2017.2.	2017-05-31 16:02:10 +02:00

README.md

⚠️ This branch might require features only available starting with Unity 2017.2.

Components for Runtime NavMesh Building

Here we introduce four components for the navigation system:

NavMeshSurface – for building and enabling a navmesh surface for one agent type.
NavMeshModifier – affects the navmesh generation of navmesh area types, based on the transform hierarchy.
NavMeshModifierVolume – affects the navmesh generation of navmesh area types, based on volume.
NavMeshLink – connects same or different navmesh surfaces for one agent type.

These components comprise the high level controls for building and using NavMeshes at runtime as well as edit time.

Documentation (draft)

https://docs.google.com/document/d/1usMrwMHTPNBFyT1hZRt-nQZzRDTciIQRVzmA7MQsFNw

How To Get Started

Download and install the latest release of Unity 5.6.

Clone or download this repository and open the project using the feature build. Alternatively, you can copy the contents of Assets/NavMeshComponents to an existing project.

Additional examples are available in the Assets/Examples folder. The examples are provided "as is". They are neither generic nor robust, but serve as inspiration.

Note: During the beta cycle features and API are subject to change. Back up existing projects before using. Make sure to backup an existing project before opening it with this build.

FAQ

Q: Can I bake navmesh at runtime?
A: yes

Q: Can I use navmesh'es for more than one agent size?
A: yes

Q: Can I put a navmesh in a prefab?
A: yes - with some limitations.

Q: How do i connect two navmesh surfaces?
A: Use the NavMeshLink to connect the two sides

Q: How do i query the navmesh for one specific size of agent?
A: Use the NavMeshQuery filter when querying the navmesh

Q: What's the deal with the 'DefaultExecutionOrder' attribute?
A: It gives a way of controlling the order of execution of scripts - specifically it allows us to build a navmesh before the (native) navmeshagent component is enabled.

Q: What's the use of the new delegate 'NavMesh.onPreUpdate'?
A: It allows you to hook in to controlling the navmesh data and links set up before the navigation update loop is called on the native side.

Q: Can I do moving NavMesh platforms?
A: No - new API is required for consistently moving platforms carrying agents.

Q: Is OffMeshLink now obsolete?
A: No - you can still use OffMeshLink - however you'll find that NavMeshLink is more flexible and have less overhead.

Q: What happened to HeightMesh and Auto Generated OffMeshLinks?
A: They're not supported in the new navmesh building feature. HeightMesh will be added at some point. Auto OffMeshLink generation will possibly be replaced with a solution that allows better control of placement.