Hi there, I have a project with a terrain of 18km x 18km (rather large) and performance is fine once in game, however I’m starting to put together some AI and upon adding my navigation mesh (approximately 160,000 instructions) my PIE is taking 5+ minutes to start. I’ve looked around and found that other’s have solved this problem be disabling auto-calculate navigation and auto-compiling of blueprints so I’ve gone ahead and done that to no avail. Could this be due to the system being bogged down upon run time or is this a problem related to the size of my terrain (and therefore my navigation bounds being extremely massive)?
1 Like
I’d also like to clarify, before adding the navigation mesh, PIE would only take 2-3 seconds even with the large terrain so I’m 95% certain this is nav mesh related?
18km x 18km is a very huge area for the NavMesh to render
You might want to slice up your level into chunks and then use level streaming to load each one of them, so that it’s easier on your engine.
Also, you can take a look at this website as a reference on how Unreal deals with it’s NavMesh generation (Unreal uses A* for their path finding algorithm)
https://qiao.github.io/PathFinding.js/visual/
Use the Euclidean heuristic in the A* section and then try to put the green and red cube at the edge. See how long it takes to generate
Look into dynamic navmesh generation, specifically ‘Navigation invoker’.
Basically with such a large terrain, you might be better served dynamically generating the navmesh at runtime where it’s needed.
1 Like