After system updates, VR launch hangs after login

[Ohioflyer15]

Hello everyone, I've been playing DCS in VR without issue for a few weeks now.  Nothing unusual to report at that time.

Today I did a windows update (one of many during these weeks) and then opened DCS in 2D to work on a mission.  No issue.

 

Upon trying to open DCS in VR later today to fly the mission with others, DCS checks for an update, displays the DCS logo initial splash screen, logs in and authorizes normally, and then hangs on that initial splash screen (desktop visible) for a very long time (minutes) before appearing to abort loading in VR and instead loads the 2D game.  It won't load into VR at all.

 

I try to then play a 2D game and it fails to load into a game because of what appears to be a graphics/DX11 issue and crashes

 

When my Index is shut down and DCS isn't trying to load into VR, the game loads faster to the main screen but still runs into the same error message and crashes.  I'm not sure what changed between the Windows update > Successful 2D play > Attempted VR play fail > Attempted 2D Fail.

 

I've checked for driver or other updates for Steam/Valve, Windows, Nvidia, DCS, etc and think I'm up to date, multiple restarts, etc.  I was playing fine and well about 3 days ago and the windows update is the only thing I can think of that changed. Logs, system info, and (possibly unrelated) error message below.

 

edit: I followed the general troubleshooting guides on removing saved games folder, repairing the program, checking pagefile size, etc.  I removed the shader files to allow them to rebuild as well.  All mods are removed.

 

I appreciate your help

 

Valve index HMD

 

dcs.log sys.nfo

Edited February 25, 2021 by Ohioflyer15

[Flappie]

Hi. Your Windows version (10.0.19042) is not known for causing issues with DCS. Can you please attach a screenshot of the latest downloaded Windows updates?

 

Your log shows 3 different issues:

At first, you're getting an "error 310" at the moment DCS tries to launch OpenVR (I don't see this often in the log - I assume this is the most important part):

 

2021-02-25 05:23:51.697 ERROR   VISUALIZER: unable to init OpenVR runtime: Unknown error (310)
2021-02-25 05:23:51.702 INFO    GRAPHICSVISTA: renderer: 'dx11backend.dll'
2021-02-25 05:23:51.733 INFO    DX11BACKEND: DX11Renderer initialization (w:3440 h:1440 fullscrn:1 vsync:0 adapter:0 monitor:0 shaderErrors:1)

 

Have you tried running OpenVR/SteamVR manually? Does it start without issue?

I googled "openvr 310" and saw a few solutions. You can try this one, and if it doesn't work, try launching SteamVR in safe mode.

[Ohioflyer15]

Thanks Flappie, I have tried the things you mentioned.  Much has also changed overnight including a new graphics driver (which I certainly checked yesterday!) and DCS also updated itself to a .1 version and I have both installed now. Long story short, the problem remains.

 

Attached are windows updates that I did as a package.  I also remembered that steamVR indicated it updated itself when I launched it prior to these issues.  I apologize for not including it before.  steamVR is on version 1.16.8, released only 3 days ago.

 

I agree there might be more than one problem happening.  The 310 error certainly points to the VR while the dx11 error I was getting in 2D regardless of the VR status. 

I always open SteamVR manually before starting DCS.  SteamVR has no problem running on it's own or running other games. 

I followed your helpful links in attempting to resolve the 310 error.  Launching the server before the utility doesn't seem to have changed anything, and launching SteamVR in safemode didn't either.

 

I had some issues when first starting VR that many files needed admin privileges.  This didn't seem to help either.

 

[Flappie]

EDIT: I was suggesting you to opt-out the SeamVR beta program, but I see the SteamVR stable and beta versions both are now 1.16.8.

 

Try to revert these recent Windows updates one after the other to see if one of them is the culprit.

 

Edited February 25, 2021 by Flappie

[Ohioflyer15]

Weird, I'm not opted into any betas in SteamVR.  Let me see if I can reverse that

[Ohioflyer15]

I went into SteamVr and uninstalled-reinstalled, no change.  But luckily, SteamVR has a "beta" options that is essentially an intentional rollback of the version to allow compatibility with older HMD's.  I selected it and it rolled back SteamVR all the way to 1.15.12 and this appears to be working!  

What method is best to run the incompatibility of the new SteamVR release up the flag pole? And should I rename this thread?

Edited February 25, 2021 by Ohioflyer15

[Flappie]

Nice find!

 

Hi @BIGNEWY. Ohioflyer15 has discovered a conflict between the latest SteamVR update (1.16.8) and the DCS VR support. This SteamVR version has just made it to the Steam stable branch. Can you please ask the team to have a look?

 

Ohioflyer15 has found a way to revert SteamVR version (1.15.12 works fine with DCS), but this solution may not last long.

Edited February 25, 2021 by Flappie

[BIGNEWY]

Strange, I am using steamVR 1.16.9 currently and no issues with the reverb G2 and have no issues with DCS