Graph Scanning Includes Tree Colliders Which are Filtered Out

Is pathfinding performance impacted by scans which include these planar surfaces found on trees?

Ideally, there would be an option to have the filter layer option not only create cuts, but prevent the associated colliders from being navigable. From my perspective this is strange behavior. The filter creates cuts – but then allows these same colliders to be navigable?

You can either use RecastNavmeshModifier or, if they’re all on the same layer, Per Layer Modifications in your graph settings. You’re using NavmeshCut for these?

Hey tealtxgr!

They are all on the same layer. I’m not specifying navmesh cuts – this is just what scan produces.

Hi

This has been fixed in the latest update. :slight_smile:

1 Like

Thanks for information