Problem with Oculus app opening during VR play and causing DCS display in headset to terminate

[2circle]

I'm playing DCS ver2.8.6.6.41066.1 OB with Oculus Quest 2 over USB 3 cable.  The last few times the Oculus app just randomly appeared on screen mid game and caused DCS to terminate (not crash mind you, it just disappeared from the headset but was still on the monitor with no way to get back into it).  I have auto updates turned off in the app (even though I already have the latest version of the software).  Has anyone else experienced this problem?  If so, any solutions?  Obviously it is super frustrating.  Thank you.

[Aquorys]

Using a Rift S. I can't even remember how many times this thing has failed in the middle of a game. Sometimes it decides that Oculus Guardian is not set up, and that you need to do it right now. Or it might just get the idea that the (hand) controllers aren't there (which is true, but it normally works without them), and right now you need to put batteries in them and reconnect them. Or it decides to complain that the HDMI cable isn't plugged in (although it obviously is, because otherwise I wouldn't be able to see the game), and then you need to pull out the USB plug, wait 10 seconds, and put it back in. You'll never get a picture again in DCS, so you can basically go kill DCS from the task manager and then restart it. And sometimes it just dies in the middle of a game, saying the headset cannot be found, and then you have to reboot.

Oh, and I forgot to mention that I always have to unplug it, wait 10 seconds and then replug it (USB only) after starting the computer, or the Oculus drivers will never even find the headset.

Plus a multitude of other problems, like Guardian actually showing up, but it's 2 meters to the left and rotated by ~40 degrees.

Not sure how many differences there are in the hardware and software between a Rift S and a Quest, but if the Quest is anything like the Rift S, then yeah - all of your problems sound pretty normal to me.

[2circle]

Wonderful!  Thanks for sharing....I'll manage my expectations accordingly.

[Lange_666]

On 7/24/2023 at 2:14 AM, Aquorys said:

Using a Rift S. I can't even remember how many times this thing has failed in the middle of a game.

I have never had it fail in the middle of a game. But...

Previous PC + my 1ste Rift-S: USB connection problems after almost each startup. Solution, unplug-re-plug USB and connection OK.
Went through the entire USB solution mic/mac, power management, powered USB hub, 2 separate PCI USB cards. The last one solved the problem for like 80%. For the other 20% the headset came with a USB connection problem i found that cycling the Oculus service on/off (through OTT for example) would let it re-connect without unplugging the USB. Simple solution.

New PC + 1ste Rift-S: No USB connection problem at all!! Worked flawlessly on each boot.
But the Guardian would sometimes have to be redone after a startup, at a given point even after each reboot/startup and then that problem stopped again without any software updated. While that was happening i checked the camera lenses, these where not dirty of had fingerprints on them.
Then early april my 1ste Rift-S suddenly wouldn't pass the sensor check anymore. Most of the time this came together with a USB connection error message, unplugging / re-plugging fixed that connection error but it still it didn't pass the sensor check. Tried everything i found, no joy. Everything pointed to the cable. Device manager needs to see 2 Rift-S devices under USB or it doesn't work, always had only one.

Went for a Pico 4 after a month of getting the Rift-S back to work without any succes. Returned the Pico 4 after 29 days, not good enough. It only gives good quality when the FPS matches the native refresh freq.

New PC + 2de hand Rift-S (bought one in mint condition): Works fine but... unlike my first Rift-S almost each time i reboot, come out of sleep or boot from a cold start i now have to unplug / re-plug the USB cable with this headset. Just once unplug / re-plug and then it's OK. If i don't, only one Rift-S entry in device manager is visible, unplugging / re-plugging creates the second one and then all is fine. So there's definatly a difference between these 2 Rift-S headsets when it comes down to USB connections.
However, cycling the Oculus service like i did with my old PC and 1ste Rift-S doesn't always work with this PC/headset. Sometimes unplugging re-plugging is the only option to get the Rift-S going again. But just as the my first Rift-S, it never disconnects while running a game.
Powered Hub gives the same problem. Power cycling the hub is not enough, the USB has to be unpugged / re-plugged before it works?
Then went for a powered PCI USB card for a little PCIE slot. No joy there either. Same problem.

Then replaced that one with one that goes into a large PCIE slot. This worked, Rift-S doesn't loose connection anymore, USB doesn't need to be unplugged / re-plugged anymore... but with the USB plugged into this card, game play isn't smooth. The headset seems to have tracking issues, the image shifts or hangs briefly (also in other games or in the Dash), sometimes the controllers end up on an entire different place as there location....etc so i removed that USB-PCI card again.