 |
VR-Forces Developer's Guide
|
All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Groups Pages
|
VR-Forces Developer's Guide
|
The diagrams on this page illustrate how various subsystems work together to specify potential targets, detect targets, and develop a target list.
The following figure is a key to the diagrams:
Based on input from its weapons systems, and the spot report generator system (if it is active), a sensor system determines what simulation objects it should try to detect.
The sensor system interacts with the physical world to detect simulation objects. The information from the physical world modifies the absolute signatures of the detected simulation objects to return an apparent signature. The apparent signature is input to the combat identification level table to determine the detection level of the detected simulation objects. A simulation object cannot attack until the detected simulation object reaches the "Identified" level of detection.
The DtContactFusionController provides a means for collating sensor data from multiple sources into one merged, easily accessible list. It has a DtSensorContactListMultiInputPort. This multiple input port allows the controller to gather sensor contacts from multiple sensors or from spot reports. It runs through each incoming list and adds new contacts or merges existing contacts. When a merge occurs, the contact with the highest detection level is used for non time-sensitive information, like force type and object type. For time sensitive information, like position and velocity, the contact that is the most recent is used. The controller's fused contact list is just a pointer to an entity's state repository objectContactList. This ensures the list stays current. Having the list in the state repository also allows quick access for any component on the entity. When the list is updated with new data, stale data is removed.
