It supplies you with the classes, functions, and utilities you need to write a simulation application, but unlike a framework, it does not provide a structure that you are required to use. For example, you will probably want to check the state of a locally-simulated entity at periodic intervals, but VR-Link does not care whether you do that using a loop (as the Listen example does (Basic VR-Link Examples)), or by using a timer or some other mechanism.

2.1.1 Multiple Layers of Access

As a VR-Link developer, you have several options for approaching application development:

Work through the protocol-independent interface, which with minimal modifications, lets you create applications that work with both HLA and DIS and shields you from many of the intricacies of the underlying protocol-specific classes and functions. Most VR-Link users take this approach.
Go below the protocol-independent interface and take advantage of the protocol-specific classes. Do this if you want to tailor your application to HLA or DIS.
Fully realize the potential of VR-Link and meet your most demanding simulation needs:
Extend VR-Link by creating new classes for HLA objects and interactions or DIS PDUs.
Use the FOM Mapper to support additional FOMs.

Regardless of how you use VR-Link, read VR-Link Concepts, The Protocol Independent Interface, and study the vrlinkExamples. If you focus on a specific simulation standard, read the protocol-specific chapters for that standard. If you want to extend VR-Link, read chapters that describe how to subclass and create your own objects and interactions.

[Home] [HLA, DIS, and Protocol Independence >>]

Table of Contents

2.1.1 Multiple Layers of Access