I've been researching this topic for weeks and can't find a solution.  I'm also having trouble describing it so please bare with me.  When I connect my Quest 2 and enter VR in MSFS 2020, everything is fine until I start my flight and am sitting in the cockpit.  Looking in front of me I can see the panel & runway like normal, but when I move side to side to side or front to back, the cockpit moves with me!  I can't put my face against the side window to look out, or lean forward to see the instruments more closely.  It is ruining my experience and I have been over the controls and settings so many times.  I just don't know what to do.  Is anyone else having this problem or have any idea what I need to do to fix this?

Here is my setup:

Oculus Quest 2 256 GB

Alienware M17 R3 (i7-10875, 32 GB RAM, RTX 2070 Super)

This might be similar to what happens sometimes with the Reverb.  

It is probably that the room you are in isn't light enough, or that you are too close to your monitor.  The tracking cameras, which work out which way you are moving by locking onto fixed objects in your room, can get overwhelmed or confused by the bright and moving picture on your monitor.

To see if that's what it is, just push your seat back a few feet (and if the room is dark, turn the lights on) and see if it sorts it.

Personally, I use a small table in front of my PC desk to put my joystick and throttle on which keeps me a couple of feet away from the monitor.  

I have this very same issue now with my Reverb 1. I tried the tracing tips  by @AJZip (changing distance, more light) which didn't help so far, though. In my case, I want to fly the EC135 where I have a small desk with the joystick between me and the monitor. But I tried the C152 as well - which worked fine before - and it shows the same effect of the cockpit moving back and forth with my head.

I recall I had this issue already once time ago and "somehow" it seems to have repaired at that time, but I don't recall how.

Has anyone another bright idea how to proceed? Is there perhaps a setting which I might have switched by accident?

Thanks and kind regards, Michael

I'm one step further in my analysis. Usually, I use the SteamVR variant of OpenXR. As a test, I switched to Windows OpenXR and, voila, gone is the issue.

Unfortunately, I have much better performance using SteamVR, so this isn't the end of the story yet.

Kind regards, Michael

I have a G2 and have had similar problems in the past but they never persisted from session to session. Occasionally I will reset the environment settings in WMR and it will recalibrate asking me to look side to side and then down.

8 hours ago, pmb said:

I'm one step further in my analysis. Usually, I use the SteamVR variant of OpenXR. As a test, I switched to Windows OpenXR and, voila, gone is the issue.

Unfortunately, I have much better performance using SteamVR, so this isn't the end of the story yet.

Kind regards, Michael

Hmmm...that's interesting!

I'm also a bit surprised about your comment of MSFS2020 running well with the SteamVR runtime.  On my own system, MSFS2020 really doesn't like the SteamVR OpenXR runtime set - in fact, on my old GPU, it flat refused to run at all.  So presently I always use the WMR OpenXR runtime for MSFS and the SteamVR OpenXR runtime for X-plane... 

Curious...on both counts.

Did you also try minimising the monitor windows to stop moving images confusing the headset tracking cameras?

9 minutes ago, AJZip said:

Hmmm...that's interesting!

I'm also a bit surprised about your comment of MSFS2020 running well with the SteamVR runtime.  On my own system, MSFS2020 really doesn't like the SteamVR OpenXR runtime set - in fact, on my old GPU, it flat refused to run at all.  So presently I always use the WMR OpenXR runtime for MSFS and the SteamVR OpenXR runtime for X-plane... 

Curious...on both counts.

Did you also try minimising the monitor windows to stop moving images confusing the headset tracking cameras?

Thanks for commenting. I'm myself surprised to see Steam OpenXR better working than Windows OpenXR. I know, usually people report just the opposite. In a typical situation, I get 25 fps using Steam OpenXR and only 15 using Windows OpenXR. This is both with a resolution setting of 100/100 (OpenXR/in-game). Visually there's not a big difference. Unfortunately, the Windows OpenXR Development Enviroment doesn't provide too many adjusting screws to play with.

I can try minimising the monitor window, but I recall the mouse stopped working under VR as soon as the monitor window isn't in focus, doesn't it?

Kind regards, Michael

Your room should be well lit and the view in front should be non reflective and preferably a pattern

5 hours ago, AJZip said:

I'm also a bit surprised about your comment of MSFS2020 running well with the SteamVR runtime.

I get much better performance with WMR. The issue that the OP has was much more pronounced for me running X-plane under Steam VR, and only occasionally occurs with MFS under WMR. Even then, as I said, it's not persistent. As  @peppy197 stated , make sure the room is well lit

32 minutes ago, mobeans10 said:

I get much better performance with WMR.

That's what I keep generally hearing. I am pretty sure there is a certain setting I may have broken or forgot to do, but given the only options I see in the OpenXR Development Environment are "Rendering Scale" and "Motion Reproduction" (which I tried) I run out of ideas what to do. 

35 minutes ago, mobeans10 said:

 As  @peppy197 stated , make sure the room is well lit

I'll try once again. However, I doubt that's the cause given (i) the issue is Steam OpenXR specific and absent using Windows OpenXR under the same lighting conditions and (ii) has been absent so far for a long time using the same lighting.

Kind regards, Michael

5 hours ago, pmb said:

I can try minimising the monitor window, but I recall the mouse stopped working under VR as soon as the monitor window isn't in focus, doesn't it?

I don't think so...I'll try it and see.  I'll let you know.

16 minutes ago, AJZip said:

I don't think so...I'll try it and see.  I'll let you know.

Well - I stand corrected. 

How strange!  With X-plane, you can minimise both the WMR screen and the 'live' monitor view and everything operates just like normal.  But you are quite correct - once the monitor window is minimised, the mouse cursor stops interacting with the controls.

I'll have a play around and if I come up with anything of any use (don't hold your breath!) I'll report back 😉

8 minutes ago, AJZip said:

Well - I stand corrected. 

How strange!  With X-plane, you can minimise both the WMR screen and the 'live' monitor view and everything operates just like normal.  But you are quite correct - once the monitor window is minimised, the mouse cursor stops interacting with the controls.

I'll have a play around and if I come up with anything of any use (don't hold your breath!) I'll report back 😉

Aha!

But not to be beaten. 😃

I:

- booted up MSFS

- chose my flight

- entered the VR cockpit

- then leant forward and simply turned off the monitor

 

Result - black screen on the monitor; VR view and VR mouse unaffected  😄

 

When I'd finished my flight, I simply leant forward and turned the monitor back on.

 

Bizarre - but it worked...

2 minutes ago, AJZip said:

Bizarre - but it worked...

Thanks. Will definitely try this tonight.

Kind regards, Michael

Here are some results.

(i) @AJZip, you are right, I can indeed switch off the monitor and VR still works - including the VR mouse. This is even more amazing as I recall a lengthy discussion on the official forum if / and if so how much fps are lost because graphics has to be rendered twice, on screen and headset. I made a test with the Shift+Z fps counter and there is no measurable improvement in fps if I switch off the monitor. 

(ii) Unfortunately no success on my initial issue. I can light the room very bright, empty environment variables, turn 180° where a booksheft with rough surfaced books is, reboot, switch the PC off - the panel still moves back and forth with my head. This isn't the helicopter anymore, it's my trusted C152 which worked so well until now.

Kind regards, Michael