The name of the character whose skeleton to extract (if this node’s input is an animation scene). Leave this blank if this node’s input is a character (if the rig tree view shows only character elements and no .char folders).

The rig in the character folder structure that contains the animation to retrieve.

The skeleton to retrieve from the character folder structure.

An APEX path pattern that defines a group of controls to extract as joints. By default, no controls are extracted.

When turned on, the bind skeleton of the character is used as part of the output skeleton. This is usually helpful because the skeleton hierarchy is more suitable for motion processing like retargeting than the control hierarchy.

When turned on, the extracted controls are parented to joints with the specified mapping property instead of using the control hierarchy. The mapping property is stored on the transform controls of the rig. This is useful because controls like IK controls can then naturally follow any motion applied to the bind skeleton.

When turned on, the abstract control values are stored as separate detail attributes following the attribute input style of FBX animations for blendshape values. When turned off, all the abstract values are collectively stored in a detail dictionary attribute called parms.