Simulated objects are represented by makVrv::DtSimState classes.

These classes contain all of the information required to display an object in your scene. This includes the name of the object, its position, velocity, and heading, and any other appearance tags. These objects correlate to a DtVrfObject in the VR-Forces back-end.

DtSimState objects are easily reachable by accessing their respective makVrv::DtStateViewCollection classes. DtStateViewCollections are in turn, accessible through the global singleton DtVrfStateViewCollectionManager. You can access them by simply calling their instance in that class. For example, if you want to access all spot report objects, you can access the DtVrfStateViewCollectionManager::instance(de).spotReportStateView. Each collection object contains a map of all objects, as well as signal functions that trigger when an object of that type is created or destroyed. Some objects can be represented in multiple collections at the same time. DtStateViewCollections do not contain a list of DtSimState objects directly. Instead, they contain a list of DtStateViews, which represents the view of a specific state. You may access the DtSimState by simply calling the state() class in DtStateView.

Each type of object has its own class and its own collection that it derives from. The following types of objects and collections are currently included in the VR-Forces front end:

DtVrlinkSimulatedBaseStateViewCollection. Contains a list of all VR-Link objects currently simulated
DtVrfSimulatedEntityStateViewCollection. Contains a list of all simulation objects in the current exercise.
DtVrfObjectDataStateViewCollection. Contains a list of all data objects in the exercise.
DtEnvironmentStateViewCollection. Contains a list of all environmental objects in the exercise. This includes waypoints and areas.
DtSpotReportStateViewCollection. Contains a list of all spot reports. Spot reports represent a possible simulation object location but not the simulation object itself.

For an example on how to use collections, please see the Entity List example.