Fix: Unity Cinemachine Virtual Camera Priority Tie Flicker

Two cinematic vcams both Priority 10. CinemachineBrain doesn’t know which to pick; toggles at the engine’s tick rate.

The Symptom

Camera oscillates between two views. Or sticks to one and the other never activates. Switching priority manually fixes it briefly.

The Fix

Vcam_Combat:    Priority = 10
Vcam_Cinematic: Priority = 20     // wins when active
Vcam_Idle:      Priority = 5

Activate vcams by setting Priority to a higher value. Deactivate by setting back to a low number. The brain always picks the highest active priority.

From Code

cinematicVcam.Priority = 100;   // take over
await CinematicEnd();
cinematicVcam.Priority = 0;     // give back

Activated Events for Debug

Subscribe to CinemachineBrain.OnCameraActivated. Logs which vcam took over and when. Useful for tracing rapid switches.

Verifying

Set distinct priorities. Toggle activation. Brain logs single transitions, not flickers. Frame Debugger shows one vcam rendering per frame.

“Unique priorities. Brain decides cleanly.”

Related Issues

For Cinemachine blend, see blend jumps. For Cinemachine Confiner 2D, see Confiner 2D.

Distinct priorities. No flicker.