A* Pathfinding Project

NavMeshCut produces too much garbage when PointOnEdgeException appears on debug log


#1

whenever the NavMeshCut results in PointOnEdgeException it will create a lot of garbage.
this isn’t much of a problem on modern PC, but on older gen (slow CPU & RAM) it will eat up a lot of the CPU time.

Note: the NavMeshCut only changes its position, not rotation and not a child of anything
the garbage is not cause by the debug logs, but because it keeps retrying on the same frame.

is it possible to change it from trying to retry on the same frame, to spread it across different frames?

block%20nav%20cut%20settings debug%20logs