5.1 - Introduction to the HLA-Specific Interface

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.

Note

If your application is intended for both DIS and HLA, or if you plan to add this support in the future, enclose your HLA-specific code within a preprocessor directive pair to ensure that it will not be compiled when you try to build for DIS:

#if DtHLA
   #if DtHLA_1516
      #if DtHLA_1516_EVOLVED
         // 1516 evolved specific.
      #else
         // 1516 specific
      #endif
   #else
      // 1.3 specific
   #endif
#endif 

[Home] [Interacting Directly with the RTI >>]