4.4 - Working with Entities

VR-Link provides many classes that help inform the exercise about the state of your locally simulated entities and other objects, and inform your application about the state of remotely simulated entities and other objects.

These classes include:

• DtObjectPublisher and its subclasses, for example, DtEntityPublisher, send updates to the exercise.
• DtReflectedObjectList and its subclasses, for example, DtReflectedEntityList, keep track of remote objects.
• DtReflectedObject and its subclasses, for example, DtReflectedEntity, represent a single remote object.
• DtStateRepository and its subclasses, for example, DtEntityStateRepository, encapsulate an object's state.

In discussing how to manage objects using publishers, reflected object lists, reflected objects, and state repositories, we will focus on the classes used to manage entities – the most common kind of object in most exercises. Our concept of entities reflects the DIS and RPR FOM concept. Entities include vehicles, life forms, and most other types of real-world objects that have a position in space.

Publishers, reflected object lists, reflected objects, and state repositories exist in VR-Link for other types of objects as well, including aggregates, emitters, transmitters, designators and receivers. For information about managing these other types of objects, please see 4.8 - Working with Other Types of Objects.

[<< Working with Interactions] [Home] [Working with Locally Simulated Entities >>]