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?

Quote:Is the size of world fixed now?

why? nothing has changed in world size

not yet ..

my computer

---

map of our have 4096 * 4096

world info

Area Size: 128
Heightmap Resolution: 128
Path Resolution: 32

My english sorry

cpu : AMD Phenom™ 2 X4 955 Processor 3.20 GHz
Ram: 4.00GB

thank you, I am investigating this

could you also attach a screen from Windows Task Manager at the moment of Editor memory exit, so I could see the total memory usage?

does the "4096 * 4096" mean number of Areas (16 million areas), or meters (4 kilometers x 4 kilometers) ?

i mean (4 kilometers x 4 kilometers) and many object.

---

this... and always same message .. other computer too.

thank you, can you attach the screen from the "processes" tab?

What is your OS? Win7? 32-bit or 64-bit?

now Win xp but company is Win7

---

and now screenshot is not have object. Only terrain.

---

My os 32bit

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

new sdk is available now through autoupdate (7z archive will be available in 18 minutes)
please let me know if the issue is gone.

thank you

now not memory exit

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

please wait for next SDK, configuring path settings will be avaiable in the editor (path mode)

Did detour crowd ever get implemented?

Thanks

No, sorry

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?

Thanks

ineisis doesn't use pathfinding

navmesh of Game::Area needs to be regenerated