Skip to content

29 — How to program Cinematic Benchmark

Product lock: 28-cinematic-benchmark.md · cinematic-benchmark design.
Siblings (separate products): Full 25 · Ladder Demo 26 — do not treat those hosts as CB’s spine now.

Cinematic Benchmark is a standalone UE5 project. It is not “another Lyra Experience on 5.8_terra_demo” for this phase. Motion Matching is required for feel; scores go to the Benchmark API. Full-game / Lyra Plugify integration is later.

Step Work Exit
0 Standalone UE project + CB maps/pawn Boots
1 Motion Matching loco (Pose Search) on CB hero Start/stop/pivot green; look-vs-body
2 Cinematic path (Sequencer / showcase map) + Foot Placement (no MM in the take) Cine path plays; feet conform — sequencer-foot-placement-cinematic.md
3 Benchmark ingest (signed / entitled → API) Row under PUID
4 Entitled package External build
Later Integrate into Full game (incl. combat) Parked — not CB exit

Kanban: Cinematic Benchmark board.

Anti-pattern Fix
Building CB as a Lyra Experience on the Demo host “for now” Standalone project — Full integrate later
Skipping MM because Ladder Demo skips it CB shall MM
Legacy Sequencer Animation track / skipping Foot Placement sequencer-foot-placement-cinematic.md — Mixer + Foot Placement
Writing scores into WP postmeta API benchmark_runs only
Treating Website Benchmark page as this product Page = shell; this = UE client
Ambient melee magnet Attack / authored windows only
Pulling Full GFP spine cards onto this board Keep board CB-only
Doc Use
28-cinematic-benchmark.md Product lock
tutorials/sequencer-foot-placement-cinematic.md Sequencer Foot Placement + Animation Mixer (no MM in cine)
22-demo.md Ladder ≠ CB
23-website.md Benchmark display
25-howto-program-full-game.md Later integration only