Actions
This page drafts a new feature not implemented at the time of writing (12-2025). It shall aid the planing and development of the feature.
Introduction
FlightGear is a very flexible and modular system. Often there is more than one way to control a certain aspects of the simulator or the simulated aircraft.
One important element are bindings which are used in several places to link some event (key pressed, joystick button, click to 3D cockpit element, ...) to a command (e.g. pause the simulation, retract landing gear, ...).
Definition
Actions are essentially a named binding, with some extra information + state:
- can be enabled / disabled
- have a unique identifier, e.g. 'toggle COM1 frequency'
- Can be modified, optionally (so aircraft can redefine what a standard action such 'toggle active COM frequency' does in their cockpit)
- can have UI prompts (description / tooltip text)
This feature is targeted for next, but could potentially be back-ported, since it needs to be done backwards compatibly anyway.
https://gitlab.com/groups/flightgear/-/epics/18
Use cases
- Places, where <binding> is already in use like
- Mapping of input events from hardware devices like keyboard, mouse, joystick, yoke, rudder pedals, throttle quadrant, MCDU, custom made cockpit hardware ...
- 3D cockpit elements ("pick animation")
- Multi-player events