Unable to play in VR after WU10 (screen tearing)

Since SU 10 I have massive screen tearing in VR which makes flying impossible. I used to have this before occasionally and when that was the case, which was very rarely, rebooting always did the trick. But now it happens on every single flight. I get stable 30-40 fps in the Fenix with relatively high settings and it feels smooth, so I don’t think it’s a performance issue as such. It‘s only when I move my head that things get weird. Especially bright objects such as lights, text or displays “jump around” like mad.

Here’s what I’ve tried so far:

  • Complete reinstall of the sim (because it crashed every time I ran it after installing SU10)
  • All graphics settings to very low
  • Latest Nvidia Game Ready driver (clean install using DDU)
  • DLSS
  • DX12
  • Tinkering around with Open XR Toolkit
  • Without OpenXR dev tool and toolkit
  • Starting the sim with Open XR running
  • Other VR games run just fine

None of this worked. The only thing that did work (sort of) was completely emptying my community folder. Also when I added just the Fenix it ran fine. But then I added Drzewiecki Design’s Krakow using Addons Linker (I have my Orbx airports on a separate drive) and the tearing was back. Now comes the weird bit. When I copied the airport directly into the community folder it was fine again. This gave me some hope. I did the same with Gaya’s Vienna but unfortunately that didn’t work. I also tired some other airports (FSDT’s Basel and Zurich), the same bad results.

I’m really at a loss now. I’ve spent my whole day off trying to find a solution and nothing seems to work. Very frustrating. Before SU10 the sim was relatively stable and ran reasonably well in VR even at big 3rd party airports with AIG traffic, GSX and all sorts of addons running but now even a single small airport brings the sim to its knees.

Does anybody have an idea what else I could try? Any suggestions are greatly appreciated.

Specs:
Windows 10
RTX 3080
i9 11900K
32GB Ram
Reverb G2
MS Store version

1 Like

I’m in the same boat and nothing really helps either. Massive tearing when looking left or right, having head steady however shows pretty decent fps. I’ve read that the recent windows 11 update might cause such issues when you have a Geforce card in your system. This might be the case for me so waiting eagerly for a fix or something. Also, today’s nVidia drivers made tearing a little less severe, however not fully fixed yet…

Thanks for your reply @yogibaboo1. I‘m on Windows 10, so it‘s got to be something different. I hope a future update will sort things out for you.

You mean SU10?

DLSS is a joke, upscaling with better marketing and not something I would use in VR or in a sim, DLSS 3 is even more of a joke as that is pure smoke and mirrors.

I had no issue with new sim update on my 3090 and up until a few days ago with my 1080ti and Rift-S, however I am on Windows 10 as 11 is still garbage.

I had similar sounding problems - I deleted my rolling cache and whatever my problems were, they cleared up after that.

try this

  1. Delete any rolling cache.
  2. Delete the Content.xml file.

(AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Content.xml)

  1. Delete the simulator .dat files

(AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SceneryIndexes*.dat)

  1. Do not add anything to the Community folder

In the search bar type CMD and hit return
This will bring up a menu selection . Select the option “Run as Adminstrator”
A DOS window will then open.

Go through each of the following steps one at a time. Copy each line, one at a time , paste it into the Dos window (crtl + V) and press return

and it will then run. Wait until each runs and finishes before you move on to the next one.

When you are completely finished, Restart your computer and then try to see in MS2020 will start and run properly

Dism.exe /online /Cleanup-Image /checkhealth

Dism.exe /online /Cleanup-Image /scanhealth

Dism.exe /online /Cleanup-Image /Restorehealth

sfc /scannow
Please note that the line sfc /scannow will probably be where you will see a lot of corrupt files repaired. If this happens, please

rerun this command again until you get the message that no corrupt files have been found.

Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore

Dism.exe /Online /Cleanup-Image /StartComponentCleanup

RESTART your computer as the last step

Please note that the line sfc /scannow will probably be where you will see a lot of corrupt files repaired. If this happens, please
rerun this command again until you get the message that no corrupt files have been found.

It may take 2 or more tries to fix everything.

I‘ve already tried this. But thanks for your suggestion!

Thanks a lot for these detailed instructions! I‘ll give it a try.

Deleting the Content.xml file and the Simulator.dat files did the trick! I haven‘t been able to do a longer flight yet but I did a quick test at LOWW with the Fenix and for the first time since WU10 I had no issues at all. Fantastic. Thanks a ton @wimpysoft and all the others who helped me sorting this out!

I have the same system and exactly the same experience. Is it Windows 11? It’s like a driver fault somewhere

Is it steam version? I don’t even have any content.xml file anywhere in the sim file structure.

I‘m on Windows 10.

Store version. my Content.xml file is located here: (User/)AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Content.xm

Thank you. Hmm, I have a store version too, and I started seeking the file from that location, no content.xml whatsoever, hidden files turned on too. Weird…

This file got removed in the last update.

1 Like

I still have it. Weird.

After SU10 I started noticing terrible screen tearing in my VR headset any time I move my mouse to my second 2D monitor. If I move the cursor back to the main monitor and click in the MSFS window, the screen tearing stops and I get decent VR performance.

Specs:
Windows 11
RTX 3080
i9 10900F
32GB Ram
Oculus Quest 2
SteamVR
MS Store version

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.