Since the last few versions I've been observing severely degraded memory performance, excessive load times (especially when leaving the habitat, sometimes so bad that the entire OS starts choking, and other background processes also get interrupted/paused) and a lot of storage activity of paging/asset loading during playing.
For a while I kind of assumed that it's because the game is starting to outgrow my system with only 4 GB memory, but now I actually watched the memory use and it turned out it's not that. The game appears to be capped at using only 1.2 GB memory at all times while on the outside map (approx 850 MB while in the hab, and about 700 MB in the main menu), even when at least another 1 GB of memory is reported being still available, while at the same time it obviously has/needs more data to work with as inditaced by the very frequent loading/paging that didn't happen before.
I suspect that this memory cap forces the game process to page a lot more than it should be if it was allowed to use more memory (ideally as much as is reported by the OS being available), and that this excessive paging also interferes with the high volume asset loading during switching from the hab interior to the exterior map (basically the game likely ends up in a paging race condition where it immediately starts paging out assets it just loaded while trying to load more assets at the same time, completely filling the storage bandwidth and causing the aforementioned OS level choking).
If the working set / VM pool requested by the game process, or memory management in general is something that can be configured in the Unity dev tools, it would worth looking into why the game appears to be requesting less memory than it obviously needs.
As sad as it is, poor / inefficient memory management is the Achilles-heel of Unity, but I normally see Unity games trying to hog literally all the memory available in the system (and in many cases then running practically without any storage activity / paging), while Lacuna Passage does the opposite of that for some reason, denying itself of the amount of memory it would need to run smoothly.
Customer support service by UserEcho