bright dawn
dear devs,
i was just flying around in the void around the 0-BJI chunk and noticed that my pc began to slow to a crawl and i took a look at my task manager and shapes 2 was hogging memory might be because the game does not unload loaded chunks in that you cant see i think that might be why some crashes might occur but I'm just speculating but here is my evidence why i think there is a memory leak and the game should be optimized
greets,
jester101
half cliff
The game keeps all loaded chunks in memory to improve performance, plus going out that far you're long past the point where the game is breaking down due to floating point inaccuracy anyway
bright dawn
yeah but still its an issue like if the devs optimize the game in such a way that "ocupied" (chunks with buildables) chunks are loaded and the unoccupied chunks are unloaded it will cost way less ram and heighten preformance on other apps you are using right?
somber bridge
Thanks for the feedback. We are aware of the issue it causes to keep all loaded chunks in memory.
We have options and ways to try and optimize the memory usage and CPU usage. To some extend there are limitations to what the Unity Engine can do, but we are working hard on optimizing the performance.
Quickly said, its a known issue we still want to tackle in early access.