Skip to main content

Introduce the 3D Rendering Runtime

Overview​

User capability

Establish Three.js and React Three Fiber for browser flight rendering

User

The AeroSim delivery team

What the user can do

Establish Three.js and React Three Fiber for browser flight rendering

Why the user benefits

The capability becomes an explicit, testable project boundary.

User need

The delivery team needs the AeroSim solution to establish Three.js and React Three Fiber for browser flight rendering.

In scope

Establish Three.js and React Three Fiber for browser flight rendering

Tasks​

AEROSIM-TS-25Planning status: Done

Establish the React Three Fiber scene lifecycle

The Web Application owns one explicit React Three Fiber canvas and scene lifecycle with isolated low-level Three.js access.

  • ComponentWeb Application — R3F flight scene
  • Depends onAEROSIM-TS-13
  • RequirementsFR-0052, NFR-0007
AEROSIM-TS-26Planning status: Done

Render the representative flight scene

A representative aircraft, terrain surface, environment, primary camera, and secondary camera render through React Three Fiber.

  • ComponentWeb Application — R3F scene composition
  • Depends onAEROSIM-TS-25
  • RequirementsFR-0052, NFR-0007
AEROSIM-TS-27Planning status: Done

Verify rendering lifecycle and browser runtime health

Automated rendering and browser smoke tests prove the representative scene mounts, updates, switches cameras, disposes resources, and emits no runtime errors in the production build.

  • ComponentWeb Application — rendering verification harness
  • Depends onAEROSIM-TS-26
  • RequirementsFR-0052, NFR-0007
AEROSIM-TS-139Planning status: Done

Onboard and render the three selected world scenes

Training Airfield, Coastal Range, and Mountain Valley each render the user-selected scene source as a visibly distinct, governed environment in the active flight viewport.

  • ComponentOnboard and render the three selected world scenes
  • Depends onAEROSIM-TS-13
  • RequirementsFR-0052
AEROSIM-TS-175Planning status: To Be Released

Replace Coastal Range with the approved documentation terrain model

The existing Coastal Range world renders the exact documentation model with consistent metre scale, bounds, spawn and collision representation.

  • ComponentCoastal Range terrain asset and world-space integration
  • Depends onAEROSIM-TS-139
  • RequirementsFR-0052

Acceptance outcomes​

  1. 01

    A representative aircraft, terrain, environment, and camera scene renders through React Three Fiber.

  2. 02

    Scene lifecycle and low-level Three.js ownership are explicit and production build emits no browser-runtime errors.

Functional requirements and measurable criteria​

FR-0052

Introduce the 3D Rendering Runtime

The system shall establish Three.js and React Three Fiber for browser flight rendering.

Acceptance 01

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

Whenthe primary capability path is completed

ThenA representative aircraft, terrain, environment, and camera scene renders through React Three Fiber

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

Acceptance 02

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

Whenthe continuation or repeat path is completed

ThenScene lifecycle and low-level Three.js ownership are explicit and production build emits no browser-runtime errors

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

Non-functional requirements

Risks​

  • Risk

    Partial introduction could leave an ungoverned or duplicated technical boundary.

Original source and prototype evidence​

Prototype and discovery boundary

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