Skip to main content

Change to Secondary Camera Views

Overview​

User capability

Change supported camera views without losing control continuity

User

An AeroSim player

What the user can do

Change supported camera views without losing control continuity

Why the user benefits

The player receives one coherent, observable capability.

User need

The player needs AeroSim to change supported camera views without losing control continuity.

In scope

Change supported camera views without losing control continuity

Tasks​

AEROSIM-TS-93Planning status: Done

Define the governed secondary-camera registry

Every supported secondary view resolves through one typed identifier to a camera rig with explicit lifecycle behavior.

  • ComponentWeb Application / R3F flight scene — secondary-camera registry
  • Depends onAEROSIM-TS-90
  • RequirementsFR-0021
AEROSIM-TS-94Planning status: Done

Switch secondary cameras through a presentation-only coordinator

One deliberate valid selection activates the requested view while preserving the simulation attempt and input owner.

  • ComponentWeb Application / Flight shell and R3F flight scene — camera switch coordinator
  • Depends onAEROSIM-TS-93
  • RequirementsFR-0021, NFR-0010
AEROSIM-TS-95Planning status: Done

Prove camera switching cannot mutate flight or control state

Trace and browser checks show supported, rapid, repeated, and invalid selections leave aircraft state, attempt identity, and control ownership unchanged.

  • ComponentWeb Application / R3F flight scene and Deterministic flight runtime — camera isolation harness
  • Depends onAEROSIM-TS-94
  • RequirementsFR-0021, NFR-0010
AEROSIM-TS-151Planning status: Done

Bind all production camera rigs to the active aircraft

Chase, Cockpit, Orbit, and Fly-by are production aircraft-bound rigs whose rendered semantics remain usable while the authoritative aircraft moves.

AEROSIM-TS-161Planning status: Done

Make every production camera a usable pilot view

Chase, Cockpit, Orbit, and Fly-by retain a usable world view and correct aircraft framing throughout sustained pilot-controlled flight for every governed aircraft.

  • ComponentWeb Application — long-flight production camera usability
  • Depends onAEROSIM-TS-151
  • RequirementsFR-0021
AEROSIM-TS-163Planning status: Done

Remove foreign and duplicated aircraft geometry from flight views

Every production camera renders exactly one intended active-aircraft presentation with no detached wing, duplicated aircraft mesh, oversized backface, or other foreign aircraft-like geometry in the frame.

  • ComponentWeb Application — production aircraft and camera scene composition
  • Depends onAEROSIM-TS-90
  • RequirementsFR-0021

Acceptance outcomes​

  1. 01

    Each supported secondary camera is deliberately selectable during flight.

  2. 02

    Changing camera does not alter aircraft state or control ownership.

Functional requirements and measurable criteria​

FR-0021

Change to Secondary Camera Views

The system shall change supported camera views without losing control continuity.

Acceptance 01

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

Whenthe primary capability path is completed

ThenEach supported secondary camera is deliberately selectable during flight

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

Acceptance 02

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

Whenthe continuation or repeat path is completed

ThenChanging camera does not alter aircraft state or control ownership

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.