Is there a way to deserialize a navmesh in async fashion?

[kerphelio]

Hi there,

I’m loading/streaming precreated navmeshes as I approach the area, and it’s working perfectly - except that I do get short hiccups/spikes/freezes when the navmeshes get deserialized, at least that’s how I understand what the Profiler is telling me. But as I understand DeserializeGraphsAdditive() is a synchronous, main-thread-only A* API call which seems to cause a visible frame spike when a navmesh graph loads into A*. Is there a better way to do this, maybe something that allows me to spread the process over a bunch of frames? I have plenty of time to do that, 5 to 10 secs, no problem, but the little stutters are quite jarring and I’d really like to get rid of them.

Thanks!

[tealtxgr]

@aron_granberg

Optimizing graph deserialization is a bit tricky since it’s very serial at the moment (everything reads from a file), and a large part of it is just allocations that parallelize badly in any case. I have some optimizations that I’ll include in the next update, but it’s not much.

To save and load recast graph chunks, I could instead recommend the method recastGraph.ToTileMeshes and recastGraph.ReplaceTiles, which will be available in the next update. In my testing it’s about twice as fast.

Or you can use the NavmeshPrefab component, which is already available and uses the same internal apis. It should load faster, and you’ll be able to load chunks on a tile-by-tile basis, instead of the whole graph at once.

This came up a bit ago, this was Aron’s response. So to answer your question directly, no not particularly, but I recommend taking a look at this post for some ideas.