Skip to main content

Experience Aircraft Motion Produced by Flight Forces

Overview​

User capability

Translate controls and aircraft state into continuous force-driven motion

User

An AeroSim player

What the user can do

Translate controls and aircraft state into continuous force-driven motion

Why the user benefits

The player receives one coherent, observable capability.

User need

The player needs AeroSim to translate controls and aircraft state into continuous force-driven motion.

In scope

Translate controls and aircraft state into continuous force-driven motion

  • StatusProposed
  • OwnerAeroSim Scope (proposed; not accepted)
  • Parent EpicAEROSIM-EP-3
  • Depends onNone

Tasks​

AEROSIM-TS-1Planning status: Done

Implement the normalized flight-force evaluator

Each fixed simulation step produces lift, drag, thrust, gravity, and net force/moment values from validated bounded gameplay parameters.

  • Component@corp-v1-aerosim/flight-core — flight force model
  • Depends onNone
  • RequirementsFR-0001
AEROSIM-TS-73Planning status: Done

Integrate aircraft state at the fixed simulation step

Net forces and moments advance aircraft position, velocity, and attitude continuously and reject invalid state transitions.

  • Component@corp-v1-aerosim/flight-core — fixed-step aircraft integrator
  • Depends onAEROSIM-TS-1
  • RequirementsFR-0002
AEROSIM-TS-74Planning status: Done

Build the governed cross-browser motion-trace verifier

Identical builds, initial states, timed inputs, fixed timesteps, and seeds produce equivalent governed motion traces across every certified browser.

  • ComponentWeb flight runtime — deterministic trace recorder and comparator
  • Depends onAEROSIM-TS-73
  • RequirementsNFR-0002, NFR-0006, NFR-0009
AEROSIM-TS-75Planning status: Done

Verify flight-runtime timing and resource budgets

The force-driven motion path satisfies explicit simulation-step, frame-time, CPU, and memory budgets under representative governed traces.

  • ComponentWeb flight runtime — performance and resource budget harness
  • Depends onAEROSIM-TS-74
  • RequirementsNFR-0001, NFR-0005
AEROSIM-TS-154Planning status: Done

Unify rendered flight state, telemetry, warnings, and recovery

Rendered motion, telemetry, warnings, initial state, boundary/collision recovery, and explicit restart have one authoritative state relationship with no unsynchronized dual-state behavior or ambiguous uncommanded reset.

  • ComponentWeb Application — authoritative flight-state relationship
  • Depends onAEROSIM-TS-75
  • RequirementsFR-0002
AEROSIM-TS-158Planning status: Done

Replace autonomous flight motion with pilot-authoritative dynamics

A neutral aircraft remains in a bounded, trimmable state and ordinary keyboard commands produce directional aircraft responses instead of an autonomous climbing turn.

  • ComponentWeb Application — authoritative flight physics and pilot controls
  • Depends onAEROSIM-TS-154
  • RequirementsFR-0002
AEROSIM-TS-173Planning status: To Be Released

Correct hidden terminal flight state after automatic recovery

A concluded flight is visibly terminal even when the asynchronous recovery decision shares the last physics step and recovery count.

  • ComponentWeb authoritative flight recovery projection
  • Depends onAEROSIM-TS-158
  • RequirementsFR-0002

Acceptance outcomes​

  1. 01

    Aircraft motion changes continuously with modeled lift, drag, thrust, gravity, attitude, and player input.

  2. 02

    The same initial state and timed input sequence produces the same motion trace within the defined tolerance.

Functional requirements and measurable criteria​

FR-0001

compute flight forces

The system shall calculate lift, drag, thrust, and gravity for each supported simulation step.

Acceptance 01

Givena valid current Feature configuration and defined initial state

Whenthe relevant user action or simulation step occurs

Thenthe observable result must calculate lift, drag, thrust, and gravity for each supported simulation step

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-0002

advance aircraft motion

The system shall advance aircraft position, velocity, and attitude from net force and moments.

Acceptance 01

Givena valid current Feature configuration and defined initial state

Whenthe relevant user action or simulation step occurs

Thenthe observable result must advance aircraft position, velocity, and attitude from net force and moments

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.