This is an old revision of the document!
Table of Contents
Start Page » DEMoCap: Drag[en]gine Motion Capture
Known Problems
VR runtimes can be tricky beasts since various manufacturers and developers are involved. This page lists known problems and potential solutions for them.
DEMoCap VR mode does not start
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.
OpenXR Layer Incompatibility
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. 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.
