I’m working on a procedural map and I’m having a hard time with the navmesh. I don’t know why I’m getting several issues. All the pieces are instances, and I checked the collision (it looks like everything is set up properly since it works with static meshes). I’d appreciate any help.
if you are dynamically generating the NavMesh probably at runtime, then when are you invoking the NavMesh generation. I have a feeling that you are hitting race conditions where your NavMesh is being generated midway through your chunk placement.
as to what is and is not an edge might be separately based on the rules set for the NavMesh, but if it is working with the meshes set in staticky known positions then it is probably still the race condition
Thanks for the reply. I’m not generating it at runtime yet, I’m still testing with a static navmesh. After further inspection, I noticed some strange behaviour related to navmesh tiling. If I increase the tile size, the problem becomes less noticeable, and I can clearly see that the issue occurs along the edges of each tile. It looks like the instance is only being calculated for one of the adjacent tiles when they share a border.
The issue is still not resolved, because apparently I can’t use a single monolithic tile, and I can’t figure out whether this is expected behaviour, a bug, or if I’m missing some configuration required for using instances with mesh tiling.
(post deleted by author)