i9-9900 3070TI Major performance find for VR

[Ghostrider711]

For, off and on a month now, I have been messing with settings to get this thing to run good in VR. Lower texture settings *Cockpit to 512* Ect. Tonight, on a whim I raised DCS VR pix dens to 1.7 and cut my headset res in half.  Not only did DCS look better, sharper on my Quest 2/link cable, performance went way up and now I can actually see enemies and spot ground targets.

I will try to screen shot all settings and update this thread but, this made a MASSIVE difference, I'm talking 40% gains. HALF whatever res you're running on the headset and then raise VR pix Dens in sim to 1.7. Magic bullet.

[Doremas]

For, off and on a month now, I have been messing with settings to get this thing to run good in VR. Lower texture settings *Cockpit to 512* Ect. Tonight, on a whim I raised DCS VR pix dens to 1.7 and cut my headset res in half.  Not only did DCS look better, sharper on my Quest 2/link cable, performance went way up and now I can actually see enemies and spot ground targets.

I will try to screen shot all settings and update this thread but, this made a MASSIVE difference, I'm talking 40% gains. HALF whatever res you're running on the headset and then raise VR pix Dens in sim to 1.7. Magic bullet.

Interesting, how much FPS did you set it to?

Inviato dal mio REA-NX9 utilizzando Tapatalk

[Ghostrider711]

I keep the fps limit in DCS to whatever my VR refresh rate is. I think it’s possible to keep lowering your headset res and keep raising pixel density until it crashes it, then back that off. You basically want enough pixel density that when you look at the mountains at a distance that the peaks are clean cut and that will allow you to spot enemy and MFD’s as well. 
 

Do not use AA or AF , use pixel density to get clarity and sharpen the image. Lower your headset resolution to give you performance headroom. Shadows of any type will have to be carefully added and check performance after every shadow change. 
 

you can lower cockpit res to 512 and with 1.7 VR pixel density, in sim, and it looks like 1024 with a higher headset resolution, in oculus software. 
 

the biggest thing we need to do is figure out why that’s like that. 

Edited August 8, 2024 by Ghostrider711

[WipeUout]

12 hours ago, Ghostrider711 said:

For, off and on a month now, I have been messing with settings to get this thing to run good in VR. Lower texture settings *Cockpit to 512* Ect. Tonight, on a whim I raised DCS VR pix dens to 1.7 and cut my headset res in half.  Not only did DCS look better, sharper on my Quest 2/link cable, performance went way up and now I can actually see enemies and spot ground targets.

I will try to screen shot all settings and update this thread but, this made a MASSIVE difference, I'm talking 40% gains. HALF whatever res you're running on the headset and then raise VR pix Dens in sim to 1.7. Magic bullet.

What you effectively did is decrease your resolution to 50% and then increase it by 289%.

The result is a resolution at 144%.

What you could simply do is leave your HMD resolution at 100% and increase your PD in DCS to 1.2 and this will result in the same 144% increase, and spare some processing.  You can also increase your HMD resolution to 144% and leave DCS PD at 1.0, it will be the same result.  You can test both and compare if there are any FPS gain, sometimes processing is done more efficiently by the HMD compared to DCS and vice versa... 

[Ghostrider711]

Yes, I am aware of that, if you leave the HMD at X res and raise PD to 1.2 from 1.0, you still have jaggy edges and a poor image quality/poor performance in DCS. By decreasing the HMD’s res and forcing a huge upscale in PD within DCS, you get a much cleaner image and your lower HMD res, in some way, prevents DCS from using VRAM. The higher res you run the HMD at, prior to changing PD numbers, the more VRAM DCS will use, by a LOT. 
 

lowering HMD res does something to cap the resources DCS is using. What I meant when I said “if we can figure out why it does this” I was referring to why that prevents DCS from eating resources when adjusted the way I describe . 
 

 

Edited August 8, 2024 by Ghostrider711

[Qcumber]

Use a single source of supersampling rather than multiple sources. OTT or ODT to set the overall Res. Leave PD in DCS at 1.

Increasing SS will reduce the need for AA. It's just finding the right balance of performance Vs quality. I have a quest Pro and find that if I SS the centre resolution to 1.4 (over Godlike in VD) I don't need to use MSAA and it looks a lot better than DLAA. 

If you have not already tried then QVFR could be a good way of optimising your performance. On a Q2 this would be fixed only but I used to run FFR on my P4 and it worked very well. 

[Ghostrider711]

4 hours ago, Qcumber said:

Use a single source of supersampling rather than multiple sources. OTT or ODT to set the overall Res. Leave PD in DCS at 1.

Increasing SS will reduce the need for AA. It's just finding the right balance of performance Vs quality. I have a quest Pro and find that if I SS the centre resolution to 1.4 (over Godlike in VD) I don't need to use MSAA and it looks a lot better than DLAA. 

If you have not already tried then QVFR could be a good way of optimising your performance. On a Q2 this would be fixed only but I used to run FFR on my P4 and it worked very well. 

If I leave PD at 1 and adjust literally anything else and any combination thereof , the performance takes an absolute nose dive. The only way it works is if DCS PD is 1.7+ and the HMD is a lower res. I’ve literally tried hundreds of combinations. 
 

I get that worked for you, but my question would be how long ago did you do that and what was your hardware at the time? Is this what you’re currently doing?

[Glide]

2 hours ago, Ghostrider711 said:

The only way it works is if DCS PD is 1.7+ and the HMD is a lower res. I’ve literally tried hundreds of combinations.

I don't believe that looks good.  I tried it, and the "pattern" in the headset lens shows through on water real bad.  I don't think there's any magic solution to your settings. 

[Qcumber]

3 hours ago, Ghostrider711 said:

The only way it works is if DCS PD is 1.7+ and the HMD is a lower res. I’ve literally tried hundreds of combinations. 

All you are doing here is increasing resolution with one setting and decreasing width another. I would advise working out what your final resolution is and then applying a single modifier. 

Just to clarify how are you changing your HMD resolution? In the meta app or with OTT/ODT? 

3 hours ago, Ghostrider711 said:

I get that worked for you, but my question would be how long ago did you do that and what was your hardware at the time? Is this what you’re currently doing?

I presume this is referring to QVFR? For my Pico 4 this was earlier this year and I used the same pc specs as listed below. With QVFR you can leave all SS settings at 1 and use the QVFR config file or quad views companion app to adjust central SS. For example, I have the centre set at x1.4 and the periphery at x0.4. 

[Ghostrider711]

In Oculus 3200x 1632, with an 80HZ RR.  OTT FOV 0.64 0.69, encode res 2912, 400 bitrate, EDB disabled.

And that's a really cool deal how that lets you adjust periphery.

Edited August 9, 2024 by Ghostrider711