Recipes on GS_Play Gameplay Framework

PhantomCam Recipes

Mon, 01 Jan 0001 00:00:00 +0000

Recipes for composing specific configurations of the GS_PhantomCam virtual camera system. Read the matching basics page first for the concept; then come here for the composition steps.

For the underlying gem reference, see GS_PhantomCam API and The Basics: PhantomCam.

Recipe Collections

PhantomCam Configurations — composing cams from Body / Aim / Additive stages (shoulder, orbital player, static showcase, first-person clamped, tracking dolly, group framing).
Camera Noise Configurations — handheld baseline, event-triggered impact, stacked handheld + impact.
Camera Tug Configurations — vista pull, doorway glance, decoupled source / destination.
Group Target Configurations — two-player party cam, combat encounter frame, collapse-to-single-view.
Influence Field Configurations — boost a cam inside a room, always-on cinematic boost.
Channel Tier Configurations — Tier 1 single cam, Tier 2 level-placed, Tier 3 multi-channel co-op, common Tier 3 patterns, lobby flow.

PhantomCam Configurations

Mon, 01 Jan 0001 00:00:00 +0000

A Phantom Camera’s behavior is the composition of one Body stage, one Aim stage, and zero-or-more Additive stages. The same GS_PhantomCameraComponent becomes a follow cam, an orbital cam, a tracking dolly, or a third-person shoulder cam depending on what is slotted from the editor’s type-picker.

Each recipe below names a Body pick, an Aim pick, and any Additive picks, plus the key field values that produce the target behavior. For the concept, the per-tick pipeline, and per-stage field references, see The Basics: Phantom Cameras and the Stage Pipeline API.

Camera Noise Configurations

Mon, 01 Jan 0001 00:00:00 +0000

Camera shake comes in two flavors, both as Noise additives on a Phantom Camera’s stage list: PerlinNoise for continuous handheld sway and ImpulseNoise for event-triggered ADSR-gated bursts. Both consume the same .camnoiseprofile asset and the same six-axis Perlin layer model; they stack freely.

For the concept, the preset library, and how to trigger impulses from gameplay code, see The Basics: Noise & Impulse. For the underlying asset format, see Noise Profiles (Framework API).

Camera Tug Configurations

Mon, 01 Jan 0001 00:00:00 +0000

Tug Fields pull the camera’s pose toward a designated point while a proxy entity is inside a defined PhysX trigger volume. Each recipe below assumes the PhysX layer setup (TugProxy ↔ TugField collision-group pair) is already configured for your project.

For the concept, the three-component model, and the PhysX layer setup walkthrough, see The Basics: Tug Fields. For the per-tick algorithm and per-field reference, see Tug Fields (Framework API).

Before starting any recipe: Confirm the PhysX layer setup. If TugProxy and TugField aren’t paired (and only paired) in your collision-group preset, nothing will fire — that is the single biggest authoring failure for this system.

Group Target Configurations

Mon, 01 Jan 0001 00:00:00 +0000

A Group Target is an entity whose world transform is the weighted centroid of a runtime-editable subject list. You point a camera at it like any other target, and the cam frames “where the group is” rather than chasing any single subject.

For the concept, centroid modes, subject-management API, and pitfalls, see The Basics: Group Targets. For the full per-field reference and the registry bus, see Group Targets (Framework API).

Recipe: Two-Player Party Cam
Recipe: Combat Encounter Frame
Recipe: Collapse to Single View
See Also

Recipe: Two-Player Party Cam

A single cam that frames both players, sliding smoothly as they spread apart and converge.

Influence Field Configurations

Mon, 01 Jan 0001 00:00:00 +0000

Influence Fields modify the effective priority of Phantom Cameras without changing their base priority values. The spatial form fires when an entity enters a PhysX trigger volume; the global form applies for the component’s entire active lifetime.

For the concept, the channel-aware bus signature, and the priority-stacking model, see The Basics: Influence Fields. For component properties and the bus surface, see Camera Influence Fields (Framework API).

Recipe: Boost a Cam Inside a Room
Recipe: Always-On Cinematic Boost
See Also

Recipe: Boost a Cam Inside a Room

The player should see a different camera when they walk into a vista room — same player priority, but a “VistaCam” that frames the view jumps to dominance inside the room.

Channel Tier Configurations

Mon, 01 Jan 0001 00:00:00 +0000

GS_PhantomCam can be configured at three different tiers depending on what your project needs. Most projects use Tier 1 (single-cam) or Tier 2 (single-player rig). Co-op, split-screen, and per-player-cinematic projects use Tier 3 (multi-channel). The per-cam authoring surface is identical across tiers — what changes is the Cam Manager configuration and how many rigs the system spawns.

For the concept of channels, the choose-a-tier table, and pitfalls, see The Basics: Channels & Instancing. For the full bus surface and internal state, see Channels & Instancing (Framework API).

Recipes

Mon, 01 Jan 0001 00:00:00 +0000

Recipes are step-by-step setups for producing specific configured outcomes. Each gem has its own categorical section; within a section, recipe collections group related setups around a single subject.

Read the matching basics page first for the concept. Then come here for the composition steps.

Recipes by Gem

PhantomCam — virtual camera composition, channels, noise, tug fields, group targets, influence fields.

Additional gem sections will land here as their recipe libraries are authored.

Recipes on GS_Play Gameplay Framework

PhantomCam Recipes

Recipe Collections

PhantomCam Configurations

Camera Noise Configurations

Camera Tug Configurations

Group Target Configurations

Contents

Recipe: Two-Player Party Cam

Influence Field Configurations

Contents

Recipe: Boost a Cam Inside a Room

Channel Tier Configurations

Recipes

Recipes by Gem