![]() |
VR-Forces 4.8 Class Documentation
|
Missiles are simulated as platform-level entities in VR-Forces.
The missile model is used to represent various categories of missiles, such as:
Missiles are typically fired from a launcher, a behavior model subsystem configured as part of the firing entity.
Missiles in VR-Forces share certain common elements. A typical missile in VR-Forces is always configured with the following:
Missiles also share many of the same systems and simulation components (controllers and actuators). To examine the systems typically configured on a missile, we'll look at a specific instance of a missile, the TOW missile. Differences arise between the various types of entities as a function of which particular sub-systems are configured on them, and the parameter values it is configured with.
Defined in parameter files Missile.ope and BGM-71_TOW_Missile.entity.
The figure below shows which systems and simulation components are configured as part of a TOW2 missile. The boxes (nodes) represent either a system of components (DtComponentSystem) or indivdiual DtSimComponent classes. The edges connecting the boxes indicate port or port group connections between components.
Individual DtSimComponents (not organized as part of a system) that make up the rest of entity:
There are no sensors configured as part of a missile entity.
There are no actuators configured as part of a missile entity.
[The Subsurface Entity Behavior Model >>] [Home] [Top of Page] [The Aggregate Entity Behavior Model >>]