2.6 - Managing Information about Events

Table of Contents

• 2.6.1 Sending Local Interactions
• 2.6.2 Receiving Remote Interactions

We use the term interaction to refer to events such as the firing of a munition, detonation of a munition, or collision of entities.

VR-Link manages interactions through classes derived from DtInteraction. Usually, the name of an interaction class is based on the interaction type, for example, the class for a fire interaction is DtFireInteraction.

2.6.1 Sending Local Interactions

For locally-defined interactions, such as firing a munition from a locally simulated entity, you create an instance of the appropriate interaction class, set its values, and send it through the exercise connection. For more information, please see 4.3.1 Sending Interactions.

2.6.2 Receiving Remote Interactions

A VR-Link application receives notification of a remote interaction through its exercise connection. The function DtExerciseConn::drainInput() causes VR-Link to read and process input. The local application reacts through the use of callback functions.

There are no built-in functions for reacting to remote interactions. You must write a callback function for each type of interaction that you want to respond to and register the callback function with the interaction class. When your application is notified that an interaction event has occurred, it passes the interaction type and affected object to your callback function, which executes whatever code you have written. For information about callbacks, please see 2.7.3 Using Callbacks.

Note

Interactions are transient, that is, they are deleted by VR-Link immediately after the last callback function registered for the interaction is called.

[<< Managing State Information] [Home] [Other Simulation Concepts >>]