Qcumber

No. It's bloody annoying. Curiously the limit is 140Mbps which is my network speed. Maybe a router setting!?

For reference it would be useful to know your final resolution rather than the multiplier so we can compare it more meaningfully. Apologies if you have already said this but there is a lot of dialogue. What is your initial resolution before applying any SS?

Why not use QVFR instead. This is the newer and better option.

What is your final resolution? Quoting multipliers can be confusing. For example, I start at 2112 in Meta and apply 1.6 for a total of 3379.

Yes and no. SSW us better than it used to be but not as good as ASW. However, VD is better at managing FPS below target refresh rate than Meta (subjective opinion).

I have managed to get it working. Not sure what I did but it now works. Thanks for the offer though.

DLSSTweaks was causing some issues when DLSS4 was first released. I think the latest release of DLSSTweaks works ok. The simplest method is replace the DLSS file in the DCS bin folder then use NVPI to change the preset.

This has gone off topic. It should be about DLSS 4. This is an interesting discussion. Could you please start a new thread.

With my setup I cannot get more than about 350 Mbps with VD. At that level my decide latency causes it to be a bit unstable. It's more stable with an ethernet cable but I have had issues connecting. Overall meta link gives me a smoother experience and is visually equal to VD. I agree. With VD I need to boost the centre resolution up by about 1.2-1.3 on Godlike to get decent visuals.

After having to do a factory reset I have redone the steps to activate ethernet. Nothing has changed in terms of hardware but I am now limited to 140Mbps rather than the 400 I had previously. WiFi is off. I have accessed the browser from the headset so can con firm I can access the internet. Any ideas?

Any idea how to stop the "useful" reminders that the handsets may not track very well without WiFi?

DLSS 4 is still crashing for me. CTD after about 1-2 minutes. I have removed all DLSS tweaks files, tried all versions of the DLSS 4 versions. Tried J and K. Multiple repairs of DCS then replace the DLSS file. It still crashes every time.

How do you get 500mbps with a QP?

You can use JoyToKey to set one HOTAS buttons as "shift" then map a while second set of keybinds. Also, a "finger mouse" means you don't need to use any buttons. There is a velcro strap which you can bind to the joystick.

Initially DLSS 4 looked very good but I have had big problems with my QP since updating to DLSS4. After a very frustrating few days I have abandoned the new DLSS and have gone back to MSAA. This involved several DCS repairs and headset factory resets. Very annoying.

OK. My thoughts after using DLSS4 for a few days: Pros: Clarity (cockpit and distance) is very good even with "performance" setting. Near perfect. Anti-aliasing is excellent. Overall a very smooth experience. Much better than MSAA. Minimal ghosting of planes against the sky (some "tadpoling" at distance but not too bad). Cons: Ghosting against the ground is very bad. Horrendous blurring. Once you see it for the first time you keep looking for it! Objects can become very difficult to see against clouds or contrasty backgrounds. Spotting dots are terrible. You just can't see them at all. The only solution is setting dots to 2 pixels. Then they look like big blobs. There is a significant performance hit compared to preset E or F. If you use QVFR there is no benefit versus MSAA x2. DCS keeps crashing after 1-5 minutes [This last one might just be my issue but I can't solve it and I can't be bothered spending any more time on it. I am very vexed]. Overall this is much better than anything before but is still not there yet. I am going to stick with no AA or MSAA for now.

I've seen this too. Ghosting in the sky is virtually gone but there is terrible ghosting against the ground. Particularly trees. Yes. With QVFR I get the same FPS with DLSS4 Quality as MSAAx2.

Thanks. I'll give that a go.

No. Reprojection is off. I think it is related to preset J and K.

I am still getting crashes and headset freezes using DLSS 4. Both with VD and meta link. Everything is fine with no AA or MSAA. I tried removing DLSSTweaks and set the global preset (K or J) with NVPI. I have cleared out the shader folders. I still get random crashes. Edit: not sure what I did but it's now working with the latest DLSS release (310.2) and preset K.

Now that I finally got rid of all CTDs and headset freezes I can fully appreciate DLSS4. It's how I hoped it would be when it was first introduced to DCS. I'm impressed.

I use headpoint for the cursor so I can point at buttons with head movement and then use a "finger mouse" strapped to my joystick to click and scroll. Alternatively you can map clicks/scroll to a "hat". I also use JoyToKey to map HOTAS buttons to centre the cursor and offset left/right etc. It allows me to easily reach and click switches anywhere in the cockpit. https://amzn.eu/d/bclX5gP

Me too. Especially as DLSS is starting to look good!

Thanks for this. I'll give it a go. If i want to verify K is being used how can i check without DLSSTweaks?