@rcdarcey Looking at those screenshots I’d have to agree with you, everything looks fine and the voxel size actually looks small enough to even increase it further without impact.
Your last screenshot tells me that the voxels we care about are not even considered as valid neighbors so they never even reach the CanNavigate test!
This could be a bug in the function ADonNavigationManager::FindOrSetupNeighborsForVolume that I haven’t yet encountered myself. Two quick brute-force checks I can think of:-
- Disable partial-caching of neighbors by commenting out the entire if (NavGraphCache.Contains(Volume)) block
- Inside AppendImplictDOFNeighborsForVolume try removing all the CanNavigate checks for the X, Y and Z blocks. Those checks are actually needed, but bypassing them will help us narrow down the root cause.
Thanks for reporting these issues, it will make life easier for new users trying to onboard the plugin.
Thanks Bruno! Incidentally I’ll need your Save plugin next month so I look forward to checking that out soon.