No cookie for

VR-Link for Unity: HLA and DIS for Unity Game Engine

HLA and DIS Interoperability Standards for Unity Game Engine – try it today!

VR-Link for Unity brings High Level Architecture (HLA) and Distributed Interactive Simulations (DIS) interoperability to the Unity game engine. Built on MÄK’s VR-Link simulation networking toolkit, this asset package allows you to bring Unity-based games into existing distributed simulation environments using standard Modeling & Simulation protocols. VR-Link for Unity supports all the various flavors of HLA and DIS, including HLA 1.3, HLA 1516, and is compatible with any compliant HLA RTI.

Interact and Engage

Through VR-Link for Unity, a role player or trainee playing a Unity-based game can interact and engage with entities modeled by external simulations, including computer-generated forces. VR-Link for Unity handles dead-reckoning and smoothing of entity positions, conversion from Unity’s local coordinate system to geocentric world coordinates, movement of articulated parts, fire and detonate events, embarkation of Unity entities on remotely simulated vehicles, transmitters, signal interactions, and laser designators.


Unity Version Support, and Platform Support

VR-Link for Unity supports Unity 3.5 and 4.0. Since VR-Link for Unity uses the plug-in API of Unity, the Pro version (as well as the MS&T version) is required. VR-Link for Unity does not work with the free version of Unity.

VR-Link for Unity supports the Windows platform.


VR-link for Unity provides a layer of game integration functionality on top of VR-Link. So, you need a VR-Link for Unity license to build a game. But you do not also need a regular VR-Link license.

One VR-Link for Unity license is required for every Unity developer working on the project. There are no additional run-time fees when an application is deployed. The first year of maintenance (including technical support and upgrades) is included with the initial purchase. For subsequent years, an annual maintenance contract must be purchased to continue receiving technical support and upgrades.

VR-Link for Unity uses FlexLM for licensing within the editor environment. When using VR-Link within the editor, it checks out a FlexLM license. If a license cannot be found, it runs in a time limited trial mode for 10 minutes. Games built with Unity do not require a license, but do require a “signed” DLL. The signing application binds the VR-Link for Unity DLL's with the built Unity game. The signing application is also license managed and requires its own license to brand a DLL. During development, if the Unity application changes, the VR-Link for Unity DLL must be resigned.

When using Unity in a development environment, (that is, within the editor), it is possible to use a license server because it is using the typical FlexLM licensing that other VT MÄK products use. The signing application is also FlexLM licensed. Any built applications are not licensed, but do require signing to allow them to run beyond the 10 minute trial mode.

Properly branded applications do not require a license and can be distributed without restrictions.

Superior Technical Support

At MÄK, technical support is not just an afterthought. Our reputation for supporting our customers is one of the key reasons that people choose our products. When you call or email us with questions, you speak directly to our product developers who know the software inside and out. When you buy MÄK's products, you can be sure that MÄK will be in your corner as you work towards successful completion of your HLA/DIS project. We've even been known to be on the phone with customers during their HLA certification process, or during key events.

We do not expect customers to need an instructional course to use VR-Link for Unity. If the documentation or technical support does not resolve your questions, we can arrange for a webinar to assist you.

When someone reports a bug, our engineers are quick to provide a patch or workaround, meaning you will not have to wait for the next release to have your problem addressed.

With maintenance, you are entitled to upgrades when they are released. Typically, new releases not only add support for the latest versions of RTIs, the RPR FOM, HLA Specifications, etc, but also try to maintain compatibility with older versions as well. For example, our current release supports many versions of the MÄK RTI, includes FOM Mappers for RPR FOMs 0.5, 0.7, 0.8, 1.0, and 2.0, and continues to support DIS 4, 5, and 6.