Modifiers target camera node classes and change selected node parameters. See Concepts -> Modifiers for lifecycle and gameplay guidance.

UComposableCameraNodeModifierDataAsset¶

Concrete data asset. This is the object gameplay code adds and removes.

Registered in the Content Browser under Composable Camera System -> Node Modifier Data Asset.

Apply Modes¶

ReactivateCamera is the default and existing behavior. When the effective modifier set changes, the PCM reconstructs the current camera from its source type asset, applies the selected modifier values before initialization, and blends from the old camera pose to the new camera pose.

ModifyExistingInstance keeps the current camera actor and node instances alive. It takes ownership of checked node properties, writes them into the live node, and optionally blends supported property values through a modifier value transition. This mode is for retuning properties on nodes that are already in the graph; it never inserts nodes into the Evaluation Tree.

Continuous value transitions are available only for property types with built-in interpolation support. Discrete properties switch when the value transition weight reaches DiscreteSwitchWeight.

UComposableCameraModifierTransitionBase¶

Stateless timing template for ModifyExistingInstance value transitions. It does not evaluate camera poses and is not a UComposableCameraTransitionBase.

UComposableCameraModifierBase¶

Base wrapper and legacy extension class.

Node Type Overrides¶

In Node Type mode, choose a camera node class and check the properties that should be overridden. Only editable, non-transient, non-deprecated, top-level node properties are eligible. Properties marked with NoModifierOverride are intentionally hidden.

For ReactivateCamera, checked fields are applied before node initialization and are protected from pin auto-resolution for that activation. For ModifyExistingInstance, checked fields are applied to the live node and remain owned by the modifier runtime state until the modifier exits.

Custom Modifier Class¶

Custom mode owns an instanced user-authored subclass of UComposableCameraModifierBase. The nested modifier supplies NodeClass and receives the legacy ApplyModifier(Node) Blueprint event after initialization.

Use this mode when the modifier needs logic instead of a static property copy. ModifyExistingInstance is intended for Node Type overrides, not arbitrary Blueprint mutation.

Matching and Priority¶

The modifier manager filters active assets through CameraTagQuery, then resolves Node Type entries per (exact node class, property) by Priority. Empty queries match every camera. Legacy CameraTags data keeps its previous "any of these tags" behavior after migration.

Disjoint checked properties on the same node class can come from different modifier assets at the same time. Overlapping properties still elect one winner by priority, then registration order. Custom Modifier Class entries remain whole-node winners because their Blueprint side effects cannot declare per-property ownership.

Transitions¶

For ReactivateCamera, add/remove changes use camera-pose transitions: OverrideEnterTransition, OverrideExitTransition, then normal camera transition resolution.

For ModifyExistingInstance, add/remove changes use value transitions: OverrideEnterValueTransition, OverrideReplaceValueTransition, OverrideExitValueTransition, or immediate application when no value transition is set. A null Replace transition preserves the legacy priority handoff rule; set a zero-duration Replace transition for an explicitly immediate replacement.

Non-Transient Cameras Only¶

Transient cameras skip modifier resolution. Clear bIsTransient if a cinematic or temporary camera must respond to modifiers.

See Also¶

• Concepts -> Modifiers
• Custom Modifiers
• Mesh Camera Layers