Hi, this is probably due to compression of PathMesh during saving (LZMA is used, which uses lots of memory for compressing, on each work thread separately).
You can try increasing "virtual memory" in windows settings (to allow for more RAM, taken from HDD).
What kind of CPU do you have? I'm interested in number of cores/hardware threads.
How many RAM do you have?
thank you, I've decreased the compression level for PathMesh to LZMA 4 (from 5) which will have 24MB usage (from 160MB)
I will upload the change in few minutes
Hello.. I know this is a really stupid question but for some reason I'm not able to make PathSettings::cellSize work.. can someone put an example here how to use it correctly?
Thanks
Regarding path Obstacles, you say that the navmesh has to be generated after each obstacle. Is this the whole navmesh or just the polygons that the obstacle falls in.
How does the current navmesh system work eg: in ineisis when you place a block, is this regenerating the navmesh?