Guides Preset Definitions

[JayJayWon]

JayJayWon submitted a new resource:

Preset Definitions - A summary of the main differences between Presets, Looks and Poses

WIP

	Look (Legacy)	Pose (Legacy)	Preset (Legacy)	General Preset	App Preset	Clothing Preset	Pose Preset	Glute Preset	Breast Preset	Skin Preset	Morph Preset	Hair Preset
Control Node Position

...

Read more about this resource...

 

[JayJayWon]

JayJayWon updated Preset Definitions with a new update entry:

Issued v1

Completed a first cut of this guide. I believe this is comprehensive and accurate, but welcome people to review and feedback!
Thanks

Read the rest of this update entry...

 

[kemenate]

Awesome!
For Skin Preset it's more precisely the settings from those tabs:

• Skin Select, Skin Materials 1&2, Skin Textures (Decals and custom Textures)
• Tongue Materials & Teeth Materials & Mouth Materials + their custom textures
• It also saves some values that are not accessible in the Skin UI like: Render queue, Offset & Scale for custom textures. But idk if they actually work

So, to note: Skin Preset does NOT save any eye setting and eyelashes. You have to use appearance presets for this.

 

[JayJayWon]

Awesome!
For Skin Preset it's more precisely the settings from those tabs:

• Skin Select, Skin Materials 1&2, Skin Textures (Decals and custom Textures)
• Tongue Materials & Teeth Materials & Mouth Materials + their custom textures
• It also saves some values that are not accessible in the Skin UI like: Render queue, Offset & Scale for custom textures. But idk if they actually work

So, to note: Skin Preset does NOT save any eye setting and eyelashes. You have to use appearance presets for this.

Interesting - thanks. I'll look to incorporate this.

 

[JayJayWon]

JayJayWon updated Preset Definitions with a new update entry:

v2 - Skin update

Refined Skin to show that Eyes and eyelash materials and textures are not included in a skin preset.
Thanks to @kemenate

Read the rest of this update entry...

 

[Deleted member 1503]

Thank you. I'm now less confused then I was before.

 

[Spacedog]

Nice guide!

There is one bit missing, Preset (Legacy) will also save Scene Animation for that atom.

 

[JayJayWon]

Nice guide!

There is one bit missing, Preset (Legacy) will also save Scene Animation for that atom.

Ok thanks - do you know that its definitely not included in Legacy Pose and Legacy Look?

 

[Spacedog]

Ok thanks - do you know that its definitely not included in Legacy Pose and Legacy Look?

Good question! I just checked and Legacy Pose also saves Scene Animation, I know for sure Legacy Look doesn't though.

 

[JayJayWon]

JayJayWon updated Preset Definitions with a new update entry:

Added Scene Animation to Legacy Presets

Thanks to @Spacedog for pointing out the Atom recording for Scene Animations is also stored in Legacy Presets

Read the rest of this update entry...

 

[JayJayWon]

JayJayWon updated Preset Definitions with a new update entry:

Update to reflect VAM v1.20 changes

In VAM version 1.20, a few changes were made to the presets system:

• Plugin Presets were introduced
• Node Presets now have the option to store bone positions

Read the rest of this update entry...

 

[CuteSvetlana]

Hi JayJay,
Can we have it in PDF format too, please?
Thanks a lot

 

[JayJayWon]

Hi JayJay,
Can we have it in PDF format too, please?
Thanks a lot

Not easily - the table is built using the native VAMHub editor - so I am not aware of anyway to export it to PDF

 

[VamBam]

really helpful! Saves a lot of time. I remember an example that i was so confused one time that my handposes wern't saving in my pose presets while in the (old) version; save pose (legacy) they were. I thought it was a bug or something.
Now I can just look it up, if it supposed to work or not. Thanks!

 

[CycloneRed]

Just to be sure, this table depicts what is saved in the preset?

 

[JayJayWon]

Just to be sure, this table depicts what is saved in the preset?

That's correct

 

[an3k]

Just a quick fyi: Since VaM 1.20.1.5 Pose Morphs can be stored in a Pose Preset.

 

[JayJayWon]

JayJayWon updated Preset Definitions with a new update entry:

Animation & Pose Presets

A couple for refinements:

• Added Animation Presets (introduced in 1.20.77)
• Refined Pose Presets to reflect an option to include Pose Morphs. Introduced since 1.20.1.5 (thanks to @an3k for pointing that out)

Read the rest of this update entry...

 

[JayJayWon]

Just a quick fyi: Since VaM 1.20.1.5 Pose Morphs can be stored in a Pose Preset.

Thanks, I've updated accordingly.

 

[zzzat16h]

Hello, I would like to ask some questions.The preset poses cannot save finger poses without morphs.I used the leap motion and the json parameters of the timeline.However, saving the preset poses for the fingers is ineffective.Will the preset poses support saving finger deformations with remote control and json parameters in the future?If possible, it would be much easier to achieve finger deformations within the poses.The general preset can save the json parameters of the fingers, but it also saves unnecessary things such as appearance, clothing,hair, etc. The result is not very satisfactory.

 

[JayJayWon]

Hello, I would like to ask some questions.The preset poses cannot save finger poses without morphs.I used the leap motion and the json parameters of the timeline.However, saving the preset poses for the fingers is ineffective.Will the preset poses support saving finger deformations with remote control and json parameters in the future?If possible, it would be much easier to achieve finger deformations within the poses.The general preset can save the json parameters of the fingers, but it also saves unnecessary things such as appearance, clothing,hair, etc. The result is not very satisfactory.

This page just documents how it currently works. My understanding is there will be no further releases of VAM 1.x before VAM2 - so what you suggest will never be implemented in VAM1. I’d suggest waiting to see how VAM 2 evolves.

 

[zzzat16h]

This page just documents how it currently works. My understanding is there will be no further releases of VAM 1.x before VAM2 - so what you suggest will never be implemented in VAM1. I’d suggest waiting to see how VAM 2 evolves.

Thank you very much for your patient response. Your plugins is very useful and I have been using them all the time.

 

[everlaster]

The collision triggers in the Jaw Physics & Triggers tab save with the General Preset's Pose checkbox. This would be good to mention in the guide, currently "Collision Triggers" is blank in the General Preset column.

 

[JayJayWon]

The collision triggers in the Jaw Physics & Triggers tab save with the General Preset's Pose checkbox. This would be good to mention in the guide, currently "Collision Triggers" is blank in the General Preset column.

Updated accordingly. Thanks

 

[everlaster]

Hi Jay, I think the Plugins and Plugin parameters rows are incorrect for General Preset column. Currently it says

This implies that Plugins always save with a general preset regardless of which of Pose, Physical and Appearance are checked, and that no plugin parameters are saved unless Appearance is checked.

In my testing, Plugins only save if App is checked. In other words, this is when the preset file contains a JSON object with the id PluginManager and an object containing the plugin file references. This is what controls which plugins are loaded on the atom, but not what their parameters are. So it should say "App" on the Plugins row.

As for plugin parameters, it seems that plugin parameters store in a general preset regardless of which of Pose, Physics and Appearance are checked. If Appearance is not checked, the plugins themselves (i,.e. references to the loaded plugin file paths) are not stored, but their parameters are still stored. Thus, it should have the checkmark on the Plugin Parameters row rather than the Plugins row.

Which parameters get saved with which checkboxes also seem to follow the storeType rules, like with legacy preset types. For example if a parameter's storeType is Full, and you haven't selected all three checkboxes, that parameter will not save.