The order of the bezier curve to build from the CVs. Defaults to 2 (linear beizer curve).

The first segment of a bezier curve consumes an order number of CVs (control vertices) for its construction. If the number of CVs is greater than the curve order, additional curve segments are created. Each additional curve segment requires an additional (order - 1) CVs, since it will share its first CV with the previous curve segment. This relationship can be expressed by the equation number of cvs % (order-1) == 1.

Order 3 and 4 curves are popular choices since they balance the smoothness and flexibility of quadratic and cubic polynomial curves, while simultaneously preserving locality that changes to a CV’s position have on the shape of a curve.

The direction down the length of the chain. By default, it is set to the -Z axis.

When turned on, constrains the orientation of the driven root to the controls. When turned off, the spline solver determines the orientation of the root.

When turned on, constrains the orientation of the driven tip to the controls. When turned off, the spline solver determines the orientation of the tip.

Segments are tags that separate each spline chain. These segment tags can be set up on the joints using an Attribute Adjust Array SOP.

By default, the segments parameter is empty, so the spline component is run once.

The TransformObject nodes to drive. You can specify the individual joints, for example, spine_01, spine_02, spine_03, or a tag that exists on the TransformObject nodes, for example, %tag(spline).

It is good practice to also specify the bind tags that are set up by default on the fktransform component’s tags parameter. The fktransform component is normally the first component that is used to start building a rig. Including the bind tag helps to ensure that you don’t include other controls that might have inherited, for example, the spline tag. So in this case, you can set driven to %tag(bind) & %tag(spline).

The root of the spline. When using segments, you can use the segment name plus the tag, for example, %tag(splineroot) & %tag({segment}). The {segment} string is used to find the segment names.

The tip of the spline. This parameter accepts APEX path patterns, so you can specify tags in this field.

When turned on, the drivers, resample, prefix, and suffix parameters are available for creating a custom spline setup.

The name of the root control.

The name of the root tangent CV (control vertex).

The name of the tip tangent CV.

The name of the tip control.

When custom is turned on, these are the drivers for the custom spline setup. The controls are created based on the drivers. This parameter accepts APEX path patterns, so you can specify tags in this field.

When custom is turned on, controls are deleted by skipping the controls using this value.

When custom is turned on, this is the prefix for the control names in a custom spline setup.

When custom is turned on, this is the suffix for the control names in a custom spline setup.

The parent of the root. If left empty, the root is parented to root's parent. If you are setting up multiple splines you can leave this field empty. However, you can set parent tags on the guide skeleton, and use the parent tag plus the segment tag to get the correct parent for each segment.

This parameter accepts APEX path patterns, so you can specify tags in this field.

The parent of the tip. This parameter accepts APEX path patterns, so you can specify tags in this field.

The parent of the CVs. This parameter accepts APEX path patterns, so you can specify tags in this field.

The tags that are added on all the nodes created by this spline component.

The scale inheritance for the controls.

The shape of the controls. It can be set to any of the built-in APEX control shapes.

The scale of the control shapes. To inherit the shape scale from the guide skeleton, set this value to (0, 0, 0).

The color of the control shapes. To inherit the shape color from the guide skeleton, set this value to (0, 0, 0).