Oculus 2 what is needed for DCS?

[Steel Jaw]

So now that I have it in play, what refresh rate should I use in the Oculus settings or the tray tool?

Edited November 29, 2021 by Steel Jaw

[TZeer]

Max out your resolution in the occulus settings. Set your frequenzy @ 90 HZ and ASW @ 30 FPS

See if you are happy with that. I'm running a RTX 2080 at the moment with MSAA x 2, PD 1.0.

Edited November 30, 2021 by TZeer

[Steel Jaw]

10 minutes ago, TZeer said:

Max out your resolution in the occulus settings. Set your frequenzy @ 90 HZ and ASW @ 30 FPS

See if you are happy with that. I'm running a RTX 2080 at the moment with MSAA x 2, PD 1.0.

 

Thanks, are you using the oculus tray tool as well?

[TZeer]

Yes. 

Im setting the ASW in the tray tool, per application.

 

 

[Steel Jaw]

On 11/30/2021 at 5:42 PM, TZeer said:

Set your frequenzy @ 90 HZ

This caused horrible VR performance.

[TZeer]

Hmm, strange. 

What do you mean with horrible VR performance?

I have my ASW @ 30Hz (set in OTT) and my headset refreshrate @ 90Hz. My framerate is then locked at 30 FPS and seems very very smooth. If I take off ASW and run @speed-of-heatVR settings and his test track I have around 30-40 ish FPS. 

What is your FPS numbers if you run his track?

 

[Steel Jaw]

15 hours ago, TZeer said:

Hmm, strange. 

What do you mean with horrible VR performance?

I have my ASW @ 30Hz (set in OTT) and my headset refreshrate @ 90Hz. My framerate is then locked at 30 FPS and seems very very smooth. If I take off ASW and run @speed-of-heatVR settings and his test track I have around 30-40 ish FPS. 

What is your FPS numbers if you run his track?

 

I have my ASW @ 30Hz (set in OTT) and my headset refreshrate @ 90Hz...causes stuttering in VR.

Honestly, this is driving me to drink...Im almost ready to go back to American Truck Sim in VR, at least it WORKS without all of this fiddling.

 

In OTT, is anyone using the Quest link settings?  Do I need it?  Using the link cable, getting 1.8Gbps but no settings make any difference to the stuttering.

 

Also, Speed's UI settings show max game res, shouldnt that be min for VR?

Edited December 12, 2021 by Steel Jaw

[Hempstead]

I have the Q2 maxed out on resolution with the experimental 120 Hz refresh rate, ASW=Auto (set in Oculus Debug Tool). But I have an RTX3080 Ultra (EVGA factory over clocked, basically). So I went with the brute force approach. This lets me turn down AA settings. If DCS supports nVidia’s DLSS, and in VR, I might give it a try instead of the brute force approach with higher resolution.

With MSAA off, I get some annoying shimmering, but not too bad. Quite ok actually. And I get about 45fps at 1,500 ft agl overhead landing pattern at Nellis.

Turing on MSAA 2x, I lose about 5fps, i,e. 40 fps, even on the runway. So, now I know where to get that extra 5fps, if I need it.

At altitude, it's even higher fps, but never over 60fps.

And, I have the expensive Quest Link optical cable. I get about 1.7Gb/sec. I don’t use OTT at all.

[Steel Jaw]

48 minutes ago, Hempstead said:

I have the Q2 maxed out on resolution with the experimental 120 Hz refresh rate, ASW=Auto (set in Oculus Debug Tool). But I have an RTX3080 Ultra (EVGA factory over clocked, basically). So I went with the brute force approach.

Just tried that without OTT and it was a slide show.  So I need OTT with my 2070 GPU it would seem.  What was your in game SS setting?  Thanks for your input, brother.

[Hempstead]

11 hours ago, Steel Jaw said:

What was your in game SS setting?  Thanks for your input, brother.

Totally Off… That was the idea - I set the Q2 to max resolution, which will tax the gfx card to render at higher resolution (what the GPU does best), then Q2’s hardware will reproject to its curved surface according to its optics. Oculus mirror even has a command line option to “flatten” out the framebuffer. Then, Q2 has to either downscale and/or crop it to native resolution of its LCDs. That’s the “theory” anyway. There is only one way to find out.

Moreover, one of my CPUs is pegged at 100%, CPU bound. And my GPU utilization was at about 60%. By rendering at higher resolution, I bumped up my GPU utilization to about 80%.

Even though I set Q2 to 120Hz, I am never expecting I could get that. I am only hoping when ASW kicks in, I get either 30, and perhaps shoot for 60 (dream on), instead half of 72, which comes to about 35. Difference between 30 and 35 fps is barely perceptible as long as they are smooth.

So, what I am doing is basically supersampling split in two parts — render at higher resolution by the GPU, and downscaling by Q2. GPU no longer does the downscaling… I hope. Therefore, I can skip the in game SS, as I found the in game SS no longer improved my perceived rendered quality.

 

And, BTW, my cloud quality is set to Ultra. I can probably squeeze out a few fps turning that down.

[Steel Jaw]

What is the main cause of jitters please?

[VR Flight Guy in PJ Pants]

I find most of the OTT functions can be done over ODT, both GUI and command line version. I have been using 2 computers to play DCS and on both of them, OTT did not run well at all. I guess it must be me.