Skip to main content

AEROSIM-TS-161

Project task

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.

AEROSIM-TS-161Canonical ID TASK-0161
Verified flow state
Done
Owner
AeroSim Architecture and Delivery
Component
Web Application — long-flight production camera usability
Repository
corp-v1-aerosim/corp-v1-aerosim

Delivery scope

Repair camera anchors, near/far planes, look targets, collision/clipping avoidance, and long-flight lifecycle. Cockpit must present a credible pilot viewpoint rather than exterior wing or empty terrain; Orbit and Fly-by must keep aircraft/world context without black frames or unusable scale.

Implementation contract

Implementation artifacts

  • applications/web/src/flight/camera/production-camera-rigs.ts
  • applications/web/src/flight/camera/camera-switch-coordinator.ts
  • applications/web/src/flight/assets/aircraft-presentation-contract.ts
  • applications/web/e2e/long-flight-camera-acceptance.browser.spec.ts

Inputs

  • Release 1.0.0.2 UAT shows no usable cockpit view in any of the nine cockpit journeys.
  • Coastal Range J04/J09/J12 and Mountain Valley J03/J07 end in black or empty frames.
  • Orbit and Fly-by evidence contains clipped aircraft, extreme scales, exterior geometry, and lost world context.
  • Follow-up Chase recordings show persistent foreign aircraft-like geometry in the frame and confirm that camera usability cannot be accepted from a single launch screenshot.
  • The separately owned duplicate/foreign-geometry correction is TASK-0163; this Task retains camera anchoring, clipping, framing, and lifecycle ownership.

Outputs

  • Aircraft-specific bounded camera anchors for all four production modes.
  • Long-flight camera updates tied to the current authoritative aircraft frame and attempt identity.
  • Visible fail-closed diagnostics before a camera can render an empty or unusable frame.

Failure boundaries

  • Fail when Cockpit lacks a usable pilot viewpoint or clips through exterior geometry.
  • Fail when aircraft or world context is missing, black, empty, off-screen, or unrecognizably scaled.
  • Fail when camera change alters aircraft state, control ownership, or attempt continuity.

Excluded scope

  • No new camera mode or aircraft asset.

Verification steps

  • Write failing tests from the exact UAT frames before camera changes.
  • Sustain all nine aircraft in all four cameras for at least 60 seconds with continuous pixel, framing, world-context, and source-step assertions.
  • Capture and visually inspect every journey through ordinary visible controls.

Traceability

Requirements

Dependencies

Acceptance evidence

Verified delivery: all 36 production camera journeys across nine governed aircraft and Chase, Cockpit, Orbit, and Fly-by retained rendered aircraft/world context for at least 60 seconds on integration revision 910a30c79efc1b6ac5d8f55e84b8cc6863ceae3f; exact integration validation and immutable image publication passed. Release completion was verified on deployed revision dbba4a186a02cb4567c64f1c3400d38556aa1a25; human post-release acceptance remains PENDING.

Current evidence boundary

No current implementation, acceptance, release, or deployment evidence is claimed for this planned Task. Any prior implementation may be used only as prototype and discovery evidence.