Quest 3 - Removing headset for a few seconds stops DCS

[Guest]

Hi All,

Putting my headset back on, no longer continues on with the game.  It used to, up until maybe 3 weeks ago.  

DCS seems frozen (but I can't tell if it is DCS that has stopped working, or it is a Quest 3 thing).

I have checked the power/sleep settings in the Q3, it does not sleep before I put it back on.

Q3 says it has the latest software.  Nvidia drivers I believe are the latest.  Windows is up to date.

Any help gratefully recieved.  (I'm new to the Q3, so a lot to learn still.)

Cheers

'52

dcs.log

[rcjonessnp175]

same issue here if using meta software,  totally uninstalled that stuff and use Virtual desktop, i now can take headset off  and put back on and doesn't go black screen like the meta software. 

[Guest]

8 minutes ago, rcjonessnp175 said:

same issue here if using meta software,  totally uninstalled that stuff and use Virtual desktop, i now can take headset off  and put back on and doesn't go black screen like the meta software. 

Oh that's great!  I'm really new at this, and got all confused.  I heard VD is great, and you can use it with a USB-C cable, so bought it, but now it seems like I have to do other things to get that to work?

So VD works without any Meta software loaded?

[rcjonessnp175]

https://discord.gg/SAq65JPh  best is to read up on the discord for the app has all the step by step instructions, short answer is no its wireless as most of us buy a second dedicated router that only the headset connects to for wireless.  Totally uninstall all the oculus and meta software as its not used for VD

[Guest]

20 minutes ago, rcjonessnp175 said:

https://discord.gg/SAq65JPh  best is to read up on the discord for the app has all the step by step instructions, short answer is no its wireless as most of us buy a second dedicated router that only the headset connects to for wireless.  Totally uninstall all the oculus and meta software as its not used for VD

That is extremely helpful!

Appreciate you taking the time to help out.

Have a good one

'52

[diego999]

3 hours ago, Gunslinger52 said:

Hi All,

Putting my headset back on, no longer continues on with the game.  It used to, up until maybe 3 weeks ago.  

DCS seems frozen (but I can't tell if it is DCS that has stopped working, or it is a Quest 3 thing).

I have checked the power/sleep settings in the Q3, it does not sleep before I put it back on.

Q3 says it has the latest software.  Nvidia drivers I believe are the latest.  Windows is up to date.

Any help gratefully recieved.  (I'm new to the Q3, so a lot to learn still.)

Cheers

'52

dcs.log 149.51 kB · 6 downloads

 

Are you using OpenXR Toolkit?

[sleighzy]

Can try putting tape over the sensor as well. A few people do that to stop it sleeping for that very reason (although in your case it hasn’t actually gone to sleep). 

[Guest]

On 2/23/2025 at 1:34 PM, diego999 said:

 

Are you using OpenXR Toolkit?

Yes I am.  And yes @sleighzy, I reverted to tape over the sensor, and it has stopped the issue.

I have purchased Virtual Desktop, so need to sort out a new router or else figure out to use it via USB-C  

[sleighzy]

1 hour ago, Gunslinger52 said:

or else figure out to use it via USB-C

Router is the way to go for official support, or if Meta change anything that prevents the steps in the below guide from working. It may be enough just to use a usb-c to ethernet adapter for VirtualDesktop and Quest 3 (it does for some folk), however if you need the extra steps to get it working (note that these may only be needed for a Quest Pro ) then you can try them here: 

 

Edited February 24 by sleighzy

[Guest]

16 hours ago, sleighzy said:

Router is the way to go for official support, or if Meta change anything that prevents the steps in the below guide from working. It may be enough just to use a usb-c to ethernet adapter for VirtualDesktop and Quest 3 (it does for some folk), however if you need the extra steps to get it working (note that these may only be needed for a Quest Pro ) then you can try them here: 

 

Appreciate it, cheers

[heavyj]

If you’re using OpenXR toolkit, turn off turbo mode to see if that fixes the issue.


Sent from my iPhone using Tapatalk

[Monash]

As the title says: If I am in a mission and I remove my quest 3 headset or simply just raise it up see out, then DCS will immediately freeze and, after 10-20 seconds, crash to desktop.  It did not do this before.  

I do not experience this issue in IL-2 (opencomposite) or Falcon BMS (OpenXR).

PS. It is not the headset going to sleep.  

PPS. I just updated the oculus link software today.

dcs.log

Edited May 13 by Monash

[BIGNEWY]

Hi, 

not seeing the crash in the log, only the openXR session timing out / going idle and then a runtime failure. 

2025-05-13 09:17:50.106 INFO    VISUALIZER (Main): [19:17:50.257][Info   ] OpenXR: XrEventDataSessionStateChanged: state XR_SESSION_STATE_FOCUSED->XR_SESSION_STATE_VISIBLE session=3 time=4730159398600
2025-05-13 09:17:50.106 INFO    VISUALIZER (Main): [19:17:50.257][Info   ] OpenXR: XrEventDataSessionStateChanged: state XR_SESSION_STATE_VISIBLE->XR_SESSION_STATE_SYNCHRONIZED session=3 time=4730159412300
2025-05-13 09:17:50.106 INFO    VISUALIZER (Main): [19:17:50.257][Info   ] OpenXR: XrEventDataSessionStateChanged: state XR_SESSION_STATE_SYNCHRONIZED->XR_SESSION_STATE_STOPPING session=3 time=4730159458800
2025-05-13 09:17:50.106 INFO    VISUALIZER (Main): [19:17:50.258][Info   ] OpenXR: XrEventDataSessionStateChanged: state XR_SESSION_STATE_STOPPING->XR_SESSION_STATE_IDLE session=3 time=4730159670900
2025-05-13 09:17:50.138 ERROR   VISUALIZER (27576): xrEndFrame failed with error: XR_ERROR_RUNTIME_FAILURE
2025-05-13 09:17:51.362 INFO    VISUALIZER (Main): [19:17:51.513][Info   ] OpenXR: XrEventDataSessionStateChanged: state XR_SESSION_STATE_IDLE->XR_SESSION_STATE_READY session=3 time=4731415279700

 

[Monash]

Hi Bignewy,

Yes I saw the same thing.  I'm staggeringly ignorant about all this stuff, but I can observe that (1) all these problems arose with updates to the Oculus Link software and (2) the log file seems to be point to an error that looks suspiciously like something the Oculus software should be handling.  So probably an Meta problem, not a DCS problem.  Which means I'm out of luck I guess.

Monash

 

[BIGNEWY]

I will ask our team members who use meta, if I hear anything I will let you know. 

[Monash]

11 minutes ago, BIGNEWY said:

I will ask our team members who use meta, if I hear anything I will let you know. 

That would be tremendously helpful.  Thank you!

[Shades71]

Similar report was submitted back in Feb, maybe try some of those suggestions.

 

[Monash]

Thanks, I will try these.  Bit embarrassed I missed that earlier post.

[BIGNEWY]

let us know if it helps. 

I will merge the posts so its all in one place it may help others in the future.

 

[Grytvanten]

I had the same issue, but with Varjo Base and Varjo Aero - Fresh out of nowere DCS started to crash, not when starting DCS, nor loading the mission/MP server, but when entering a slot. - I did everything in my power, but eventually I made a clean install of both Win 11 as with DCS World. It did not work with just installing DCS or Varjo Base, only the fresh install helped. - It might have been something in registry or Appdata, hidden files and so on, I do not know, but I didn't have time to bother, figured out a fresh download and aclean install of Win 11 as with DCS World would go faster.. And it worked.

[skywalker22]

Same issue with Quest Pro for the last couple of months. 

PS: also tried with Turbo mode on OFF, and the game still crashes when putting headset off my head.

Edited May 14 by skywalker22

[Mr_sukebe]

Try going into Device Manager, and disabling the power saving mode for the USB hubs.

[Monash]

I have removed DCS and the Saved Game folder and reinstalled just the base game, no mods, no additional modulus.  I have confirmed power saving mode is off for all USB controllers in device manager.  The problem is still there.  Going to dig into the suggestions in the other thread and see if anything there works.  Thanks all for your suggestions.

[Monash]

I feel pretty foolish.  After reading the old thread I turned off OpenXR Toolkit and now the problem appears to be resolved.  I really should have thought of this obvious possibility before reinstalling!  Going to reinstall the modules and hope the fix remains.  Cheers everyone.