solved Oculus quest 2 "correcting" itself

[Moxica]

I normally press 5 on numeric keyboard if head posistion gets out of whack.
Today, it happens if I lean hard to get closer to a button, or look out the window.
I have no idea why i started behaving like this, or how to make it stop.
Do any of you?

[The_Nephilim]

well if it has inside/out tracking it could just get lost. sometime my G2 just shifts ingame with me not moving..

[Lange_666]

Has the overall light intensity in the room changed?
A reset of Guardian should help (even if you only set a floor level).

[Hoirtel]

I think this has happened to me recently, doesn't exactly match up with any specific movement or control so isn't repeatable. I felt like recently it is more sensitive to poor room light conditions. I also noticed that the internal sensor needed a bit of a clean. Done those and so far so good, but it's a case of waiting really. 

[Moxica]

No light has changed. I use same source.
Today was the worst: Falklands, Ah-64 Many targets, horrible framerate.
It "recentered" as soon as I looked at targets outside to the left or right.
-And sometimes when looking forward again.
Darn, the amount of technical "challenges" this sim has brought. I hardly get to fly.

[Aquorys]

On 11/27/2022 at 8:09 PM, Moxica said:

I normally press 5 on numeric keyboard if head posistion gets out of whack.
Today, it happens if I lean hard to get closer to a button, or look out the window.
I have no idea why i started behaving like this, or how to make it stop.
Do any of you?

Yes, I guess you might be experiencing this bug. If that is the case, then in all likelyhood, it's not really your Oculus Quest 2 at fault, much rather it's a programming error in DCS' VR code.

The part that could be attributed to the VR headset messing up is that it temporarily loses track in the first place, which triggers the bug in DCS as a result, but has no effect in other VR applications, because they don't have the same bug. With the multiple gyroscopes and accelerometers that the VR headset has built-in, there is no reason for it to continuously require the cameras to track its position. Even if the cameras were unable to see anything for a minute or two, it should still be able to track pretty accurately. The cameras should only be used to prevent gyroscope drift.

[Moxica]

4 minutes ago, Aquorys said:

Yes, I guess you might be experiencing this bug. If that is the case, then in all likelyhood, it's not really your Oculus Quest 2 at fault, much rather it's a programming error in DCS' VR code.

The part that could be attributed to the VR headset messing up is that it temporarily loses track in the first place, which triggers the bug in DCS as a result, but has no effect in other VR applications, because they don't have the same bug. With the multiple gyroscopes and accelerometers that the VR headset has built-in, there is no reason for it to continuously require the cameras to track its position. Even if the cameras were unable to see anything for a minute or two, it should still be able to track pretty accurately. The cameras should only be used to prevent gyroscope drift.

I cleared the guardian history within the Oculus menu. It appears to have solved the problem.
I even got a desent framerate on the ship-landing-quickstart at the notorious Marianas.
(Until I've landed. Then the slideshow started again) So I alt tabbed out, and back in a couple of times, and the framerate got acceptable again. 
 

[Flappie]

Thanks for your feedback.

[Hoirtel]

On 11/28/2022 at 8:06 PM, Moxica said:

I cleared the guardian history within the Oculus menu. It appears to have solved the problem.
I even got a desent framerate on the ship-landing-quickstart at the notorious Marianas.
(Until I've landed. Then the slideshow started again) So I alt tabbed out, and back in a couple of times, and the framerate got acceptable again. 
 

I'm going to try clearing the guardian as I have still experienced the problem. Mine doesn't seem to be as bad as others since I made sure I had good light and clean sensors. It does seem to happen when I look extreme right and down. I turn back to center and I'm in a different place. This is the spot in my simpit which should give the worst tracking. Didn't happen before 2.8 though.

[Moxica]

I'm not using 2.8 atm, because unacceptable bad framrate.
I haven't experienced such tracking problem since.
(Except if I look extreme right and down, actually  )

[Hoirtel]

Clearing Oculus guardian didn't change anything. Issue is still present but definitely linked to down and right head position but not ever single time. I will add some checkerboard to this spot in my Simplot as I am sure it's DCS's response to tracking loss rather than a random event. 

[Hoirtel]

So for some reason this problem was really really bad yesterday. Same mission, same slot..I had resaved it with different weather. Lots of "corrections" looking at various different angles. Also seemed to be trying to recorrect itself. Not sure why it suddenly got so bad, it also seemed to reduce after running mission. Many issues get posted as unplayable and mostly they are fine. Yesterday was the first time I really wasn't sure I could carry on. I will try and get a track but sometimes it just doesn't happen. Please unmark this as solved, because I don't believe it is. 

[Hoirtel]

As mentioned in the other thread that relates to this. Unchecking the use snap views option appears to have fixed this for me.

[IronStar95]

Hi, note that I have gained quite a bit of FPS and stopped a lot of stuttering by using Virtual Desktop instead of the Oculus Air Link. If it helps...