Quest 3 & Virtual Desktop Crash- OpenXR Call Failed, Error Code: -2

[Slvrsurfer]

hello everyone,  I just updated to 2.9 and whenever I try to run it in VR with MT, it always seems to crash.  When using Virtual Desktop, I get an OpenXR Call Failed, Error Code: 2 message and the game fails to load past the initial splash screen.

When trying it using Oculus Airlink,  it does load the window where you see the Mig in the hangar, then the game instantly closes down.

Playing DCS on a flat screen MT works flawlessly, and I have had zero issues before updating it to 2.9.  Single thread works as well in VR.  Any idea how to fix this? 

*PS- I don't have reshade files as per another recent post*

 

I am running a 5800x3d, 4090, 64gb 3200 ram on Windows 11

 

Crash dump is attached.

dcs.log-20231019-172420.zip

dcs.log

 

 

* Update, I think I had opencomposite installed, so I deleted all of the openvr_api.dll files and am validating all install files in DCS.   Hopefully that solves it. 

 

**Update 2-  that fixed it, but now I can't seem to get MT to work in VR.   It works on flat screen, but no command line combination can get it to work in VR.

 

https://mbucchia.github.io/OpenXR-Toolkit/opencomposite#step-by-step

Edited October 20, 2023 by Slvrsurfer

[actually_fred]

> 2023-10-19 20:23:15.080 INFO    APP (Main): Command line: Z:\SteamLibrary\steamapps\common\DCSWorld\bin\DCS.exe --force_enable_VR --force_steam_VR

Remove --force_steam_VR, and make sure you have your OpenXR runtime set to Oculus. Also make sure you have multithreaded beta enabled in the steam game settings.

Edited October 21, 2023 by actually_fred

[Slvrsurfer]

Thanks for seeing that, as it gave a huge clue on the problem.   So, I double checked the OpenXR runtime as well as the open beta status, and everything is correct.  HOWEVER, the command lines as well as the correct executable aren't running correctly according to the info.log.   The shortcut does correctly point to the MT executable, but it runs the ST exec instead, and all of my command line arguments aren't being recognized according to the log.  I also noticed that for some reason, I can't add the "quotes" to my shortcut for some reason.   I wonder if this is part of the problem.

 

Update- The lack of quotes are not the problem since my target path doesn't have any spaces between words.  The problem is something else entirely, and since the issue differs greatly from the initial topic, I'm going to start another topic if I can't find the answers I need.

Edited October 24, 2023 by Slvrsurfer

[ghawkgu]

Virtual Desktop has just released 1.29.3 beta, which has native support for OpenXR. Yes, streamVR is no longer needed.

It runs quite smoothly on my machine.

For details, take a look of VD's discord channel.

Edited October 24, 2023 by ghawkgu

[Lorenzo.D]

Virtual Desktop has just released 1.9.3 beta, which has native support for OpenXR. Yes, streamVR is no longer needed.
It runs quite smoothly on my machine.
For details, take a look of VD's discord channel.

Do tuo use open xr toolkit or other program?

What you chose for open xr in the virtual desktop menu and how you lunch dcs?

Inviato dal mio CPH2219 utilizzando Tapatalk

[ghawkgu]

Alright, let me try to make it clearer.

To run DCS with the native OpenXR runtime of Virtual Desktop (VDXR), simply follow the 6 steps below.

1. You need to install the latest beta version of VD, 1.29.3.

Quote

To install this beta version, navigate to the store page of Virtual Desktop on the Meta website (https://www.meta.com/experiences/2017050365004772/) or phone app. Scroll down to the version number, click it and select the BETA channel. You should get an update in your headset shortly after. You will also need to manually install the Beta Streamer from here: https://download.vrdesktop.net/files/beta/VirtualDesktop.Streamer.Setup.exe

2. Launch the VD streamer app, pick VDXR as the OpenXR runtime.

3. Disable the OpenXR toolkit for DCS. This is based on my test.

4. Check your shortcut for DCS. You need MT & OpenXR.

The command line will be like

"C:\DCS world\bin-mt\DCS.exe --force_OpenXR --force_enable_VR"

5. Launch the game by double clicking the shortcut.

Note that you don't use the "Launch Game..." menu of the VD streamer app.

 

6. Do a pre-flight check, make sure VDXR is enabled.

 

And here's my game streaming setting for VD.

I'd recommend the Snapdragon Super Resolution, this is by far the best upscaling solution I've tried on Quest 2, saves a lot of GPU power.

My rig has a i9-11900k cpu, rtx3090 GPU, 64G mem, My GPU usally runs at 55% for single player scenario in good weather.

With SSW on, it has some artifacts to bump the FPS in headset to 90, while GPU is throttled at 44fps in most of time.

Edited October 25, 2023 by ghawkgu

[Mordants]

36 minutes ago, ghawkgu said:

Alright, let me try to make it clearer.

To run DCS with the native OpenXR runtime of Virtual Desktop (VDXR), simply follow the 6 steps below.

1. You need to install the latest beta version of VD, 1.29.3.

2. Launch the VD streamer app, pick VDXR as the OpenXR runtime.

3. Disable the OpenXR toolkit for DCS. This is based on my test.

4. Check your shortcut for DCS. You need MT & OpenXR.

The command line will be like

"C:\DCS world\bin-mt\DCS.exe --force_OpenXR --force_enable_VR"

5. Launch the game by double clicking the shortcut.

Note that you don't use the "Launch Game..." menu of the VD streamer app.

 

6. Do a pre-flight check, make sure VDXR is enabled.

 

And here's my game streaming setting for VD.

I'd recommend the Snapdragon Super Resolution, this is by far the best upscaling solution I've tried on Quest 2, saves a lot of GPU power.

My rig has a i9-11900k cpu, rtx3090 GPU, 64G mem, My GPU usally runs at 55% for single player scenario in good weather.

With SSW on, it has some artifacts to bump the FPS in headset to 90, while GPU renders 44fps in most of time.

 

Hi I can't seem to get the update. I click on it and the box says purchased but then nothing, any ideas?

[ghawkgu]

50 minutes ago, Mordants said:

Hi I can't seem to get the update. I click on it and the box says purchased but then nothing, any ideas?

Hi Mordants, 

I'm sorry, I have no idea how exactly the Quest public test channel works.

Every time When I set the version to BETA, I just leave it powered on. When I get back after about 30min, it is already downloaded automatically.

How magic it is, right?

[Mordants]

1 hour ago, ghawkgu said:

Hi Mordants, 

I'm sorry, I have no idea how exactly the Quest public test channel works.

Every time When I set the version to BETA, I just leave it powered on. When I get back after about 30min, it is already downloaded automatically.

How magic it is, right?

Hey thanks for the reply, It's updated itself so all good. Cheers for instructions.

 

[nephilimborn]

I am having a similar issue with VDXR; using the shortcut approach is the only way for me to launch MT exe however it never loads (black loading screen). It should not matter to MT as VDXR is simply another OpenXR runtime i guess. Not sure if this exacerbates the issue some people are having with the MT version requiring the use of process lasso (P-cores only and hyper threading disabled)?

Only way i can get MT version to work is via the Oculus link cable approach unfortunately.

[Qcumber]

On 1/8/2024 at 10:45 PM, nephilimborn said:

Only way i can get MT version to work is via the Oculus link cable approach unfortunately.

I find that this is the better option with quest pro as there are less compression artifacts.

 

On 1/8/2024 at 10:45 PM, nephilimborn said:

I am having a similar issue with VDXR; using the shortcut approach is the only way for me to launch MT exe however it never loads (black loading screen).

Are you using open composite by any chance? 

[nephilimborn]

On 1/10/2024 at 7:15 PM, Qcumber said:

I find that this is the better option with quest pro as there are less compression artifacts.

 

Are you using open composite by any chance? 

No mods nor open composite...agree with you that wired is likely the best option; TBH i am not sure why i am even wasting time with this; my original intent was curiosity with HEVC 10bit compression over 150Mbps however i am certainly not interested in compression artefacts nor any additional load on the 4090. 

[Qcumber]

2 hours ago, nephilimborn said:

No mods nor open composite...agree with you that wired is likely the best option; TBH i am not sure why i am even wasting time with this; my original intent was curiosity with HEVC 10bit compression over 150Mbps however i am certainly not interested in compression artefacts nor any additional load on the 4090. 

I did not really notice any compression artifacts with the Pico 4. It's only when I did a comparison with QP using VD vs link-cable that I released the cable at 960 Mbps looked better. You could try the AV1 encoding with VD as this is only supported with the Q3.  

[Schlomo1933]

Short question : why u use virtual desktop? 
 

I run my quest 3 just with the Oculus PCVr App (same app as my older Rift S) via PC-Link Kabel. 

Without any problems…
 

The Oculus PCVr App also uses natively Open XR.

 

so what’s the thing to use Virtual Desktop?