What causes a Unity cutscene freezing because time scale is zero?

The PlayableDirector uses the default GameTime update method, so when you pause gameplay with Time.timeScale = 0 the director's playhead freezes too.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix Unity Cutscene Freezing Because Time Scale Is Zero

Quick answer: Set the director's Update Method to Unscaled Game Time (or DSPClock for audio sync) so the cutscene advances independently of Time.timeScale.

A cutscene meant to play over a paused game stays frozen because it follows timeScale. Switching its update mode to unscaled fixes it. Here is how.

How to fix it

1. Set the director update mode

On the PlayableDirector, set Update Method to Unscaled Game Time so the cutscene advances even while Time.timeScale is zero for the rest of the game.

2. Use DSPClock for audio-driven cutscenes

If the cutscene must stay locked to its audio, use the DSPClock update method so the playhead follows the audio clock rather than scaled game time.

3. Pause gameplay without touching the director

Alternatively, pause gameplay systems with your own flag instead of Time.timeScale, leaving the director on GameTime so it keeps playing normally.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Unity error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Ship the fix, watch the signature disappear from the next build. That's how you know it's really gone.