VR-Link Capabilities

VR-Link is an object-oriented C++ toolkit that developers use to quickly and easily build interoperable HLA, and DIS compliant simulation applications.

Learn all about VR-Link by clicking through the tabs below or download the VR-Link Capabilities document.

VR-Link is an object-oriented C++ toolkit that simulation developers use to quickly and easily build HLA, and DIS compliant applications. It provides a set of libraries that implement a stable, consistent, and documented API (Application Programmer's Interface) above the various protocols - an SDK (Software Developer's Kit) for interoperability. When you link your application you simply pick a protocol specific library to use. To use a different protocol, just relink your application. When you use VR-Link, your developers are free to concentrate on the specific goals of your project, rather than spending their time worrying about the details of networking protocols. A few calls to VR-Link's functions replace thousands of lines of code that you would otherwise need to write yourself, saving time and money on development and maintenance.

VR-Link's top-level API abstracts away from the networking protocols. For example, application code sets the current state of locally simulated entities and objects, and any needed information is automatically sent to other applications either through the HLA's RTI or DIS network. On the incoming side, VR-Link processes information from other applications, and provides access to the current state of remote objects, without the application even having to know when individual updates arrive. If you are using either HLA, or DIS, there is great benefit in using VR-Link, since it saves you the time it would take to write all of the code that is necessary to interoperate using your protocol of choice. But if you need to be able to speak more than one protocol, (e.g. HLA and DIS or more than one version of HLA), or might have to in the future, then VR-Link is doubly valuable. That is because VR-Link implements all of these protocols largely through the same API. This means that you can write code once, and switch between DIS, HLA 1.3, IEEE 1516-2000, and IEEE 1516-2010 just by recompiling and linking with the appropriate versions of the VR-Link libraries.

ST Engineering