Table of contents
- World scale override
- Shaking reduction
- Brightness, contrast and saturation
- Turbo mode
- Motion reprojection
- Lock motion reprojection
- Frame rate throttling.
- Field of view
- Screen capture
- Record statistics
- CA Correction (Varjo Aero Exclusive)
World scale override
The world scale override can be used to change the relative position of the eye cameras (also known as the Inter-Camera Distance, or ICD). This can affect your perception of the size of the world in VR. Reducing the scale (ie: a scale under 100%) will make the world appear smaller, while increasing the scale (ie: a scale above 100%) will make the world appear bigger.
Previously known as “prediction dampening” this setting allows to reduce the jitter that can be observed when head or controller is predicted “too long in advance”. This often manifests as “over-sensitivity” with your head movements. For example, some people have reported the view in the headset shaking with their heartbeats. That is an example of over-sensitivity. Set a negative value to reduce the amount of prediction and reduce shaking, for example -50% will cut in half the requested amount of prediction. Experimentally, best results have been achieved with values between -20% and -40%.
Brightness, contrast and saturation
The OpenXR Toolkit applies some simple post-processing to adjust the brightness, contrast and saturation of the images displayed in the headset. The way these settings affect the image is comparable to the settings found on your TV or computer monitor. They are applied on the rendered images as a whole, and are subject to limitations due to color encoding.
Each setting has a default value of 50, which means no changes to the game’s output. The saturation adjustments can be applied to all 3 color channels (red, green, blue) or individually for each channel.
Note: This is a highly experimental feature. If it makes your game crash or misbehave, please disable it.
Turbo mode makes the game entirely ignore any frame timing or throttling dictated by the OpenXR runtime. In other words, Turbo mode forces the game to draw and submit frames as fast as possible regardless of any recommendations or policies from the OpenXR runtime.
Turbo mode can increase your frame rate under certain conditions, but there is no rule or guarantee.
Turbo mode can also have undesired side effects:
- Any statistics or performance measuring tool might now present incorrect data for frame times (however frame rate will be reported correctly). For example, on WMR, when using the performance overlay, all app CPU/GPU values will read 0.
- Any feature of your platform that relies on frame timing data, such as Motion Reprojection/Motion Smoothing/ASW, will not behave correctly. For example, on WMR, the motion reprojection will not engage automatically anymore, but it can be forced via the Lock motion reprojection option.
- Latency is increased, in a way that may or may not visible.
Note: Turbo mode is offered as-is. There will be no support for issues filed while using Turbo mode.
Note: This settings is only available to Windows Mixed Reality users.
The Motion Reprojection setting is essentially the same as the motion reprojection setting from the OpenXR Tools for Windows Mixed Reality. The key differences are that:
- The OpenXR Toolkit Motion reprojection setting overrides the setting from OpenXR Tools for Windows Mixed Reality.
- The OpenXR Toolkit Motion reprojection setting is saved per-application, rather than globally.
- OpenXR Toolkit Motion reprojection setting set to On will enable use of the the Lock motion reprojection feature.
If set to Default, the Motion reprojection setting in OpenXR Toolkit does nothing, and the setting from OpenXR Tools for Windows Mixed Reality is used instead.
Note: The motion reprojection setting “Automatic” in OpenXR Tools for Windows Mixed Reality is misleading: it is equivalent to “Always on” but only for Microsoft Flight Simulator 2020. There is no equivalent in OpenXR Toolkit, using On is equivalent to “Always on” from OpenXR Tools for Windows Mixed Reality.
|OpenXR Toolkit||OpenXR Tools for Windows Mixed Reality||Result|
|Default||Automatic||Enabled only in FS2020|
Unless the Lock motion reprojection option described below is used, Motion Reprojection will always attempt to select the best achievable frame rate. If motion reprojection is not needed, the game will freely render at 60 or 90 Hz depending on your configured refresh rate. If motion reprojection is needed, the runtime will force 1/half, 1/third or 1/quarter frame rate as appropriate.
Lock motion reprojection
Note: This settings is only available to Windows Mixed Reality users.
The Lock motion reprojection setting can be used to force the motion reprojection rate, rather than let the OpenXR runtime automatically choose the rate based on the current performance. This is useful if you are experiencing large fluctuations in frame rate, and prefer to lock the frame rate to a smaller (but steadier) value. The motion reprojection rate is a fraction of the headset’s refresh rate, for example with 90 Hz refresh rate, the available rates are 1/half (45 FPS), 1/third (30 FPS) and 1/quarter (22.5 FPS).
Frame rate throttling.
This option can be used to throttle down the frame rate of the application and avoid fluctuations in frame rates. This option may introduce unwanted latency, since the locked frame rate might not properly phase with the scan-out of the headset.
This option will not appear for Windows Mixed Reality users if the Motion Reprojection is forced to On in the System tab. You must use the Lock motion reprojection instead (see above). This is because the Motion Reprojection rate locking is preferred, since it is latency-aware and produces better results.
Field of view
The field of view override adjusts the pixel density per degree. A smaller field of view is covering a smaller region of the view but with the same amount of pixels, effectively increasing the perceived resolution. Two levels of controls are available: simple and advanced. The former adjusts the fied of view for both eyes simulatneously, while the latter offers individual controls per-eye.
In order to activate this feature, you must check the Enable screenshot box in the OpenXR Toolkit Companion app, and select an image format for the screenshots. The OpenXR ToolKit supports the following formats: DDS*, PNG, JPG and BMP.
You may then press
Ctrl+F12 to take a screenshot of the left-eye image view. Screenshots are saved under
%LocalAppData%\OpenXR-Toolkit\screenshots. This folder may be opened from the OpenXR Toolkit Companion app by clicking the Open screenshots folder button.
Enabling and accessing screenshots
*The DDS format is a lossless format native to DirectX but some tools might have issues opening DDS files. The tools that were confirmed to properly open them with the OpenXR Toolkit are GIMP and Paint.net
This option can be enable to continuously record some statistics from the application to a comma-separated values (CSV) file stored under
When this option is toggled from off to on, a new file is created, with a file name including the date/time (eg:
stats_20220822_183013.csv for a recording on August 22nd, 2022 at 18:30:13).
The CSV file contains rows with the average FPS, frame times, and VRAM utilization over one second. Every second, a new row is appended.
CA Correction (Varjo Aero Exclusive)
The CA Correction option on Varjo Aero HMDs allows you to correct for a problem called longitudinal chromatic aberrations, which can cause red and blue colors to appear shifted in depth. This option scales the red and blue color channels relative to the green color channel to help mitigate this problem.
It is recommended to disable the AutoIPD setting in Varjo Base and either use the value provided by your optician or the value measured by Varjo using the AutoIPD feature, since the AutoIPD setting can change between measurements and throw off your correction values.
Negative values move colors further away, while positive values bring colors closer.
There is a small app called RedShiftTester that can help you find the best correction values for your eyes.
Note that by default, this correction option is only available on Varjo Aero HMDs using Varjo Base’s OpenXR implementation, and not when using SteamVR. However, you can enable this feature on OpenXR through SteamVR by setting a registry key to allow CA correction:
Key: HKEY_LOCAL_MACHINE\SOFTWARE\OpenXR_Toolkit\allow_ca_correction Value: 1 Type: DWORD32
Please keep in mind that this will only work on OpenXR apps and not on OpenVR overlays.
You can use the same correction values for all apps you run with the OpenXR Toolkit, but you will need to re-enter them individually for each application, since they are treated as a separate setting.