Quick answer: Enlarge the dead zone in the Position Composer so small target movements are ignored, and widen the soft zone so the camera eases the target back when it drifts out.
If your Cinemachine camera jitters with every step the player takes, the dead zone is too small. Sizing the framing zones fixes it. Here is how.
How to fix it
1. Enlarge the dead zone
In the Position Composer, increase the Dead Zone width and height so the camera holds still while the target moves within that central region.
2. Widen the soft zone
Set a soft zone larger than the dead zone so when the target leaves the dead zone the camera eases it back rather than snapping to recenter.
3. Tune damping with the zones
Pair the larger zones with moderate damping so the recenter that does happen is smooth; tiny zones plus low damping is what makes the camera feel nervous.
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.