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

[ralch]

Hi everyone, 

I hope someone can help my 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, it ruins my gameplay when I am trying to gun down my enemy for example, so the solution would seem obvious:  Use the oculus debug tool and set AWS to 45FPS and ASW=Disabled.


(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)


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 quite noticeable when looking left or right.

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, DCS World Open Beta latest update, not using SteamVR.  in the Quest software, I have configured a  refresh rate of 72Hz and resolution of 4864x2448 that Quest classifies as 1.3X, Windows 11

[AlpineGTA]

Coincidently, I noticed the same thing last night with my Quest 2. I always play with ASW off because, as you've already stated, ASW on causes ghosting of moving objects. Therefore, I have my settings so I can play most scenarios at 72FPS with ASW off and everything looks nice and smooth - no ghosting. Sometimes however, usually on multiplayer or missions with lots happening, this can drop below 72FPS, so I thought the logical thing would be to use ASW off locked to 36FPS, but like you, I noticed this produced ghosting. Switching back to just ASW off and 72FPS the ghosting disappears. You would think locking it to the lower 36FPS would give better performance but that doesn't seem to be the case. I don't know why. On multiplayer I leave it on ASW off, 72FPS and it'll default itself to 36FPS when it needs to.

[ralch]

Yes, I have been like this from day one on the Quest 2 and it happens the same in Rift S. 

 

I tried to open a support ticket with Oculus and they said they couldn't help with DCS.  I posted a similar topic in the MSFS forum (same behavior) and I got this: Why 36FPS with ASW=Disabled gives less headroom than 72FPS with ASW=Disabled - Virtual Reality (VR) / Hardware & Performance - Microsoft Flight Simulator Forums

However in my DCS VR settings, VSync is disabled... so that didn't help.  ASW=ON fixes the stutter but I already explained why I don't like it.

My only ideas now are:
1.  People haven't noticed or don't care because when looking straight the problem is not so big.  This issue is most noticeable when looking left/right during baking at low level.
2.  The problem cannot be fixed changing settings because the LCD panel wants 72FPS.   Well maybe I could but my graphics settings are already at the minimum compromise for me.
3.  Buy the RTX 4090