End-to-end walkthroughs that take a realistic goal and build it from an empty project slot. Each tutorial picks one concrete outcome, names the nodes or classes involved, and shows the full wiring — graph, Blueprint calls, and any C++ when required. The intent is to connect the vocabulary from the Concepts tour and the cataloged behavior from Reference into something that runs.

Prerequisites¶

All five tutorials assume you've finished Getting Started — that is:

• The plugin is installed and compiled into a C++ project.
• AComposableCameraPlayerCameraManager is your GameMode's PCM class (or your PlayerController's override).
• showdebug camera prints the in-game overlay during PIE. CCS.Debug.Panel 1 enables a richer always-on overlay — either works for the verification steps in the tutorials.

You do not need to have read the full User Guide. Each tutorial links back to the concepts it leans on so you can drill down as needed.

The five walkthroughs¶

Follow Camera¶

Build a classic third-person follow camera — pivot on the player, camera offset behind, stick-driven orbit, soft collision pushback. The output is a single camera type asset that you can drop onto any character and activate from Blueprint.

Concepts covered: pivot vs camera, reflection-driven parameters, ControlRotateNode input binding, CollisionPushNode tuning, activation from a K2 node.

Time to complete: 15–25 minutes.

Cutscene Context¶

Push a cutscene context during a scripted sequence, hand control to a cinematic camera, and blend cleanly back to gameplay on pop — with the gameplay camera live under the cutscene the whole time, so the blend back is seamless.

Concepts covered: Context Stack, reference-based inter-context blending, transition resolution across a context pop, Activate Camera with a Context Name (implicit push), TerminateCurrentCamera / PopCameraContext.

Time to complete: 20–30 minutes.

ADS / Aim Camera¶

Push an aim-down-sights context on right-click, blend into a tighter camera with lower FOV and slower sensitivity, pop back to the gameplay camera on release. A practical use of context pushing driven by held input rather than a trigger overlap.

Concepts covered: Context Stack, context push via held input, inertialized transition tuning, per-weapon modifier layering via camera tags.

Time to complete: 15–25 minutes.

Level Sequence Integration¶

Play a ULevelSequence as a CCS-managed cutscene using the Play Cutscene Sequence node. The plugin handles context pushing, camera cuts, proxy camera creation, and cleanup automatically — one Blueprint node is all it takes.

Concepts covered: Context Stack, Play Cutscene Sequence async action, inter-context transitions, CameraCut track integration, StopCutsceneSequence for early termination.

Time to complete: 20–30 minutes.

CCS Camera in Sequencer¶

Author a CCS camera inside Sequencer rather than bridging an existing LS into CCS. Bind an AComposableCameraLevelSequenceActor as a Spawnable, assign a TypeAsset, and keyframe its exposed parameters (distances, FOV, offsets) directly on the Sequencer timeline. The camera runs the full CCS node chain each frame — collision push, screen-space constraints, spring damping — and projects its pose through the CameraCut track as if it were a standard CineCameraActor.

Concepts covered: AComposableCameraLevelSequenceActor, FComposableCameraTypeAssetReference, Sequencer Spawnable bindings, keyframeable parameter tracks, PCM-independent evaluation.

Prerequisites: Follow Camera and Level Sequence Integration completed.

Time to complete: 20–30 minutes.

What's not a tutorial¶

Tutorials focus on realistic end-to-end flows. A few things that might sound like tutorials but live elsewhere:

• Authoring custom nodes, transitions, modifiers, and actions. Those are extension recipes — see Extending.
• A walkthrough of the graph editor UI. That's The Graph Editor in the User Guide — a UI tour rather than a build-this-thing recipe.
• Reference for every node's parameters. That's the Node Catalog plus the per-class C++ API Reference.
• A deep dive on the Context Stack's implementation. That's Concepts → Context Stack.

If