Plugins + Scripts Expression Randomizer 2

[VamTimbo]

VamTimbo submitted a new resource:

Morph Randomizer 2 - New and improved

This is a re-write of the original Expression Randomizer - I did a re-write instead of an update to preserve settings and scenes people already created with the original plugin. This new version has been drastically re-designed - so I thought it best to start a new hub posting rather than update the existing. Special thanks to: Everlaster (coded the original plugin), Acid Bubbles (Some code I used is inspired by TimeLine), Hazmhox, Juno, and VamFantasy (all of them helped me debug...

Read more about this resource...

 

[bill_prime]

@VamTimbo
Awesome job! This looks great, I have to check it out.
Question: Does this version fix the issue with non-preload morph packs?
For example, when you load a scene/expression randomizer preset and have Preload Morphs option off for say some of the AshAuryn packs, those morphs don't get automatically loaded.

 

[JKLIKE]

@VamTimbo Excuse me

Why is it that when there are two different targetType entries in formulas, the morph cannot be read?

"formulas" : [
{
"targetType" : "RotationX",
"target" : "lowerJaw",
"multiplier" : "15.34057"
},
{
"targetType" : "OrientationX",
"target" : "lowerJaw",
"multiplier" : "-1.933971"
}
]

 

[VamTimbo]

@VamTimbo Excuse me

Why is it that when there are two different targetType entries in formulas, the morph cannot be read?

"formulas" : [
{
"targetType" : "RotationX",
"target" : "lowerJaw",
"multiplier" : "15.34057"
},
{
"targetType" : "OrientationX",
"target" : "lowerJaw",
"multiplier" : "-1.933971"
}
]

Can you provide a little more context? I’m not sure what I’m looking at here.

 

[JKLIKE]

Can you provide a little more context? I’m not sure what I’m looking at here.

Example: Editing Expressions in AshAuryn’s Expression Pack

Take AshAuryn’s Expression Pack as an example.
For the 2022 Worried expression, there are two files: a .vmb and a .vmi.

The .vmi file contains a formulas section where you can add or modify parameters to adjust expression details.

Example from AshAuryn.AshAuryn's_2022_Expression_Pack_3_Nauseous.2.var:
AA 2022 Worried.vmi
{
"id" : "AA 2022 Worried",
"displayName" : "AA 2022 Worried",
"group" : "AshAuryn",
"region" : "AshAuryn/Expressions/2022 Promo Packs",
"min" : "0",
"max" : "1",
"numDeltas" : "3900",
"isPoseControl" : "true",
"formulas" : [
{
"targetType" : "RotationX",
"target" : "lowerJaw",
"multiplier" : "1"
},
{
"targetType" : "RotationX",
"target" : "tongueBase",
"multiplier" : "0.5"
},
{
"targetType" : "RotationX",
"target" : "tongue01",
"multiplier" : "0.1"
}
]
}


As long as all the targetType values are the same (for example, all set to "RotationX"), the plugin can usually recognize them without any issues.

However, if there are mixed types (e.g. one is "RotationX" and another is "OrientationX"), the plugin will not recognize them.

Example of a problematic case:

{
"targetType" : "RotationX",
"target" : "tongueTip",
"multiplier" : "1"
},
{
"targetType" : "OrientationX",
"target" : "lowerJaw",
"multiplier" : "1"
}


When this happens, in the main UI Morphs, the expression will display with a red gear icon and the warning:
“Has bone morphs. Animation not recommended.”

That’s the behavior I’ve observed so far.