Fix: Unity Animation Event Timing Off by One Frame

Your attack animation plays a sword swing at frame 18. The hit sound is supposed to fire on that frame, but sometimes it plays on frame 17 and other times on frame 19. The animation looks fine; the event timing does not. The bug lives in the relationship between your event’s time value and the clip’s sample rate.

Why It Happens

Animation events are stored as floating-point times in seconds. Unity fires the event on the first frame whose elapsed time equals or exceeds the event time. If your 30-FPS clip has an event at 0.6333s (approximately frame 19), rounding to a floating-point value like 0.6334 pushes it past frame 19 into frame 20. A clip at 24 FPS hits different rounding errors than 30 FPS, which is why the same event moves between imports.

The Fix

Step 1: Lock the event time to a frame boundary.

// Snap an event to a specific frame in an editor script
void SnapEventToFrame(AnimationClip clip, int eventIndex, int frame)
{
    var events = clip.events;
    events[eventIndex].time = frame / clip.frameRate;
    AnimationUtility.SetAnimationEvents(clip, events);
}

Step 2: Match the Animator Update Mode to your gameplay clock. For visual effects, use Normal. For animations that drive Rigidbody motion via root motion, use Animate Physics. Mixing them causes events to fire at inconsistent intervals relative to game logic.

Step 3: Move events away from loop boundaries. An event at the exact end of a looping clip can fire twice per loop — once for the current frame, once for the restart. Place events at 0.01 seconds before the end to force a single fire per loop.

The State Machine Alternative

For critical timing, use State Machine Behaviours instead of clip events. An OnStateEnter or OnStateMachineExit callback fires exactly once per state transition, independent of clip timing. This is more reliable for gameplay logic like damage application or combo windows.

Verifying the Fix

Add a Debug.Log in the event handler that prints Time.frameCount and Animator.GetCurrentAnimatorStateInfo(0).normalizedTime. Play the animation ten times. The frame count on each fire should increase by exactly the clip’s frame count. If it varies by ±1, your event is straddling a frame boundary.

Understanding the issue

Animation runs on its own tick group, often separate from gameplay. When animation and gameplay communicate (events firing, state changing), the timing of that communication affects visual consistency.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

The triage path for this kind of bug is long. The symptom appears in gameplay, but the cause is in a different system. The reporter describes the gameplay effect; the engineer has to translate that into a hypothesis about the underlying cause. Misdirection is common.

At the engine level, the behavior comes from a deliberate design decision in Unity. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

Verifying this fix in isolation is straightforward: reproduce the bug, apply the change, confirm the bug no longer reproduces. The harder verification is regression - did this fix introduce a new bug elsewhere? Run your standard regression suite, plus any tests that exercise the same code path with different inputs.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

For shipping titles with a long support window, watch for this issue resurfacing after dependency updates. Engine upgrades, driver updates, OS releases - each one can resurface a bug class you thought you'd fixed because the underlying behavior changed slightly. Regression tests catch the obvious ones; player reports catch the rest.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

Diagnostic approach

Diagnosing this class of bug benefits from a structured approach: confirm the symptom, isolate the variables, hypothesize the cause, and verify the hypothesis before writing fix code. Skipping the isolation step is the most common mistake; without it, fixes often address symptoms while the underlying cause continues to produce other variations.

For Unity-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

The tooling around this bug class matters as much as the fix itself. Good logging, accessible profilers, and clear error messages turn 30-minute investigations into 5-minute ones. If your project doesn't have visibility into this code path, the first fix should add the visibility - the second fix uses it.

Within Unity, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Boundary conditions deserve specific testing attention. What happens when the input is zero, maximum, negative, or NaN? What happens at the start of a session vs hours in? What happens at the boundary between two systems handling the same data? These are where bugs hide and where regression tests are most valuable.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

When this bug class affects multiple teams (often the case for cross-system issues), early communication prevents duplicate work. The team that owns the symptom may not own the cause. A 15-minute conversation at the start of triage often saves hours of independent investigation.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Animation events are time-based, not frame-based. Snap them to frame boundaries and the inconsistency disappears.”

Related Issues

For animations not playing at all, see Unity animation not playing animator. For blend tree issues, see Unity blend tree stuck at one parameter.

For any event that has to fire on an exact frame, use a State Machine Behaviour. Clip events are for visuals; behaviours are for gameplay.