Why doesn't increasing vcam Priority make it active?

Priority resolves ties; if two vcams have priority 10, last enabled wins. Use distinct priorities (10, 20) or call vcam.MoveToTopOfPrioritySubqueue().

Brain LookAt vs vcam Look At?

Each vcam has its own LookAt/Follow targets. Brain doesn't override; vcam's settings apply during its time live.

Solo function for testing?

vcam → Solo button (top-right gizmo) forces it live regardless of priority. Useful for previewing without scene-state changes.

Fix: Cinemachine vcam Priority Change Ignored

Quick answer: Use distinct priority values per vcam. Or vcam.MoveToTopOfPrioritySubqueue() to push to active.

Switching vcams via priority doesn’t take effect until you also disable the previous one. Tied priorities cause non-deterministic activation.

The Fix

// Distinct priorities
idleVcam.Priority   = 10;
combatVcam.Priority = 20;     // becomes active

// Or move-to-top API
combatVcam.MoveToTopOfPrioritySubqueue();

Distinct values eliminate ties. MoveToTopOfPrioritySubqueue is fire-and-forget for transient swaps.

Verifying

Set priority. Brain switches to higher-priority vcam. Disable: switches back. Solo button forces preview.

“Distinct priorities. Or move-to-top.”

Related Issues

For TargetGroup, see TargetGroup. For StateDriven, see StateDriven.

Distinct values. Brain switches.