public sealed class CameraBlendTableWhich blend to use between two named shots, when the default will not do.
No guide page documents this yet — the page shows what the code says about itself.
Remarks
Cinemachine's custom blend asset, as a runtime table. A game usually wants one default and three exceptions — "cut into the death camera, never blend", "take four seconds coming out of the map" — and writing those as a rule per pair is both smaller than a state machine and easier to reason about than one.
The most specific rule wins, and specificity is counted rather than ordered: a rule naming both shots beats one naming either, which beats the director's default. An order-dependent table is a table whose behaviour changes when somebody sorts it.
Fields and properties (1)
public int CountHow many rules there are.
Methods (3)
public CameraBlendTable Add(Entity from, Entity to, CameraBlend blend)Adds or replaces a rule.
public void Clear()Removes every rule.
public CameraBlend Resolve(Entity from, Entity to, CameraBlend fallback)The blend for a transition.
Used by (2)
- CameraDirectorSystemVixen.Engine
- CameraDirectorTestsVixen.Engine.Tests