Skip to content

Components ​

The Framework applies the Addon's components when it builds the avatar. This reference is for inspecting or customizing an Addon; normal installation uses the Installer.

This is Salt's hierarchy after installation. Select a component beside an object to jump to its description.

Hierarchy
All
Avatars
Salt
Armature
Body
Kemono_Ear
Face Tracking
Mouth TrackingMerge MotionBlend Set
Mouth Ear MotionForward Parameters
Face Tracking MeshesComponent Property Overrides
Modular Avatar components such as Menu Installer and Parameters are omitted.

Back up before editing

An upgrade can replace values edited directly in an Addon prefab. Keep a record of any settings you want to carry forward.

Face Tracking Settings ​

In the supplied prefab, expand Face Tracking under the avatar and select Face Tracking Settings to adjust the eye, mouth and Reset options in the Inspector.

AdjustmentInspector setting
Eye tracking strengthEye Weight. Preview the eyes to compare weights.
How far the jaw dropsJaw Strength.
How much of a custom face shape remains during movementAdjust the relevant Reset group. For example, preview closed eyes to correct eyelid clipping. Groups vary by Addon.

VRC Face Tracking Installer ​

Adds native VRChat face tracking settings to the VRC Avatar Descriptor. The component on the Addon prefab records:

  • Meshes used for tracking
  • Features to enable, such as gaze, eyelids and visemes
  • Blendshape Sets and Parameter Behaviors to add

The Framework merges these into the Descriptor at build time.

Opening the Installer

This component runs during the build. To install an Addon, open TriturboFT › Face Tracking Installer in Unity.

Face Tracking Blend Set ​

Adds one face tracking Blendshape Set to the Descriptor. VRC Face Tracking Installer can also supply sets. Use this component when a child prefab owns its own set, for example the eyelids. Specify:

  • Set name
  • Mappings from tracking inputs to Blendshapes
  • Default weight

Enable Control Weight and configure States to vary the weight by condition. Set Weight Output Parameter to write the same weight to a Float that other animations can read.

Face Tracking Toggle ​

Generates Animator controls that switch weights by condition. Each state has conditions and a weight from 0 to 1. The first matching state in list order wins.

The weight can drive either of these targets.

TargetSetupIf no state matches
Blendshape SetSelect the set. Its weight follows the active state. Optionally write the same Float to Weight Output Parameter.Use the set's default weight.
Blend Tree or component that reads a FloatLeave the set empty and enter the destination Float in Blend Parameter.Write the Toggle's Default Weight.

For example, if a Blend Tree uses a Float to make ears follow an expression, set only the blend parameter, use a default weight of 1, and add a manual-mode state with weight 0. In manual mode the ears stop following the expression.

Tracking State Router ​

Coordinates tracking and animation for the eyes and mouth. Several layers may use VRC Animator Tracking Control for the same region. At build time the Router:

  1. Finds VRC Animator Tracking Control behaviors on states and state machines in each Playable Layer.
  2. Converts the eye and mouth Tracking/Animation settings into requests and sets their original fields to No Change. Other body parts retain their settings.
  3. Adds a Tracking State Router layer to FX that resolves the requests separately for eyes and mouth.

Choose the layers in Require Approval On, then set Allow Animation Conditions separately for eyes and mouth. Animation requests from selected layers are checked against the region's conditions. Other layers can take control directly.

A Tracking Output Parameter can report each region's result to other components: 1 for Tracking, 0 for Animation.

Example from the supplied prefab

The supplied Face Tracking Settings prefab stores the menu mode in an integer named FT/ExpressionMode and selects FX for approval. The prefab defines this name and the mode values. When configuring a Router yourself, you can use your own Animator parameters in its conditions.

In this prefab, an FX animation can take over the eyes when eye tracking is off or FT/ExpressionMode equals 2 (Expression Priority). The mouth uses its own tracking switch with the same rule. Requests directly from Gesture pass through.

VRChat SDK: Animator Tracking Control

Face Tracking Merge Motion ​

Adds an Animation Clip or Blend Tree to a Playable Layer. Unity calls both a Motion. Clip paths can be relative to the avatar root or another specified root, so the same animation can be used on prefabs in different locations.

Enable Motion Variants to switch by condition. The first matching variant wins. If none matches, the original Motion plays.

Variant modeWhen the condition matches
Override MotionKeep the Motion and replace a clip or Blend Tree input. For example, replace TongueX with a manual control Float or with 0 to keep the tongue centered.
New MotionPlay another clip or Blend Tree, such as a dedicated manual-control tree.

Face Tracking Forward Parameters ​

Converts SDK tracking inputs into Floats the Animator can read. Each rule defines input Tracking Keys, a calculation and an output parameter name. The build generates a Forward to Animator parameter behavior.

For example, Max of EyeClosedLeft and EyeClosedRight returns the larger eye closure value. Other calculations include Min, Add, Multiply and custom expressions.

A Blend Tree can use this Float to drive animation from the selected Tracking Keys. The animation determines the target, such as ear movement or the weight of a face tracking Blendshape.

Identical calculations share an output. Different calculations using the same name are resolved by scope; conflicting rules in one scope produce an error. Enable Allow External Name Sharing if animations outside the hierarchy should read the same name.

Component Property Overrides ​

Replaces component properties on the build copy of the avatar. Each entry specifies a target component, a serialized property path and its replacement value. The scene object retains its original value.

For example, the Installer records mesh overrides on Face Tracking Meshes so the target Skinned Mesh Renderer uses the patched mesh at build time. After replacing a renderer or updating a prefab, check that the target component and property still exist.