VR-Forces 4.3.1 Class Documentation: VR-Forces 4.0.4 to 4.1 API Changes

VR-Forces has the following changes to its APIs:

Tasks, Sets and Reports now use a string as a type identifier instead of an integer.
Simulation engine:
- The simulation engine now supports streaming and paging of feature data. The API has been updated to add this support. (For details, please see section 15.6 in VR-Forces Developers Guide.)
- DtSimComponent now has a virtual preFirstTickInit() method, called before the first call to tick().
GUI:
- The DtNetworkMessageCallbackManager class was renamed to DtGuIThreadNetworkCallbackManager.
- For attributes and capabilities settings, the attributes.mtl and capabilities.mtl files are no longer used. The values are read from the SISO .xml file. All items should now be SISO compliant.
- dis-entity-types.csv is no longer used in the Entity Editor or //front-end for selecting entity types. The SISO .xml file is now used.
- Many GUI elements are now available to create via the DtVrfTaskSetVariableWidgetManager. Any parameter that is added to a scripted tasked is created using this factory. The list of GUI elements that can be created are in vrfScriptedTasks.h.
- Task, Set and Create menu configuration is now initially set from configurations found in the DtVrfSimulationManager. The menuManipulation example has been modified to show the new usage.

The VR-Vantage Control Toolkit has the following changes:

View control messages are sent using DtDataInteractions. DtDataInteractions provide a receiverId field. The recieverId's siteId and applicationId are now used when processing view control messages. If these match the siteId and applicationId of the connection receiving the message, the message is processed. The message is also processed if siteId and applcationId are both -1's (wildcards). For backwards compatibility, siteid/applicationId of 0/0 is also processed.
Some view control messages control observer-specific settings. These messages now let you specify the name of an observer mode to modify. If no observer mode is specified, then these commands affect all observer modes currently in use. If an observer mode is specified, then only that observer mode is affected.