DCS Crashes after taking off VR Headset

[WisMan]

Whenever I pause the game and take off my headset for more than a few second the game will freeze up and won't recover. When I put the headset back on it will the screen is frozen and I see the hour glass Icon for 30-60 seconds then DCS just closes. 

Is this a known common issue? Is there a known workaround or do I just need to keep my headset on for the duration of my mission.

On the most recent open beta version with a Quest 2 using OpenXR toolkit.

Computer spec:

RTX 3080, Ryzen 5 5600X, 32 gig ram. 

[BIGNEWY]

Hi, 

not a known issue. 

Please include your dcs log it may have some clues. 

I would also suggest checking your headset and its timeout / sleep settings 

thank you

[dutchili]

+1

The dcs.log does not mention it, nor is there a crash log created.

'Crash' is not the right word for me. When you put the (oculus quest 2) headset back on the screen is mostly black and the white hour glass is showing its waiting animation. 

The only way to recover is to restart DCS.

[Glowingheat]

I had something similar which was caused by the proximity sensor - I put some tape over it so that when I take the Quest 2 headset off it thinks its still on my head!

[WisMan]

6 hours ago, BIGNEWY said:

Hi, 

not a known issue. 

Please include your dcs log it may have some clues. 

I would also suggest checking your headset and its timeout / sleep settings 

thank you

The issue is very repeatable for me. Attached is a log file of it happening. I created a simple mission flew around for ~5 min then took off my headset for 10 seconds and when I put it back on the game was frozen. Approximate 30 seconds later the game closed itself.  No .crash or .dmp file is created. 

I'm will look into the timeout / sleep settings, but it happens so fast that I do not believe it is related to that. The default timeout for quest 2 is 2 min. 

5 hours ago, dutchili said:

'Crash' is not the right word for me. When you put the (oculus quest 2) headset back on the screen is mostly black and the white hour glass is showing its waiting animation. 

This sounds like exactly what is happening to me, except my game closes itself. 

 

1 hour ago, Glowingheat said:

I had something similar which was caused by the proximity sensor - I put some tape over it so that when I take the Quest 2 headset off it thinks its still on my head!

I've gotten around it by holding my thumb over the sensor if I'm taking it off to look at something quickly. 

dcs.log

[ricktoberfest]

I’ve also had this happen several times with a Rift S using the openxr runtime.  The openxr just seems so much less stable for me than the oculus runtime, including many uncommanded head re-centers. 

[juanar10]

Hi! I have the exact same issue as it was described. It doesn't happen 100% of the time, but maybe 80%?
Sometimes the game just hangs for ever, others it closes itself without any user prompt.

[diamond26]

Try this 

 

[juanar10]

14 hours ago, diamond26 said:

Try this 

 

Although this will help, it is by no means a solution to the problem nor the cause.

[diamond26]

On 3/31/2023 at 4:52 PM, Steel Jaw said:

What is “unlocked” motion reprojection?  Is that the auto asw in the ott?

 

9 minutes ago, juanar10 said:

Although this will help, it is by no means a solution to the problem nor the cause.

Until ED fix the issue is the only option in my case.

[SPAS79]

I have the same issue with a Q2. I put something on the sensor if I know I have to be off for more than 2 seconds. 

[juanar10]

A bit more to add: when you remove the headset, DCS keeps running, I believe the problem happens when you put it on again: one of the CPU threads gets locked at 100% and eventually it crashes.

This is what I got on the logs as soon as I placed the headset back on:

2023-04-20 21:25:16.993 WARNING LOG (23900): 58360 duplicate message(s) skipped.
2023-04-20 21:25:16.993 ERROR   VISUALIZER (Main): OpenXR xrWaitFrame failed with error: XR_ERROR_RUNTIME_FAILURE
2023-04-20 21:25:16.995 INFO    DXGUI_WIN_ADAPTER (Main): resize main window to [3440, 1440]
2023-04-20 21:25:17.005 ERROR   LuaHooks (Main): [string "I:\Xxxx\Saved Games\DCS\Scripts\DCS-gRPC\grpc.lua"]:263: attempt to index global 'grpc' (a nil value)
2023-04-20 21:25:17.005 INFO    VISUALIZER (Main): OpenXR: request restart
2023-04-20 21:25:17.005 INFO    VISUALIZER (Main): OpenXR: request exit
2023-04-20 21:25:17.005 INFO    EDCORE (Main): (dDispatcher)enterToState_:5
2023-04-20 21:25:17.005 ERROR   LuaHooks (Main): [string "I:\Xxxx\Saved Games\DCS\Scripts\DCS-gRPC\grpc.lua"]:263: attempt to index global 'grpc' (a nil value)
2023-04-20 21:25:17.005 ERROR   VISUALIZER (Main): OpenXR xrWaitFrame failed with error: XR_ERROR_SESSION_LOST
2023-04-20 21:25:17.006 ERROR   LuaHooks (Main): [string "I:\Xxxx\Saved Games\DCS\Scripts\DCS-gRPC\grpc.lua"]:263: attempt to index global 'grpc' (a nil value)
2023-04-20 21:25:17.006 ERROR   VISUALIZER (Main): OpenXR xrWaitFrame failed with error: XR_ERROR_SESSION_LOST
2023-04-20 21:25:17.008 INFO    APP (Main): application shutdown
2023-04-20 21:25:19.245 INFO    EDOBJECTS (Main): lTypeObjectManagerImpl::clear 0
2023-04-20 21:25:19.248 INFO    EDOBJECTS (Main): lTypeObjectManagerImpl::clear 1
2023-04-20 21:25:19.249 INFO    EDOBJECTS (Main): lTypeObjectManagerImpl::clear 2
2023-04-20 21:25:19.393 INFO    EDOBJECTS (Main): lTypeObjectManagerImpl::clear 3
2023-04-20 21:25:19.513 INFO    EDOBJECTS (Main): lTypeObjectManagerImpl::clear 4
2023-04-20 21:25:19.530 INFO    EDOBJECTS (Main): lTypeObjectManagerImpl::clear 5
2023-04-20 21:25:19.533 INFO    EDOBJECTS (Main): lTypeObjectManagerImpl::clear 6
2023-04-20 21:25:19.537 INFO    EDOBJECTS (Main): lTypeObjectManagerImpl::clear 7
2023-04-20 21:25:19.538 INFO    EDOBJECTS (Main): lTypeObjectManagerImpl::clear 8
2023-04-20 21:25:19.541 INFO    EDOBJECTS (Main): lTypeObjectManagerImpl::clear 9
2023-04-20 21:25:19.541 INFO    EDOBJECTS (Main): lTypeObjectManagerImpl::clear 10
2023-04-20 21:25:19.542 INFO    EDOBJECTS (Main): lTypeObjectManagerImpl::clear 11
2023-04-20 21:25:19.543 INFO    EDOBJECTS (Main): lTypeObjectManagerImpl::clear 12
2023-04-20 21:25:19.543 INFO    EDOBJECTS (Main): lTypeObjectManagerImpl::clear 13
2023-04-20 21:25:20.573 INFO    TERRAIN (Main): lSystem::exit()
2023-04-20 21:25:20.578 INFO    TERRAIN (Main): lSystem::CleanScenes()
2023-04-20 21:25:28.788 INFO    DXGUI_WIN_ADAPTER (Main): resize main window to [3440, 1440]
2023-04-20 21:25:28.789 WARNING SCENE (8824): Scene was removed with 4 alive objects
2023-04-20 21:25:28.790 WARNING SCENE (8824): Scene was removed with 1 alive lights
2023-04-20 21:25:28.796 WARNING SCENE (8824): Scene was removed with 4 alive objects
2023-04-20 21:25:29.248 INFO    DX11BACKEND (8824): DX11Renderer::shutdown()
2023-04-20 21:25:30.502 INFO    EDCORE (Main): try to write dump information
2023-04-20 21:25:30.505 INFO    EDCORE (Main): # -------------- 20230420-212531 --------------
2023-04-20 21:25:30.505 INFO    EDCORE (Main): DCS/2.8.4.38947 (x86_64; MT; Windows NT 10.0.19044)
2023-04-20 21:25:30.506 INFO    EDCORE (Main): I:\Games\steamapps\common\DCSWorld\bin-mt\DCS.exe
2023-04-20 21:25:30.506 INFO    EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ff6c3b559d1 00:00000000
2023-04-20 21:25:30.507 INFO    EDCORE (Main): SymInit: Symbol-SearchPath: '.', symOptions: 532, UserName: 'Xxxxs'
2023-04-20 21:25:30.508 INFO    EDCORE (Main): OS-Version: 10.0.19044 () 0x300-0x1
2023-04-20 21:25:30.510 INFO    EDCORE (Main): 0x00000000008959d1 (DCS): SW + 0x3FF2C1
2023-04-20 21:25:30.510 INFO    EDCORE (Main): 0x000000000085457f (DCS): SW + 0x3BDE6F
2023-04-20 21:25:30.511 INFO    EDCORE (Main): 0x0000000000107a27 (Visualizer): smSceneManager::DestroySceneManager + 0xD7
2023-04-20 21:25:30.512 INFO    EDCORE (Main): 0x000000000086fb1e (DCS): SW + 0x3D940E
2023-04-20 21:25:30.512 INFO    EDCORE (Main): 0x000000000236153a (DCS): AmdPowerXpressRequestHighPerformance + 0xFBC536
2023-04-20 21:25:30.512 INFO    EDCORE (Main): 0x0000000000c51a92 (DCS): SW + 0x7BB382
2023-04-20 21:25:30.513 INFO    EDCORE (Main): 0x0000000000017604 (KERNEL32): BaseThreadInitThunk + 0x14
2023-04-20 21:25:31.352 INFO    EDCORE (Main): Minidump created.
2023-04-20 21:25:31.352 INFO    Lua::Config (Main): stack traceback:

 

[biotech]

If you using OXR Toolkit, check Turbo Mode option in it. In my case that option in 'ON' state causes DCS to crash when headset taked off an then on (or switched off -> on by its own button).

Edited May 2, 2023 by biotech

[Ratfink]

I get this happen most times when I pause the flight, remove headset, wait a while, put headset back on in MT with Rift S. I don't recall this being an issue until now, and seems entirely repeatable.

[Edit - does not occur in ST which uses Oculus API and not OpenXR]

I can see the paused image, though mainly missing, and the spinning hour glass before it CTD

Log attached. Guessing this is the crucial bit

2023-05-02 21:29:31.669 ERROR   VISUALIZER (Main): OpenXR xrWaitFrame failed with error: XR_ERROR_SESSION_LOST
2023-05-02 21:29:31.677 INFO    EDCORE (Main): (dDispatcher)enterToState_:5
2023-05-02 21:29:31.678 ERROR   VISUALIZER (Main): OpenXR xrWaitFrame failed with error: XR_ERROR_SESSION_LOST
2023-05-02 21:29:31.684 WARNING LOG (10996): 1 duplicate message(s) skipped.
2023-05-02 21:29:31.684 INFO    APP (Main): application shutdown

dcs.log

Edited May 2, 2023 by Ratfink

[Ratfink]

Oculus app updated today to Oculus app version 53.0.0.105.132 (53.0.0.105.132) but DCS MT still crashes on pause (tested with F-18 free flight on Caucasus - flew for 20 secs or so, pause game, remove headset, wait 10 secs replace headset - hang then CTD)

I opened the log from OpenXR Toolkit Companion, pasted below. Maybe I will try the registry hack to disable OpenXR and force Oculus API

[OXRTK] 2023-05-03 17:43:06 +0100: OpenXR Toolkit - GA-2 (v1.2.4)
[OXRTK] 2023-05-03 17:43:06 +0100: dllHome is "C:\Program Files\OpenXR-Toolkit"
[OXRTK] 2023-05-03 17:43:06 +0100: OpenXR-Toolkit layer is active
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_KHR_D3D11_enable
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_KHR_D3D12_enable
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_KHR_opengl_enable
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_KHR_vulkan_enable
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_KHR_vulkan_enable2
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_KHR_composition_layer_depth
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_KHR_win32_convert_performance_counter_time
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_KHR_convert_timespec_time
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_KHR_composition_layer_cube
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_KHR_composition_layer_cylinder
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_KHR_composition_layer_equirect
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_KHR_visibility_mask
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_KHR_composition_layer_color_scale_bias
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_EXT_win32_appcontainer_compatible
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_EXT_debug_utils
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_OCULUS_recenter_event
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_OCULUS_audio_device_guid
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_FB_color_space
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_FB_display_refresh_rate
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_META_performance_metrics
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_META_headset_id
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_OCULUS_ovrsession_handle
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_FB_haptic_amplitude_envelope
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_FB_haptic_pcm
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_FB_touch_controller_pro
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_FB_touch_controller_proximity
[OXRTK] 2023-05-03 17:43:06 +0100: Runtime supports extension: XR_OCULUS_external_camera
[OXRTK] 2023-05-03 17:43:06 +0100: Application name: 'DCS World', Engine name: ''
[OXRTK] 2023-05-03 17:43:06 +0100: Using OpenXR runtime Oculus 1.85.0
[OXRTK] 2023-05-03 17:43:06 +0100: Using OpenXR system Oculus Rift S
[OXRTK] 2023-05-03 17:43:06 +0100: Overriding OpenXR resolution: 2250x2424
[OXRTK] 2023-05-03 17:43:06 +0100: Using OpenXR resolution (no upscaling): 2250x2424
[OXRTK] 2023-05-03 17:43:06 +0100: Using OpenXR resolution (no upscaling): 2250x2424
[OXRTK] 2023-05-03 17:43:09 +0100: Using Direct3D 11 on adapter: NVIDIA GeForce RTX 3080
[OXRTK] 2023-05-03 17:43:09 +0100: MipMap biasing for upscaling is: -0.000
[OXRTK] 2023-05-03 17:43:10 +0100: Open menu with CTRL+F2
[OXRTK] 2023-05-03 17:43:10 +0100: Creating swapchain with dimensions=2252x2424, arraySize=1, mipCount=1, sampleCount=1, format=29, usage=0x21
[OXRTK] 2023-05-03 17:43:10 +0100: Creating swapchain with dimensions=2252x2424, arraySize=1, mipCount=1, sampleCount=1, format=29, usage=0x21
[OXRTK] 2023-05-03 17:43:13 +0100: Projection calibration: -0.06915, 0.06993 | 0.06915, 0.06993
[OXRTK] 2023-05-03 17:43:19 +0100: Late initializeInterceptor() call
[OXRTK] 2023-05-03 17:44:50 +0100: xrEndFrame: XrResult failure [XR_ERROR_SESSION_NOT_RUNNING]
    Origin: OpenXrApi::xrBeginFrame(m_vrSession, nullptr)
    Source: D:\a\OpenXR-Toolkit\OpenXR-Toolkit\XR_APILAYER_NOVENDOR_toolkit\layer.cpp:3254
[OXRTK] 2023-05-03 17:45:34 +0100: D3D11Device destroyed
[OXRTK] 2023-05-03 17:45:34 +0100: Session destroyed

 

 

 

[Ratfink]

OK so DCS MT crash after remove/replace headset DOES NOT occur when forcing Oculus API by setting registry key

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenXR\1

ActiveRuntime="None"

Ran DCS MT forced in Oculus

Later confirmed using Oculus API not OpenXR

2023-05-03 17:35:25.405 ERROR   VISUALIZER (Main): OpenXR exception: XrResult failure [XR_ERROR_RUNTIME_UNAVAILABLE]
    Origin: xrEnumerateInstanceExtensionProperties(nullptr, 0, &instanceExtensionCount, nullptr)
    Source: Projects\Visualizer\Source\OpenXR\openxr_program.cpp:163
2023-05-03 17:35:25.536 INFO    VISUALIZER (Main): LAUNCH IN VR OculusRift: OculusRift : Oculus Rift S

So issue seems to be related to OpenXR crashing causing DCS to crash when remove/replace headset

[Ratfink]

According to https://registry.khronos.org/OpenXR/specs/1.0/man/html/XrResult.html

Error code from my dcs.log

XR_ERROR_SESSION_LOST

The XrSession was lost. It will need to be destroyed and optionally recreated.

How can the cause of the lost XrSession be determined? It's clearly linked to removal of the headset making the device sleep, but I can't find a way to stop that happening.

It's happening 9/10 times, and is really quite frustrating as though it doesn't happen with native Oculus API on my system, OpenXR performance is much better for me. Enabling Turbo mode in OXR smooths out all the sticky/stutter menus at load time which I haven't found a solution for with OTT or any other setting. (Only an issue in MT)

Hoping this can be fixed soon.

 

[kerlcat]

+1

Same here with Pico4. Image frozen after headset took off, everytime. No crash recorded while nothing more could do but kill the process thread and restart again. 

No tool kit or something used. Only run it w/ OpenXR. 

[Recluse]

Just chiming in with exactly this issue on Oculus QUEST 2 + OpenXR + MT. 

 

EDIT: I taped over my QUEST 2 Proximity Sensor as described in one of the posts above and it SEEMS to be a good workaround.  Would be nice to fix the issue so it wasn't necessary, but for now, it  does the trick.

Edited May 17, 2023 by Recluse

[Ratfink]

Just chiming in with exactly this issue on Oculus QUEST 2 + OpenXR + MT. 
 
EDIT: I taped over my QUEST 2 Proximity Sensor as described in one of the posts above and it SEEMS to be a good workaround.  Would be nice to fix the issue so it wasn't necessary, but for now, it  does the trick.

Yes, a bit of ripped post it note over the sensor is my solution

I did notice DCS MT wouldn’t load unless the headset was active (on head prior to post it note solution) and have concluded the Open XR runtime must have the headset active to allow DCS to function, whereas using ST or forcing Oculus API using reg edit fix it’s fine.


Sent from my iPhone using Tapatalk

[Suet]

Same problem here, using Quest Pro with AirLink.

Please note this is NOT a problem with the VR headset going sleep.
Mine is configured to enter sleep mode after 15 min. of inactivity, but this problem occurs as soon as i wear off the headset.

 

[Recluse]

16 minutes ago, Suet said:

Same problem here, using Quest Pro with AirLink.

Please note this is NOT a problem with the VR headset going sleep.
Mine is configured to enter sleep mode after 15 min. of inactivity, but this problem occurs as soon as i wear off the headset.

 

Tape/Post-it over the sensor. Problem solved (for now...it would be nice to fix it on the DCS end) Just be sure to shut down the headset manually when you are done with it.

Edited June 2, 2023 by Recluse

[actually_fred]

On 5/4/2023 at 4:31 PM, Ratfink said:

According to https://registry.khronos.org/OpenXR/specs/1.0/man/html/XrResult.html

Error code from my dcs.log

XR_ERROR_SESSION_LOST

The XrSession was lost. It will need to be destroyed and optionally recreated.

How can the cause of the lost XrSession be determined? It's clearly linked to removal of the headset making the device sleep, but I can't find a way to stop that happening.

It's happening 9/10 times, and is really quite frustrating as though it doesn't happen with native Oculus API on my system, OpenXR performance is much better for me. Enabling Turbo mode in OXR smooths out all the sticky/stutter menus at load time which I haven't found a solution for with OTT or any other setting. (Only an issue in MT)

Hoping this can be fixed soon.

 

FWIW, the session being terminated is not an unexpected error - the error is DCS calling a function that requires a session after the session has been terminated, i.e. DCS is not properly handling the OpenXR session lifecycle (https://registry.khronos.org/OpenXR/specs/1.0/html/xrspec.html#session-lifecycle)

The XR_SESSION_STATE_LOSS_PENDING message should have been received by DCS first, and DCS should have paused its' interaction with the headset, and recreated later:

https://registry.khronos.org/OpenXR/specs/1.0/html/xrspec.html#XrEventDataSessionStateChanged
 

Quote

Receiving the XR_SESSION_STATE_LOSS_PENDING state indicates the runtime is no longer able to operate with the current session, for example due to the loss of a display hardware connection

Probably Link de-activating or entering some kind of sleep mode when you remove the headset. This especially makes sense for airlink on battery.
 

Quote

 An application should call xrDestroySession and may end its process or decide to poll xrGetSystem at some reasonable cadence to get a new XrSystemId, and re-initialize all graphics resources related to the new system, and then create a new session using xrCreateSession. 

XR_ERROR_SESSION_LOST means that no handling has been done here, and calls are incorrectly being made with a no-longer-valid XrSession.

IMO the 'may' behavior here is basically the bare minimum for any VR experience with play sessions that last more than a few minutes: all headsets should enter a lower power/heat mode when removed from the head, and terminating the session is a reasonable low-power behavior for wireless headsets. Removing the headset temporarily should be expected for games with multi-hour sessions.

A better alternative would be MSFS-style switching between VR and non-VR: when the XrSession is lost, switch to non-vr. When user hits shift-tab or some other shortcut, recreate the session and switch back.

Edited June 4, 2023 by actually_fred

[hannibal]

On 4/9/2023 at 2:01 AM, diamond26 said:

Try this 

 

i need to try this, because i have the same problem on a quest pro

Edited June 4, 2023 by hannibal

[actually_fred]

Quote

Oculus API

The difference here is that the Oculus PC API is basically unchanged since the original Rift, and no new features will be added to it; when using the Oculus PC API, link/airlink are designed to act like a Rift, where 'shut down the headset entirely when I take it off my head' doesn't make sense - so there is no concept of removing and re-connecting a headset mid-game in the Oculus PC API. There is in OpenXR, and DCS isn't handling it well.

Edited June 4, 2023 by actually_fred