TFS Posted April 19 Posted April 19 Hello y'all, been using the Quest 3 since launch in DCS and I have always been able to take the headset off and leave for either a break, or a brief moment to do something on the PC and return to the game no problem. As of the past few months anytime the internal sensor isn't blocked and I leave the headset while in game, it is a 100% guarantee DCS crash due the headset going into whatever mode it does when you take it off. This was never the case. I use link cable, I have Virtual Desktop but Link is better for me in DCS. This is a pain as if I am flying quite the distance and need or use the restroom or take care of something it's a guaranteed crash to desktop for DCS. This is the only game this occurs in. I tried taping over the sensor and this did not work. Anyone else encounter this, or have any ideas? Thank you.
Soggy Posted April 19 Posted April 19 Not sure about how to fix the problem itself, but a quick stopgap solution would be to turn on the 'Bypass Proximity Sensor Check' option inside the Oculus Debug Tool. Should stop the headset from going into standby/sleep when you take it off. Ryzen 7 5800X3D - RTX 3080 10Gb - 64Gb RAM 3600MHz - 2Tb NVME - Quest 3 (using Link Cable)
TFS Posted April 19 Author Posted April 19 Oculus debug tool you say... I will look into downloading this right now, thank you!
Soggy Posted April 19 Posted April 19 Should already be included with your Quest Link install. The path should look something like: C:\Program Files\Oculus\Support\oculus-diagnostics 1 Ryzen 7 5800X3D - RTX 3080 10Gb - 64Gb RAM 3600MHz - 2Tb NVME - Quest 3 (using Link Cable)
TFS Posted April 19 Author Posted April 19 Just now, Soggy said: Should already be included with your Quest Link install. The path should look something like: C:\Program Files\Oculus\Support\oculus-diagnostics Perfect found it and turned that bypass on, hopefully that works around it. I play with Link Cable anyways so it's not like the HMD would ever lose power if left on. Thank you for the workaround if this works. I don't know what changed in the recent months.
Zligor Posted April 19 Posted April 19 I use masking tape over proximity sensor so it's allways turned on, but it will go in sleep mode after 1 minut if there is no movement of headseat. Under 1 minute i change my joystick or look at the phone. Toilet problem could be solved by hanging a hedseat (with masking tape on it) to something that will swing it or rotate it by a milimetre or two for a long time. Child on a swing, rope twisted... Even a slight movement will make it staying alive. 1 AMD 5800X3D, RTX 4070ti super, 32Gb DDR4, 2Tb nvme m2, Win10, Quest2 on link cable with max resolution (slider all right) , OTT profile with 0,8 h&v fov reduction, QVFR (h&v focus size 42%, foviate res. 145%, periph.res. 18%), DCS settings all ultra and high, PD 1.0, DLAA, No hangar mod, and usually maintaining 72Hz.
Simo Posted April 19 Posted April 19 Are you using Quadviews, or OpenXR Toolkit with Turbo Mode enabled? Seem to recall this being a cause of crashes when headset is removed.
DayGlow Posted April 20 Posted April 20 14 hours ago, Simo said: Are you using Quadviews, or OpenXR Toolkit with Turbo Mode enabled? Seem to recall this being a cause of crashes when headset is removed. This is the issue. Turbo mode will cause these crashes "It takes a big man to admit he is wrong...I'm not a big man" Chevy Chase, Fletch Lives 5800X3D - 64gb ram - RTX3080 - Windows 11
Hootman9104 Posted April 20 Posted April 20 New to Oculus but experiencing this as well, I'll check tomorrow and verify if it's XRTookit Turbo, probably is. Don't have that problem with Turbo in anything else though. I don't think IL-2 has ever frozen up or crashed when taking a break, using Toolkit turbo there as well. I also have issues at times as the DCS launch into VR doesn't seem consistent, sometimes it loads up to main menu quickly, sometimes it takes quite some time, and sometime it just hangs up and have to use task manager to kill DCS.EXE. VR....think of it this way, one day many years from now you'll be able to tell kids all about the "early days" of VR. Like I tell people of the "early days" back when I had an Atari 2600
mbucchia Posted April 20 Posted April 20 (edited) The issue with OpenXR Toolkit Turbo when removing the headset is 100% root caused to be an issue where the Quest Link OpenXR runtime violates the OpenXR standard. In other words, it's a Meta bug. I've reported it directly to their engineers over a year ago (maybe even 18 months IIRC) and they won't bother to fix it (extremely simple bug fix). Edited April 20 by mbucchia 1 I wasn't banned, but this account is mostly inactive and not monitored.
Roosterfeet Posted April 22 Posted April 22 That's a shame. My Quest 3 runs DCS a lot better with Turbo mode enabled. Quadviews doesn't crash when I turn on turbo mode with it but I prefer not to use any foviation with my non-eyetracking headset. Anyone have a solution to enable turbo alone in Quadviews? 5800x3D, rtx4070, Quest3 (sometimes)
mbucchia Posted April 22 Posted April 22 3 hours ago, Roosterfeet said: That's a shame. My Quest 3 runs DCS a lot better with Turbo mode enabled. Quadviews doesn't crash when I turn on turbo mode with it but I prefer not to use any foviation with my non-eyetracking headset. Anyone have a solution to enable turbo alone in Quadviews? There was an additional workaround to Meta's bug that went in the Quad Views tool. It was never back-ported to OpenXR Toolkit. There is no solution to use only Turbo in Quad Views. I wasn't banned, but this account is mostly inactive and not monitored.
TFS Posted April 22 Author Posted April 22 I must have turbomode enabled from when I used it for MSFS, I never needed turbomode, I will try disabling that and see if that fixes it.
Recommended Posts