Dependent Parameters

With Poser you can set up meta-level parameters, called dependent parameters, which allow you to modify other parameters and morph targets with a single parameter dial. An example of this type of dependent parameter would be a full range of belly types, with the following values along the dependent parameter dial:

The Dependent Parameters editor can help you do this and more. Refer to for additional information about this feature.

• -1.0 underweight belly
• -0.5 sixpack belly
• 0.0 regular belly mesh
• 0.5 slightly protruding belly
• 1.0 large protruding belly
• 2.0 hanging beer belly

This range of belly types would incorporate various morph targets and parameter values at each of the key points along the dependent parameter dial. Thus, dependent parameters are far more powerful in the scope of modifications they can encompass than a single morph target or parameter dial.

The following sample code illustrates how to set up a dependent parameter. This code is an example of a targetGeom channel in a CR2 file. The resulting dependent parameter will appear as a morph target parameter dial named “bump3”.

targetGeom bump3

{

name bump3

   initValue 0

   hidden 0

   forceLimits 1

   min -100000

   max 100000

   trackingScale 0.02

   keys

   {

   static 0

   k 0 0

   }

   interpStyleLocked 0

   numbDeltas 261

   useBinaryMorph 1

   blendType 0

   valueOpKey

   Figure 1

   bone_1:1

Custom_Morph

   beginValueKeys

   valueKey 0.5 0

   valueKey 0.75 1

   valueKey 1 0

   endValueKeys

}

The end of this sample defines some interesting interactions with regards to the “bump3” dependent parameter. The “valueOpKey” keyword identifies a section that defines that this parameter can be driven by the Custom_Morph dial on the bone_1 actor of the specified figure. The “ValueKeys” section defines how exactly the “bump3” dependent parameter will be affected:

• If Custom_Morph equals 0.5, the value of bump3 will increase by 0.
• Once Custom_Morph reaches 0.75, the value of bump3 will increase by 1.
• By the time Custom_Morph equals 1, the value of bump3 will increase by 0 again.
• Values in between these points are determined by spline interpolation.

In the next example, we are looking at the rotateX parameter of an actor (in this case bone_2:1, which is not apparent from the code sample below). The resulting dependent parameter dial is called “xRotate”.

rotateX xRotate

{

name xrot

   initValue 0

   hidden 0

   forceLimits 0

   min -100000

   max 100000

   trackingScale 1

   keys

{

static 0

   k 0 0

}

interpStyleLocked 0

valueOpKey

   Figure 1

   bone_1:1

Custom_Morph

   beginValueKeys

   valueKey 0.25 0

   valueKey 0.75 45

   valueKey 1 0

   valueKey 1.25 -45

   valueKey 1.5 0

   endValueKeys

}

As in the previous example, the “valueOpKey” section defines that the Custom_Morph parameter dial on bone_1:1 of the specified figure can take control of this parameter. The “valueKey” value pairs add rotation in degrees of xRotate to certain values of the Custom_Morph parameter.