Tutorials & Guides

MAK VR-Engage Integration

Integrate MAK Technologies VR-Engage military simulation with the motion platform.

1 Requirements

Both ForceSeatPM and VR-Engage must be running on the same Windows PC.

2 Configuration

1. If it is required, start the license server using MAK License Manager.

2. Start VR-Engage with --showConsole command option.

Tip

Console will be automatically opened if you launch VR-Engage from ForceSeatPM (by clicking Run the game button in the profile).

3. Once VR-Engage loads, press Shift + F12 to switch to Admin mode and gain access to top menu.

4. In the top menu click Settings and then Plug-ins....

5. Click + to add new plug-in.

6. Enter motionSystemsConnector as name.

7. Remove all existing entries.

8. Click + to add new entry.

9. Select vrfSim, Windows64, Release and Independent.

10. Click on Plug-in Library cell and select ForceSeatPM directory\connectors\MotionSystems_MAKConnector64.dll.

11. Make sure that Load Plug-in is checked and then close the dialog.

3 Operation

Since there is no option to automatically select an active entity, every time the player entity is changed, a console command must be invoked to track the new entity.

1. If it is required, start the license server using MAK License Manager.

2. Start VR-Engage with --showConsole command option.

Tip

Console will be automatically opened if you launch VR-Engage from ForceSeatPM (by clicking Run the game button in the profile).

3. Start the session, e.g. unhosted on Grid terrain.

4. Once the session loads, second console will open.

5. Place a new or select an existing vehicle and press Engage.

6. When the simulation loads, press Esc to display name of the Engaged Entity.

7. Switch to the second console, and type mosy-track-entity ENTITY_NAME

8. The connector will start collecting telemetry data for the selected entity.

4 Configuration file

The connector stores its configuration in appData\settings\vrfSim\mosy_connector.cfg file. The AppData is in VR-Engage local appData directory (not the AppData directory from Windows user profile).

The example path to the configuration file is as follow:

C:\MAK\vrengageTOT2025-05-15\appData\settings\vrfSim\mosy_connector.cfg

The configuration file contains the name of the entity that should be tracked by the connector:

ENGAGED_ENTITY_NAME=Police 1

If the file is modified by external application, use mosy-reload-config command to reload the configuration and start tracking the new entity specified in the configuration file.