Same issue here. I kindof saw this coming, because sooner or later Oculus is going to make their betas the regular version of their software. I tried enabling the beta thing again to see if there’s a beta version which performs better, but no juice.
I guess we’ll have to inundate the peeps over at Oculus to make them look into this. What a sad state of affairs… the main reason I got MSFS is to play it in VR in the first place. let’s hope this gets resolved soon, somehow.
Can you monitor the FPS I expect you will find that ASW is enabled in the cockpit whereas there is less demand out of the cockpit so ASW is not required.
Try disabling ASW. To be 100% sure you’ll have to put the performance HUD on and then you can see the FPS being kept below whatever HZ rate you’ve set you headset to run at.
It’s described as a flash but it’s actually a picture change, you move out of the aircraft for a frame or 2. My guess is a timing issue related to ASW, if you disable ASW it goes away assuming your GPU is strong enough to run the SIM.
I hope I can be of help. We all know that the FS flashes are linked to Oculus PC runtime v26, which was in Beta recently (causing flashes for those participating) and became the official v26 release two days ago - still with the same flashes in FS.
WORKAROUND: change Khronos-OpenXR runtime from Oculus-OXR to SteamVR-OXR. Tested successfully and it killed the flashes for me!
you DON’T NEED need the Steam-Version of Flight Simulator for this to work
you NEED Steam-client including working SteamVR (I run on 1.16.8 in Beta mode)
IMPORTANT: Oculus Debug Tool / Tray Tool core settings like Super-Sampling, ASW mode/off, FOV are still working - even if running via SteamVR. Additional SteamVR resolution-settings, motion smoothing etc. are complementary - that means they come on top! Bear this in mindin order not to over-tweak your resolution (FPS!) or in case you want to switch ASW off (which I definitely recommend)
For the ones knowing how the above config works: come, see, confirm back and spread the word! For all others, instructions below:
1. How to change Khronos-OpenXR runtime in your Registry from Oculus-OXR to SteamVR-OXR?
I’ll skip the classic regedit process, because there s a way more convenient way in SteamVR, as described by @CptLucky8 here:
2. How can I opt-in to SteamVR Beta?
From your computer, open the Steam app.
On the left panel, click the drop-down menu and select Tools.
Right-click SteamVR, and then and select Properties.
Go to the Betas tab.
In the Select the beta you would like to opt into drop-down list, select beta - SteamVR Beta Update.
3. How do I launch FS on Oculus using SteamVR now, after applying the changes?
Activate Link (Quest) / Oculus Home (Rift)
If you are using Oculus Debug or Tray tool, reconfirm all your main settings now
In the Oculus Home, go to apps and launch SteamVR
Launch FS and wait until loaded into Main Menu
Switch to SteamVR (default CTRL+TAB).
Enjoy FS in VR without white flashes!
4. How do I configure Flight Simulator to run smoothly?
Please feel very much invited to my guide and the subsequent forum discussion:
@CodeLoran69 confirming FS via SteamVR 1.16.8 Beta finally performs EXCELLENT on my Quest 2!
SteamVR was broken in FS two months ago and still really poor only a month ago, but with the latest release SteamVR has overtaken the Oculus runtime. FPS feel about the same, maybe even a bit faster, but what is more important: much more solid - way less micro-stutters compared to Oculus.
It runs so smooth that I have even changed the runtime in Assetto Corsa (my 2nd-biggest VR love) from Oculus to OpenVR (=SteamVR) now! Of course I can only confirm this for my setup, but I hope others will follow…
I tried Steve’s solution using SteamVR, and while the flashes are gone, the sim becomes very stuttery for me. I may try and revert to version 24 of the oculus software, and see if that gets me going flash-free again.
I’ve gone with the v24 solution and it appears to be working well.
The only challenge now though, if everyone stops using the V26 Oculus drivers, is knowing when the problem has been fixed and when we can go back. However, it looks pretty easy to reverse the fix and reapply it again, if necessary, after trying out each new release of the Oculus software.
My Rift updated itself last night. I tried to make a flight this morning and now again with the flashing every second. I agree. Totally unusable. I think I might throw my headset down a flight of stairs. Heh.
I’ll keep v26.x. I really dislike to get back on old versions or drivers on my secured machine, and I don’t feel I should be the person fixing their issues each time they fail. Saying that I’m glad for all people who I found the provided solution with v24.x and will keep flying
Me I stopped flying anyway until this is fixed, so we’ll know when Oculus or MSFS Devs will fix this issue.
I had a new feedback from the MSFS support team, I don’t think I break any forum rule here by saying what they said : they apologize for the frustration we have and confirmed the devs team is looking at this specific issue.
So that’s great and we just need to be patient now