PD value does nothing after last patch?

[zvina]

I was not sure whether this is something on my end but my squadron colleague just tested it and it's the same for him. It does not matter which value we input for the PD, it always looks the same and runs the same fps.

[5ephir0th]

Working here, i use 1.3 PD on DCS and if not works (so, will be 1.0) it´s easy to see the difference.

Try to change de value, accept and reboot DCS

[zvina]

Bumping this up again. PD definitely does not work for Quest2 using Oculus runtime. It does work when running SteamVR or OpenXR. 
 

same thing confirmed by a squadron colleague that also uses Quest2. 

[diamond26]

It's not working on my side too with Oculus API. No difference in graphics or performance. 
For some reason seems to work when using OpenComposite (OpenXR)

Graphs below are:

1. with PD 1.6

2. with PD1.0

null

[ddc196]

I don't use the PD setting in DCS. I use the Oculus tray tool and adjust the super sampling. That has given me much better performance. I highly recommend trying it. I also force 45 FPS. Using Rift S.

[dburne]

Yeah I have not used PD setting in DCS in quite some time. I use either Steam VR or Open XR Toolkit depending on how I have the game running. I leave DCS at 1.0 default.

Edited June 8, 2022 by dburne

[diamond26]

Obviously the question is not what method of supersampling is used (I personally have PD 1.0 and use ODT or OTT for Oculus if I need to increase it) but if PD is working as supposed to and if the issue is with specific API like it seems to be with Oculus.