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 Timeline Control Track Leaving Particle Effects Playing

Q: What causes a Unity Timeline Control track leaving particle effects playing?

The Control clip plays a particle system but the clip's Post-Playback state is set to leave it active, or the system loops, so it keeps emitting after the clip ends.

Quick answer: Set the Control clip's particle handling and Post-Playback to deactivate, or disable looping, so the effect stops when the clip is over.

Particles that keep playing after a cutscene clip ends were left active by the Control track. Setting the wrap behavior fixes it. Here is how.

How to fix it

1. Set Post-Playback to Inactive

On the Control clip, set Post-Playback State to Inactive so the controlled object (and its particle system) is deactivated when the clip finishes rather than left running.

2. Disable looping on the system

If the particle system is set to Loop, it will keep emitting regardless of the clip length; turn off Loop or set a Duration that ends within the clip.

3. Stop on cutscene end as a fallback

In the director's stopped callback, explicitly call Stop(true, ParticleSystemStopBehavior.StopEmittingAndClear) on any cutscene VFX so a skip cannot leave them emitting.

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.

Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.