Skip to main content

Fly Using the Primary Chase Camera

Overview​

User capability

Provide the primary full-screen chase-view flight experience

User

An AeroSim player

What the user can do

Provide the primary full-screen chase-view flight experience

Why the user benefits

The player receives one coherent, observable capability.

User need

The player needs AeroSim to provide the primary full-screen chase-view flight experience.

In scope

Provide the primary full-screen chase-view flight experience

Tasks​

AEROSIM-TS-89Planning status: Done

Implement the authoritative primary chase-camera rig

Active flight starts in the primary chase view, which follows the controlled aircraft continuously without becoming a second owner of aircraft state.

AEROSIM-TS-90Planning status: Done

Compose and verify the chase-camera flight viewport

The representative viewport keeps the aircraft, flight direction, and nearby hazards legible while the chase camera follows the aircraft within the declared latency budget.

  • ComponentWeb Application — Three.js flight viewport composition and camera verification
  • Depends onAEROSIM-TS-89
  • RequirementsFR-0019, NFR-0010
AEROSIM-TS-126Planning status: Done

Correct the delivered Chase viewport to the approved design

The primary gameplay viewport matches the approved aircraft-visible Chase composition, camera control, Menu control, and shared HUD.

  • ComponentWeb Application — Release 1.0.0 user journey
  • Depends onAEROSIM-TS-90
  • RequirementsFR-0019, NFR-0010
AEROSIM-TS-140Planning status: Done

Keep the controlled aircraft visible in the chase camera

The default chase camera frames and follows the controlled aircraft continuously from the first launched frame.

AEROSIM-TS-155Planning status: Done

Make /flight a bounded runtime-only route

After launch, /flight mounts one route-specific runtime-only screen with no legacy setup/Foundation selectors or content and bounded supported-viewport document geometry.

Acceptance outcomes​

  1. 01

    The initial active-flight view is the chase camera and follows the controlled aircraft continuously.

  2. 02

    Aircraft, flight direction, and nearby hazards remain legible in the representative viewport.

Functional requirements and measurable criteria​

FR-0019

Fly Using the Primary Chase Camera

The system shall provide the primary full-screen chase-view flight experience.

Acceptance 01

GivenAEROSIM-FT-12 is exercised within its governed scope under supported conditions

Whenthe primary capability path is completed

ThenThe initial active-flight view is the chase camera and follows the controlled aircraft continuously

EvidenceFuture reviewed automated and browser evidence must verify this exact outcome against the current requirement.

Acceptance 02

GivenAEROSIM-FT-12 is exercised within its governed scope under supported conditions

Whenthe continuation or repeat path is completed

ThenAircraft, flight direction, and nearby hazards remain legible in the representative viewport

EvidenceFuture reviewed automated and browser evidence must verify this exact outcome against the current requirement.

Non-functional requirements

  • NFR-0010 — Responsive flight interaction

    Supported input-to-state and state-to-render paths meet the declared latency budget across ordinary flight, bounded heavy scenes, pause, camera selection, outcomes, and recovery.

Risks​

  • Risk

    Representative browser or input configurations may expose an unmet outcome.

Original source and prototype evidence​

Prototype and discovery boundary

Existing implementation is discovery evidence only; it establishes no current approval, acceptance, or release state.