 |
VR-Link C# API Documentation
|
All Classes Namespaces Files Functions Variables Enumerations Enumerator Properties Events Macros Pages
|
VR-Link C# API Documentation
|
Most VR-Link users will find that the protocol-independent interface meets all of their needs.
However, if you are developing only for HLA, you may want to work with the HLA-specific classes, rather than generic classes. This chapter describes the HLA-specific interface. 6 - FOM Agility and 7 - The VR-Link Code Generator go into greater detail in explaining how to use VR-Link with FOMs other than the RPR FOM.
VR-Link’s HLA-Specific Interface provides a robust and flexible API for integrating distributed simulation applications with High Level Architecture (HLA) federations. The interface abstracts the complexities of HLA standards, supporting multiple versions including IEEE 1516-2000, IEEE 1516-2010 (HLA Evolved), and HLA 4, while maintaining compatibility with various RTI implementations.
The HLA-Specific Interface enables applications to join federations, publish and subscribe to object and interaction classes, manage attribute updates, and synchronize simulation time. It provides mechanisms for creating and managing federates, handling FOM and MIM modules, and configuring federation execution parameters such as federate name, type, and FED file location. The API supports dynamic discovery and removal of objects, attribute reflection, and interaction delivery, ensuring seamless communication between federates.
Configuration of HLA-specific parameters is achieved through dedicated config variables and XML/MTL files, allowing users to specify RTI settings, FOM modules, local settings designators, and advanced options such as advisory switches and class/object update requests. VR-Link’s interface also facilitates time management, save/restore operations, and exception handling for RTI version mismatches.
By leveraging VR-Link’s HLA-Specific Interface, developers can rapidly build interoperable simulation systems that conform to HLA standards, with minimal effort required for protocol integration and configuration. The interface is designed for extensibility, supporting both basic and advanced federation features, and is tightly integrated with VR-Link’s protocol-independent configuration mechanisms for unified application setup.