Skip to main content

AEROSIM-TS-177

Project task

Complete HUD design conformance

The player reads complete, coherent flight instruments through an outlined surface-free HUD in Chase, Cockpit, Orbit and Fly-by without losing current controls or later approved layout improvements.

AEROSIM-TS-177Canonical ID TASK-0177
Verified flow state
Unverified
Owner
AeroSim Architecture and Delivery
Component
Active-flight HUD instrument presentation
Repository
corp-v1-aerosim/corp-v1-aerosim

Delivery scope

Complete the missing arched airspeed gauge, navigation scale, altitude tape and combined altitude/vertical-rate presentation with outlined surface-free readability across Chase/Cockpit/Orbit/Fly-by. Preserve metric altitude and vertical-rate, matching Camera/Menu buttons beside each other, compact right-side Throttle/Pitch/Bank/Yaw/Flaps input readouts, the full-viewport scene and retained editable controls. Distinguish command inputs from physical aircraft attitude and read authoritative flight state.

Implementation contract

Implementation artifacts

  • applications/web/src/flight/hud/MinimalEdgeHud.tsx
  • applications/web/src/flight/views/ChaseFlightView.tsx
  • applications/web/src/flight/views/ChaseFlightView.css
  • applications/web/src/styles.css

Inputs

  • MartynasP requested exactly two corrective backlog Tasks and Release 2.0.0 planning inclusion: https://discord.com/channels/1518726359512387766/1537544173366943886/1555105892108607509
  • Bounded source discrepancy report, not visual/UAT acceptance: https://discord.com/channels/1518726359512387766/1537544173366943886/1555105221502570566 and https://discord.com/channels/1518726359512387766/1537544173366943886/1555105221179478079
  • Application source inspected by Scope: https://gitea.lego-cloud.eu/corp-v1-aerosim/corp-v1-aerosim/src/commit/9bdc1a093b0f8ae306708bea591f898dfe6adb20/applications/web/src/flight/hud/MinimalEdgeHud.tsx — text instruments and separate ALTITUDE/VERTICAL do not implement the complete requested gauge/scale/tape presentation. ChaseFlightView.tsx shares that HUD across camera IDs; this is not a visual verdict or full missing-capability audit.
  • Corrective provenance: TASK-0125 and TASK-0174 retain their exact historical states and append-only evidence. Preserve the later compact controls and Camera/Menu correction recorded in TASK-0174, including https://discord.com/channels/1518726359512387766/1537227683191197807/1554430066799280190.

Outputs

  • Complete arched airspeed gauge, navigation scale, altitude tape and combined metric altitude/vertical-rate display from authoritative flight state.
  • Shared readable outlined surface-free instrument presentation in all four camera modes with existing controls and Camera/Menu arrangement intact.
  • Exact-design and candidate-bound UAT evidence distinguishing visual conformance from Delivery unit/static/build results.

Failure boundaries

  • Fail if gauges/scales/tapes remain text-only substitutes, use a competing flight-state source, or report command input as physical attitude.
  • Fail if old imperial Penpot sample values or obsolete camera placement replace later approved metric units and adjacent Camera/Menu buttons.
  • Fail if HUD backgrounds obscure the scene, instruments overlap or clip, viewport coverage shrinks, or editable controls/keyboard bindings disappear.

Excluded scope

  • Registration and planning only; no implementation, Focus admission, Architecture allocation, deployment, UAT acceptance or release approval is granted.
  • No physics or asset redesign, new Feature, reopening of historical Tasks or rewriting of their evidence.

Verification steps

  • Pending before implementation: UI/UX must retrieve the recorded AEROSIM-UIUX-REL-1.0.0 Penpot file/page at baseline revision 6608, inspect UIUX-100-CHASE and UIUX-100-CAMERAS frames, and reconcile later approved metric units, adjacent Camera/Menu and compact right-side inputs. Registration does not independently verify current design revision or parity.
  • Inherited prerequisite TASK-0096 follows the existing parent Feature dependency on AEROSIM-FT-3; correction-specific sequencing remains for Architecture review.
  • Pending Architecture readiness: verify correction derivation, requirements, dependencies, release allocation and implementation gate before Focus admission; no readiness or allocation is inferred.
  • Delivery adds RED/GREEN unit checks for authoritative gauge/tape values, metric formatting, combined altitude/vertical-rate semantics, command-input distinction and retained controls; run required static/build checks.
  • UAT compares the verified design with ordinary flight in Chase/Cockpit/Orbit/Fly-by on one exact deployed candidate, including normal/warning/invalid values, bright and dark scenery, and supported wide/narrow/short viewports.
  • UAT proves full viewport, outline readability, no clipping or overlap, adjacent matching Camera/Menu and ordinary editable/keyboard control behavior; record visual evidence independently of source inspection.

Traceability

Dependencies

Acceptance evidence

Required future evidence: UI/UX revision verification, complete interaction/design checks and independent candidate-bound UAT. The owner requested corrective backlog registration; source discrepancies do not establish visual/UAT acceptance or invalidate historical completion evidence.

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.

Planning boundary​

Release 2.0.0 planning board inclusion records the Scope owner's backlog request, not Architecture allocation, Focus admission, implementation approval or release acceptance. UI/UX revision verification and Architecture readiness remain pending. Requirement links identify existing corrective context, not a new approved solution package.

Corrective provenance​

Historical Task states and evidence remain unchanged: