Log in
Register
  • Hi Guest!

    We are extremely excited to announce the release of our first Beta1.1 and the first release of our Public AddonKit!
    To participate in the Beta, a subscription to the Entertainer or Creator Tier is required. For access to the Public AddonKit you must be a Creator tier member. Once subscribed, download instructions can be found here.

    Click here for information and guides regarding the VaM2 beta. Join our Discord server for more announcements and community discussion about VaM2.
  • Hi Guest!

    VaM2 Resource Categories have now been added to the Hub! For information on posting VaM2 resources and details about VaM2 related changes to our Community Forums, please see our official announcement here.

Recent content by newmark42

  1. N

    Not A Bug VAM 800MB per-character-instance memory consumption easily fixable (1.x/2.x)

    Okay, sorry for the multi-posting, and thanks for your reply. I do hope the 2.x instance memory usage can be dramatically reduced. A DAZ mesh is about 80MB, so at some level it should be very practical to have a character instance use only about that much memory, textures aside. Which means...
  2. N

    Not A Bug VAM 800MB per-character-instance memory consumption easily fixable (1.x/2.x)

    And just for a quick idea of what my code looks like to apply a "partial morph" to the per-instance mesh, it's really really simple and tiny.. (you can ignore the "AffectedVertexAABB" code, that's computing the bounding box of every affected vertex of a morph, to setup a camera for automatic...
  3. N

    Not A Bug VAM 800MB per-character-instance memory consumption easily fixable (1.x/2.x)

    Here is an example screenshot of our Unity-based project, with 100 DAZ Genesis 3 figures spawned, all custom morphable and posable. Each taking about 80MB of memory. Of course VAM will not be able to do this many characters, because it also has softbody simulation and clothing sim, and lots of...
  4. N

    Not A Bug VAM 800MB per-character-instance memory consumption easily fixable (1.x/2.x)

    I'm a computer programmer, and I'm reaching out to help you fix a really easy and important problem in VAM. The 800MB per-character instance memory consumption problem. It's not textures, it's morph data, and it's trivial to fix. After fixing in my own DAZ/Unity project, character instances...
See more
Back
Top Bottom