Editing animation clips in game timeline

Editing Animation Clips in Game Timeline

Unity Timeline is not simply "cinematics for cutscenes." It is an orchestration tool that synchronizes animations, audio, object activation, Cinemachine cameras, and custom signals into a single sequence with frame accuracy. When configured correctly, an entire cutscene or gameplay event is managed by one PlayableDirector. When done hastily — you get a chaotic set of Coroutines scattered across five scripts that desynchronize when FPS changes or frames are skipped.

Animation Tracks and Binding

Each animation track in Timeline is bound to a specific Animator through Output binding. This is the first place where problems arise when reusing Timeline Assets between different characters: bindings are stored in the PlayableDirector component, not in the .playable file itself. This means one Timeline Asset can be reused with different characters through director.SetGenericBinding(track, newAnimator) — convenient for dialogue systems where the same cutscene structure is played with different NPCs.

Clips on the animation track are managed by two parameters: Ease In/Out and Clip Transform. Ease In/Out controls the blend from a neutral pose to the animation, controlling how the clip "appears." But the neutral pose is not T-pose or idle, it is the last pose the Animator had before Timeline started. If the character in idle stands with lowered arms, but the cutscene starts with a hand at the face — without proper Ease In there will be a hard pop.

Solution: create a short transition clip (0.5–1 second) that starts from idle pose and smoothly leads into the first cutscene pose. Put this clip first on the track with minimal Ease In. Then overlap with the main action. Now the transition works regardless of what state the character came from.

Blending Clips and Override vs. Additive Mode

By default, each animation track is in override mode: it fully controls the entire Animator. For cutscenes with multiple simultaneous layers (body walks, head turns, hand gestures) the correct architecture is multiple tracks with different Layer Weights, or a single track with animations covering the needed bones through Avatar Mask.

Avatar Mask on an animation track in Timeline limits which bones this track controls. This is equivalent to Animator Layer Mask, but at the Timeline clip level. Pattern: track 1 (Full Body mask) — locomotion or idle. Track 2 (Upper Body mask) — gesture or gesture. Track 3 (Head mask) — look-at or reaction. Blending between them is managed by Track Weight.

The problem arises when two tracks with overlapping masks compete for one bone. Timeline uses override blending by default — the last track wins. If additive blending is needed (combine transforms), Track Mode should be switched to Override with Additive Clip. This is not obvious in the UI — the setting is in the track context menu, not the clip inspector.

Signal Track and Synchronization With Gameplay Logic

Signal Track is one of the most underrated Timeline tools. It is a mechanism for sending events from the timeline into gameplay logic without direct dependency. Signal Emitter on timeline → Signal Asset (ScriptableObject) → Signal Receiver on GameObject with subscribed method.

Applications: enable hitbox on a specific attack frame in a cutscene, launch particle system at explosion moment, switch AI state after dialogue animation finishes. Without Signal Track, all this is done through Animation Events on clips or Coroutine with WaitForSeconds — both methods break when animation timing changes.

Important: Signal Emitter only fires during normal playback (not during scrubbing in Editor). For debugging, either manually invoke the signal receiver or use Retroactive flag on Emitter (fires if Timeline was seeked past the signal point).

Cinemachine Integration and Camera Editing

Cinemachine Track in Timeline is an editing table for game cameras. Each clip on the track is one virtual camera (CinemachineVirtualCamera). Blending between cameras is managed by Ease In/Out and overlap length.

Standard problem: when transitioning between cameras with different Look At targets, Cinemachine tries to interpolate between two different aim points, creating unwanted "swimming" in the transition frame. Fix — Blend Hint: Override Lookat On Blend = true on the second camera, or manual control through CinemachineBrain.m_DefaultBlend.

Cost is determined after examining the current project structure and the list of required sequences.