Crash / freeze issue quest pro

[markturner1960]

So this morning, my VR froze 3 times....at least one of those, DCS was still running on my monitor.Not sure if this is DCS related or quest related, how can I tell? I looked in the DCS logs file and there was no crash file, only the log file.

Is there a crash file generated anywhere by the oculus software? I have had zero issues with stability up until now, seems strange to crash 3 times within 15 minutes.....

Any ideas? Dont think I have changed anything..... 

[Werewolf_fs]

After the update to v54, I had to do a hard reset to the device because it had lag even in the menu of the device itself. Factory reset (with the same v54) was solved. It is already known that ANDROID (on which the META system is based) tends to do these things. Will be the cause? 

[markturner1960]

Thanks, i will try that....where is the reset done? Via Oculus home on the PC desktop or from within VR ? 

[Werewolf_fs]

In the Oculus APP in your phone. MENU ---> DEVICES ---> select your QPro, ---> AVANCED CONFIG ---> FACTORY RESET 

ALTERNATIVE ----> Turn off the device, turn on by pressing the POWER + VOLUME + button at the same time. . When the meta logo appears, release the buttons, you will see the recovery menu, select WIPE DATA/FACTORY RESET,---> yes, boot device and login again.

 

Edited June 10, 2023 by Werewolf_fs

[markturner1960]

Thanks, is there any kind of crash log generated anywhere within the Oculus software? I need to narrow it down to the headset, or a DCS issue....I dont have a crash log generated by DCS after the incidents, does that confirm its headset related? 

 

EDit: Just tried re setting from within the headset......when I released power and volume buttonss, I got a graphic of a small green droid, lying on its side with a hatch open on it showing a keypad underneath, with a red warning triangle and explanation mark above it.....Under there was text saying " No Commmand" 

Edit 2: Managed to do a factory re set, but still getting a crash. I have looked in reliability history and for each freeze / crash it says DCS stopped interacting with windows - hang type, "Top level window is idle" . Puzzled why I have no DCS crash log generated though. It seems to happen when I have been in the sim approx 20 - 25 minutes, each time.

Edited June 11, 2023 by markturner1960

[markturner1960]

Hi, I have done a factory reset, still getting the issue..... in reliability history, I saw that OVR server.exe had stopped working, here is the details:

Faulting application name: OVRServer_x64.exe, version: 54.0.110.284, time stamp: 0xb187d0a5
Faulting module name: OculusAppFramework.dll, version: 54.0.110.284, time stamp: 0xbed55e49
Exception code: 0xc0000005
Fault offset: 0x00000000000f497f
Faulting process ID: 0x1718
Faulting application start time: 0x01d99cf160155d64
Faulting application path: C:\Program Files\Oculus\Support\oculus-runtime\OVRServer_x64.exe
Faulting module path: C:\Program Files\Oculus\Support\oculus-runtime\OculusAppFramework.dll
Report ID: 9d2070d3-5ea5-45f2-af76-28307872b5ae
Faulting package full name: 
Faulting package-relative application ID: 
 

 

Can anyone help? Have gone from being super pleased with new headset to not being able to use it in one week.....

[diamond26]

I don't know if you are using MT and if the freezes/crash happen when you put the headset aside but here is what I was experiencing with a Quest2 and how I resolved 

Another possible reason for the system to crash is a problematic cable. You can eliminate this by checking if crashes occure while using Airlink

Edited June 12, 2023 by diamond26

[markturner1960]

Thanks, I was using MT, but tried in normal mode and without the force enable VR shortcut addition, it still crashes. 

I do have developer mode enabled, but cant see anything in any settings regarding the proximity sensor. I did find sleep delay settings ( set this to 4 hours) 

This did not prevent it crashing again.....

I did not realise you could use airlink to run DCS? I tried that, but performance was soooo bad, it was unuseable

Edited June 12, 2023 by markturner1960

[diamond26]

33 minutes ago, markturner1960 said:

I did not realise you could use airlink to run DCS? I tried that, but performance was soooo bad, it was unuseable

You have to leave dynamic bitrate to default (0) in ODT (since I cannot recall the exact name by heart, try to leave bitrate options to 0 to be sure) to make it work properly. In my case the performance is almost the same as Link. I don't see a reason why QPro will be different with Airlink

BTW you don't need the VR enable option if you have the VR setting enabled in DCS

Edited June 12, 2023 by diamond26

[markturner1960]

I have set those back to default and tried running airlink on its own. When connected, my wifi is all good, I get all green ticks in the troubleshooter, but I am unable to maintain a connection long enough to test unfortunately....I have 3 times set DCS going, and it was running nicely, only to come back 30 minutes, 45 minutes, an hour later to find that the connection was lost. 

Is it really likely a week old cable with no damage is the cause? As it does not look like I can run long enough on airlink to see if there is a crash. 

[markturner1960]

OK, well 2 days of trying has not resulted in any progress.......I am carrying out the nuclear option of a fresh windows install with fresh DCS and Oculus install.....lets see where that takes me......

[slughead]

I'd consider reinstalling the Oculus App or perhaps a repair of it if there is an option. It's possible that some settings may have become corrupted whilst using the ODT.

Uninstall, then check the program files area for leftover junk. Even check C:\Users\USERNAME\AppData\Local\Oculus and clear it out.

Logs can be found in C:\Users\USERNAME\AppData\Local\Oculus