Unity Cinemachine: Design Camera Selection and Directional Blends

Define who controls the rendered view

In Cinemachine 3.1, a CinemachineBrain on a Unity camera selects an eligible Cinemachine camera and manages cuts or blends. A CinemachineCamera describes a shot through targets, procedural controls, and lens settings. Establish which Brain owns each rendered view before adjusting individual shots. Channel filtering matters when several Brains coexist, such as in a split-screen arrangement. [1][2]

Make selection follow a camera state

Under normal Brain selection, higher priority gives an active eligible camera precedence. Timeline can override those decisions, so a priority change is not a universal command to replace the visible shot. [1][2]

Represent inspection, exploration, and other camera modes explicitly in project logic. On entering a mode, set its target and eligibility consistently; on leaving, restore the intended alternative. Avoid relying on an unexplained priority tie. When the wrong shot appears, inspect active cameras, priorities, channels, and Timeline ownership before changing blend duration.

Specify a concrete inspection transition

Imagine a museum game with cameras named Explore and Inspect. Give the exploration shot priority 10. While inspecting an artifact, activate the inspection shot at priority 20 and aim it at the selected object. On exit, remove that inspection precedence so exploration becomes eligible to lead again. These priorities are illustrative project choices.

Create a custom blend from exploration to inspection lasting 0.6 seconds, and a separate return blend lasting 0.2 seconds. The slower arrival gives the object time to become readable; the shorter return is a design hypothesis to evaluate during play. Directional entries allow those durations to differ. [1][3]

Treat blend names as maintained configuration

Custom blend From and To fields match camera names, rather than storing references to particular scene objects. Renaming a camera can therefore stop a rule matching. If no rule matches, the Brain's default blend applies; more specific matching entries take precedence over broader ones. [3]

Use unique, stable names for shots that need special transitions. Review their blend settings after renames or prefab reuse. Choose a deliberate default so an unconfigured transition remains understandable, and use a cut where continuity would communicate the wrong spatial relationship.

Review the whole transition, not only its endpoints

A readable starting shot and ending shot do not guarantee a readable journey between them. Inspect the moving subject's screen position, changes in framing and lens settings, intervening walls, and an exit requested before the arrival finishes. Camera blend hints can alter how position and aim behave during transitions, so review the selected configuration rather than assuming one universal path. [2]

Use the Brain's live-camera and blend debug display to connect visible behavior to the active rule. Review both transition directions under the actual gameplay conditions. The example durations are proposed starting values, not measured comfort or performance results. [1]

Sources

1. Cinemachine Brain component — Unity Technologies.
2. Cinemachine Camera component — Unity Technologies.
3. Cinemachine Blender Settings asset — Unity Technologies.