Its quite simple really just use Oculus Tray Tool or Oculus Debug / Cli to set the ASW mode to Forced 45hz. Enjoy.
The flash is detected both inside the plane and outside the plane.
Time lines for the video
0.00-0.30 Secs this is normal ASW flashes both in and out the plane.
You then see me stare at the top left corner of the screen, this is me setting the ASW to Forced 45.
0.32 - 0.50 secs - Forced 45hz
0.51 - 1.20 - Normal ASW
1.20 - End This is back to forced.
Happy Flying
I tried the OTT tool and ODT, OTT does not work for me for some reason, loads of tearing and artefacts. ODT did work in v25 for me and now it doesn’t work in v26 even when forced to 45 or disabled and stencil off. Going to have to buy try using Virtual Desktop this evening.
Try and follow every step of this initial post.
Then
OTT is finicky some settings seem to stick/persist others not. Below si what works for me every time 100% of the time.
The Quest Link Settings at 1080ti once set will persist even when you reboot the machine. You can set the bitrate here and again that will persist between reboots.
All ASW settings. You can swap these live but they will get reset “most” times you close the app and “every” time you reboot the machine
You can see the ASW settings take effect by setting Visual HUD to performance. Set forced and the Framerate MAXIMUM will be Half whatever setting you have your device set at in the Oculus Home - 72, 80 or 90hz. Forced will set 36, 40 ad 45 accordingly. “Sometimes” the HUD setting will persist after closing the OTT app (even though it should not), but will not persist after a reboot.
So to take 100% control of OTT and your Oculus experience never start OTT before you start MSFS2020
You now have full control of the OTT. If in doubt reboot your PC make sure OTT does not start with Windows!
Good luck.
maybe thats why OTT never worked for me, I always start it before MF.
Unfortunately it doesn’t work for me on the Rift S 
what did you do? revert to v24? did you use OTT or ODT? also?
I reverted back to v24
AFAIK you don’t stop the flash, you lower the framerate by locking to 45 so it happen less often (at least on my machine). Test as I did : lower renderscale, and you’ll have more flash, again, and more flash again, because more fps. Raise it, and you’ll have less flash, because less fps, etc. The bug is here from months, and this “trick” help, but don’t fix it 100%.
Yes but even when I was locking it down to 45 /30/ 18 it was still happening in v26. Flicker every 4-5 seconds which renders it unplayable.
Yes, for Oculus users it’s been there since day 1 but v26 had caused it to be much more prevalent. That said when I turn off asw and run it at 40hz I see a flash every minute or two.
I had it no matter what settings I used (have a low end 1070 until i can get a good price 3080). But i had to switch to steamVr for now to fly. If i use openXR it just does that every 3 seconds or so
Turn off beta mode in oculus and click the restart button above it. It will reinstall oculus working driver. My white flashes were every 1 second and none since
This fix don’t work anymore for all “lucky” guys like me who received the new official v26.x release in advance in the update rolling process Oculus use. I have beta off and I’m on v26.x official release.
If you didn’t receive the v26.x official release like me, turning off the beta flag will get you back to the stable v25.x official release, and fix the issue. The problem started with v26.x. Beta version.
Be patient, soon you’ll have the same issue than me, unless MSFS Devs and Oculus ones work together and fix it for good.
My oculus tray tool starts with windows & is fine for all else
For MSFS2020 I just have to click from standard auto to 18hz then to my desired setting of 30 hz then it picks that up
Otherwise Vert 90 horz 90 will not work
( closing in the black box slightly for performance boost , not noticeable within headset )
I’ve got the update v26 and since set all the settings in the Oculus debug tool except for the AWS force 45 to default and it does remove the white flashing.
I do run the Quest 2 @ 90hz and the second 1.3 on the slider with 0.7:0.7 best flight’s yet today.
Thank you @Player744061147
I took some advice and turned beta mode back on, then let it install v27 and haven’t experienced one flash yet.
Playing around with the OTT settings seemed to only limit the flashes in v26
Confirmation V27 fixed the issue.
Where do you guys see v27?? I don’t see it offered in my Oculus menu anywhere. It says 1 update is available and is “queued”, but nothing happens (headset is on). It’s set to auto update, but no update v27 happens.
Did you select the Public test Chanel (translated from my french version) on the Beta tab of the Oculus Software? If yes reboot, restart all, it should be downloaded and installed.
Yes, I’m in Beta test channel.
I did a total new setup and download, but it’s only v26, not v27! Where did you get v27? Was it an automatic download or did you manually go and get it?
