Yes, I use motion smoothing enabled in SteamVR - not force on. If I use WMR And OpenXR I use repro always on.
Iām really tempted to go back to Win 10 too. But I recently upgraded to a 12700K ,and generally the new 12th Gen Intel CPUs perform better on Win11 due to the improved thread manager handling the E cores properly . Iāve noticed that clearing the environment data in the WMR settings every time before launching FS2020 (as suggested in a post way above) has a very positive impact. The issue is almost - but not completely - gone. But at least playable.
Iām gonna wait until a new Nvidia driver and OpenXR version have been released. I might switch back to Win 10 then. However some people in this forum have reported that the issue persisted even after switching back to Win10. Some people have stated that the bug got introduced with the second last Nvidia driver 497.09. Makes me think that it is more of a driver issue or a combination of driver and OS issue. Did anyone try downgrading to Nvidia driver 472.12 or anything before 497.09?
I just went ahead and tried a downgrade to 472.12 using DDU. Partial fix. No more rubber-banding and shaking when looking around (slowly). Way, way better. However the G2 is still over sensitive to vibrations caused by i.e. touching,head shaking or speaking. Iām guessing OpenXR is the culprit there.
My understanding is that using WMR OpenXR will allow for 22.5fps motion smoothing. Doesnāt going the SteamVR route limit you to 45fps or nothing?
Yes, I think thatĀ“s correct. WMR motion smoothing works better imo.
There seems to be a couple of different issues being described in this thread. One of them, disabling HAGS seems to be important. The other seems to be a W10 vs W11 thing. I will just say that MSFS was unplayable for me with the W11 jittering. So glad I did the W10 reinstall. I have a 5950X, so I donāt have to worry about 12th gen Intel considerations, though I am usually an Intel guy.
Simming invovles so much tedious tweaking that I need to get away from my usual mindset of upgrading the moment thereās something shiny out there. Thereās a lot to be said for the stability that comes from using something just a little older than the absolute bleeding edge.
Hi, 472.12 was a beta-driver imo. My best experiences so far I made with 496.76 (this was the last one before 497.09). I use a i7-10700k and a 3080ti-FE
I think OpenXR is poorly optimized for the G2 on Win11. I have zero issues with SteamVR games.I found a Reddit thread (WindowsMR) from about 14 days ago where an OpenXR/WindowsMR official confirmed that the team was totally unaware of the issue 
. I guess theyāre not reading posts frequently here. So if you have any future complaints it seems Reddit is the way to go.
And yes , you always kinda end up being an involuntary beta tester when getting shiny new things or a new OS. I was hoping that Win11 was more like a facelift of Win10 with a few optimizations for Intel 12th Gen. My original plan was to upgrade from 9700k to a 10900k and staying with Win10. But a one generation jump only seemed kinda silly and not as future-proof. But Iām slowly starting to regret my choice.
1 Like
I think I skipped that driver. Maybe Iāll try it out. Thanks for the tip.I have read that Nvidia is due to release a new driver tomorrow. It is supposed to have some new and improved features like DLDSR. I hope that VRSS will be coming to MSFS someday in the hopefully not so distant future, too.
this still a big problem for me feels like im having a seizure whilst playing. the violent shaking goes when i turn vr off but who ā ā ā ā wants to play like that. gutted spent loads of money on this game with a new pc new g2 the game itself and all the downloads with it. ā ā ā ā ā ā ā
1 Like
As far as I know there will be an OpenXR update late January or early February. Thereās a good chance thatāll fix or help mitigate the issue to some extent . Some folks are looking into this.
where is this menu?
In Steam. Right click on Microsoft Flight Simulatorāā> Properties
Hi, This is Matt from the OpenXR team at Microsoft.
I wanted to give an update on this issue.
First off, I wanted to explain a couple of things regarding the reporting of issues.
We did not know about this issue until recently (the reddit thread mentioned by @CPSweatPants). My team does testing of Flight Simulator 2020 for every release, typically 2-3 people including me. I generally do Windows 10, and my co-workers are on Windows 11. At this point, nobody in my team is seeing the issue reported here.
We also monitor bug reports filed through the Windows Feedback hub. There too, we have not received any indication of an issue.
So it seems that the only place this issue is being discussed is this thread (well, and later, reddit). One thing thatās especially difficult for us is to look at problem descriptions, then seeing a few messages later things like āI reverted this driver and the issue is now goneā or āIāve turn on/off this setting and the issue disappearedā. This tends to indicate that whatever is causing the issue is not our components or something in our control, or sometimes simple user error (or even user tendency to run at settings that are not appropriate/realistic for their setup). Thatās why we cannot keep tab of all the open issues here, because we simply cannot look at every combination of driver/software/hardware and their respective settings which could cause āfalse issuesā.
I invite everyone who havenāt yet done so to go read my post about OpenXR for WMR releases and how to properly report issue once they are confirmed to be due to our OpenXR runtime:
Now, back to the issue of shaking.
Iāve been in contact since last week with some folks (including @CPSweatPants) who can reproduce the issue consistently (since again, here at the office, we cannot reproduce this issue), and weāve tested a few things that apparently resolve this problem. Iāll pass on the technical details, but for short weāve experimented with ways to limit the motion prediction algorithm, effectively avoiding prediction error since the game runs at a less-than-optimal frame rate for the current prediction to be the best.
Weāre looking into ways to include this change into the upcoming update of the OpenXR for Windows Mixed Reality, in later January/early February. If for some reasons this release gets delayed, we also have a way to release this improvement using my open source side-project āthe OpenXR Toolkitā (which also targets a release at the end of this months).
We appreciate your patience here, and looking forward to releasing the change.
14 Likes
Iāve had this issue since I updated to Windows 11. Can actually see the shake just with my heart beat. If you need any help with testing new released or have any sort of a beta program, let me know, Iād be happy to help out.
Mike
PS your name here made me do a double take. my name is Mike Luchia 
1 Like
Matt,
You taking the time to send an update here is a testament to you and your teamās dedication to this community - a huge thank you for this!
Canāt wait for the fix, thatās awesome news. Iām curious if you have been able to link it to W11? I too started to have it when I upgraded.
Cheers
1 Like
Hello Matt
This is very easy to reproduce but you must compare to Win10 to fully appreciate the difference.
Latest OpenXR motion reprojection ON and like another person said ā¦ just look around cockpit and shake is clear as day. Revert to WIN10 and you will see the improvement immediately.
Alienware R11 I9 2080 super 32 gb.
As for this is the only place mentioning issue thatās because I donāt know anywhere else to report apart from when asked why reverting to Win10 so hopefully MS pass on those comments to you.
Yes, thank you for posting this. This is the only thing making me pause before upgrading to Win 11. Hopefully youāll be able to fix it soon.
For some reason, the shaking is NOT present anymore in my setup. Changed nothing.
It may be related to a recent Windows 11 quality update.
Itās even noticeable when at the MSFS menu level.
I would say itās as smooth as it was in Windows 10.
This is the best news Iāve heard in a log time. Thanks for your effort in correcting this problem.