Class RecastMeshObj Extends VersionedMonoBehaviour

Bounds GetBounds ()

Bounds completely enclosing the mesh for this object.

Collider GetCollider ()

MeshFilter GetMeshFilter ()

void GetAllInBounds (

List<RecastMeshObj>	buffer
Bounds	bounds

)

Fills the buffer with all RecastMeshObjs which intersect the specified bounds.

int area

Voxel area for mesh.

This area (not to be confused with pathfinding areas, this is only used when rasterizing meshes for the recast graph) field can be used to explicitly insert edges in the navmesh geometry or to make some parts of the mesh unwalkable.

When rasterizing the world and two objects with different surface id values are adjacent to each other, a split in the navmesh geometry will be added between them, characters will still be able to walk between them, but this can be useful when working with navmesh updates.

Navmesh updates which recalculate a whole tile (updatePhysics=True) are very slow So if there are special places which you know are going to be updated quite often, for example at a door opening (opened/closed door) you can use surface IDs to create splits on the navmesh for easier updating using normal graph updates (updatePhysics=False). See the below video for more information.

Bounds bounds

bool dynamic = true

Check if the object will move.

Recalculation of bounding box trees is expensive so if this is true, the object will simply be stored in an array. Easier to move, but slower lookup, so use wisely. If you for some reason want to move it, but don't want it dynamic (maybe you will only move it veery seldom and have lots of similar objects so they would add overhead by being dynamic). You can enable and disable the component every time you move it. Disabling it will remove it from the bounding box tree and enabling it will add it to the bounding box tree again.

The object should never move unless being dynamic or disabling/enabling it as described above.

Mode mode = Mode.WalkableSurface

Surface rasterization mode.

bool solid = false

If true then the mesh will be treated as solid and its interior will be unwalkable.

The unwalkable region will be the minimum to maximum y coordinate in each cell.

If you enable this on a mesh that is actually hollow then the hollow region will also be treated as unwalkable.

int surfaceID = 1

Voxel area for mesh.

This area (not to be confused with pathfinding areas, this is only used when rasterizing meshes for the recast graph) field can be used to explicitly insert edges in the navmesh geometry or to make some parts of the mesh unwalkable.

When rasterizing the world and two objects with different surface id values are adjacent to each other, a split in the navmesh geometry will be added between them, characters will still be able to walk between them, but this can be useful when working with navmesh updates.

Navmesh updates which recalculate a whole tile (updatePhysics=True) are very slow So if there are special places which you know are going to be updated quite often, for example at a door opening (opened/closed door) you can use surface IDs to create splits on the navmesh for easier updating using normal graph updates (updatePhysics=False). See the below video for more information.

When mode is set to Mode.WalkableSurfaceWithTag then this value will be interpreted as a pathfinding tag. See Working with tags.

Mode

bool _dynamic

void Awake ()

List<RecastMeshObj> dynamicMeshObjs = new List<RecastMeshObj>()

Dynamic objects are stored in a list since it is costly to update the tree every time they move.

void OnDisable ()

void OnEnable ()

int OnUpgradeSerializedData (

int	version
bool	unityThread

)

Handle serialization backwards compatibility.

void RecalculateBounds ()

Recalculates the internally stored bounds of the object.

void Register ()

bool registered

void Reset ()

Handle serialization backwards compatibility.

RecastBBTree tree = new RecastBBTree()

Static objects are stored in a tree for fast bounds lookups.