I got in my map a NavMeshBoundsVolume placed with the settings:
Static
No Generate Overlap Events
No Collision
RecastNavMesh-Default with:
Enable Drawing
No rebuild at RunTime
In the Project Settings → Navigation Mesh:
No Rebuild at Runtime
In the Project Settings → Navigation System:
All unchecked, only “Add Players to Generation Seeds” enabled
1º- Build the map with the navmesh…
2º- Play and replay in the editor and work fine.
3º- Save all and close all.
4º- Open the engine, open the map = NO NAVMESH
Notes:
The model of the ground are a static mesh placed in the map using a box collision created in the engine (Model editor).
All time the editor say NAVMESH NEEDS TO BE REBUILD.
I attempted to reproduce this in-house but so far I haven’t been able too. Is this only reproducible in your project or can you also repro it in a new project?
First of all, fail in all my maps of the project, all the maps have a sub-level (the same in all maps) with the light, fog & post process only.
When change between the levels, the closed level at re-open bump no navmesh. *When i compile the maps (build) don’t open the swarm or show nothing about compiling, but generate the navmesh.
No luck at the moment in new projects.
Now, i have created a new project and then in the default map add a navmesh volume with the size of 2000x2000x200.
Then go to the project settings and change in the in the Navigation Mesh → Uncheck the “Rebuild at Runtime” if is checked, then go to the Navigation System and uncheck all, only check the “Add Players to Generation Seeds”.
Now go to the editor preferences and to → Level Editor - Miscellaneous and uncheck Update BSP Automatically & Update Navigation Automatically.
Now in the map make a a build, save all, close all,then open the editor and open the project and the map = NO NAVMESH. (Or without close nothing, click in load map and load the same map).
Now you can change between the maps of the project and going to have the same problem all time.
I was able to reproduce this in 4.6.1. I found a report in our system for this same issue and it has now been fixed in our latest internal build. You should see this updated in a future release.
The only workaround that I know for this would be to to enable ‘Update Navigation Automatically’ again. When I reproduced it, this was the cause of the issue.