Qcumber

I have noticed today that the foveated region is not as clear and sharp as the image is without QVFR at the same resolution. For example, if I use VD at Godlike resolution the image looks clear and sharp without applying any sharpening. With QVFR set to 1.0x centre and 0.5x periphery (0.25x0.25 size) the foveated image is "fuzzy". I have to apply quite a lot of sharpening and it still does not look as good. [DLSS Quality, 72Hz, latest version of VD, HEVC 10bit at 150mbps]

Which update? Could you please post the version number? Headset and app. Are you using PTC?

I just loaded up a 4x4 dogfight over Normandy and was straight in. Took about 3 minutes. A lot faster than using the old fast mission generator. It also allows for better control of opponent aircraft etc.

I've tried this a couple of times and it works ok for me. For a very quick mission generator it does tho job. A welcome addition. It does need some improvements but is a reasonable start. It feels like a beta version that just has a way to go yet. I like that it has been introduced at this stage. It provides opportunity for constructive feedback about how we want the final version to look. The create fast mission generator was useless for me. With anything WW2 related it basically creates the same missions without being able to control specific planes etc. The new generator has more options. Yes it is not perfect but it has potential.

I asked above but I did not get a reply but I'd there any specific advantage using the autoexec config (DLSS_Preset = 'K') versus using NVPI.

NVPI has retained the DLSS settings for me the last 2 driver updates.

I have always found NVPI easy to use. Is there any specific advantage using the autoexec config file other than the MFD option? I presume it will need reinstalling after each DCS update.

Is it worth upgrading from 64gb to 128gb RAM for VR? If I did it would be 4 sticks. I've read that 4 sticks of DDR5 RAM can be unstable.

@BIGNEWY What is the default preset now for the least DLSS version? Maybe there is now a better performance optimization in DCS!? I need to do some tests but haven't had chance yet. BTW: The latest version of NVIDIA profile inspector allows you to automatically select the latest version of DLSS and choose which preset version.

DLSS 310.2.1.0 is DLSS 4. I know it does not appear to make sense. You would expect DLSS4 the begin with a 4 but this is the most recent version of DLSS. You still need to select DLSS in DCS. Now DLSS in DCS will default to the latest version.

Seriously though if this is the first time you have tried DLSS4 it's a massive improvement. I've not tested yet to see if there is any significant difference with the optimisation.

How much less? Enough to change your name to "ghost29"

Yes. It looks that way. https://www.techpowerup.com/download/nvidia-dlss-dll/

I use JoyToKey software. This can centre the mouse and also apply offsets to the mouse cursor position when it is locked to head movements.

How are you checking which version of DLSS and which preset you are using? DCS does not show this.

I had this issue sometimes, a while ago but not for about 18 months, even with my old setup (5800x3d, rtx4070). It might be worth just going back to basics with no mods etc. As Mr_sukebe says. Check VRAM and RAM usage.

Use NVIDIA profile inspector. You can set this to automatically use the most recent DLSS version and the preset.

Ghosting can be minimized/eliminated by increasing resolution. I do this by using QVFR so that I can push the foveated resolution up to about 5000 pixels (equivalent). It really depends on how much your GPU can handle. With a 4090 you should be able to do ok.

I'm not sure if this works with the Q3. With the QP you need to make a change to the headset android settings before it will work.

I only really noticed it against certain backgrounds such as low over the sea and only when I use an ethernet-usb link to my headset. I wonder if it is cable interference. I will try a shielded ethernet cable to see if that helps. I have not noticed this but have not really flown on the map enough yet.

Not yet but I intend to. I've not had much time to work in this recently but hopefully I can get something together soon.

Well done. You managed to bleed the stone.

I am getting very good results with VD since the last update. Very smooth and sharp. Good latencies. But I have noticed a slightly annoying moire. It's not always noticeable, only really when my eyes are close-focussed on a very flat, dark background such as the sea. Has anyone seen this? I am using an Ethernet to USB connection rather than WiFi.

You need to activate the overlay in VD. This will show the bitrates and latencies.

There is an option in the VR headset. I can't remember where it is.