Layers

1m 25sPublished Sep 25, 2025Partial+1 changes

SummaryVersion Notes (Draft)

The primary teaching objective of this course is to thoroughly master the parallel layer architecture (State Machine Layers) and multi-track interaction design paradigms within Rive.

In legacy animation or game UI pipelines, if different visual components exhibit unique cycles or time frequencies (such as a character's constant walk cycle versus a sporadic blinking cadence), designers are typically forced to bake them into a single timeline by calculating a massive least common multiple. This leads to rigid keyframe management and wasted file weight. Rive resolves this friction by introducing isolated runtime layers. Each layer establishes its own logic entryway graph, enabling independent multi-track timelines to run concurrently and asynchronously without locking one another, unleashing creative freedom for complex multi-state UI elements.

Asynchronous Multithreading Essence of Layers: State Machine Layers function as separate logical threads running in parallel within a singular runtime instance. Every track encapsulates its own isolated Entry, Any State, and Exit nodal mechanics, consuming global Inputs uniformly while advancing timelines independently.
Property Overwrite & Mixing Matrix: When multiple tracks run concurrently, they operate completely cleanly if they govern distinct vector fields (e.g., Track 1 driving Object A's position, Track 2 driving Object B's rotation). However, if keyframe tracks compete for the exact same target property vector, the track positioned lower in the layer stack order (rendered on top) takes execution override priority.
Optimizing Complex Asset Footprints: Separating micro-interactions (like secondary character breathing, clothing sways, or button glow particles) from macro structural states (like core locomotion loops or menu exits) prevents timeline bloating. This decoupling ensures your motion system remains modular and highly performant, directly trimming down the final exported .riv binary package footprint.

Some content differs from current version1 changes

2025.2Disable layers

Disable individual SM layers.

📌 Key Points

SM layers play multiple animations simultaneously with independent states/transitions.

📝 Notes

Markdown

0 chars

Step by Step

00:00:04

Defining the Concurrency Challenge:

Instructor Ross introduces the demo asset: the Animations pane contains two linear clips with misaligned playback speeds—a brief red square translation red and a much lengthier blue square translation blue.
00:00:23

Creating a New State Machine Layer:

To break the structural limitation preventing simultaneous execution, click the plus icon located at the top-left of the state machine controller deck to append Layer 2 alongside the base Layer 1.
00:03:40

Wiring the Secondary Graph Flow:

Activate the Layer 2 canvas grid workspace. Drag the blue linear timeline asset from the sidebar directly into the graph space and connect its input vector to this layer's individual Entry node.
00:00:39

Verifying Dual-Track Asynchronous Execution:

Launch state machine playback. Even though the red and blue keyframe spans and loop loops are fundamentally out of sync, they process simultaneously under their respective layers without intersection or stuttering.
00:00:51

Advanced Character Rigging Field Case:

Pivot to a practical skeleton character use case. Break down the anatomy of the movement: the cyclic walk animation (walk) loops inside a 1-second metric, whereas the organic blink sequence (blink) maps to a 10-second span.
00:01:05

Concluding Multi-Layer Handoff Superpowers:

Map walk to the baseline layer and nest blink in the upper parallel layer stack. The engine automatically blends and matrices both bone vectors dynamically during runtime—a workflow completely unachievable inside static video tools without extensive code intervention.