Since | 20.5 |
The IK/FK blend component sets up the necessary constraints and blends to do a local blend between an IK and FK chain.
Parameters ¶
name
The name that is appended to the IK/FK blend nodes in the setup. The name is not necessary when using segments, as the segment name is also added to the nodes to clearly identify the segment they belong to.
guidesource
The guide skeleton that is used as a reference when creating controls.
mapping
The mapping is used to specify the relationship between nodes. When the IK and FK nodes are created using the fktransform component, a mapping entry in the properties
dictionary attribute is added to the nodes. This mapping entry contains the name of the skeleton and the joint that was used to create the node, for example, "mapping:Guides.skel":"pelvis"
.
Settings ¶
An abstract control drives the blend value between the IK and FK.
abstractpos
The position of the abstract control. By default, the abstract control is placed in the middle of the joint chain.
abstractscale
The scale of the abstract control.
Driven ¶
segments
Segments are tags that separate each IK/FK blend. For example, *Leg
loops over L_Leg and R_Leg. Segment tags can be set up on the joints using an Attribute Adjust Array SOP.
By default, segments is empty and is run once.
iknodes
An APEX path pattern that specifies the IK nodes that are included in the IK/FK blend.
fk_prefix
The prefix of the new FK chain. When setting up the IK/FK blend, you don’t need to have FK nodes in the hierarchy. The IK/FK blend component creates an FK chain if one doesn’t already exist.
fk_suffix
The suffix of the new FK chain. When setting up the IK/FK blend, you don’t need to have FK nodes in the hierarchy. The IK/FK blend component creates an FK chain if one doesn’t already exist.
fknodes
An APEX path pattern that specifies the FK nodes to include in the IK/FK blend. This can be used if the FK nodes already exist in the rig hierarchy. The IK/FK blend component loops over the IK nodes and makes sure that the FK and IK hierarchies match using the mapping value.
Driver ¶
parent
The main driver of the abstract control. When empty, the abstract controls are not parented.
Tags ¶
See also |