DCS Crashes after taking off VR Headset

[Suet]

On 6/2/2023 at 5:34 PM, Recluse said:

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.

 

I found a workaround by sofware: disabling Guardian in Settings->Developer features. It seems that turns off the proximity sensor as well.

Your account must be registered as developer, to get access to this option.

[slughead]

On 6/6/2023 at 10:07 AM, Suet said:

I found a workaround by sofware: disabling Guardian in Settings->Developer features. It seems that turns off the proximity sensor as well.

Your account must be registered as developer, to get access to this option.

I have had problems with tracking and dropping down to 3DOF with the guardian disabled. Have you experienced this?

[Recluse]

On 6/6/2023 at 5:07 AM, Suet said:

I found a workaround by sofware: disabling Guardian in Settings->Developer features. It seems that turns off the proximity sensor as well.

Your account must be registered as developer, to get access to this option.

Since I got the update to V55, I noticed that the Oculus Debug Tool now has an option to Bypass the Proximity Sensor Check

.  It does not "stick" and has to be enabled every time you bring up the Debug tool.   I took the tape off my Prox Sensor and used this option and it seems to work (unless something else got fixed by the update). No need to go to Developer Mode

null

[DaPhoenix]

On 5/2/2023 at 10:45 AM, biotech said:

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).

 

^This^! Was having this exact issue and this has taken care of it. THanks

[Lange_666]

It doesn't only crash when i take the headset off but also when i wait to put it on. Before the second to last update i started to not put the headset on while DCS was loading because it took an awful lot of time to load (which is corrected an update or 2 ago). When not putting the headset on it gives the same crash result in MT with Turbo set to ON.

Just to add to the story...

 

 

[Ahdidaas]

I'm getting something similar.  I'm using Airlink, and I used the meta quest developer hub to turn off guardian and proximity.  mine crashes while playing, i'm not taking the headset off even.  I'd love some advice here.  Never had this problem before, seems to have started about two weeks ago.  I even factory reset my gaming laptop to start fresh, nothing changed, I always crash around 10-15 min in the game.
 

2023-08-31 05:45:26.687 INFO    LUA (Main): Lua CPU usage: metric: average game loading: 40.0621 %
2023-08-31 05:46:46.287 INFO    DXGUI_WIN_ADAPTER (Main): resize main window to [1380, 1380]
2023-08-31 05:46:46.414 INFO    VISUALIZER (Main): OpenXR: request restart
2023-08-31 05:46:46.414 INFO    VISUALIZER (Main): OpenXR: request exit
2023-08-31 05:46:46.414 INFO    EDCORE (Main): (dDispatcher)enterToState_:5
2023-08-31 05:46:46.414 ERROR   VISUALIZER (Main): OpenXR xrWaitFrame failed with error: XR_ERROR_SESSION_LOST
2023-08-31 05:46:46.416 WARNING LOG (18268): 1 duplicate message(s) skipped.
2023-08-31 05:46:46.416 INFO    APP (Main): application shutdown
2023-08-31 05:46:46.687 INFO    EDOBJECTS (Main): lTypeObjectManagerImpl::clear 0
2023-08-31 05:46:46.689 INFO    EDOBJECTS (Main): lTypeObjectManagerImpl::clear 1
2023-08-31 05:46:46.689 INFO    EDOBJECTS (Main): lTypeObjectManagerImpl::clear 2
2023-08-31 05:46:46.771 INFO    EDOBJECTS (Main): lTypeObjectManagerImpl::clear 3
2023-08-31 05:46:46.835 INFO    EDOBJECTS (Main): lTypeObjectManagerImpl::clear 4
2023-08-31 05:46:46.845 INFO    EDOBJECTS (Main): lTypeObjectManagerImpl::clear 5
2023-08-31 05:46:46.847 INFO    EDOBJECTS (Main): lTypeObjectManagerImpl::clear 6
2023-08-31 05:46:46.848 INFO    EDOBJECTS (Main): lTypeObjectManagerImpl::clear 7
2023-08-31 05:46:46.848 INFO    EDOBJECTS (Main): lTypeObjectManagerImpl::clear 8
2023-08-31 05:46:46.849 INFO    EDOBJECTS (Main): lTypeObjectManagerImpl::clear 9
2023-08-31 05:46:46.849 INFO    EDOBJECTS (Main): lTypeObjectManagerImpl::clear 10
2023-08-31 05:46:46.849 INFO    EDOBJECTS (Main): lTypeObjectManagerImpl::clear 11

 

[Ahdidaas]

I may have found it - I recently started running the Q2 on 90hz, getting a steady 45fps w/ aws.   I changed it to 72hz (still getting 45+ fps), and played a 3 hr session with no issues.  even taking it off to goto the bathroom.  Not sure it applies to folks here, it worked for me (so far).

[Recluse]

As posted above, this has not happened to me since turning BYPASS PROXIMITY SENSOR CHECK - ON in Oculus Debug Tool at the start of every session.

I am using AIRLINK (with cable connection for power) 90 Hz and OPENXR Toolkit with MT executable.

Edited August 31, 2023 by Recluse

[Falconeer]

try setting turbo mode to off in OpenXR, before removing headset

[bruto12]

That ia the trick! Switching off turbo mode no more freezing.  Thanks Falconeer

Hope it will be fixed soon by the OPenxr teams.

 

Tx!

[Falconeer]

You're welcome