VR runtimes can be tricky beasts since various manufacturers and developers are involved. This page lists known problems and potential solutions for them.

This can have various reasons. When looking for the source of the problem take first a look at the log files after an unsuccessful attempt to start VR mode. The log files can be found here:

• Linux: ~/.config/delauncher/logs/games/e31f1c11-3ca6-c66b-adca-95484bedfc1f/logs/last_run.log
• Windows: %LocalAppData%\DELaunchers\Logs\games\e31f1c11-3ca6-c66b-adca-95484bedfc1f\logs\last_run.log

Search for Start VR Runtime… . After this point in the log file you can look for known problem patterns.

If the list below does not help solve the issue please file a Bug Reports or head over to the Discord Channel and post a help request. Please attach the log files. If the file is too large to attach to your message use a service like PasteBin. When using PasetBin please set the paste expiration time to a couple of days. This ensures your paste is not retained forever.

II [OpenXR] [...] VIVE Trackers:
EE [BasicRecovery] [...] The thread tried to read from or write to a virtual address for which it does not have the appropriate access.
EE [BasicRecovery] [...] 00007FF9161C3C10: xrNegotiateLoaderApiLayerInterface ; ??:0

DEMoCap tried to find Vive trackers but one of the loaded OpenXR Layers crashed. This is a typical sign for an OpenXR Layer installed by hardware you currently use or once used to be incompatible. OpenXR Layers need to be ABI compatible or very bad things can happen. Outdated OpenXR layers installed by certain hardware can cause such issues.

To solve this try disabling installed OpenXR Layers one by one to find the problematic layer. You can find the dialog to disable OpenXR extensions like this.

This problem can happen on laptops with dual GPU setups. These are typically gamer laptops with a discrete nVidia/AMD GPU paired with a weak Intel GPU. The idea here is that by default the weak Intel GPU is used to keep the laptop cooler and to consume less energy. The discrete GPU is then used for applications requiring good performance, like games. Unfortunately Windows 10/11 has the tendency to use the weak Intel GPU instead of the strong nVidia/AMD GPU with Drag[en]gine launchers since they do not use strong GPU demand right of the bat.

This problem can be detected by looking at the log file: %LocalAppData%\DELaunchers\Logs\games\e31f1c11-3ca6-c66b-adca-95484bedfc1f\logs\last_run.log . If the log file contains lines like these below the problem is most certainly the weak Intel GPU being used by Windows:

II [OpenGL-RT] [...] LoaderThread: Starting
II [OpenGL-RT] [...] Vendor: Unknown (Intel)
II [OpenGL-RT] [...] Version: 4.6 (4.6.0 - Build 32.0.101.5768) [4, 6]

You can force Windows to use the strong GPU for all Drag[en]gine based games and applications (including DEMoCap) like this:

Open the Windows Settings and navigate to the application graphics settings:

Add the application to change the settings for. For running games and applications through steam or manually through the GUI launcher find the application “delauncher-gui-engine.exe”.

Select the application you just added and select the discrete GPU from the dropdown list.