Memory Usage about marching-cubes-terrain HOT 5 CLOSED

I will take a look at this today!

from marching-cubes-terrain.

I tried the old version myself with render distance of 7, and the memory usage was about 6gb (not quite 10gb, but that is still a lot). I then did some changes and disposed the mesh data arrays after generation and the memory dropped to around 1.8gb with render distance of 7. Pushed these changes to the develop branch.

All testing was done using both Unity's profiler and Win10 task manager with a built version of the game (= not in editor)

from marching-cubes-terrain.

perfect! yea the editor profiler reports about 6gb of nativearray data. the rest most likely comes from the mesh renderer mesh data and editor things

from marching-cubes-terrain.

while the memory usage during runtime is much lower now at startup when all chunks are build it still spikes and runs out of memory. but that's for the chunk loading over time issue imo

from marching-cubes-terrain.

Yes, I will be implementing the async chunk loading within a few days maybe, that should help both memory usage and the lag spikes.

from marching-cubes-terrain.