- Always make sure you are running the latest version
- Menu is not showing
- Reset all the settings
- Disable ReShade
- Missing Visual C++ system component:
- Start in Safe mode
- Inspect the log file
- Missing DirectX legacy runtime
- Confirming that the Ultraleap OpenXR layer is active
- Disabling the OpenXR Toolkit with incompatible applications
- Checking if you are CPU or GPU limited
- Asking for help
- Filing a bug report
- Capturing a trace file
Before starting troubleshooting, always make sure you are running the latest version of the following:
Latest version of your OpenXR runtime. This is typically updated or installed via the Windows store (for Windows Mixed Reality) or the vendor’s software (for Oculus, Varjo). Sometimes, you will need to manually check the vendor’s website (for Pimax unofficial runtime for example).
Latest version of OpenComposite if applicable (ie: your application does not use OpenXR natively). If using the OpenComposite launcher, look for the update button.
Latest version of OpenXR Toolkit, downloadable from the front page of this website.
Half of the “something does not work for me” issues are resolved by updating to the latest software.
There are a few common situations leading to this issue.
OpenXR Toolkit can only work if the application uses OpenXR for interfacing with the VR platform. Either your application natively support OpenXR (eg: Microsoft Flight Simulator, iRacing…) or it requires OpenComposite to bridge to OpenXR.
After running your application for the first time, open the OpenXR Toolkit Companion app, and inspect the list of applications:
The list of recognized applications
If your application does not show up here: it’s not using OpenXR or OpenComposite is not properly setup. The OpenXR Toolkit will not work.
If your application does not support OpenXR natively and requires to use OpenComposite, please refer to the OpenComposite instructions to setup and troubleshoot OpenComposite.
Certain versions of the OpenXR runtime have issues with 2D overlays like the OpenXR Toolkit menu. Try switching to “legacy mode”. Enable Safe mode before starting the application:
Enabling safe mode
Hopefully, the menu will now be displayed. Navigate to the Menu tab, then toggle Use legacy mode to On:
Enabling legacy menu
You can now disable Safe mode and start your application normally.
This has been reported due to certain keyboards requiring special key presses to use the Function keys (such as Fn+F1 for example). This can also be due to 3rd party software intercepting the Function keys.
Use the Keyboard tester to check if your key combinations work.
Please use the OpenXR Toolkit Companion app to try different hotkeys, selecting keys other than the Function keys.
While an application is running, you may at any point reset all the settings to their default values by pressing simultaneously the keys bound to all 3 of the menu actions. If no custom key combinations have been set in the OpenXR Toolkit Companion app, this combination is Ctrl+F1+F2+F3.
You can also navigate to the Menu tab and choose Restore defaults:
Restoring default settings
If you had previously installed ReShade or any similar mod for your application, please disable or delete it in order to use the OpenXR Toolkit.
If the OpenXR Toolkit makes your application refuse to start, try installing the Visual C++ Redistributables.
This issue will manifest itself with the
XR_ERROR_FILE_ACCESS_ERROR when using Windows Mixed Reality, or with the -32 error code with OpenComposite:
Errors you will see when missing Visual C++ Redistributables
If an application fails to start due to some settings changes, you may use the OpenXR Toolkit Companion app (found on the desktop or Start menu) to Enable safe mode. In this mode, the settings for this application will not be loaded.
Enabling safe mode
You may then either:
Change your settings to avoid the problem. Note that in safe mode, settings are not loaded, but the modified settings are still stored. You may need to toggle a setting on/off a few times to make sure the new value is saved before exiting Safe mode.
In order to inspect the log file to try to understand issues with the toolkit, you may open the OpenXR Toolkit Companion app (found on the desktop or Start menu) and click the Open log file button. This will open the file located at
Accessing the log file
Please note that certain applications may run in a security-sandbox environment. In this case, the log file may be located under the corresponding application subfolder in
%LocalAppData%\Packages. You may search for a file named
XR_APILAYER_NOVENDOR_toolkit.log if unsure of the exact location.
An example log file
Check for the following error in the log file:
[OXRTK] 2022-02-28 20:41:32 -0600: HRESULT failure  Origin: m_fontWrapperFactory->CreateFontWrapper(get(m_device), m_fontFamily.c_str(), set(m_fontNormal))
To solve this problem, please install the DirectX legacy runtime package.
Note: this is applicable for troubleshooting hand tracking with Ultraleap devices only.
To confirm that the Ultraleap OpenXR layer is active and loaded in the correct order, open the OpenXR Toolkit Companion app (found on the desktop or Start menu) and hover the mouse cursor on the OpenXR Toolkit layer is active label.
Listing the OpenXR layers
XR_APILAYER_ULTRALEAP_hand_tracking layer must appear after the
XR_APILAYER_NOVENDOR_toolkit layer. If this is not the case, you may re-install either one of the layers to correct the order.
You might reach a point where you determine that an application is not compatible with the OpenXR Toolkit. You may use the OpenXR Toolkit Companion app (found on the desktop or Start menu) to disable the OpenXR Toolkit just for that application.
Perform the test below with any form of motion reprojection or asynchronous space warp (ASW) disabled and any frame limiting/throttling feature disabled (eg: in your driver or NVIDIA control panel).
Use the Detailed overlay (see Overlay) to inspect your application CPU and GPU times (respectively app CPU and app GPU).
When the value of app GPU is greater than the value of app CPU, you are limited by your GPU, and you may use features such as Upscaling or Foveated Rendering to relieve your GPU. If you are not GPU limited, then these features will not help to gain performnce. Instead, you may alter other settings of your application, such as details settings, and increase them until you become GPU limited, and can enable the performance-enhancing features previously mentioned.
Some issues may be known by the community. Please read the Support channels on our Discord server and ask questions there if you do not find the answer already.
Please do not file issues for questions about tuning of the settings. Use the Discord server for that.
Please do not file issues about OpenComposite. Use the OpenComposite GitLab page for that.
To file an issue on GitHub, click the “New issue” button, then select a type of issue and click “Get Started”:
There are templates providing fields to input all this information. Always use the templates. Issues filed without the necessary information will be closed without being looked at! No exceptions!
Always include the log file as an attachment by drag and dropping the log file in the attachment area.
If applicable, you may include screenshots (see Other features).
Thank you for taking the time to report issue and help us improve the software!
Only do this when the developer asks you to do so.
Open the OpenXR Toolkit Companion app, and click “Capture trace”.
Follow the prompts:
Now it’s time to reproduce your problem while the data is being recorded!
When done, stop the trace:
After a few seconds, a File explorer window will open at the location of the trace file:
Compress both files (it is important, the
OXRTK.etl file can be large) and send them to the developer privately.