DCS taking 10mins to startup in VR

[Elthas]

Hello,

 From 2 days ago DCS suddenly started taking a literal 10mins to start the game.

DCS logs show an 8min jump in timestamps, so probably something is happening there which isnt supposed to ?

2024-10-16 21:21:25.889 INFO VISUALIZER (21248): SceneManager initialization

2024-10-16 21:21:25.975 INFO VISUALIZER (21248): DCSScene initialized

2024-10-16 21:29:02.194 INFO VISUALIZER (21248): [23:29:02.998][Info ] OpenXR: Available reference spaces: 3

2024-10-16 21:29:02.194 INFO VISUALIZER (21248): [23:29:02.998][Info ] OpenXR: Creating swapchain for view 0 with dimensions Width=2064 Height=2272 SampleCount=1

Using autoexec.cfg as per support faq link did not give anymore details in the logs as can be seen: 

2024-10-17 18:55:58.260 INFO    VISUALIZER (9232): DCSScene initialized
2024-10-17 19:03:33.607 INFO    VISUALIZER (9232): [21:03:34.101][Info   ] OpenXR: Available reference spaces: 3

 

Running with:

• my VR set is a Meta Quest 3 software version 641203492, using quest link with cable. 
• PC is windows 11, rtx 4090,  i7-14700K , 64gb ram

What i tried thus far:

• start in 2D, starts fine.
• Microsoft flight simulator 202 starts and works fine in VR
• I rolled back the minor update i got from DCS/2.9.8.1214.1 to the previous version with DCS_updater.exe, still slow
• i uninstalled and completely redownloaded DCS, still slow
• I uninstalled processlasso, still slow
• upgraded my 4090 to latest drivers (32.0.15.6590), still slow 
• i updated my quest 3 to latest software version (50151600073800510, still slow
• i factory reset the quest 3, still slow
• i uninstalled and re-installed the windows meta quest link app, still slow
• deleted metashader and fxo folders in savedgames/dcs folder , still slow
• disabled antivirus (default one from win 11) still slow

 

So i'm out of ideas at the moment.. anyone who can assist in troubleshooting?

[BitMaster]

Which version of Win11 are you running ?  which updates have been installed last few days ?

Any FW Upgrades available for any of your components ?  like ssd/nvme, bios, peripherie    

 

Just some points to look at

[sleighzy]

Can you drop the full log here please.

[Elthas]

18 hours ago, BitMaster said:

Which version of Win11 are you running ?  which updates have been installed last few days ?

Any FW Upgrades available for any of your components ?  like ssd/nvme, bios, peripherie    

im on windows 11 23H2, which i already had on 04/01/2024 accordign to update history. last updates were on  14/10, 'cummulative update KB5044285' and '.net framework 3.5 and 4.8.1 .. KB5044033 '

il check the fw upgrades later. not much time atm :).

12 hours ago, sleighzy said:

Can you drop the full log here please.

Sure. see attached.

Im happy to report that i got speedy load times again of the game by switching from meta quest link as openXR runtime to steamvr . Still willing to find the cause though 

 

dcs.log dcs (1).log

Edited October 20, 2024 by Elthas

[Qcumber]

1 hour ago, Elthas said:

Im happy to report that i got speedy load times again of the game by switching from openxr runtime to steamvr runtime. Still willing to find the cause though 

I am not sure what you mean by this as DCS uses open XR as the API even through steam VR. Do you mean that you are using steam link rather than meta link? 

[sleighzy]

Your log shows that have the Virtual Desktop API layer but you’re using the Meta OpenXR runtime. Do you not use Virtual Desktop and it’s VDXR runtime (which will be more performant than the Steam one, and even Oculus unless you’ve switched to using the cable… even then though )?

Edited October 20, 2024 by sleighzy

[Elthas]

32 minutes ago, sleighzy said:

Your log shows that have the Virtual Desktop API layer but you’re using the Meta OpenXR runtime. Do you not use Virtual Desktop and it’s VDXR runtime (which will be more performant than the Steam one, and even Oculus unless you’ve switched to using the cable… even then though )?

 

This is not on purpose. I dont have a ethernet cable to my pc so i dont use VD. i only did that during the meta quest v63 issue as temporary workaround. could it still be active therefore?  how to disable it?

1 hour ago, Qcumber said:

I am not sure what you mean by this as DCS uses open XR as the API even through steam VR. Do you mean that you are using steam link rather than meta link? 

Yes, sorry, learning as i go.  I use meta quest link normally only with a usb cablle. but for trying to get around the slow start issue i went into steam and configured steamVR as the openxr runtime https://academy.vrex.no/knowledge-base/openxr/ . I edited my previous reply 

Edited October 20, 2024 by Elthas

[Qcumber]

41 minutes ago, Elthas said:

This is not on purpose. I dont have a ethernet cable to my pc so i dont use VD. i only did that during the meta quest v63 issue as temporary workaround. could it still be active therefore?  how to disable it?

Yes, sorry, learning as i go.  I use meta quest link normally only with a usb cablle. but for trying to get around the slow start issue i went into steam and configured steamVR as the openxr runtime https://academy.vrex.no/knowledge-base/openxr/ . I edited my previous reply 

 

Are you using any open XR layers such as Open XR toolkit or XR necksafer? If so then disable them all as there have been issues with these since the last update. 

This is a useful too to monitor which layers are active. https://github.com/fredemmott/OpenXR-API-Layers-GUI

[Elthas]

13 minutes ago, Qcumber said:

Are you using any open XR layers such as Open XR toolkit or XR necksafer? If so then disable them all as there have been issues with these since the last update. 

This is a useful too to monitor which layers are active. https://github.com/fredemmott/OpenXR-API-Layers-GUI

Yes i have openxr toolkit, indeed i have read it too that its unsupported now and had an issue somewhere. Thanks, will try this tonight. 

Edited October 20, 2024 by Elthas

[sleighzy]

1 hour ago, Elthas said:

could it still be active therefore?  how to disable it?

It’s not active per se, just available. No need to disable anything, you’re not using the runtime so nothing being used. 
The log does show OpenXR Toolkit (no mention of Necksafer) but there are no issues with it and won’t be causing your issue as far as I’m aware, you can disable it using the Companion app to confirm anyway. 

Edited October 20, 2024 by sleighzy

[Qcumber]

2 minutes ago, sleighzy said:

It’s not active per se, just available. No need to disable anything, you’re not using the runtime so nothing being used. 
The log does show OpenXR Toolkit (no mention of Necksafer) but there are no issues with it and won’t be causing your issue as far as I’m aware. 

I have had issues with OXRTK and no longer use it. It would be worth trying running without it. 

Just to clarify open XR is the API not the runtime. The runtime is Oculus link or steam VR. 

[Marshallman]

2 hours ago, Elthas said:

This is not on purpose. I dont have a ethernet cable to my pc so i dont use VD. i only did that during the meta quest v63 issue as temporary workaround. could it still be active therefore?  how to disable it?

Yes, sorry, learning as i go.  I use meta quest link normally only with a usb cablle. but for trying to get around the slow start issue i went into steam and configured steamVR as the openxr runtime https://academy.vrex.no/knowledge-base/openxr/ . I edited my previous reply 

 

Game changer buying a 20 metre Ethernet cable from Amazon and connecting direct.....

[Elthas]

1 hour ago, Marshallman said:

Game changer buying a 20 metre Ethernet cable from Amazon and connecting direct.....

Oh i got those, got them on rolls of 100m even :). But not want to route it through the middle of my appartement living room now , girlfriend wouldn't accept.

Edited October 20, 2024 by Elthas

[Marshallman]

I'm in a bungalow, its all through the roof

[Elthas]

9 hours ago, Qcumber said:

Are you using any open XR layers such as Open XR toolkit or XR necksafer? If so then disable them all as there have been issues with these since the last update. 

This is a useful too to monitor which layers are active. https://github.com/fredemmott/OpenXR-API-Layers-GUI

So.. for testing this i switched back to meta quest link, and i started the game just to confirm the baseline before i would do anything else and.. it works again as quickly as ever. So yesterday after all my trials which didn't change anything,  only switching to steamVR restored the performance, and going back now today to meta quest link its ok again. I don't understand it, other then a variant of 'have you tried turning it on and off again'. 

Since i cant replicate the issue anymore i cant try find the actual cause or solution, other then the 'this worked for me' solution of switching between steamVR and back to meta quest link. Hope this is now stable.

Anyway, thank you all for your help, much appreciated. Happy flying

[Qcumber]

30 minutes ago, Elthas said:

So.. for testing this i switched back to meta quest link, and i started the game just to confirm the baseline before i would do anything else and.. it works again as quickly as ever. So yesterday after all my trials which didn't change anything,  only switching to steamVR restored the performance, and going back now today to meta quest link its ok again. I don't understand it, other then a variant of 'have you tried turning it on and off again'. 

Since i cant replicate the issue anymore i cant try find the actual cause or solution, other then the 'this worked for me' solution of switching between steamVR and back to meta quest link. Hope this is now stable.

Anyway, thank you all for your help, much appreciated. Happy flying

Glad it's working for you. Hopefully it will stay that way. 

[sleighzy]

10 hours ago, Qcumber said:

I have had issues with OXRTK and no longer use it. It would be worth trying running without it. 

Just to clarify open XR is the API not the runtime. The runtime is Oculus link or steam VR. 

I refer to the runtimes as OpenXR runtimes as this is a) how the runtime apps refer to them, e.g. "default OpenXR runtime", b) the terminology as detailed by Mbucchia, c) the fact that both Oculus and SteamVR both provide runtimes for supporting other implementations, e.g. the Oculus OVR runtime and the SteamVR OpenVR runtime.

[slughead]

While OXRTK is no longer "supported," it has also not needed any work for quite some time and is thus considered complete. As such, it still works with the caveats in the wiki. If you follow the wiki, it can coexist with QVFR. I still use OXRTK to reduce the FOV and thus the render resolution slightly to boost my frame time headroom with a Quest Pro over Virtual Desktop.

[sleighzy]

3 hours ago, slughead said:

I still use OXRTK to reduce the FOV and thus the render resolution

Yeah, a lot of people still use it for that reason. Interestingly the Quad-Views-Foveated docs actually state that the FOV in OXRTK shouldn't be used with it.

(Although, apologies, I've made an assumption here that you're using both)

Edited October 22, 2024 by sleighzy

[slughead]

6 hours ago, sleighzy said:

Yeah, a lot of people still use it for that reason. Interestingly the Quad-Views-Foveated docs actually state that the FOV in OXRTK shouldn't be used with it.

(Although, apologies, I've made an assumption here that you're using both)

 

I don’t use QVFR. It’s not necessary with a 4090, 13900k and DLSS. It can reduce performance on high end systems especially over cities.

[Qcumber]

21 hours ago, slughead said:

I still use OXRTK to reduce the FOV and thus the render resolution slightly to boost my frame time headroom with a Quest Pro over Virtual Desktop.

I have tried this and it really messes up QVFR with eye tracking.