Current settings - Quest 3

[av8orDave]

Every now and then I play around with my VR settings just to see what has changed. A few things I figured I'd pass along:

System specs: Ryzen 9 7950X, RTX 4090, 64GB DDR, Quest 3

- I've been using:

- Oculus set to 72hz, 1.3 in the Quest/Meta app. DCS in-game PD set to 1.3; DLSS Quality; Textures set to high, terrain textures high, shadows medium, water medium

- With the recent update of the Quest/Meta app to v66, I decided to try ASW again. Note that I've always hated motion smoothing.

- Using 90hz, 1.5 in the Quest/Meta app, PD 1.3 in the Oculus debug tool, and ASW forced on (45 fps), DLAA rather than DLSS, and all settings to "high", I'm getting a crazy-smooth experience with minimal ghosting. I think this will be my new go-to setting. I think Meta must have tweaked something with ASW, because it suddenly works surprisingly well on my system with very few visual artifacts/issues.

[Phantom711]

Compared to the motion reprojection of WMR or Virtual Desktop, I find ASW the absolute best. It still shows some artefacts/wobble sometimes though.

I‘m also on a 4090 and my philosophy is a little different: I leave ASW on AUTO, so that it‘s only acting as a fallback option for the 5-10% of situations, where I can‘t maintain 72FPS (Trying 80FPS/80Hz lately though). It‘s mostly just at airfields or at the carrier. Compared to the others, ASW is also very smooth at kicking in.

However, I fly the F/A-18 almost exclusively (and the F-4 lately), so your use-case might be different.

[jurinko]

I have found, switching the ground shadows off but letting the shadow blur on smooths the sim immensely, while still providing shadows. Dcs got worse for me with the Phantom patch but this fixes it. Quest 3 cable. 

[Hoirtel]

In the past I have found vsync setting to fast very good but in last year or so set this to application controlled and set my DCS FPS to 85 for an 80hrz headset setting. I find this helps with some artifacts. 

Do any Q3 owners use the openxr toolkit now it's not longer in dev? I basically only use this for a bit of foveated rendering and minor super sample, which I can probably do with PD. 

Haven't tried DLSS/DLAA since release as I really didn't like the smearing. I use a 0.2 super sample with 2xMSAA. 

[TFS]

I have 4090 with Q3, I use MSAA 2x .65 with all other settings high, some visibility of details like grass and clutter around medium. I am not super savvy in this stuff at all, but I have my head set in the oculus settings at 120hz with ingame max FPS set to 75, why I don't know but everything works, and everything else maxed. I get an incredibly clear and smooth experience. It's mind blowing really. I used to have it at 4x MSAA but lowered to 2x and noticed no difference. I don't know what this ASW setting you guys are speaking of and I don't know what to do with PD..... Like in the VR tab in settings. I get lost in this topic easily, but I monitor my PCU and GPU temps and been running everything lately very well. My build was last October, seems to be improving with updates to be honest.  

[LaunchAlert5]

3 hours ago, TFS said:

I have 4090 with Q3, I use MSAA 2x .65 with all other settings high, some visibility of details like grass and clutter around medium. I am not super savvy in this stuff at all, but I have my head set in the oculus settings at 120hz with ingame max FPS set to 75, why I don't know but everything works, and everything else maxed. I get an incredibly clear and smooth experience. It's mind blowing really. I used to have it at 4x MSAA but lowered to 2x and noticed no difference. I don't know what this ASW setting you guys are speaking of and I don't know what to do with PD..... Like in the VR tab in settings. I get lost in this topic easily, but I monitor my PCU and GPU temps and been running everything lately very well. My build was last October, seems to be improving with updates to be honest.  

Are you locked at 60 FPS with ASW? 

 

If you can achieve 72 FPS stable, try setting your headset back to 72 Hz and eliminate ASW completely. 

 

On second thought, don't touch anything if you're happy with it. It's a dirty trap & viscous cycle chasing the FPS-dragon.   

[TFS]

2 hours ago, LaunchAlert5 said:

Are you locked at 60 FPS with ASW? 

 

If you can achieve 72 FPS stable, try setting your headset back to 72 Hz and eliminate ASW completely. 

 

On second thought, don't touch anything if you're happy with it. It's a dirty trap & viscous cycle chasing the FPS-dragon.   

I don't know what ASW is and if I have it on? Most maps my fps is locked at 72 in single player. Multi-player usually is smooth, sometimes I get slight jitters near farps for the first minute or after just joining. I also fly very low all the time as I'm in helicopters mainly, very impressed, cant imagine the clarity of a crystal or pimax super is like really, the q3 is amazing. 

[JesterIsDead]

On 6/21/2024 at 9:52 AM, davidrbarnette said:

Every now and then I play around with my VR settings just to see what has changed. A few things I figured I'd pass along:

System specs: Ryzen 9 7950X, RTX 4090, 64GB DDR, Quest 3

- I've been using:

- Oculus set to 72hz, 1.3 in the Quest/Meta app. DCS in-game PD set to 1.3; DLSS Quality; Textures set to high, terrain textures high, shadows medium, water medium

- With the recent update of the Quest/Meta app to v66, I decided to try ASW again. Note that I've always hated motion smoothing.

- Using 90hz, 1.5 in the Quest/Meta app, PD 1.3 in the Oculus debug tool, and ASW forced on (45 fps), DLAA rather than DLSS, and all settings to "high", I'm getting a crazy-smooth experience with minimal ghosting. I think this will be my new go-to setting. I think Meta must have tweaked something with ASW, because it suddenly works surprisingly well on my system with very few visual artifacts/issues.

Thanks for this. I tried it and it works better than before the recent patch. I have been trying to maintain 72 hz with no ASW. Works OK most of the time but the Phantom+ Caucasus map drops it down to 50-60fps. Using 90hz locked at 45 ASW is a bit smoother. I have a 4070 so PD=1 with zero super sampling

[gdx65]

Hi,

Good info here. I have started to test a Quest 3 with DSC and have started to use these settings (used for 1 hour yesterday only) as explained in this video DCS VR Multiplayer Settings Guide | Quest 3 | 2024

Do one really need to download al lthese 3rd party SW? such as Oculus Tray tool, which is not longer available but one can still download the last revision (OTTSetup_0.87.8). And the OpnXR Toolkit? Shouldn't the Quest 3 just be plug and play with DCS (after configuring the proper settings)?

My DCS machine has an ASUS TUF Gaming B650-PLUS WIFI with an AMD Ryzen 7 7800X3D; ASUS Dual GeForce RTX 4070 OC; 64GB  Kingston FURY Beast RGB DDR5-6000
DDR5, 2 x Crucial T700 SSD - 2TB. I normally use it with a LG 42" C4 4K OLED evo TV (2024) with all DCSS settings maxed out and works like a charm, super fluid. I use TrackHat and i do not see the need for VR. However, I am trying to force myself to use VR since I have a Quest 3 available. Hopefully with VR I skip to build a full size cockpit.....

 

[av8orDave]

8 minutes ago, gdx65 said:

Hi,

Good info here. I have started to test a Quest 3 with DSC and have started to use these settings (used for 1 hour yesterday only) as explained in this video DCS VR Multiplayer Settings Guide | Quest 3 | 2024

Do one really need to download al lthese 3rd party SW? such as Oculus Tray tool, which is not longer available but one can still download the last revision (OTTSetup_0.87.8). And the OpnXR Toolkit? Shouldn't the Quest 3 just be plug and play with DCS (after configuring the proper settings)?

My DCS machine has an ASUS TUF Gaming B650-PLUS WIFI with an AMD Ryzen 7 7800X3D; ASUS Dual GeForce RTX 4070 OC; 64GB  Kingston FURY Beast RGB DDR5-6000
DDR5, 2 x Crucial T700 SSD - 2TB. I normally use it with a LG 42" C4 4K OLED evo TV (2024) with all DCSS settings maxed out and works like a charm, super fluid. I use TrackHat and i do not see the need for VR. However, I am trying to force myself to use VR since I have a Quest 3 available. Hopefully with VR I skip to build a full size cockpit.....

 

You’re going to get varied input from different people, but my simple answer is: no. You don’t need all the third party software. I use the regular Meta App combined with Oculus Debug Tool (already in your Quest software) to make any necessary changes. VR in DCS doesn’t need to be a science project. Frankly, many of the “benefits” people seem to tout from 3rd party software I believe to either be a placebo effect or unique to their specific system / setup. 
 

Find some settings that work for you and go enjoy. At this point OTT is obsolete and OpenXR Tools might be as well.

[jurinko]

Openxr toolkit is inevitable for many for switching turbo mode on to get smoooth performance. This can be alternatively done by the foveated rendering software.

[gdx65]

4 minutes ago, av8orDave said:

You’re going to get varied input from different people, but my simple answer is: no. You don’t need all the third party software. I use the regular Meta App combined with Oculus Debug Tool (already in your Quest software) to make any necessary changes. VR in DCS doesn’t need to be a science project. Frankly, many of the “benefits” people seem to tout from 3rd party software I believe to either be a placebo effect or unique to their specific system / setup. 
 

Find some settings that work for you and go enjoy. At this point OTT is obsolete and OpenXR Tools might be as well.

Thanks for the feedback. That is why I felt something is not wrong with those videos showing how to use VR in DCS. I just gave it a try as first shot. Later I will remove these third party sw and just use the Meta tools....

1 minute ago, jurinko said:

Openxr toolkit is inevitable for many for switching turbo mode on to get smoooth performance. This can be alternatively done by the foveated rendering software.

Have you tried without? I will try as well...

[gdx65]

On 1/28/2025 at 1:11 PM, gdx65 said:

Thanks for the feedback. That is why I felt something is not wrong with those videos showing how to use VR in DCS. I just gave it a try as first shot. Later I will remove these third party sw and just use the Meta tools....

Have you tried without? I will try as well...

Little update. I now do not use Openxr toolkit at all, only DCS and Meta quest 3 all working smooth. I use the USB cable

[Gunslinger52]

Hi all,

is anyone here on a low-end card like my 3060?  have just bought a Q3, and starting to experiment with all the settings to try and find an acceptable level of experience.  I'm an ex G2 user, where things were pretty good.  

Unfortunately, a 4090 isn't on the horizon just now, so wondering if my only option is to turn down the settings in DCS?  Have ASW on Auto, 1.3 on the slider, 400Mbps fixed in the debug tool.  FPS is fine for me (about 35-45), but ghosting down low over a city or forest is terrible.  

Have a good one

'52

[Qcumber]

Have your tried QVFR in fixed mode? 

https://github.com/mbucchia/Quad-Views-Foveated

[Gunslinger52]

3 hours ago, Qcumber said:

Have your tried QVFR in fixed mode? 

https://github.com/mbucchia/Quad-Views-Foveated

A long time ago with an extremely old Pimax.  Must admit, it made a good difference.  Tried this guys tips today, and seemed overall to work well (a lot less ghosting, higher average FPS, no FPS tanking, and very readable MFD's.  

 

But I will try his QVFR, thanks for the tip.

Have a good one. 

'52

[diego999]

5 hours ago, Gunslinger52 said:

Hi all,

is anyone here on a low-end card like my 3060?  have just bought a Q3, and starting to experiment with all the settings to try and find an acceptable level of experience.  I'm an ex G2 user, where things were pretty good.  

Unfortunately, a 4090 isn't on the horizon just now, so wondering if my only option is to turn down the settings in DCS?  Have ASW on Auto, 1.3 on the slider, 400Mbps fixed in the debug tool.  FPS is fine for me (about 35-45), but ghosting down low over a city or forest is terrible.  

Have a good one

'52

 

I had a 3060ti until a week ago. You can play fine, accepting there's going to be compromises. 

Have you tried reducing your FoV? You can cut a good chunk of the total pixel count. It depends of the facial interface, how close your eyes are to the lenses, and the general shape of your face. In my case, I can't even see the difference with 0.85 or higher, so that's a nice boost right there.

Start by lowering in 0.05 increments. So, 0.95, 0.90, .0.85, 0.80 until you start to see the black box. When you get to that point, it's too much, go back one step.

You can do that with Oculus Tray Tool or Oculus Debug Tool.

QVFR should be a good option too if your cpu can take the hit.

[Gunslinger52]

On 2/9/2025 at 4:11 PM, diego999 said:

 

I had a 3060ti until a week ago. You can play fine, accepting there's going to be compromises. 

Have you tried reducing your FoV? You can cut a good chunk of the total pixel count. It depends of the facial interface, how close your eyes are to the lenses, and the general shape of your face. In my case, I can't even see the difference with 0.85 or higher, so that's a nice boost right there.

Start by lowering in 0.05 increments. So, 0.95, 0.90, .0.85, 0.80 until you start to see the black box. When you get to that point, it's too much, go back one step.

You can do that with Oculus Tray Tool or Oculus Debug Tool.

QVFR should be a good option too if your cpu can take the hit.

Ahhrr nice one, thanks for that!

[Hecate_Megami]

i'll mark this，and read it later