Multiple Versions of VR-Forces in the Same Federation

Multiple versions of VR-Forces can be connected to the same HLA federation or DIS exercise, however they will treat each other as if they are non-VRF applications. This is behavior similar to using the session ID startup parameter and running VR-Forces with two sessions. All standard HLA/DIS data will be passed between versions, but any messages specific to VR-Forces include the VR-Forces version in their header, and are ignored by VR-Forces instances that do not match that version.

The expected behavior is:

• VR-Forces GUI from one version can only load, save, play, and pause scenarios on VR-Forces sim. engines from the same version.

• Entities published by any version of VR-Forces display in all VR-Forces GUIs.

• The sim. engines for all versions of VR-Forces react to entities published by any version of VR-Forces (detected by sensors, fired at, and so on).

• Entities published by one version of VR-Forces can be tasked only by VR-Forces GUIs from the matching version.

• A scenario saved from one VR-Forces GUI includes entities that are published by VR-Forces sim. engines of the matching version.

Possible issues:

• The Global Environment object is part of the HLA/DIS standard data (as of VR-Forces 5.1) and therefore will be passed across versions. Because of this, you should disable the publishing of the Global Environment object in one of the VR-Forces scenarios so that there will not be two of them on the network. This can be done when creating a new scenario using the Advanced tab of the Scenario Properties dialog box.

  Open

  

• Starting in VR-Forces 5.2, this option is not available to existing scenarios, and you should use the Simulation → Load Distribution dialog to remove any unwanted global weather or terrain objects from scenarios.

  Open