In my project I’m trying to calculate a path over a long distance through complex geometry. In some cases the path only partially completes when the path reaches ~30 corners. Is there a hidden cap to the amount of corners or distance when using NavMesh.CalculatePath()? I’m using version 5.4.1p4.
Yes, there is a limit of how many relevant polygons from the NavMesh can be tracked internally when searching for a path. The larger and more complex the NavMesh is, the higher the chance of hitting that limit and getting back a partial path as a result. On the other hand the size of the returned path is quite generous and it can accommodate a sufficient number of corners in most cases.