Astcit
Member
- Jan 14, 2021
- 444
- 855
Loading times are bad indeed, don't even know why the caching option exists, makes almost no difference since the engine struggles to do anything most of the time. There's a huge bottleneck in data read and write somewhere.
There's also a slight memory leak over time. Usually sessions hover around 8 to 10 gb of RAM use (OS resources included since swap and paging files seems to be used even if you have absurd amounts of free RAM), but after an hour or so, a gb starts to be added for no reason at all (no additional atoms or anything new added to the scene, etc...).
I blame Unity not the devs. KSP for example, which is another game heavy on physics and parts quantity, runs like shit too because of Unity's inherent bad resource management and use on any PC. Also suffers a lot from the same issues VAM has, like collision detection and efficient physics calculations.
There's also a slight memory leak over time. Usually sessions hover around 8 to 10 gb of RAM use (OS resources included since swap and paging files seems to be used even if you have absurd amounts of free RAM), but after an hour or so, a gb starts to be added for no reason at all (no additional atoms or anything new added to the scene, etc...).
I blame Unity not the devs. KSP for example, which is another game heavy on physics and parts quantity, runs like shit too because of Unity's inherent bad resource management and use on any PC. Also suffers a lot from the same issues VAM has, like collision detection and efficient physics calculations.