A trigger can be intentionally blocked while a previous animation cycle finishes. Adobe documents that Let Cycle Finish can prevent other triggers in the same swap set from starting until completion, including configured reverse playback. Before reassigning keys, inspect the cycle's end policy and determine whether interruption or completion is the intended performance.
Locate the state that owns the wait
Observe whether the new trigger fails only during one animated gesture or also fails when the character is at rest. A wait that ends at a repeatable animation boundary suggests a state-policy check. A trigger that never works needs a different investigation of its assignment and controlled artwork.
Note which group carries Cycle Layers and whether the competing trigger belongs to the same swap set. Do not infer a shared state relationship just because the two keys are adjacent on the keyboard. A recorded take and a live rehearsal can also involve different active controls, so identify which one you are reviewing.
Choose the interaction the scene needs
A ceremonial bow may need to finish before another action begins, while a live presenter may need an immediate interruption to answer a question. Write that requirement first. Adobe's On Trigger End distinguishes stopping immediately from letting the cycle finish; reverse and held-last-layer choices can affect what completion looks like.
Changing the policy is an artistic decision as well as a technical one. Interrupting a gesture in the middle may leave an awkward silhouette, while waiting may miss an important spoken cue. Do not call the fastest response the best response without comparing both against the scene's purpose.
Test the same command at several cycle phases
For a hypothetical mascot wave followed by a pointing gesture, record the effect of requesting the point early, midway and near the wave's end. This is an original rehearsal matrix, not an executed software test.
| Request phase | Observe before changing policy | Acceptance question |
|---|---|---|
| Early wave | Immediate switch, wait or no later action | Is the planned introduction preserved? |
| Middle | Wrist and arm silhouette at interruption | Is the transition readable? |
| Near completion | Forward and optional reverse ending | Does the new action arrive on cue? |
Record key release separately from requesting the next state. If reverse playback is enabled, do not assume the last forward picture is already the completed cycle. Observe when the system actually permits the next trigger.
Verify the saved performance and reset state
After choosing the intended policy, record a short take with a genuine cue from the script. Replay it without unintended live input interfering. Check that no old hand remains, the next gesture starts when approved and the character can return to a useful rest.
Save the policy and the tested transition examples with the puppet's control notes. If the current configuration still cannot meet the required interruption cleanly, revise the gesture design or the scene timing rather than pretending a delayed response is random lag. Imagild may supply the visual concept or shot plan, but these cycle and swap-set controls belong to Adobe Character Animator. This guide reports no measured input latency; it offers a phase-based review that distinguishes a documented completion rule from a broken key.