8.3 - The Fixed-wing Entity Behavior Model

Table of Contents

• 8.3.1 Core Elements of Fixed-wing Entities
• 8.3.2 Component Systems that Make Up a Fixed-wing Entity
  • 8.3.2.1 A Specific Example: Attack/Strike Fixed-wing Entity
  • 8.3.2.2 Systems
  • 8.3.2.3 Other Simulation Components
    • Sensors
    • Controllers
    • Actuators

This page describes how fixed-wing entities are represented in VR-Forces.

8.3.1 Core Elements of Fixed-wing Entities

Fixed-wing entities share certain common elements. A fixed-wing entity in VR-Forces is always configured with the following:

• DtFixedWingEntityStateRepository – Holds state information specific to fixed-wing entities.
• DtSimIndividualLocalEntityNetInterface – Handles network publishing of individual (platform-level) entities.

Fixed-wing entities are also typically military aircraft, and therefore are configured with a DtVrfRadio, which enables radio-like communication between entities in the same unit.

8.3.2 Component Systems that Make Up a Fixed-wing Entity

To examine the systems typically configured on a fixed-wing entity, we'll look at a specific instance, the F-16A Fighting Falcon entity. It is a representative example that includes many of the common systems and components that make up a fixed-wing entity. Differences arise between the various types of entities as a function of which particular sub-systems are configured on the vehicle, and the parameter values it is configured with.

8.3.2.1 A Specific Example: Attack/Strike Fixed-wing Entity

Defined in parameter files Fixed_Wing_Aircraft.ope and F-16A_Fighting_Falcon.entity.

The figure below shows which systems and simulation components are configured as part of an Attack/Strike Fixed-wing entity. The boxes (nodes) represent either a system of components (DtComponentSystem) or individual DtSimComponent classes. The edges connecting the boxes indicate port or port group connections between components. Data flows between components through these connections.

8.3.2.2 Systems

Major sub-elements of an entity's capabilities are organized into systems.

• Movement – models all movement behavior of fixed-wing aircraft
• Damage – models damage from direct and indirect fire.
• Maverick Missile Launcher – Air-to-ground missile launcher.
• Sidewinder Missile Launcher – Air-to-air missile launcher.
• Airborne Targetting Radar – What entities can I see?
• IFF Transponder – Manage publishing of IFF data for the entity.
• Counter Measures Launcher – Models chaff and flares launched to counter enemy missiles.
• US Fighter-Bomber Bomb Bay – Allows aircraft to drop bombs.
• Spot Report Generator – Send spot reports based on my contact list.
• Spot Report Receiver – Listen for spot reports.

8.3.2.3 Other Simulation Components

Individual DtSimComponents (not organized as part of a system) that make up the rest of entity:

Sensors

• DtUnderFireDeterminationSensor – Am I under fire?

Controllers

• DtScriptMultiTaskController – The controller for scripted tasks.
• DtScriptReactiveTaskController – The controller for reactive scripted tasks.
• DtOrganizationController – Maintain my position in the aggregate organizational hierarchy.
• DtContactFusionController – Fuse contact information from various sources into a single list.
• DtLocalEntitySetController – Respond to a DtSetDataRequest, such as set location, set heading.
• DtFixedWingEmbarkationController – Support entity's ability to embark on other entities.
• DtSendRadioMessageController – Send text or task messages through the radio.

• DtTargetSelectionController – Choose target for weapon system.

Actuators

There are no actuators configured as part of this entity.

[<< The Human Entity Behavior Model] [Home] [Top of Page] [The Rotary-wing Entity Behavior Model >>]