GC due to PathNNConstraint.Walkable returning a new() PathNNConstraint every time its called

Just want to chime in and say that I would also like a way to opt-in to avoid these allocations. I posted about this a while ago: Allocations when calling AIBase.SearchPath? (5.0.5 Pro)

The constant allocations have been one limiting factor for me in the past when trying to significantly ramp up the number of pathfinding agents I have active at any given time. It’d be really nice to eliminate it.

1 Like