Internally, LiteFlite® is based on an extensible, plug-in architecture.  The LiteFlite® SDK is an optional component providing developers with the C++ elements needed to create custom extensions to the simulation.  This SDK provides developers object-oriented direct access to LiteFlite®’s simulation primitives, its DIS/HLA integration, and, the rich visual system provided by AAcuity® Image Generators.  With the SDK, developers can integrate other simulation code into LiteFlite®, developing custom LiteFlite® plug-in object models for these plug-in classes:

• Aircraft flight models and Space vehicle models
• Avionics systems – radio transceivers, radar, IFF
• Ordnance and Weapons Systems
• Sensor systems
• Engines
• Cockpit instruments – include support for GL Studio® authored instruments

• Ground stations (for spacecraft, UAVs and MAVs)

The architecture also provides support for creating generalized Extension plug-in classes.  These classes are used to add special features and functions to the simulation that are outside of the capabilities listed above.  Note that all of the core LiteFlite® simulation features are developed using the same SDK available to customers.

Wherever possible, LiteFlite® employs user-editable tables to drive its operation.  This approach make LiteFlite® adaptable to the widest range of applications.  Examples of configurable data files include:

Aircraft -- Flyable aircraft are defined using NASA-accepted parametric information.  Aerodynamic coefficients, thrust, mass and landing gear properties are all assignable in a text file.

Stores layouts – munitions load out is table driven.

EO Pod Capabilities – Sensor properties such as the sensor type – visual spectrum, II, or IR – field-of-view, magnification steps are all controlled through editable parameters specific to a given vehicle.  Operational characteristics of the turret include platform range of motion and rate limits are modeled.

DIS / HLA entity type to visual model mapping – Special models required for a given task or exercise are easily added.

Weapons Effects – DIS / HLA munitions-types can be mapped to specific damage effects and visual signatures (explosions and smoke)

Scenarios – LiteFlite® “scene” files are used to define the setting for a given exercise.  Terrain database, time-of-day and weather conditions can be pre-established using the scene file.  Drone aircraft as well as ground-based targets can be configured in a scene file.