Why 36FPS with ASW=Disabled gives less headroom than 72FPS with ASW=Disabled

Hi everyone,

I hope someone can help me to understand/fix this weird problem, because if I ask half the performance I obtain much worse results always, no matter if using Rift S or Quest2 with Win10 or Win11:

I have configured my settings in such a way that 75%-80% of the time the game can run in 72FPS without AWS. It’s almost perfect in every way for me.

Sometimes, the scene is too complex so the game cannot support 72FPS. The FPS becomes very instable, its so distracting that it ruins my gameplay , so the solution would seem obvious: Use the oculus debug tool and set AWS to 45FPS and ASW=Disabled, which for the Quest2 this translates to 36Fps.

(I cannot use AWS=Auto/ON because when there are other planes flying at my left or right, they seem too ghostly or blurry due to inaccuracies when AWS=Auto/ON including props,etc).

The problem: When I configure 45FPS and AWS=Disabled or Enabled, the game plays much worse 100% of the time, there is always stutter, blurriness and ghosted images super noticeable when looking left or right. If I turn on the performance panel in Quest, it shows terrible headroom (this explains the title of this post)

What am I doing wrong? How can I fix this?

Thank you very much!

My specs:
Intel 12700K, 32GB RAM DDR5, RTX 3080 12GB, Quest 2, MSFS from Steam but not using SteamVR, not using OpenXR. In the Quest software, I have configured a refresh rate of 72Hz and resolution of 4864x2448 that Quest classifies as 1.3X, Windows 11

1 Like

Set motionn reprojection to on and set fps to off in nvidia display on desktop. V sync also off. I fly the fenix with similar specs and its virtually fluid.

2 Likes

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