result ;-)

Here's the code I'm using:

[[searchmatch]code[/searchmatch]] CVRChaperone chaperone = new CVRChaperone(OpenVR.GetGenericInterface(OpenVR.IVRChaperone_Version, ref err));
if (err != HmdError
corners.vCorners) {
Debug.LogFormat("Found soft corner: ({0}, {1}, {2})", corner.v[0], corner.v[1], corner.v[[searchmatch]2[/searchmatch]]);
}
}
[/[searchmatch]code[/searchmatch]]

before it gets merged and pushed to default branch. I can't invest time in trying out the latest 1.2.0 version of the plugin right now since the API change causes compilation errors in 3rd party code we

).

https://steamcommunity.com/app/250820/discussions/2/152390648080950188/
https://www.reddit.com/r/SteamVR/comments/fq7kgy/steamvr_wont_start_anymore_error_code_300/

Do you have any third-party anti-virus or anti-spyware that

Originally posted by Duj_:

Originally posted by Bob Loblaw:

Wow. I'm out of my depth and guessing at this point, maybe wait and see what Valve says. A search for that error reveals that

saying:

"The VRLink Driver encountered a fatal error: [EOS] Threads never reset. Waited 10s. Timed out."

Looking in Windows Event Viewer I see two errors occur when I crash like this:

Faulting
application name: vrserver.exe, version: 2.7.1.0, time stamp: 0x667209b8
Faulting module name: KERNELBASE.dll, version: 10.0.19041.4522, time stamp: 0xf7a99bd4
Exception code: 0xe06d7363
Fault offset: 0x

the game with -vr, etc:

Unable to initialize HMD tracker. Error code 1000
Unable to get VRMode adapter from OpenVR. VR mode cannot be enabled. Try restarting and then enabling VR again.

Of course
UTC - error Unable to connect to Oculus Runtime (1000) when initing driver oculus from D:\Program Files\Steam\steamapps\common\OpenVR\drivers\oculus\bin\win32\driver_oculus.dll.
Sat Sep 20 00:43:34 2014

: vrserver.exe, version: 1.14.16.0, time stamp: 0x5f652da3
Faulting module name: driver_holographic.dll, version: 1.2.406.0, time stamp: 0x5f7b9122
Exception code: 0xc0000409
Fault offset: 0x000000000000a

Originally posted by Ray:

I had the same 301 error.
After starting SteamVR I looked in Event Viewer - Windows Logs - Application.
I found the error below which led me to uninstall

stamp: 0x5f652da3
Faulting module name: driver_holographic.dll, version: 1.2.406.0, time stamp: 0x5f7b9122
Exception code: 0xc0000409
Fault offset: 0x000000000000a586
Faulting process id: 0x35b0
I had the same 301 error.
After starting SteamVR I looked in Event Viewer - Windows Logs - Application.
I found the error below which led me to uninstall SteamVR for WMR, after which I

incorrect and/or missing, no symbols loaded for vrclient_x64.dll]
vrclient_x64.dll!000007fee654a963()
Engine.exe!OpenVRManager::EndFrame() Line 806 + 0x2f bytes C++
[/[searchmatch]code[/searchmatch]]

This is the exception:
[[searchmatch]code[/searchmatch]
);
if ( err != vr::VRCompositorError_None )
{
printf ( "Compositor Submit error: %d\n", err );
}
}
[/[searchmatch]code[/searchmatch]]
The crash happens during the pCmp->Submit() call.

Here is the creation code for

Returning to this to provide some more info since nothing has changed since the non-beta 2.8 release, I still randomly get no images to the headset from my app.

Everything looks fine regarding the
image acquisition/wait/release from the color & depth swapchains, the "shouldRender" property of xrWaitFrame, and no relevant validation errors as well.

However, I noticed this by accident: If I leave my

be at the mercy of Nvidia.

EDIT: Found at dmesg:
[drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000800] Failed to apply atomic modeset. Error code: -22
Okay, there are some news of my progress:
1. Thanks to modeset=1, there is no input lag now. No need to fiddle with vsync_to_photons_increment now.
2. Thanks to modeset=1, the worst part of the