If you create applications using the VR-Forces APIs, you may need to deploy them to internal or external customers.

To deploy a VR-Forces application:

The deployment site must run the license manager and each application must have a VR-Forces run-time license.
On Windows, you do not have to set any Registry values.
You do not have to set any environment variables, unless the application will be used for development. In a development environment an application would have the same requirements as described in this chapter.
You must include all of the DLLs from the ./bin directory for the protocol in which you are running the applications (DIS, HLA 1.3, HLA 1516, or HLA Evolved.)
Any configuration files that you have modified from their default configurations to support your application are required, except that if you are not using the OPD Editor, you do not have to ship dis-simulation object-types.csv. Configuration files are located in ./config, ./appData/settings/vrfGui, ./appData/settings/vrfSim, and in the various directories under ./data/simulationModelSets.
You do not have to include files from the ./data subdirectories that you will not use, for example, any terrain databases that you do not need, example scenarios, and so on. If you customize the object parameter database, you must determine which of the files supplied by MAK are required.