Skip to content

Export Nodes SourceIOSfmFkChainNode

REDxEYE edited this page Nov 20, 2026 · 1 revision

SFM FK chain

Gives every bone along a bone path its own SFM rig handle, so the chain can be posed joint by joint (FK). Use it for spine extensions, tails, ears, capes and similar parts that are not two-bone IK limbs.

SFM FK chain node

Category: SFM rig. Node ID: SourceIOSfmFkChainNode.

Inputs

None.

Outputs

Socket Type Meaning
FK chain SFM FK chain socket Link to FK chains on an SFM IK rig node.

Properties

Property Meaning
Name Base of the control names (default tail): rig_<name>_0, rig_<name>_1, … in parent-to-child order, or rig_<name> when the chain is a single bone. Letters, digits and _ only.
Start bone First bone that gets a rig control.
End bone A descendant of the start bone that ends the chain. Every bone on the path from start to end gets a control. Blank creates one control, for the start bone only.
Control group SFM control group of the handles. Blank uses RigExtra.

The bone pickers search the armature of the rig node this chain is linked to.

Example workflow

  1. Add an FK chain, Name tail, Start bone tail_01, End bone tail_05.
  2. Link FK chain to the SFM IK rig's FK chains input.
  3. After export, SFM shows rig_tail_0 … rig_tail_4 in the group RigExtra.

Each handle is parented to the handle of the nearest ancestor bone that has one (or to rig_root if there is none).

Caveats

  • The end bone must be a descendant of the start bone ("must be a descendant of …").
  • FK chain names must be unique across FK chains and SFM finger nodes.
  • A bone can be driven by only one control: do not overlap with other FK chains, the pelvis/spine/neck chain, or IK limbs.
  • A handle cannot be created for a bone that hangs below an IK-solved joint (the middle or start bone of an IK chain); use a constraint on that bone instead.
  • All bones must exist in the model's armature, which is checked at export.

Back to Export Nodes.

Clone this wiki locally