Skip to main content

Choose the Flying World

Overview​

User capability

Select one supported world or terrain before flight

User

An AeroSim player

What the user can do

Select one supported world or terrain before flight

Why the user benefits

The player receives one coherent, observable capability.

User need

The player needs AeroSim to select one supported world or terrain before flight.

In scope

Select one supported world or terrain before flight

Tasks​

AEROSIM-TS-7Planning status: Done

Present and select canonical flying worlds

Each supported flying world is shown with an identifiable name and description, and one selection resolves to its canonical terrain configuration.

  • ComponentWeb Application — Pre-flight configurator
  • Depends onAEROSIM-TS-34
  • RequirementsFR-0010
AEROSIM-TS-111Planning status: Done

Propagate the confirmed world into the launch configuration

The launch configuration contains exactly the canonical world identifier and terrain configuration confirmed during pre-flight.

  • ComponentWeb Application — Pre-flight configurator to Flight shell boundary
  • Depends onAEROSIM-TS-7
  • RequirementsFR-0011, NFR-0011
AEROSIM-TS-112Planning status: Done

Load the confirmed terrain configuration for the session

The new flight session renders and collides against the world identified by the immutable launch configuration.

  • ComponentWeb Application — R3F flight scene and deterministic flight runtime
  • Depends onAEROSIM-TS-111
  • RequirementsFR-0011, NFR-0011
AEROSIM-TS-113Planning status: Done

Verify world-selection performance, resource, and browser compatibility

World listing, confirmation, and launch pass the declared timing, browser-resource, namespace-resource, and compatibility checks.

  • ComponentWeb Application — Pre-flight and flight integration test suites
  • Depends onAEROSIM-TS-112
  • RequirementsNFR-0001, NFR-0005, NFR-0006
AEROSIM-TS-123Planning status: Done

Conform flying-world selection to the approved Flight Setup design

Every supported world appears and selects through the approved Flight Setup presentation without catalogue or navigation drift.

  • ComponentWeb Application — Release 1.0.0 user journey
  • Depends onAEROSIM-TS-113
  • RequirementsFR-0010, FR-0011, NFR-0001, NFR-0005, NFR-0006, NFR-0011
AEROSIM-TS-134Planning status: Done

Integrate world selection into the new-flight journey

A player starting from Home selects one supported world before pre-flight, and the exact confirmed world remains present through summary and launch.

  • ComponentIntegrate world selection into the new-flight journey
  • Depends onAEROSIM-TS-34
  • RequirementsFR-0011

Acceptance outcomes​

  1. 01

    Each available world is identifiable before selection and resolves to one canonical terrain configuration.

  2. 02

    Launch loads exactly the world confirmed in pre-flight.

Functional requirements and measurable criteria​

FR-0010

list supported scenes

The system shall list each supported flying scene with an identifiable name and description.

Acceptance 01

Givena valid current Feature configuration and defined initial state

Whenthe relevant user action or simulation step occurs

Thenthe observable result must list each supported flying scene with an identifiable name and description

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

Acceptance 02

Givenan invalid or unsupported input at the same boundary

Whenthe system evaluates the input

Thenthe system must reject or recover visibly without publishing a misleading result

EvidenceFuture negative-path tests and browser evidence must verify explicit failure or recovery behaviour.

FR-0011

apply chosen scene

The system shall load the chosen scene for the next session.

Acceptance 01

Givena valid current Feature configuration and defined initial state

Whenthe relevant user action or simulation step occurs

Thenthe observable result must load the chosen scene for the next session

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

Acceptance 02

Givenan invalid or unsupported input at the same boundary

Whenthe system evaluates the input

Thenthe system must reject or recover visibly without publishing a misleading result

EvidenceFuture negative-path tests and browser evidence must verify explicit failure or recovery behaviour.

Non-functional requirements

Risks​

  • Risk

    Prototype behaviour may not meet the current acceptance outcomes.

Original source and prototype evidence​

Prototype and discovery boundary

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