Please use the troubleshooting below to resolve the following issues with OpenXR Motion Compensation and Sim Racing Studio: 

  • Re-centering In-game View
  • "Swimming" or "Laggy" Image
  • Confirming if OXRMC has Installed Correctly
  • Conflict with other OpenXR API layers
  • Customizing OXRMC settings for different applications
  • WitMotion Sensor Calibration (Numbers next to Bullseye in SENSOR are erratic) 
  • Motion Compensation isn't compensating for Yaw, Linear Sway, or Heave
  • Witmotion Sensor is not detected by Sim Racing Studio
  • Witmotion Sensor is not working properly
  • iRacing or other games not working after installing OXRMC


NOTE: Sim Racing Studio is unable to guarantee support resolution for the experimental feature of motion compensation. If support is needed, join the Sim Racing Studio Motion Compensation Discord channel here. If additional support is required, please book an appointment with the Sim Racing Studio VIP Service here. 


For information on setting up and using OpenXR Motion Compensation with Sim Racing Studio, please use the setup guide here.



Re-centering In-game View

If you re-center the in-app view during a session, the reference pose is reset by default. Therefore, you should only re-center while your motion rig is in neutral position. It is possible (depending on the application) that this automatic recalibration is not triggered, causing the view and reference pose to be out of sync and leading to erroneous motion compensation. Perform the following steps to fix the issue: 

  1. Deactivate motion compensation by pressing the activate shortcut
  2. Bring your motion rig to neutral position. Face forward if yout using a virtual tracker
  3. Re-calibrate by pressing the center shortcut
  4. Reactivate motion compensation by pressing the activate shortcut



"Swimming" or "Laggy" Image

When the VR image appears to be lagging behind what is occurring or the image feels like its swimming and not matching the movements, adjustments to the translation and rotation filters might be needed. These settings can be changed in the OpenXR-MotionCompensation.ini file. 


translational_filter and rotational_filter: set the filtering magnitude (key strength with valid options between 0.0 and 1.0) number of filtering stages (key order with valid options: 1, 2, 3)


vertical_factor is applied to translational filter strength in vertical/heave direction only (Note that the filter strength is multiplied by the factor and the resulting product of strength * vertical_factor is clamped internally between 0.0 and 1.0).


  1. Go to the folder: ...\Users\<Your_Username>\AppData\Local\OpenXR-MotionCompensation\OpenXR-MotionCompensation.log

  2. In the folder, locate the default configuration file OpenXR-MotionCompensation.ini.

  3. Open the OpenXR-MotionCompensation.ini file in NotePad
  4. Edit the values in the translation_filter and rotation_filter to increase or decrease filtering:

    [translation_filter]
    ; value between 0.0 (filter off) and 1.0 (initial location is never changed)
    strength = 0.50
    ; single (1), double (2) or triple (3) exponential moving average filter
    order = 2
    ; factor for modifying filtering in vertical direction (>= 0.0)
    vertical_factor = 1.0

    [rotation_filter]
    ; value between 0.0 (filter off) and 1.0 (initial rotation is never changed)
    strength = 0.50
    ; single (1), double (2) or triple (3) slerp filter
    order = 2

  5. Go to File and select Save then close Notepad.



Confirming if OXRMC has Installed Correctly

To confirm if OpenXR Motion Compensation has been installed correctly, OpenXR Explorer can be utilized to verify the correct installation:

  1. Install OpenXR Explorer (Download here: https://github.com/maluoi/openxr-explorer/releases)
  2. Connect your HMD
  3. Start your corresponding VR runtime application (e.g. SteamVR, Oculus App, Mixed Reality Portal, Varjo Base, PiTool, etc.)
  4. Start OpenXR Explorer
  5. Search for the section xrEnumerateApiLayerProperties (should be in the middle column at the bottom by default)
  6. Check if the entry XR_APILAYER_NOVENDOR_motion_compensation with version v1 exists



Conflict with other OpenXR API layers

There could be issues with other OpenXR API layers that are installed on your system. Issues can generally be resolved by by using the correct order of installation since it determines the order in which the layers are loaded.

Examples include:

  • XRNeckSaver needs to be installed before OXRMC.
  • OpenKneeBoard needs to be installed before OXRMC.
    • If you install one of the above with after OXRMC, you can just run the OXRMC installer afterwards to modify loading order.



Customizing OXRMC settings for different applications 

The default configuration file for OXRMC is OpenXR-MotionCompensation.ini. However, when a new OpenXR game is started for the first time, a configuration file named after the application is created in the same directory. This new configuration file can be used to copy (partial) sections from the default configuration file whenever you want to make changes only for that application specifically.



Witmotion Sensor Calibration (Numbers next to Bullseye in SENSOR are erratic)

If you need to reset or calibrate your Witmotion Sensor due to inaccurate readings, please download the 'WITMOTION PC Software ' from https://www.wit-motion.com/. You can find the software located in the Download Center and selecting WITMOTION PC Software (Direct Link: https://www.wit-motion.com/searchq.html. Download the WitMotionNewSoftware.zip and extract the folder onto your PC. Open the folder and run the WitMotion.exe. Note: You must close SRS to connect to Witmotion software and vice versa.

Run the MiniMU.exe file in the downloaded zip folder. You can monitor the output via the tabs at the top of the program. To recalibrate the Witmotion Sensor, select Config from the menu at the top. In the new window, click on each of the 5 buttons in the Calibrate section (Acceleration, Magnetic Field, Reset Height, Angle Reference, and Reset Z-axis Angle. When you select Magnetic Field, select the Start Calibrate button at the bottom and rotate the Witmotion Sensor on all axes as instructed. Once done rotating, select End Calibrate. You can then verify the Witmotion Sensor is now steady in the main window and close the program before you relaunch SRS. 




Motion Compensation isn't compensating for Yaw, Linear Sway, or Heave

Sim Racing Studio Motion Compensation will compensate platform movement on the Pitch, Roll, Sway(Roll), and Surge axis for actuator and non-actuator platforms. Yaw(Tracton Loss), Linear Sway(Double Traction Loss), and Heave are not compensated.



Witmotion Sensor is not detected by Sim Racing Studio

If the Witmotion Sensor is unable to be detected by Sim Racing Studio, ensure you have any other software that could potentially be blocking its COM Port turned off. This includes the Witmotion Sensor software or other similar programs like SimHub. 

Please also check that the COM Port in the Sim Racing Studio config.ini file has not be hard coded. To do so, close Sim Racing Studio and then open the config.ini file in your ...\Documents\SimRacingStudio 2.0 folder. Scroll down the to [MOTION_COMPENSATION] section and verify the com_port appears as the following. 

com_port = ""

If it doesn't appear as above, please correct it and save the config.ini file. Then reopen Sim Racing Studio and go the the SETUP > Hardware page and and ensure that Motion Compensation (Witmotion) is Enabled and that the Com Port is set to Auto Search. 


If there was a recent Windows Update, it is possible the Windows update over-wrote the Witmotion Sensor's driver. Please check the Windows Update if a fix has been released. In addition, the Witmotion software can be downloaded to verify the driver is installed correctly. Please download their software located at the bottom of the page here. Note: You must close SRS to connect to Witmotion software and vice versa.



Witmotion Sensor is not working properly

If the Witmotion Sensor is not being detected after troubleshooting, is transmitting data to slowly, or providing inaccurate data, then it is likely the Witmotion Sensor cable is defective. Please try replacing the Witmotion Sensor cable to resolve the issue. 



iRacing or other games not working after installing OXRMC

If after installing OXRMC and you are using a Windows Mixed Reality Headset (ie HP Reverb G2), iRacing or other games no longer launch, please try reinstalling Windows Mixed Reality (WMR). You can download the latest version of WMR from here: https://learn.microsoft.com/en-us/windows/mixed-reality/enthusiast-guide/install-windows-mixed-reality