VR-Forces simulates individual entities and units.
Entities are simulated objects (DtVrfObjects) that correspond approximately to HLA RPR FOM and DIS platforms and lifeforms. In VR-Forces, units are modelled as a single simulation object that represents an organizational structure (an aggregated unit) or as simulation objects that represent an organizational structure (a disaggregated unit). The members of a disaggregated unit can be individual entities or smaller units.
VR-Forces uses the following mechanisms to simulate simulation objects. These mechanisms are discussed in detail in this chapter, and in some cases, in later chapters in this manual.
-
Highly parameterized models, which allow you to change the characteristics of simulation objects. VR-Forces Users Guide describes how to set parameter values in the object parameter database. The important point to understand as a developer, is that when you create new components, you need to consider whether or not you want the components to have parameters that users can set in the object parameter database, and if so, design the components accordingly. For more information, please see 4.6 - State Repositories for simulation objects.
-
A component architecture and Component Manager. To simulate simulation object behaviors and carry out tasks, VR-Forces uses a component architecture similar to that used in many robotics applications. The Component Manager creates, connects, and maintains the lists of components. Please see 4.2 - Components and The Component Manager.
-
The Organization Manager. The Organization Manager maintains a simulation object's place in the organizational hierarchy. Please see 4.5 - The Organization Manager.
-
Process state repositories and the Process State Repository Manager. Process state repositories maintain the state of a simulation object. When you save or checkpoint a scenario, the information in the process state repository is written to the order of battle file. Please see 4.6 - State Repositories for simulation objects.
-
The Task Manager. The Task Manager does the processing and message handling required to execute a task. It does not execute specific tasks. Please see 4.8 - The Task Manager.
-
Resources and the Resource Manager. The Resource Manager tracks simulation object resources, such as ammunition, fuel, and so on. Please see 4.10 - The Resource Manager
-
The Plan Manager. Each simulation object has a Plan Manager to manage its plan. For details, please see 13 - Plans.
-
Radios. VR-Forces simulates a radio-like communication system for sending tasks to simulation objects and receiving reports from simulation objects. Each simulation object has a radio. For more information about radios, please see 11 - Simulation Object Communication.
4.1.1 The Basic Structure of an Simulation Object
As stated previously, all simulation objects are DtVrfObjects. VR-Forces does not use derived classes to distinguish different types of simulation objects, such as ground vehicles, missiles, and so on. They are distinguished from each other and from other objects by the state repository and other subcomponents that get created when they are instantiated. An simulation object is expected to have the following subcomponents:
The particular subcomponents that get created for a simulation object are determined by the subcomponents section of the entity’s parameter block in the object parameter database.
[Home] [Top of Page] [Components and The Component Manager >>]
