navmesh agent path calculation throttling when using destination?

Maybe it's just a bug but I'm guessing it's throttling the max number of in progress paths it will calculate. But if so it's a ridiculously low number.

This happens when setting the agent via destination. State stays in pending for up to minutes at a time with around 500 agents. If I just calculate the path myself and then use SetPath, it's all good agent starts moving immediately.

 

Yes, there's a limit on NavMeshQueries per frame, and when you're dealing with 500 agents you will probably be way over that.
Are you recalculating the path for each agent manually, or are you calculating one path and then set that identical path for each agent?

 

I calculate for each agent. Guessing at one point they had some reason for throttling. At this point calculating paths is dirt cheap, crowd handling is where all the cpu time is.

 

Just increase NavMesh.pathfindingIterationsPerFrame if you think it throttles too early.