• 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.

VaM 1.x Failures into the application

Threads regarding the original VaM 1.x

TheMontyBDSM

Member
Joined
Oct 5, 2024
Messages
74
Reactions
69
Hello, I'm writing to inform you about several problems I've encountered with the VaM application that are making it difficult (or even impossible) to create new content. It all started after the 1.22.0.12 security update, when one of the plugins I regularly used (Naturalis) began malfunctioning, forcing me quit the plugin from the equation. After that, the default saved poses started failing, and the physics model was frequently corrupted. Now I can't create any new .var files with the package builder because it won't let me, indicating that an exception occurred during creation. Has anyone else experienced these errors, or is it just me?
 
What do you mean by default saved pose failing? Also are you referring to the default T pose when you add a person atom or the default pose of the created scene.
You should add the error log message here so someone that can help and also you can let the creator know of this in the discussion page of the naturals plugin. The creator will see it also and will be able to look into it.
 
What do you mean by default saved pose failing? Also are you referring to the default T pose when you add a person atom or the default pose of the created scene.
You should add the error log message here so someone that can help and also you can let the creator know of this in the discussion page of the naturals plugin. The creator will see it also and will be able to look into it.
I'm referring to the default pose you can save instead of the default T-pose, giving you two default poses instead of one. You can have the T-pose (which is set and can't be changed) and the default pose that you, as the user, set. It's the second one that started malfunctioning.
 
I have encountered the weirdest total crashes of my VaM clients over the years and most often they came without any hint as to why. The latest one was my screenshots and all textures going poof. From what I understand and heard, naturalis isnt one of the plugins that should have gotten affected by the security update. (or the one prior, I guess it was .7?)

Create a fresh VaM client and copy over anything essential for the workflow you need - leave out the rest. You'll likely have a working VaM again that will have the added benefit of running with way better performance.
:)
 
Last edited:
I have encountered the weirdest total crashes of my VaM clients over the years and most often they came without any hint as to why. The latest one was my screenshots and all textures going poof. From what I understand and heard, naturalis isnt one of the plugins that should have gotten affected by the security update. (or the one prior, I guess it was .7?)

Create a fresh VaM client and copy over anything essential for the workflow you need - leave out the rest. You'll likely have a working VaM again that will have the added benefit of running with way better performance.
A new VaM client? You mean a new folder with the app installed in it, right? I did that, and almost all the problems disappeared. I also copied all my essential plugins and work files and moved them to the new folder. For now, VaM is working fine, but as I said, for now.
 
Back
Top Bottom