Shimmering without any AI or Upscaling

[broda]

Hi everyone,

I have been playing on the Quest 3 for quite some time. To be able to spot easier, I have switched off all upscaling and AI.

My problem now: Crazy amount of shimmer, that starts driving me crazy. (example in the attached video)

What can I do to avoid that? Activating DLAA or MSAA just add ghosting and destroys my capability to spot targets properly. 

Attached also my graphics settings.

Would appreciate any recommendations.

My System:

RTX 4090, Ryzen 7800X3D, 64GB RAM, Quest 3 connected to my PC via USB-C

 

 

Edited Monday at 03:59 AM by broda

[YoYo]

Unfortunately, this is normal for DCS and you have to accept it. The solution is always to increase the resolution of the goggles to the maximum threshold when you start having problems with performance on your hardware. Also try the DLSS and DLAA settings. This is quite convenient but unfortunately the image starts to be slightly blurred and ghosting may appear. I personally fly with a resolution of about 3300 pxt per eye plus MSAA x2.

[Qcumber]

4 hours ago, broda said:

Hi everyone,

I have been playing on the Quest 3 for quite some time. To be able to spot easier, I have switched off all upscaling and AI.

My problem now: Crazy amount of shimmer, that starts driving me crazy. (example in the attached video)

What can I do to avoid that? Activating DLAA or MSAA just add ghosting and destroys my capability to spot targets properly. 

Attached also my graphics settings.

Would appreciate any recommendations.

My System:

RTX 4090, Ryzen 7800X3D, 64GB RAM, Quest 3 connected to my PC via USB-C

 

 

 

What is your Meta link scaling set to? This is the base resolution before applying a multiplier with PDx1.6. It helps to know what your final resolution is so that we can properly advise. 

Try pushing the whole image resolution to about 5000 pixels. This should help with ghosting in DLSS, but will give a huge performance hit even with a 4090. You will need to use DLSS performance settings, which is now surprisingly good.

I use Quad View Foveated Rendering to increase the centre resolution to the equivalent of about 5000 pixels. This eliminates DLSS ghosting and gives a very crisp image. With a Quest 3 you will need to use fixed foveated rendering mode with QVFR which means a reduced peripheral resolution but you should be able to find the right balance of settings to work for you. For example you could try setting the PD in DCS to 1 then set the periphery to x0.8 in QVFR and the centre to x2 with a size of 0.3x0.3. it will increase your CPU load but a 7800x3d should be able to handle it OK. 

 

[sleighzy]

In addition to this you could try adding the below config (made available in the last couple of DCS updates) to use a different preset to see if it helps in reducing the ghosting. Note, as mentioned by Qcumber this will never go away completely unless you can burn through it  

Add the below line to the C:\Users\username\Saved Games\DCS\Config\autoexec.cfg file, create it if it doesn't already exist

DLSS_Preset = 'K'

The additional optional line below can also be added to that file. This will bypass the HUD and MFD for DLSS, means greater control if you'd like to use DLSS4 for the game, but hate ghosting on the MFDs and don't want to apply to those. Best of both worlds.

HUD_MFD_after_DLSS = true

[YoYo]

Also try just DLAA (AntiAliasing section), without any upscaling, i.e. without DLSS, e.g. DLAA creates some artifacts but overall the image is the best in terms of smoothing the lines.

Edited Monday at 12:42 PM by YoYo

[broda]

Thanks for all your input guys! Some stuff to test out over the next days

Quote

23 hours ago, Qcumber said:

What is your Meta link scaling set to? This is the base resolution before applying a multiplier with PDx1.6. It helps to know what your final resolution is so that we can properly advise. 

Try pushing the whole image resolution to about 5000 pixels. This should help with ghosting in DLSS, but will give a huge performance hit even with a 4090. You will need to use DLSS performance settings, which is now surprisingly good.

I use Quad View Foveated Rendering to increase the centre resolution to the equivalent of about 5000 pixels. This eliminates DLSS ghosting and gives a very crisp image. With a Quest 3 you will need to use fixed foveated rendering mode with QVFR which means a reduced peripheral resolution but you should be able to find the right balance of settings to work for you. For example you could try setting the PD in DCS to 1 then set the periphery to x0.8 in QVFR and the centre to x2 with a size of 0.3x0.3. it will increase your CPU load but a 7800x3d should be able to handle it OK. 

 

 

3936 x 2112 at 80hz (which is 1x)

Will try the DLSS Settings and quad view. Is it better to max out the Meta resolution and cut back the PD Setting in game?

22 hours ago, sleighzy said:

In addition to this you could try adding the below config (made available in the last couple of DCS updates) to use a different preset to see if it helps in reducing the ghosting. Note, as mentioned by Qcumber this will never go away completely unless you can burn through it  

Add the below line to the C:\Users\username\Saved Games\DCS\Config\autoexec.cfg file, create it if it doesn't already exist

DLSS_Preset = 'K'

The additional optional line below can also be added to that file. This will bypass the HUD and MFD for DLSS, means greater control if you'd like to use DLSS4 for the game, but hate ghosting on the MFDs and don't want to apply to those. Best of both worlds.

HUD_MFD_after_DLSS = true

tried that already. MFDs seem fine, no more shimmering but horrible ghosting.

19 hours ago, YoYo said:

Also try just DLAA (AntiAliasing section), without any upscaling, i.e. without DLSS, e.g. DLAA creates some artifacts but overall the image is the best in terms of smoothing the lines.

Will try that. Will this effect spotting? 

Edited 22 hours ago by broda

[Qcumber]

33 minutes ago, broda said:

Is it better to max out the Meta resolution and cut back the PD Setting in game?

It's better to do everything in one place if possible so I would advise using Meta and the Oculus Debug Tool or Oculus Tray Tool 

Edited 21 hours ago by Qcumber