Quick answer: CinemachineBrain → Default Blend → Style: EaseInOut, Time: 1.0 (or your preference). For per-pair overrides, edit the Custom Blends asset.
You set the active virtual camera and expect a smooth 1-second blend. The view cuts instantly. CinemachineBrain is using Cut as the default blend style.
Blend Configuration Layers
Cinemachine blends are determined in priority:
- Per-camera override (rare).
- Custom Blends asset entry matching the From→To pair.
- CinemachineBrain’s Default Blend.
If a Custom Blends asset specifies Cut for your pair, that wins regardless of the brain default. Edit the asset to use a different style or time.
The Fix
- Select CinemachineBrain in the scene.
- Inspector → Default Blend.
- Style: EaseInOut.
- Time: 1.0.
For all unspecified pairs, blends now last 1 second with smooth easing.
Custom Blends per Pair
For specific blends (e.g., Cam_Combat → Cam_Death should be a 2-second slow blend; everything else uses default):
- Project → Create → Cinemachine → Custom Blends.
- Open the asset. Add an entry: From Camera Cam_Combat, To Camera Cam_Death, Blend Curve EaseInOut, Time 2.0.
- Assign the asset to CinemachineBrain’s Custom Blends field.
Specific pair gets the override; everything else still uses default.
Runtime Override
brain.SetCustomBlend(fromCamName, toCamName,
new CinemachineBlendDefinition(CinemachineBlendDefinition.Style.EaseInOut, 1.5f));
For scripted contextual blends (slow blend during cutscene, fast during gameplay). Override the default per-context.
Verifying
Switch vcams in Play mode. Watch the transition; should ease over the configured duration. If still snapping, check Custom Blends asset for an interfering override.
“Default Blend on the brain handles most cases. Custom Blends asset handles exceptions. Snap = unintended Cut style somewhere.”
EaseInOut as the project default at 0.7s — feels good across most gameplay-camera transitions; tune specific pairs for cinematic moments.