Contents
Unreal Engine 5.8 · System guide
Cameras and Cinematics
Build gameplay cameras and cinematic shots
On this page
Choose a task
Build and understand
Cine Camera Actor and lensOpen reference →Experimental Gameplay Camera SystemOpen reference →Network, accessibility, and performanceOpen reference →Rails, cranes, and shot recipesOpen reference →Sequencer cuts, blends, and gameplay handoffOpen reference →Spring Arm follow, lag, and collisionOpen reference →Transitions, modifiers, and shakesOpen reference →
Troubleshoot
Workflow and boundaries
Use these checks when a task crosses several systems. The focused references above contain the specific actions.
Choose the ownership model
Read references/system-selector.md.
- Pawn-relative gameplay follow/orbit -> Camera Component + Spring Arm.
- Central local-player rules/overlays/view-target control -> PlayerCameraManager.
- Reusable complex data-driven rigs -> Gameplay Camera System, but Experimental in UE 5.8.
- Authored shot/cut -> Cine Camera Actor + Level Sequence/Sequencer.
- Dolly/jib motion -> Camera Rig Rail or Crane in Sequencer.
The camera is local presentation. Replicate gameplay targets/state that influence it, not the final per-frame camera transform, unless a special shared-camera design explicitly requires otherwise.
Execute
- Define the camera's gameplay job, local owner, subject/target, input authority, and comfort limits.
- Choose gameplay or cinematic ownership and a single component responsible for final POV.
- Establish pivot, distance/FOV, rotation, framing, and collision before adding lag or shake.
- Add state transitions with explicit blend/interrupt/return policy.
- Layer recoil, shake, post process, and offsets in a stable ordered stack with intensity controls.
- For Sequencer, define cameras, cuts/blends, bindings, spawnable/possessable ownership, and handoff.
- Test obstruction, teleport, low/high frame rate, split screen, network corrections, and accessibility.
- Profile camera queries, post process, depth of field, and cinematic rendering on target hardware.
Load only what applies:
references/gameplay-camera-architecture.mdreferences/spring-arm-follow-and-collision.mdreferences/transitions-modifiers-and-shakes.mdreferences/gameplay-camera-system.mdreferences/cine-camera-and-lens.mdreferences/sequencer-cuts-and-handoff.mdreferences/rails-cranes-and-shot-recipes.mdreferences/network-accessibility-and-performance.mdreferences/debugging-patterns.md
Hard rules
- Establish a stable unlagged, unshaken base camera before layering secondary effects.
- Use Spring Arm
SocketOffset, not an arbitrary relative Camera offset, when collision tracing must account for the final framing position. - Higher Spring Arm lag speed follows the target faster; lower speed creates more lag.
- Apply camera behavior once. Do not let Pawn, Controller, CameraManager, and Sequencer fight over POV.
Set View Target with Blendchanges the local PlayerController's view; define interruption/return.- World camera shakes affect nearby local players and do not replicate automatically.
- Cap stacked shake and expose an intensity slider including zero.
- Treat the Gameplay Camera System and VCam as Experimental in UE 5.8; provide a shipping fallback.
- Camera Cut Track owns active cinematic camera; define blend-to/from-gameplay and sequence completion.
- Separate camera collision/readability from visual occlusion fixes; never move the player collision capsule merely to solve a camera obstruction.
See references/sources.md for the UE 5.8 source trail.
Version and evidence
Targets Unreal Engine 5.8 documentation. This label does not establish that every procedure was tested in an editor or packaged build.
Read the documentation sources and verification notes →