Unity-Cinemachine-Kameras

Cinemachine Gameplay Cameras

Inspect the installed Cinemachine major version, camera/Brain setup, target update loop and render pipeline. Cinemachine 2 and 3 have different APIs and component layouts; preserve the current version unless migration is part of the task.

• Define the player-facing camera behavior: framing, aim, orbit limits, obstruction response, transitions and motion comfort. Pick the rig for that behavior rather than accumulating competing extensions.
• In Cinemachine 3, verify Unity.Cinemachine and the installed CinemachineCamera/follow/aim APIs before writing code. Do not paste CinemachineVirtualCamera or old FreeLook examples into a version-3 project.
• Give one Brain authority per intended output camera. Verify output channels, enabled state, priority and explicit activation; inspect which camera is actually live instead of assuming a priority change succeeded.
• Match the Brain's update/blend mode to physics, animation and target movement. Investigate target jitter, interpolation and update ordering before increasing damping.
• Test obstruction layers, player self-collision, narrow doors, occluders and return damping. Distinguish staying outside geometry from preserving line of sight.
• Check blend paths when targets are on opposite sides or a camera teleports. Use supported cut/warp/blend controls deliberately; avoid unrequested shake and provide motion-reduction options.
• Timeline can own the camera during a shot. Define bindings, interrupted-cutscene behavior and the handback to gameplay input and camera control.

Verify at variable frame rates, with moving platforms, camera swaps, obstruction and cutscene interruption. Confirm both visual framing and authority restoration.

Reference: Cinemachine upgrade guide; it is a compatibility reference, not an instruction to upgrade.