When you are in the MSFS menu screens and you enter VR mode, you get a ‘void’ type environment with a grid pattern. The MSFS screen being in the middle.
I would like to know what the quality of this environment is like for you.
For me it is really bad. The grid is heavily distorted and badly aliased.
I’ve recently upgraded to 7900xt, and it wasn’t like this before on the 3070 I had.
But the same type of grid construct appears on the oculus link home environment too, and when loading steam VR home environment. Both of those are perfect, so this is somehow a problem I’m getting only in MSFS.
The poor quality visuals are happening in sim too. I’m getting bad shimmering effects. But other VR games are running perfectly with the 7900xt being very capable in terms of performance.
I’ve experimented with various settings and the only time I’ve seen the MSFS menu appear badly aliased and grainy is when my Encode Bitrate has been too low, or when I set it to Dynamic.
My grid screen is normally ok, both when first loading the sim, and when returning to the menu after a flight.
However I have seen something like you describe a few times when flying in a complex aircraft (eg 787) during a long flight (about an hour). It goes wrong in the cockpit, and stays wrong when I return to the menu screen. The only way I can restore the normal view is to reboot the Quest 2.
For me it looks like a memory leak within the Quest 2 caused by sustained complex inputs, i.e. Q2 memory being used by MSFS but not subsequently released.
Your case looks different, though it may be related. What happens if you start off in the home environment (when everything looks good) and then start FS2020 without exiting VR mode? The point at which the image degrades may be an indicator of what is causing the problem.
Is what you’re seeing the issue where the bottom part of the Quest 2 display slowly goes very grainy and eventually goes white?
If so, there is a fix for that, it’s down to rendering in slices in the Quest 2. There’s a thread on it somewhere in these forums, I also think you can change the number of slices or disable that in Oculus Debug Tool (I might be wrong on that).
I used to get that issue when I was nearly out of VRAM.
Hi all, sorry for delayed reply, been quite busy lately.
I have been dabbling with settings lately, trying to optimise and see what I can get out of the new GPU I bought, AMD 7900XT. Here’s what I have learned.
Disable asynchronous spacewarp in Oculus Debug Tool. It creates screen tearing artifacts in MSFS. Without it on, you don’t get the framerate locked to half of headset refresh rate but neither do you get the artifacts. Note you have to disable ASW after you’ve loaded up Quest link, even if the setting says disabled in ODT, it initially isn’t. Click on it again to actually disable it.
I can max out the render resolution slider to 5408x2736 at 80Hz, and with TAA on, 100 render scaling in MSDS, settings on mostly medium across the board, I can get between 50-80 FPS depending on scenery load. It looks great I have to say, and I can cope with 50 fps smoothness in game even in VR. Dropping the resolution a bit makes it easy to achieve 80fps. This is impressive performance for such a demanding game.
So, ASW off is the key, and the 7900XT is a strong raster performer and runs VR great for me using Quest 2 over link.
Note the original topic, about the distorted construct grid on the main menu (before you are actually flying in VR), is still there. Doesn’t happen in cockpit itself or in any other VR game so I conclude it’s a MSFS bug.