Most crashes in VAM are now happening because their are to much vars to manage and they cause the death for VAMs already bad memory management the requirements are exploding the memory leaking becomes even worse it seems.
Not good how VARs are handled memory wise the current GC is also so bad no words for it after 3-4 scenes memory crash has become pretty unavoidable because the memory with 300 GB of VARS to manage is at it's total end already at load and it gets worse and worse every scene (load and destroy) cycle.
could be also that some plugins are so unstable handling memory and their own destruction but i doubt this but overall it's not a pleasant experience with so many VARS not just from the Performance Point of view but that overall is not so problematic as the growing memory usage and chaos handling just the 300 GB VARs pure existence the cache managing continuous in memory decompression surely is also a part of this exploding memory management problem now, aswell as those dupes and their useless indexing and overall existence.
If 3-4 Scenes doesn't survive stable loading/destroying after each other with 16 GB without going out of memory than something goes into the very wrong direction more unstable than DAZ Studio is not really a good thing.
Circumventing 1 issue with another is obviously going to push heavy on other resources if you not attack the culprit of the problem at it's core though if you have no real access to the core you are fucked.
Though this needs a closer look @ now it's a entire new situation to analyze i really hope 2.0 will get also more stable at the same time with such amount of data crunching and management.
johnwithlenon
remove .dat put into \Custom\Atom\Person\Hair
