Class NavmeshUpdates

float updateInterval

How often to check if an update needs to be done (real seconds between checks).

For worlds with a very large number of NavmeshCut objects, it might be bad for performance to do this check every frame. If you think this is a performance penalty, increase this number to check less often.

If negative, no updates will be done. They must be manually triggered using ForceUpdate.

For almost all games, this can be kept at 0. If you are smoothly moving navmesh cuts around, however, you may want to increase this a bit, to avoid triggering a navmesh update every frame.

An update not only has the cost associated with the update directly, but also the cost of recalculating the path for any agents that are using the affected part of the navmesh.

// Check every frame (the default)
AstarPath.active.navmeshUpdates.updateInterval = 0;

// Check every 0.1 seconds
AstarPath.active.navmeshUpdates.updateInterval = 0.1f;

// Never check for changes
AstarPath.active.navmeshUpdates.updateInterval = -1;
// You will have to schedule updates manually using
AstarPath.active.navmeshUpdates.ForceUpdate();
You can also find this in the AstarPath inspector under Settings.

AstarPath astar

float lastUpdateTime = float.NegativeInfinity

Last time navmesh cuts were applied.

List<NavmeshUpdateSettings> listeners = new List<NavmeshUpdateSettings>()