Taking off quest 3 crashes DCS

[Dave317]

It doesn't always do this but more often than not if I take of my headset DCS will hang and then crash.  Is there any way around this?

[unlikely_spider]

The default is for the headset to sleep almost right when you take it off. Somewhere in the settings is one that I changed to 15 minutes I believe. I could be wrong but I think that's the cause.

Edited February 23, 2024 by unlikely_spider

[slughead]

ED is not handling the Quest in this regard particularly well as I understand it.  mbucchia added a workaround in his Quad View Foveated Rendering OpenXR layer. The fix is fairly simple and ED could incorporate it into their code should they choose. In the meantime, you could install QVFR and if you don't like it, you can disable it for DCS... but the sleep fix still works. That's what I have done.

[killerquagmire]

On 2/23/2024 at 12:19 PM, Dave317 said:

It doesn't always do this but more often than not if I take of my headset DCS will hang and then crash.  Is there any way around this?

if you are using XR tool kit Turbo mode and DCS MT then it will result in a freeze/crash when you take off the headset. Turn off turbo mode in XR tool kit and that should fix the issue.

At least it did for me. 

[Steel Jaw]

Happens with quest 2  as well 

[diego999]

1 hour ago, killerquagmire said:

if you are using XR tool kit Turbo mode and DCS MT then it will result in a freeze/crash when you take off the headset. Turn off turbo mode in XR tool kit and that should fix the issue.

At least it did for me. 

Exactly this.

A simple but not very elegant fix is to cover the sensor with a piece of tape.

[Dave317]

Thanks for the replies.  I tried the bit of tape over the sensor but that made no difference.  For me it was turbo mode that was causing it. 

[slughead]

42 minutes ago, Dave317 said:

Thanks for the replies.  I tried the bit of tape over the sensor but that made no difference.  For me it was turbo mode that was causing it. 

Are you also using the quad view foveated rendering openxr layer?

[Dave317]

I was by I couldn't get on with it so I deleted it. 

[slughead]

10 minutes ago, Dave317 said:

I was by I couldn't get on with it so I deleted it. 

Ok. It’s just that if you have both installed you should only use the turbo mode in qvfr.

[McDaniel]

Or use sidequest and disable proximity sensor... the headset will always be on...drawback battery life

McD Out

[Raffa]

I had this issue with the Q2 and Q3. It happened using Oculus link, steam vr via virtual desktop and natively in virtual desktop.

What happens to me is that the image freezes in the headset, the audio and the game still goes, and if I lift the headset, the visual in the monitor still goes like nothing has happened.

I noticed this crash when the vram gets very low (i currently have a 4070ti super) or when switching often between f10 map and cockpit.

Raised this issue in the virtual desktop discord but the devs (amazing guys) couldn't find and explanation nor being able to reproduce the issue.

[PatMcKrotch]

On mine, I'm using steamVR as I find that Meta just crashes out of the gate.  Virtual desktop works, but no hand tracking.   The game runs fine for awhile, then my PC fans spool down and the system freezes.  I just got the Quest 3 working, then it this started happening. FML

On 4/9/2024 at 8:13 AM, Raffa said:

his crash when the vram gets very low (i currently have a 4070ti super) or when switching often between f10 ma

 

DxDiag.txt dcs.log

[sleighzy]

On 2/9/2025 at 5:54 PM, PatMcKrotch said:

On mine, I'm using steamVR as I find that Meta just crashes out of the gate.  Virtual desktop works, but no hand tracking.   The game runs fine for awhile, then my PC fans spool down and the system freezes.  I just got the Quest 3 working, then it this started happening. FML

 

DxDiag.txt 156.17 kB · 4 downloads dcs.log 540.28 kB · 3 downloads

This log is when using the SteamVR OpenXR runtime. I've listed the issue below. Would be interested in seeing a similar log when running the Meta OpenXR runtime to see what the root cause is in there as well.

VirtualDesktop does actually support hand tracking as well.

I've run your log through the DCS log analyzer which has identified this as a GPU error:

There is a GPU-related error

• Remove any overclocking from your GPU. (some GPUs come with a factory overclock if you are not doing this yourself, check with MSI Afterburner)
• Uninstall your GPU driver with DDU and install a clean one.

This can also be seen in your log with the spammed DXGI_ERROR_DEVICE_REMOVED errors. See the article below on this as well.

Errors or Crashes on startup or gameplay of DCS World

Looking at your log I see you also have a dxgi.dll file in the DCS\bin directory. I know of only two reasons why you would have put that there, it does not come with the game, and that has also been known to cause crashes. Remove that as well.

Additional performance tuning items, note that SSAO and SSLR are performance hits with little benefit.

• Turn off SSAO.
• Turn off Depth of Field.
• Disable civil traffic.
• Turn off SSLR.

 

EDIT: Realise this is for a completely different problem. @PatMcKrotch , if problems persist after this then raise a new post vs. piggy-backing off this one.

Edited February 10 by sleighzy

[PatMcKrotch]

On 2/9/2025 at 2:24 PM, sleighzy said:

This log is when using the SteamVR OpenXR runtime. I've listed the issue below. Would be interested in seeing a similar log when running the Meta OpenXR runtime to see what the root cause is in there as well.

VirtualDesktop does actually support hand tracking as well.

I've run your log through the DCS log analyzer which has identified this as a GPU error:

There is a GPU-related error

• Remove any overclocking from your GPU. (some GPUs come with a factory overclock if you are not doing this yourself, check with MSI Afterburner)
• Uninstall your GPU driver with DDU and install a clean one.

This can also be seen in your log with the spammed DXGI_ERROR_DEVICE_REMOVED errors. See the article below on this as well.

Errors or Crashes on startup or gameplay of DCS World

Looking at your log I see you also have a dxgi.dll file in the DCS\bin directory. I know of only two reasons why you would have put that there, it does not come with the game, and that has also been known to cause crashes. Remove that as well.

Additional performance tuning items, note that SSAO and SSLR are performance hits with little benefit.

• Turn off SSAO.
• Turn off Depth of Field.
• Disable civil traffic.
• Turn off SSLR.

 

EDIT: Realise this is for a completely different problem. @PatMcKrotch , if problems persist after this then raise a new post vs. piggy-backing off this one.

 

I had some time today to try out the fixes.

 

I uninstalled Gamefirst (Asus program to boost system resources to games)

Uninstalled AI Suite 3 (GPU was running on Smart mode in this program)

Used the NVIDIA App to "Automatically tune" the GPU

removed the chipset driver that ASUS installed via armory crate and installed the one from the AMD website support page.

Shut down all non essential start up programs.

Ran a repair on DCS, deleted all excess files.

 

Along the way I tried running the game with similar crashes, but the repair run seemed to do the trick.

 

The game ran for quite some time, there were a few stutters in game.  I couldn't keep up in a dog fight in my tomcat vs a Viggen as the lag was making it appear to jump all over the place.  The game did end up crashing when I switched to external view after being in the F10 map.  I find if I switch views and go into the map too much, the game lags a bit more.

 

It's definitely a step in the right direction and I appreciate the help.  Ironically the computer is drawing less power and is a lot quieter without all that ASUS crap running it proving to me, that it's really doesn't help.

DxDiag.txt dcs.log

[sleighzy]

1 hour ago, PatMcKrotch said:

 

I had some time today to try out the fixes.

 

I uninstalled Gamefirst (Asus program to boost system resources to games)

Uninstalled AI Suite 3 (GPU was running on Smart mode in this program)

Used the NVIDIA App to "Automatically tune" the GPU

removed the chipset driver that ASUS installed via armory crate and installed the one from the AMD website support page.

Shut down all non essential start up programs.

Ran a repair on DCS, deleted all excess files.

 

Along the way I tried running the game with similar crashes, but the repair run seemed to do the trick.

 

The game ran for quite some time, there were a few stutters in game.  I couldn't keep up in a dog fight in my tomcat vs a Viggen as the lag was making it appear to jump all over the place.  The game did end up crashing when I switched to external view after being in the F10 map.  I find if I switch views and go into the map too much, the game lags a bit more.

 

It's definitely a step in the right direction and I appreciate the help.  Ironically the computer is drawing less power and is a lot quieter without all that ASUS crap running it proving to me, that it's really doesn't help.

DxDiag.txt 150.87 kB · 0 downloads dcs.log 264.37 kB · 0 downloads

Raise a new forum post, these issues are unrelated to the current topic.

The latest crash is the same as the last one, i.e. GPU issue. This is also seen with the LiveKernelEvent errors with code 141 in your DxDiag report. Based on your comment above it doesn't sound like you've followed the steps to address it yet. The latest log also shows that hotplugging has been enabled in the DCS controls settings (wasn't present in the earlier one). Disable that as well as it can cause stutters as it polls for new devices.

Edited February 11 by sleighzy