• Hi Guest!

    Please be aware that we have released a critical security patch for VaM. We strongly recommend updating to version 1.22.0.7 using the VaM_Updater found in your installation folder.

    Details about the security patch can be found here.
DAMAR morphs

Morphs DAMAR morphs

These can not be used with paid content at all, hence the CC-BY-NC-ND license.
 
Hi Damarmau, sorry newbie question - do user need to keep previous versions of VAR's which contain morphs ? (like your package)

Or by other words - certain (old) looks have linked to certain versions of such VAR's ? Or they can use morph with the same name from last VAR version automatically ?
 
Hi Damarmau, sorry newbie question - do user need to keep previous versions of VAR's which contain morphs ? (like your package)

Or by other words - certain (old) looks have linked to certain versions of such VAR's ? Or they can use morph with the same name from last VAR version automatically ?
You just need the latest var. I don’t remove old versions of morphs when I add new ones so the latest morph var should work for all my looks old and new.

If you come across any issues of something not working from latest var just let me know.
 
You just need the latest var. I don’t remove old versions of morphs when I add new ones so the latest morph var should work for all my looks old and new.

If you come across any issues of something not working from latest var just let me know.
Thanks for quick reply. Sorry just for clarify - this rather was extensive question (for understanding VAM fundamental things), and mean not only your morphs VAR package, but in general. This question born from "many heap section" error, well you know about this problem i think. So, i plan to delete morph's related VAR's from different artist (old versions of one and the same morps ofcourse), but in the same time afraid to broke compatibility for some old looks. I understand that you can't be sure for other artists packages, but if theoretically assume they packed in such normal way that last version contain all previous morps, then there is no should be problem for old looks ? Do i right understand you
 
For my morphs and looks yes. For other creators I’m not sure as I think a lot just package the morphs in the look’s var and not as a separate morph var.

I haven’t run into the heap section error myself so am not familiar with what causes it.
 
For my morphs and looks yes. For other creators I’m not sure as I think a lot just package the morphs in the look’s var and not as a separate morph var.

I haven’t run into the heap section error myself so am not familiar with what causes it.
Doing a search on discord turned this up:

Post in thread 'Too many heap sections'
https://hub.virtamate.com/threads/too-many-heap-sections.38525/post-108657

So it looks like it is caused by too many morphs. I assume this will be more common in unmerged morphs which are possibly being duplicated in various vars especially by certain creators based on the solution.

If you are having this problem check to see if you don’t have a lot of universens vars or noheadnoleg ones.

If you have a massive folder of loose morphs (not inside vars) you can try copying that to a different location and clearing out the loose morphs in your vam install.
 
Yes thanks i already saw that thread (as well many others by that topic).

I haven’t run into the heap section error myself so am not familiar with what causes it.
Well this problem usually (just my observation) starts to often appear with 20k+ VAR's (1TB + of AddonPackages folder)

I remember when i had about 10k yet i maybe got this error just once.
But in last times this become for me really headache. I just load single look in empty scene, starts to adjusting morphs and get this error lol.
So i decide to dig into. Already delete a bunch of old\doubled morphs related stuff. Will see.
 
Last edited:
Back
Top Bottom