Fix: Unity Time Scale Not Affecting Physics

You add a pause menu, set Time.timeScale = 0, and the game freezes as expected — except for one rigidbody that keeps visibly drifting, or a coroutine that keeps ticking, or an animation that keeps playing. “Pause” in Unity is not one switch. It is a cluster of switches and whichever one you forgot is the bug.

The Symptom

You call Time.timeScale = 0. Most things stop. But:

• A Rigidbody with Interpolation enabled slides forward slightly for a frame after the pause.
• A custom script using Time.unscaledDeltaTime continues to update.
• A character controller keeps moving because its script reads input and applies velocity using Time.unscaledDeltaTime.
• A coroutine with yield return new WaitForSecondsRealtime continues counting down.

What timeScale Actually Does

Setting Time.timeScale = 0 multiplies Time.deltaTime and Time.fixedDeltaTime by zero. This means:

• Update still runs, but Time.deltaTime returns 0.
• FixedUpdate stops running entirely (Unity does not schedule physics ticks when fixedDeltaTime is 0).
• Animations driven by Animator with update mode Normal pause because they read scaled delta.
• Coroutines using WaitForSeconds pause.

But: anything reading unscaledDeltaTime, unscaledTime, or realtimeSinceStartup is immune. And the Animator update mode Unscaled Time is also immune. The “bug” is usually that something in your project chose to opt out of scaled time and you forgot about it.

The Fix

Step 1: Make a single PauseManager.

public static class PauseManager
{
    public static bool IsPaused { get; private set; }

    public static void Pause()
    {
        IsPaused = true;
        Time.timeScale = 0f;
        AudioListener.pause = true;
    }

    public static void Resume()
    {
        IsPaused = false;
        Time.timeScale = 1f;
        AudioListener.pause = false;
    }
}

Every pause flow must go through this. If you have two scripts setting timeScale, you will eventually get a race condition where the game appears paused but is not.

Step 2: Audit unscaled time usage.

Search your project for unscaledDeltaTime, unscaledTime, and realtimeSinceStartup. Each hit is a place where pause will not work by default. You have two choices:

• Gate the code on PauseManager.IsPaused and skip updates while paused.
• Switch to scaled time so timeScale does the work automatically.

Step 3: Freeze rigidbodies that use Interpolation.

public class PausableRigidbody : MonoBehaviour
{
    private Rigidbody _rb;
    private RigidbodyInterpolation _savedInterp;

    void OnEnable()  { _rb = GetComponent<Rigidbody>(); }

    public void OnPause()
    {
        _savedInterp = _rb.interpolation;
        _rb.interpolation = RigidbodyInterpolation.None;
    }

    public void OnResume()
    {
        _rb.interpolation = _savedInterp;
    }
}

Interpolation lerps the visual transform between physics frames based on unscaled time, which is why paused bodies still drift visibly. Disabling interpolation during pause locks them in place.

Step 4: Use manual physics simulation for games that need it.

// In Start or a bootstrap script
Physics.simulationMode = SimulationMode.Script;

// In your own update loop
void Update()
{
    if (!PauseManager.IsPaused)
    {
        Physics.Simulate(Time.fixedDeltaTime);
    }
}

Manual simulation gives you full control: physics only steps when you call it. This is the most reliable pause behavior, at the cost of managing the fixed-timestep loop yourself.

The Animator Gotcha

Animators have an Update Mode property with three values: Normal (scaled), Animate Physics (in FixedUpdate, scaled), and Unscaled Time (ignores timeScale). A designer sets one Animator to Unscaled Time because they want the UI to keep animating during pause, and six months later you ship a pause bug because that mode was applied to an enemy too.

Audit your Animators: search project assets for Animator controllers and check the Update Mode on the Animator component itself (not the controller). Decide which ones need Unscaled Time and document the list.

Verifying the Fix

Build a test scene with a rolling ball, a moving platform, a particle system, an Animator, and a UI button. Press pause. Every non-UI object should freeze in place visibly. Press resume. Everything should continue from exactly where it was. If any object continues to move during pause or teleports on resume, you have another place using unscaled time.

Understanding the issue

Game physics is a contract between authoring (the body, mass, collision shapes you set) and the solver (how the engine integrates them per tick). Bugs at this boundary usually surface as 'the values look right but the behavior is wrong' - a sign that one side of the contract isn't honoring the other.

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

Bugs of this class are particularly easy to ship past internal QA because they often depend on specific runtime conditions - hardware combinations, network states, or asset configurations that QA didn't reproduce. Players hit them in the wild, file reports that are hard to repro, and the bug accumulates negative reviews while engineering tries to recreate the failure mode.

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

Live games surface this bug class at scale. What's a rare edge case in development becomes a daily occurrence once you have a few thousand concurrent players. The class isn't 'this player has a unique setup'; it's 'one in N thousand sessions will trigger this exact combination'.

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

The diagnostic tools available depend on your engine and platform. Use the engine's native profilers and debug overlays before reaching for external tools. The native tools have context that external tools lack - they know which subsystem owns the code, which assets are loaded, and what state the engine is in.

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.

“Pause in Unity is not a feature, it is a convention. Pick one switch (timeScale) and make every other time-dependent system in your project respect it.”

Related Issues

For broader Unity physics problems, see Unity physics jittery movement. For pause-related UI issues, see Unity UI button not responding to clicks. For coroutine timing problems, see Unity coroutine not starting or stopping early.

Keep a single PauseManager and route every pause action through it. Two scripts setting timeScale independently is the source of every pause bug you will ship.