VR-Link API Documentation for DIS
 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Friends Macros Groups Pages
1.3 - Simulation Standards Supported

Table of Contents

1.3.1 Overview

VR-Link provides interoperability between distributed simulation applications by supporting multiple industry-standard protocols. This enables seamless communication and data exchange across diverse simulation environments.

1.3.2 Supported Standards

VR-Link provides comprehensive support for both HLA and DIS simulation standards. For detailed information about the specific versions supported in your release, please consult the official release documentation. Additionally, you can check the MAK Product Specifications page for platform and protocol support updates.

1.3.2.1 Distributed Interactive Simulation (DIS)

1.3.2.2 High Level Architecture (HLA)

For a brief introduction to DIS and HLA, please see 2.2 - HLA, DIS, and Protocol Independence.

1.3.2.3 NATO Standardization Agreements (STANAG)

1.3.3 Configuration

VR-Link provides flexible configuration options for setting up simulation exercises. Configuration can be performed using XML configuration files, such as MAKOne-2025-Config.xml, or programmatically via the VR-Link API. The configuration file allows users to specify protocol versions (DIS, HLA), network interface and port settings, federation and federate names, FOM/FED/FDD file references, and time management options. These parameters ensure that each federate is correctly initialized and able to participate in the distributed simulation.

When configuring an exercise connection, users should ensure that all federates use compatible protocol versions and FOMs. The configuration file can be customized to match the requirements of the simulation environment, including advanced options such as time synchronization, data encoding, and federation management. For more complex scenarios, VR-Link supports multiple FOM modules and custom mappings via the FOM Mapper.

Programmatic configuration is also supported, allowing developers to set connection parameters directly in code. This is useful for dynamic environments or automated deployments. The VR-Link API provides methods to set protocol type, network settings, federation details, and FOM file references, giving users full control over the exercise connection setup.

Proper configuration is essential for interoperability and performance. Users are encouraged to review the configuration file and API documentation to ensure all parameters are set appropriately for their use case.

1.3.4 Extensibility

1.3.5 References

1.3.6 HLA Version Compatibility

VR-Link supports multiple versions of the High Level Architecture (HLA) protocol:

1.3.6.1 Interoperability Between HLA Versions

1.3.6.2 Migration and Upgrades

1.3.6.3 Limitations

1.3.6.4 Recommendations

1.3.7 VR-Link Interoperability and Configuration

1.3.7.1 Interoperability Between HLA 1516 Evolved and HLA 4

VR-Link supports interoperability between federates using HLA 1516 Evolved (IEEE 1516-2010) and HLA 4 (IEEE 1516-2025) standards. This enables mixed simulation environments to communicate and exchange data, even when federates are based on different HLA protocol versions. Interoperability is achieved through compatible FOMs, standardized object models, and VR-Link's bridging capabilities. Users should ensure that FOMs and federation agreements are aligned for successful data exchange between HLA 1516 Evolved and HLA 4 federates. For more information, refer to 5.11 - Interoperability Between HLA 1516 Evolved and HLA 4 Federates.

1.3.7.2 HLA Configuration File Formats

1.3.8 VR-Link API: Creating an Exercise Connection

The VR-Link API provides a straightforward mechanism for creating an exercise connection using the information specified in the configuration file. The typical workflow is: 

1. Load the configuration file (e.g., MAKOne-2025-Config.xml).
2. Parse connection parameters (protocol, network, federation, FOM, etc.).
3. Initialize the VR-Link API with these parameters.
4. Join the exercise (federation) and begin simulation data exchange.

The API abstracts protocol-specific details, allowing users to focus on simulation logic rather than low-level networking or configuration management. For more details, see 4.2 - Connecting to Exercises.

1.3.9 HLA FOM Support

VR-Link provides extensive built-in support for the Real-Time Platform Reference FOM (RPR FOM). (For version information, please see release documentation.)

The RPR FOM is a reference FOM developed by the SISO-sanctioned RPR FOM Standards Development Group, which consists of representatives from many companies that used the DIS protocol in the pre-HLA era.

The goal of the RPR FOM is to facilitate a priori interoperability (to about the extent we had in DIS) among HLA simulations that choose to use it. In other words, if you use the RPR FOM (either as is, or with your own extensions), then you know that you will be able to interoperate with anyone else who chooses to use this FOM. Another advantage of using the RPR FOM is that many simulation tools, including those offered by MAK Technologies, support this FOM.

1.3.9.1 RPR FOM Versions Supported

1.3.9.2 NETN FOM Versions Supported

1.3.9.3 Supported NETN FOMs

The following NETN FOM modules are supported and included in the default configuration:

1.3.9.4 MAK-Extended FOM Modules

The following MAK-Extended FOM modules are also supported:

Note
All the above FOM Modules are included in the VR-Link product installation. Each version of VR-Link is shipped with the compatible version of these files, where x denotes a verison number.

1.3.10 Default FOM Versions in VR-Link

By default, VR-Link applications and the DtVrlApplicationInitializer class use the following values as specified in the DtExerciseConnConfig constructor:

These defaults can be overridden by specifying different values in the configuration file or via the API. They are chosen to provide a baseline for interoperability and compatibility.

1.3.10.1 Using a Different FOM Version

Users can specify a different FOM version in their configuration file or via the VR-Link API. To use a different FOM, update the FOM file reference in your configuration XML or set it programmatically:

1.3.10.1.1 Example (XML):

<connectionConfig>
<settings>
<hlaConnection>
<fedFileName value="RPR_FOM_v2.0_1516-2010.xml"/>
<rprFomVersion value="2.0"/>
<rprFomRevision value="2"/>
</hlaConnection>
</settings>
</connectionConfig>

1.3.10.1.2 Example (API):

DtVrlApplicationInitializer initializer;
initializer.setFedFileName("RPR_FOM_v2.0_1516-2010.xml");
initializer.setRprFomVersion(2.0);
initializer.setRprFomRevision(2);

The DtVrlApplicationInitializer class also accepts FOM file parameters, allowing you to override the default FOM version at initialization.

1.3.11 Support for FOM Agility

VR-Link provides built-in support for the Real-Time Platform Reference FOM (RPR FOM), enabling out-of-the-box interoperability for most simulation environments.

For users with custom FOMs, VR-Link can be configured to work with other FOMs by using the FOM Mapper. The FOM Mapper allows you to define mappings between VR-Link's protocol-independent interface and the objects, interactions, parameters, and attributes defined in your custom FOMs.

This approach enables FOM agility, allowing VR-Link to adapt to new or evolving FOMs without requiring changes to the core API. For more information, see 6 - FOM Agility.

VR-Link has a FOM Mapper for the MATREX FOM. For details on MATREX FOM or to request additional FOM Mapper capabilities, please contact a MAK salesperson.

Document ID: Generated on Thu Oct 16 00:12:25 EDT 2025 from SVN revision 280738
Copyright © 1992-2025 MAK Technologies. All Rights Reserved (www.mak.com)