Oculus Quest Freeze

[PatMcKrotch]

I lucked out a bit today,

The game froze, but I was able to Run DXDIAG while the game was frozen.

Headset was at an 84% charge when I started.  Maybe this has something to do with Oculus' charging system while it's plugged into the PC?  But it's not affecting other VR games.   I had also used "--force_enable_VR --force_oculus_VR" in the command line.

dcs.log DxDiag.txt

[Phantom711]

Do you use a powered hub? MAybe for some reason your USB ports don´t deliver enough power? 

In the dcs.log that you posted, there are still some references to the Hawk module which is not supported anymore. 

Other than that...no, I don´t know of any such software.

Edited August 23, 2024 by Phantom711

[Phantom711]

vor 1 Stunde schrieb PatMcKrotch:

I had also used "--force_enable_VR

You don‘t need this anymore and it might also create conflicts with the new DCS launcher.

 

vor 1 Stunde schrieb PatMcKrotch:

-force_oculus_VR

Why? 
I recommend to remove this. And in the Meta App (on the PC) set Oculus as OpenXR runtime.

Unless you have some very good reason not to, that is.

[Maddaawg]

I just started having Quest 3 freezing too. It starts stuttering and then I know what's about to happen and it locks up. It's kind of like the screen is tearing/freezing and increases the more I move my head until it just freezes. Usually, DCS is still working and the last frame frozen in the Q3 headset but not every time. I had this randomly happen with Meta Link but now I am on VD and I have not seen the issue since changing over and it's been happening since yesterday and the only change I made was to try Open kneeboard again, but it was giving me issues of not seeing my keyboard commands. The headset has to be rebooted to clear its screen but often I can still close DCS with a mouse but this last crash I had to use task manager.

Another thing I noticed is that it usually happens right after using F10. I have noticed that when returning to F1, there is a delay of 2-3 seconds sometimes. Both of the last two crashes happened after I completed the first leg of a mission, landed and rearmed. Then while on the tarmac using F10 to get my next targets and when returning to F1 the wobbling screen begins and increases until the crash. This also happened at the start while on the carrier and returning from F10 though I put 3 other F18's on the carrier so I thought that overwhelmed my system.

Here are some screenshots and log file:

 

 

dcs.log

Edited August 27, 2024 by Maddaawg

[PatMcKrotch]

Sorry for the late reply, works been busy lately.  I added the Force Enable oculus because DCS uses OPen XR by default and I'm trying to narrow down reasons why it it's freezing.  

 

I ran it just a few moments ago with the Force Enable oculus (Loaded and froze immediately)  Then I ran it with OpenXR.  I got to a server selection page, began loading, then froze when I got a "Allow SRS to Load" notification.

[Rushman]

The same problem for me !

quest3, 4090, virtual desktop and oculus link!

 

[Maddaawg]

12 hours ago, Rushman said:

The same problem for me !

quest3, 4090, virtual desktop and oculus link!

 

More info please, like when, how and what happens. Like which map and do you use F10 and then....? For me it's F10 on Syria and also once during the debrief screen. I have a post in VR Bugs, go join that and add to it, with logs etc. This needs a fix and we need more voice in the VR Bug section if the forum.

[zmz125000]

same happened to me, freeze when using steam link VR or VD. game still working and tracking headset movement, but HMD image freeze. steam link throw error something like video stream encoder failed. It happened since i got my Quest 3 (purchased on launch 2023). freeze only occurred in DCS. maybe caused by high GPU and/or VRAM Usage.

 

5700x + RTX4080 + 64GB DDR4

Edited September 12, 2024 by zmz125000

[PatMcKrotch]

Tried again today,

Again, connected via direct PC link (Cable).  The game froze again once the batter reached 90 percent.  I disconnected the cable after DCS Froze and shut down the headset, so running a DXDiag would have been useless.  I'll try again later

I wanted to try today because the META Quest Link App recently updated along with its' drivers.

 

I was also running core temp at the time, my CPU never went above 68 C, so I can rule out thermal throttling.

 

I'm going to recharge this and try it again later today as I noticed that wifi is on an auto connect through Oculus.  I'll try switching that off and see if it affects anything.

dcs.log

[Maddaawg]

3 hours ago, PatMcKrotch said:

Tried again today,

Again, connected via direct PC link (Cable).  The game froze again once the batter reached 90 percent.  I disconnected the cable after DCS Froze and shut down the headset, so running a DXDiag would have been useless.  I'll try again later

I wanted to try today because the META Quest Link App recently updated along with its' drivers.

 

I was also running core temp at the time, my CPU never went above 68 C, so I can rule out thermal throttling.

 

I'm going to recharge this and try it again later today as I noticed that wifi is on an auto connect through Oculus.  I'll try switching that off and see if it affects anything.

dcs.log 467.55 kB · 0 downloads

I see two things in your log that are not in mine. First is Debug, yours has a lot of that I have none. Second, you end with "ERROR   VISUALIZER (Main): OpenXR xrWaitFrame failed with error: XR_ERROR_SESSION_LOST". I don't know if this is a result of another issue causing the OpenXR fail or that is showing an OpenXR issue.

 

I'm hoping the procedure I have done fixed this issue as I have not seen it since I did this.

1. Make a backup of saved games/dcs folder

2. Delete the saved games/dcs folder

3. Run DCS in 2D to let it recreate the folder

4. Move back to the saved games/dce folder

a. Saved Games\DCS\MissionEditor\logbook.lua
b. Saved Games\DCS\config\input\*any aircraft keyboard and control bindings you want*

5. Run DCS full repair

6. Test in VR

Edited September 15, 2024 by Maddaawg

[PatMcKrotch]

Just ran again to collect Data,

I haven't Tried your procedure yet Maddaawg. I'm hoping that'll work tomorrow when I have the day off work.

 

The only thing different about today is, I let the game run in a frozen state and didn't shut it down.  It was frozen for about 5 minutes, then I got a "Connection timed out" showing that I was kicked out of the server.  I tried connecting to 4YA Syria again and it froze again once I had picked the apache at Allepo.

Also, my keyboard has lost power twice just typing this out so I'm looking at my power plan.  nullnullnullnull

dcs.log DxDiag.txt

[Maddaawg]

I use QuickCPU to make sure my power plan is working for full performance as well as stopping the parking of cores. Depending on the CPU you have, this may be of help. This is especially helpful with newer Intel and the "E" cores.

[PatMcKrotch]

On 9/15/2024 at 2:08 PM, Maddaawg said:

I see two things in your log that are not in mine. First is Debug, yours has a lot of that I have none. Second, you end with "ERROR   VISUALIZER (Main): OpenXR xrWaitFrame failed with error: XR_ERROR_SESSION_LOST". I don't know if this is a result of another issue causing the OpenXR fail or that is showing an OpenXR issue.

 

I'm hoping the procedure I have done fixed this issue as I have not seen it since I did this.

1. Make a backup of saved games/dcs folder

2. Delete the saved games/dcs folder

3. Run DCS in 2D to let it recreate the folder

4. Move back to the saved games/dce folder

a. Saved Games\DCS\MissionEditor\logbook.lua
b. Saved Games\DCS\config\input\*any aircraft keyboard and control bindings you want*

5. Run DCS full repair

6. Test in VR

 

I tried the outlined process today, and I had a total system freeze within 5 mins into a game.  The freeze lasted for 6 minutes at which point I was kicked off the server for a timeout.  The quest 3 had discharged from 100% to 93% before I shut it down.

I'm also getting a notification from the Meta Quest Link app 

Before, I was hitting the reset button and now that I know I can wait a few minutes, this should allow me to collect better data.  

I also downloaded quick CPU, but it'll take me some time to figure out how to use it.

After running the repair on DCS, I turned on "Allow ED to collect anonymous Data".  Hopefully that will help as well.

Last but not least, I bumped up the graphics settings a little bit in VR.  nullnullnull

DxDiag.txt dcs.log

[Maddaawg]

That last image with the warning of not finding the headset from Meta Link makes me think you're having a Quest problem, either software, cable or HMD. Have you played other games with it? Tested the cable in Meta Link? Tried a different cable? Though my headset would lockup too with a frozen image in the headset, I never saw that Meta disconnect warning. It could be that I didn't wait long enough. But I moved onto VD and it happened there too. Make sure your cable is testing good and better yet try another one just in case.

You have everything on high, that might be an issue, especially on servers. Try it the other way around, everything on low. Mine would lockup constantly on a PD higher than 1.1. What's your PD setting in Meta Link? 

Also, In your DxDiag I see a huge page file size at 82GB. This kind of usage will severely degrade your system. Is your physical memory 128GB? If so that page file needs to be either at the minimum or have no page file. It's possible that your 4090 is too much for you CPU to process and frames are going to the pagefile.

Edited September 18, 2024 by Maddaawg

[PatMcKrotch]

23 minutes ago, Maddaawg said:

That last image with the warning of not finding the headset from Meta Link makes me think you're having a Quest problem, either software, cable or HMD. Have you played other games with it? Tested the cable in Meta Link? Tried a different cable? Though my headset would lockup too with a frozen image in the headset, I never saw that Meta disconnect warning. It could be that I didn't wait long enough. But I moved onto VD and it happened there too. Make sure your cable is testing good and better yet try another one just in case.

You have everything on high, that might be an issue, especially on servers. Try it the other way around, everything on low. Mine would lockup constantly on a PD higher than 1.1. What's your PD setting in Meta Link? 

Perhaps the headset itself is thermal throttling?  I'd like to find a way to test that.

[Maddaawg]

3 minutes ago, PatMcKrotch said:

Perhaps the headset itself is thermal throttling?  I'd like to find a way to test that.

I've heard it makes an audible alarm sound, look at my edit above regarding your pagefile. Set your DCS to minimums and try a solo run of DCS.

Is Windows set to automatically adjust the pagefile?

 

 

I want to emphasize this part, your settings are all on high. The 4090 with a top tier CPU can't do all high settings, and you don't have a top tier CPU, so your CPU bound.

[PatMcKrotch]

8 minutes ago, Maddaawg said:

I've heard it makes an audible alarm sound, look at my edit above regarding your pagefile. Set your DCS to minimums and try a solo run of DCS.

Is Windows set to automatically adjust the pagefile?

 

 

nullFirst time I've ever seen this page.  I set it to the recommended size.

I'll have to try DCS on low settings later on today and see what happens.

null

[Maddaawg]

Let windows set the page file.

Adjust for best performance or minimal stuff like I have. Mine is optimized for gaming, not what Windows wants to wow me with. I think I followed a video from Jabbers, but not sure.

[PatMcKrotch]

nullDialed all graphics down to the lowest setting, same issue.  Total system freeze for about 5 mins.  It doesn't seem like graphics settings are the issue here.nullnullnullnull

DxDiag.txt dcs.log.old

[Rushman]

Hello,

i have unstalled  oculus  software, I use only virtual desktop, and lasso, I have updated open XR toolkit . and after two days no freeze.

???? 

 

[Maddaawg]

2 hours ago, PatMcKrotch said:

Dialed all graphics down to the lowest setting, same issue.  Total system freeze for about 5 mins.  It doesn't seem like graphics settings are the issue here

Did you run a solo mission or on a MP server? Do you have the ability to do as @Rushman suggested 

 

57 minutes ago, Rushman said:

i have unstalled  oculus  software, I use only virtual desktop

Also, I'm guessing you have run it with other games to be sure there is no HMD issue?

Or even try WiFi with Meta Link?

[PatMcKrotch]

1 hour ago, Rushman said:

Hello,

i have unstalled  oculus  software, I use only virtual desktop, and lasso, I have updated open XR toolkit . and after two days no freeze.

???? 

 

My wifi router isn't good enough (Yet) for a wireless connection.  I do have virtual desktop, but I'm using a cabled connection with the Q3.

 

Based on this site, there might be a conflict between Oculus software and Openxr.  I have some more reading to do on this.  

https://communityforums.atmeta.com/t5/OpenXR-Development/Quest-3-v-68-conflict-with-Open-XR-Toolkit/td-p/1223282

[Maddaawg]

2 hours ago, PatMcKrotch said:

My wifi router isn't good enough (Yet) for a wireless connection.  I do have virtual desktop, but I'm using a cabled connection with the Q3.

 

Based on this site, there might be a conflict between Oculus software and Openxr.  I have some more reading to do on this.  

https://communityforums.atmeta.com/t5/OpenXR-Development/Quest-3-v-68-conflict-with-Open-XR-Toolkit/td-p/1223282

The title of that is confusing, I'm not sure if they are having an Open XR problem or an Open XR Toolkit problem. The toolkit is an app to configure Open XR games and is not needed and is no longer supported by the dev. You probably can switch to OpenVR or SteamVR, even VD is VDXR, so there are options to try. I don't know the ins and outs of switching to the others except VDXR is selected in the VD streamer app with the other choice being SteamVR.

Edited September 19, 2024 by Maddaawg

[Phantom711]

vor 5 Stunden schrieb PatMcKrotch:

Based on this site, there might be a conflict between Oculus software and Openxr.  I have some more reading to do on this. 

No…this is outdated already. The problem got fixed by Meta after a few days with a hotfix.

 

vor 2 Stunden schrieb Maddaawg:

The toolkit is an app to configure Open XR games and is not needed and is no longer supported by the dev.

This is a bit misleading. Even though it is not being developed any further, it still works.

[Maddaawg]

1 hour ago, Phantom711 said:

No…this is outdated already. The problem got fixed by Meta after a few days with a hotfix.

 

This is a bit misleading. Even though it is not being developed any further, it still works.

It's working but @mbucchia has this on his OXRTK page: 

Quote

AS OF 2024, SUPPORT FOR OPENXR TOOLKIT IS DISCONTINUED. THERE IS NO NEW DEVELOPMENT AND NO TECH SUPPORT OF ANY SORT. THE DEVELOPER DOES NOT RECOMMEND TO INSTALL/USE OPENXR TOOLKIT, AS IT IS KNOWN TO CAUSE ISSUES WITH MANY OF THE NEWER GAMES RELEASED IN SINCE 2024.

So, while it works for many, some are having issues with it that use Quests depending on which update they have and in troubleshooting issues eliminating the extras that you don't need to run DCS are a good step. Reintroducing them once you have solved the issue. The statement I made is correct it is not needed, and development has stopped, it is an optional app.