This lesson breaks down the single most common mistake beginners make within the Rive State Machine: the "frozen property value" glitch. When transitioning between states, if a targeted timeline lacks explicit keyframes for a previously modified asset, the value simply locks onto whatever the preceding state left behind. By addressing this under-the-hood mechanism, the instructor establishes the golden rule of Rive: "You must be explicit with keyframes to drive predictable visual returns."
- Property Value Persistence Law: Rive's rendering engine maintains modified property states globally. Moving away from an animation track will never trigger an automatic rollback or default reset to baseline canvas coordinates unless explicitly commanded by keyframes.
- The Keyframe Symmetry Rule (Industry Handoff Guide):
- Core Guideline: If a property (such as X/Y coordinates, opacity, scale, or color hexes) is keyed in any timeline on a state machine layer, it should be keyed in all other companion timelines on that same layer to preserve structural integrity.
- Debugging Checklist: When shipping micro-interactions, if an element gets stuck in an un-hovered state or fails to drop its color highlights, use the
Uhotkey to cross-check asset properties across your state paths. Ensuring equal property representation is the fastest way to squash runtime interface freezes.