I am not sure if this is a bug or intended feature on the WP-NavMesh, since it still marked as Experimental.
So, I have big world that being setup using World Partition, and obviously I need NavMesh for the enemy AI. Currently, the NavMesh Runtime Generation is set to STATIC, and I already make sure all the settings on each worls is correct.
However, am seeing a memory allocation of 100x the actual NavMesh, everytime I open a level (e.g., there is 3.4GB allocation, while the actual navmesh is only 39MB). The memory allocation is freed on the next 1-3mins by auto GC (manually calling CollectGC using blueprint doesn’t seem to do anything).
I tried to debug it using visual studio and Unreal Insight, and I just can’t believe NavMeshRecast actually allocate that HUGE MEMORY! why do this need 3.4GB of memory?? that doesn’t make any sense.
maybe anyone know about this and want to share? This additional 3.4GB on every load map is ridicolous! Am targetting player with memory below 12GB (the initial plan was 8GB, but the spike on load is not something I can control)