Qcumber

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.

VD can be a bit twitchy sometimes unless you have very good latencies. Can you post a screenshot of your VD overlay (the one in your headset) then we can see what your latencies look like.

Sorry typo regarding VRAM. Thankfully I don't fly the Chinook. Please keep the "angry" bleed away from this thread otherwise it will deter new VD users. Your comments relate to very specific factors and it derails the point of this thread.

DLSS in DCS is an older version so using DLSS 4 and preset K will give you much better visuals. Sharper and much less ghosting.

Have you followed all the setup guide for VD, including using the right router setup etc?

Everything I have tested so far does not go above 13Gb with the 5080. Including F-4 on Marianas map on takeoff. But yes simpler maps and modules use much less.

You need to download NVIDIA profile inspector and then you can select to automatically use the most up to date DLSS release and can select preset K. https://github.com/Orbmu2k/nvidiaProfileInspector/releases Check out this thread too:

Is that VRAM allocation or VRAM use?

If it was early '90s it was probably a 386 or 486 with a 40 or 60 MB HDD. That was my first desktop PC.

I have found the best results with DLSS quality preset K. QVFR centre resolution set to equivalent of about 5000 pixels with peripheral about half native. This gives a really sharp image with no ghosting and good AA.

I've been there. That or accidentally putting my prescription lens inserts in the wrong orientation.

I gave up with Q link last night and switched back to VD. The latest update gives 2-pass encoding with good performance.

For me it appears random. Just sudden crash of link app. DCS still runs in the background. It usually happens within about 5 minutes of starting a mission.