Been iterating frequently on a large, modular map design and running into some annoyances with NavMesh regeneration. Not entirely sure if I’m seeing a bug or intended design (although a little annoying if so).
The scenario is: large map, broken into multiple sub-levels (Persistant contains navMesh) for gameplay elements, landscape, buildings, FX etc. Map is primarily built out of the same set of staticmeshes, kit-bashed together as buildings.
The problem: whenever we iterate on the building meshes collision externally and reimport or change their NavArea class the NavMesh does not automatically regenerate. If we force a regeneration using the console command RebuildNavigation, it does rebuild but does not take into account the changes in collision or NavArea settings.
The only sure fire way we’ve found to update successfully that takes into account the changes is to either: wiggle the buildings or wiggle the NavMesh.
Is there a suggested way to force rebuild navigation that does take into account changes in import collision or NavArea, other than wiggling meshes/volumes in the scene?
(Focusing on the NavArea changes as they are most frequent and annoying).
New Map, add nav mesh bounds volume to cover a biggish area.
Create new sublevel for geometry.
Throw a static mesh into the project (or use an existing one) - make sure it has collision.
Add a bunch of these meshes to the scene (specifically in the geometry sublevel), nav should generate around them.
Open that static mesh and in the Static Mesh Editor, scroll right down to the Navigation section and change AreaClass from None to Null, save the asset.
Navigation does not regenerate (issue one)
Try RebuildNavigation console command, still doesn’t take the AreaClass change into consideration (issue two)
Move/Wiggle all the changed static meshes in the scene, or the NavMeshBoundsVolume (Now imagine a team member has either of these checked out - issue three).
We’ve recently made a switch to a new bug reporting method using a more structured form. Please visit the link below for more details and report the issue using the new Bug Submission Form. Feel free to continue to use this thread for community discussion around the issue.