Skip to main content

AEROSIM-TS-163

Project task

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.

AEROSIM-TS-163Canonical ID TASK-0163
Verified flow state
Done
Owner
AeroSim Architecture and Delivery
Component
Web Application — production aircraft and camera scene composition
Repository
corp-v1-aerosim/corp-v1-aerosim

Delivery scope

Diagnose and correct the production scene and camera composition that renders a complete active aircraft together with oversized black wing-shaped polygons and separate cyan/white detached-looking geometry. Enforce one active presentation root, camera-safe visibility and clipping rules, and deterministic cleanup across launch, camera change, crash, recovery, and attempt replacement. Do not assume the source is terrain or a second aircraft until scene-graph and render evidence identifies it.

Implementation contract

Implementation artifacts

  • applications/web/src/flight/SceneRoot.tsx
  • applications/web/src/flight/assets/AircraftModel.tsx
  • applications/web/src/flight/cameras/camera-rig.ts
  • applications/web/e2e/single-aircraft-presentation.browser.spec.ts

Inputs

  • Release 1.0.0.2 production UAT failed all 36 ordinary journeys and every screenshot was judged visually unacceptable by RootAtSkic.
  • Three follow-up production flight videos, each about 52 seconds, show a complete F-14 together with recurring oversized black wing-shaped geometry and a separate cyan/white detached-looking object.
  • The foreign geometry recurs across worlds and reappears after implicit attempt replacement; the earlier 36-journey screenshots show equivalent defects with fighter, trainer, and utility aircraft.
  • RootAtSkic identified the visible extra wing/plane defect in Discord messages 1550580266580447333 and 1550583772309889217.

Outputs

  • A diagnosed scene-graph record identifies the exact source, ownership, material/backface state, transform, and lifecycle of every aircraft-like rendered object.
  • Production camera composition mounts and shows exactly one intended active-aircraft presentation root.
  • Automated and visual evidence covers all nine aircraft, all four cameras, all three worlds, launch, crash, recovery, and attempt replacement.

Failure boundaries

  • Fail when a complete aircraft is visible together with any detached wing, second aircraft mesh, oversized aircraft surface, backface, stale model, or unexplained aircraft-like polygon.
  • Fail when a camera clips through the active aircraft or exposes geometry that belongs outside the selected camera composition.
  • Fail when a stale presentation root survives launch, camera change, crash, recovery, or attempt replacement.
  • Fail when pixel diversity, scene load success, or a single clean frame substitutes for full-flight visual review.

Excluded scope

  • This Task does not change flight physics, world terrain, control bindings, or introduce new aircraft assets.
  • Root cause must be demonstrated rather than inferred from the visible shape alone.

Verification steps

  • Write failing scene-lifecycle and ordinary-browser visual regression tests from the preserved 1.0.0.2 screenshots and video frames before changing production rendering.
  • Assert exactly one active aircraft presentation root and zero stale aircraft roots through launch, camera changes, crash, recovery, and attempt replacement.
  • Record at least 60 seconds in each camera for every governed aircraft class across all three worlds and independently inspect time-sampled frames for detached, duplicated, oversized, clipped, backface, or stale geometry.
  • Preserve full video, sampled frames, scene-root telemetry, and per-journey screenshots as fail-closed evidence.

Traceability

Requirements

Dependencies

Acceptance evidence

Verified delivery: ordinary rendered flight reproduced and removed the detached world-space wind-indicator geometry; exact integration validation proves one governed aircraft presentation root, zero stale roots, zero world-space indicator meshes, preserved terrain identity, and clean screenshots for all nine aircraft, four production cameras, and three worlds. 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.