I am getting the following error when using world composition and Data Gathering Mode for navigation set to Lazy while using nav invokers.
I have tried to copy 1:1 the DefaultEngine settings from the Kite demo but am still getting crashes when opening a level with terrain and a nav bounds volume.
EDIT: Tried using Fixed Pool Size of 1024-4096 and am still getting crashes. HOWEVER, If I set Lazy to Instant and then back again, editor won’t crash until I close and restart it.
What’s your RecastNavMesh.MaxSimultaneousTileGenerationJobsCount? I never got around to making lazy geometry gathering to work with MaxSimultaneousTileGenerationJobsCount > 1.
Navmesh generation is done off the game thread, MaxSimultaneousTileGenerationJobsCount just specifies how many jobs we allow. This shouldn’t have noticeable influence on the game thread, unless you have really big tiles with a lot of geometry in them, and even them it would cache the gather geometry and following updates should be seamless.
Having multiple invokers close to each other doesn’t impact navmesh generation, the invokers are processed beforehand to figure out which tiles need regeneration and only those get requested.
Have you tried using stat navigation to see what’s going on? Or better yet, using UE4 profiling tools?
I had crashes as well, I’m assuming you are using Dynamic nav mesh? If so then here are my setting. I just have a dynamic nav invoker on my AI and everything is AOK.
You’re correct, I had to adjust my tile size and dirty areas update frequency. I did use the profiling tools and it led me to the navigation system. I have it working very well now within PIE. However when I launch I am now getting this error -