OTT ASW 45fps disabled with Quest 3 doesn't work properly

[Derfel75]

Hi all, I'm using a Quest 3, link cable connected, together with OTT to play DCS with the following settings:

SS in OTT = 1.7

Resolution in Meta app = 1.0 @72hz

Bitrate = 850

Ingame PD =1.0

I've installed Mbucchia QVFR

No AA, texture med, terrain low, shadows flat, clouds std, vis range med, LOD 0.4, grass 0, forest vis 100%, all the rest set to off.

My PC specs are below into the segnature.

In Syria into instant action free flight with F18, I have a smooth experience  @72fps with some stutter now and then (which I can easely ignore).

The experience become less pleasant with more stuttering (due to an fps fluctuation between 65 and 72 fps) for example with mission 1 of the single player campaign Operation Cerberus North (both when taxing to runway, and especially when fly over Adana city), or into F4's instant action cold start or free flight over big cities always over Syria.

I know that there Is an OTT option to force half fps with ASW disabled (It should be something like "45fps-asw disabled"). So that I decided to disable Quad Views from DCS options and set Turbo mode = 0 in settings.cfg file of MBucchia QVFR in order tonavoid conflicts, and set 45fps-disabled by using the key bindings in OTT.

The result is very strange: if I keep my gaze fixed forward the experience is very smooth, but when I look sideways or I roll the plane, everything become confusing, as if the frames are doubling for each object rendered.

I tried to google for a solution, but It seems that nobody had my experience. It could be a bug of OTT? Maybe my monitor refresh rate interferes in some way with the Q3/OTT settings in cutting the frames to half? Is Better tò use VD instead of OTT?

The same happens also of I set "45fps ASW enable" except that the experience get worse.

Can anyone help me please to understand why It happens and how to solve? 

Thanks!!!

[Tensorial_Architect]

I can't recall but I believe MBucchia does not recommend using Oculus Tray Tools with his stuff. OTT is badly outdated and most of its functions can be handled by the Oculus Debug Tool or calibrations within Meta Link or Quadviews.

[Roosterfeet]

I've been using the Quest 3 and I've found that the best results are to either maintain 72 FPS or have 36 FPS with ASW enabled. Leaving ASW in Auto accomplishes both depending on the demands of DCS on your GPU. Don't bother with OTT. Use shortcuts to enable ASW.

Ctrl numpad 4 = ASW Auto (recommended)

Ctrl numpad 1 = ASW Off

Ctrl numpad 2 = half refresh ASW Off

Ctrl numpad 3 = ASW On

Make sure hardware accelerated GPU scheduling is off in Windows settings.

Ideally, with ASW in auto, the frame counter should display 72 or 36 fps and never anything in between. I had to turn hardware GPU scheduling off or I would get a lot of inconsistent frame rate between 36 and 72 which caused stuttering.

I don't like leaving ASW on all the time because there are fewer graphics artifacts when my system is able to maintain 72 FPS. For instance, ASW produces artifacting when looking at a clear, blue sky which is also when I am most able to maintain 72 FPS so it works out well most of the time.

Also, using turbo mode in Quadviews is essential for preventing stutters with ASW enabled.

 

Edited January 17 by Roosterfeet

[Derfel75]

Thanks for the reply, I already have the GPU scheduling off (same experience of yours), and I use OTT only to easely control FOV multiplier avoiding to put everytime figures in ODT. 

What I don't understand is why, when I use "half refresh ASW Off" everything in game starts to judder. For me have 36hz/fps and no ASW will be the best option everything should be smooth thanks to my system's average 65fps performance.

I was wondering if my main monitor refresh (144hz) can affect in some way the ASW when I set "half refresh ASW Off".

I think it's not a matter of OTT ageing as ODT is quite old as well and the former just act on ODT to apply settings.

In the end from my point of view it seems to be a matter of synchronization between Q3 and DCS, but I dunno if there is some other "things" I'm not caring about and that are crucial to solve the issue.

[Roosterfeet]

21 minutes ago, Derfel75 said:

What I don't understand is why, when I use "half refresh ASW Off" everything in game starts to judder. For me have 36hz/fps and no ASW will be the best option everything should be smooth thanks to my system's average 65fps performance.

Here's my best guess, so take it with a grain of salt. As you probably know, the headset is going to display 72 frames per second no matter what. With ASW on, your GPU gets limited to 36 FPS and feeds that to the headset; the headset takes two of those frames at a time (creating a tiny bit of latency) and does AI voodoo magic to generate in-between frames. The net result being you get 72 frames that are perfectly synced to the headset's refresh rate. With "half refresh ASW Off" the headset gets 36 frames and then has to display them 72 times. My guess is that it displays 2 identical frames then jumps to the next frame to maintain 72 hz and the effect is that any object moving across your filed of view will look doubled like you have bad astigmatism. Objects in front of you don't move very fast relative to your field of view so you don't notice it. Object's our your side view move faster and thus, blursville. Objects closer to you look worse than object's far away because close objects move across your field of view more quickly.