Huge VR improvement with unk setting

[Mike_CK]

Ok…so just a recommendation for those of you- like me- who don’t really understand all the various VR settings. Sorry for long post but  want to give enough info that someone can correct me if I’m wrong. This made a HUGE improvement for me.

I use Oculus 3 with Oculus Tray Tool. I had headset res. at 1.0 (so 4128x ?) with a PD of 3. My encode resolution at 3650 and my bitrate at 300. Any higher bitrate resulted in stuttering. Well, I found out that THAT was caused by ASW even though I had it “off” in OTT. you still have to turn it off in game with R.CNTRL + 1 (or R. CNTRL +2 to lock at 50% 72hz=36fps)

 I read to set encode resolution close to your headset resolution. So I raised my encode to 4128 but also increased the headset resolution to 1.1 (so like 4400?). But I lowered PD to 1.2 and also raised encode bitrate to 400. The Image was a little better and things were somewhat smoother with no FPS drop. Great.

BUT…today I read further and it mentioned - for Oculus 3- to set Encode Bitrate to 450 and in Oculus Debug to go to Codec and select  264 in drop down. So I did.

Holy S**t. Image is much clearer, image quality is much better, planes no longer stutter as they go by AND - even better- on an F-4 Kola campaign mission where I used to get 48-52fps, my FPS went to a steady 72 FPS. Retribution mission went from 38-44fps to 60-65fps

So, if you have Oculus 3 and haven’t already, go onto Oculus Debug and turn on Codec 264!!

Edited July 14 by Mike_CK

[draconus]

Would be helpful to include your hw spec, at least cpu and gpu.

Also why would you mess with scaling in two places? Leave one at 1.0x and test with the other.

I have not yet tried to change my encode res but use other settings currently - check this thread:

As for the encoding value and its meaning:

https://vrchase.com/encode-resolution-width/

[Mike_CK]

9 hours ago, draconus said:

Would be helpful to include your hw spec, at least cpu and gpu.

Also why would you mess with scaling in two places? Leave one at 1.0x and test with the other.

I have not yet tried to change my encode res but use other settings currently - check this thread:

As for the encoding value and its meaning:

https://vrchase.com/encode-resolution-width/

By scaling im guessing you mean the Oculus resolution as well as PD? B.c I find the PD to be a “finer” adjustment. Meaning upping my goggles another level effects performance but going from PD1 to 1.1 improves clarity a little with no impact.

but also…b/c I don’t know a lot about this stuff

i was just never aware of the “Codec” thing and it had a significant impact.

I run:

Intel i-9 12900

128GB DDR5 RAM

Radeon Rx 6900 XT 

[Raven (Elysian Angel)]

https://forum.dcs.world/forum/302-virtual-reality/

[draconus]

PD is also scaling but on the DCS side and it has the same impact - you may just not notice the performance changes.

[Mike_CK]

I thought PD is processed by the CPU/Graphics card and is part of the image data delivered to the Oculus goggles. Meaning that PD is processed by a different means than increasing headset resolution so that one may impact performance whereas the other may not. Is that incorrect?

either way, the purpose of the post was to alert Oculus users to the Codec 264 setting and trying to get Encode resolution close to headset resolution to avoid artifacts and image issues due to upscaling. Two things I wasn’t aware of and both had a huge impact on image and performance for me

[twistking]

Can someone else confirm that disabling ASW in OTT does not in fact disable ASW in DCS?

[Qcumber]

53 minutes ago, twistking said:

Can someone else confirm that disabling ASW in OTT does not in fact disable ASW in DCS?

If ASW is disabled then it will remain disabled in any application, including DCS. I would advise using keybinds in OTT to toggle ASW on/off whilst in DCS. 

[draconus]

On 7/16/2025 at 5:56 PM, Mike_CK said:

I thought PD is processed by the CPU/Graphics card and is part of the image data delivered to the Oculus goggles. Meaning that PD is processed by a different means than increasing headset resolution so that one may impact performance whereas the other may not. Is that incorrect?

Let's make some things clear. Headset has a fixed LCD resolution. DCS PD or Oculus software scaling or Steam VR scaling and even DLSS all does the same - render the image in different resolution - this is what most severly impacts performance and is done purely by GPU. Changing resolutions have no impact on CPU. The rendered image is then rescaled to the native headset resolution to display it but it's an easy job, with no perceived performance cost.

[Mike_CK]

On 7/19/2025 at 8:32 AM, Qcumber said:

If ASW is disabled then it will remain disabled in any application, including DCS. I would advise using keybinds in OTT to toggle ASW on/off whilst in DCS. 

Disabling ASW in OTT and/or Oculus debug does not always actually disable it in game for me. I often times will notice studdering and go ahead and press Right CTRL + 1 (numpad) which turns off ASW and will instantly clear it. I then hit Right CTRL + 2 to lock frames at 50% (36fps for me since bouncing around from 60-72 creates jerkiness). 

what I don’t know is what program/application hitting CTRL +1 is effecting. Meaning is pressing those keys telling Oculus debug to turn of ASW (even though it’s set to off), OTT or some other program.

all I know is it worked

but Selecting 264 as the Codec really boosted performance and I had never heard of that