What is the intention behind NavigationData::bForceRebuildOnLoad=True?

[anonymous_user_3e0dac6e]

I have a level in which after some delay, a number of nav-relevant actors are spawned. I have dynamic nav mesh rebuilding enabled for my project. I was investigating why the nav mesh wasn’t being rebuilt when the actors were first spawned, but would rebuild correctly when they were moved, and have discovered that this appears to be the intended default behaviour.

	By default navigation will skip the first update after being successfully loaded
	 setting bForceRebuildOnLoad to false can override this behavior

What is the intention behind this behaviour? From my perspective, it appeared to be a bug. Why would you want the first requested update to be ignored, when this would likely lead to an invalid nav mesh? What’s the use-case?

Thanks,

[unit23]

Here is a related post

Optimizing Dynamic Navigation Mesh Generation

Mar 29, 2021.Knowledge Originally written by Jon L. Using a dynamic navigation mesh and generating navigation mesh at runtime can take a lot of CPU resources. Here is a list of tips and strategies that can limit that cost. Tips Use the highest CellHeight and CellSize possible (in Project Settings ->Navigation Settings) Those parameters are used to define the size of the voxels used to generate the navmesh. The bigger they are, the less voxels are needed and the faster the tile generation …