Qcumber

Overall this is really amazing. I can run DLSS in balanced and preset J and it looks better than MSAAx2 with much better performance. No ghosting, no jaggies. The only issue I have is my headset freezes after about 10 minutes. Something else to troubleshoot!

Me too. Set it to K and it defaults to J. J still looks good though!

I thought I was being clever being ready at 1400. We are so naive

DLSSTweaks update https://www.nexusmods.com/site/mods/550

I updated the drivers and deleted DLSSTweaks files from DCS bin and still CTD. Profile inspector wouldn't run either. All very frustrating. Could you please share the exact sequence of what you did? That was quick. I checked about 2 hours ago. Does this solve the CTD?

Me too. I was on NVIDIA and Scan and kept refreshing but could not get access to an "add to basket" button. Scan are offering some at MSRP (£979) but now out of stock!!

Thanks. I'll give it a go. Hopefully there will be a DLSSTweaks update soon.

DLSS now causes headset freeze and CTD when I try to load a mission. Not sure why. I am using 571.96 and preset J. I have tried a slow repair and deleting all the shaders but no difference. Anyone else having this issue?

In my tests ghosting in aircraft flying against sky is gone but there is some smearing when planes fly over the ground, particularly against trees. Spotting is an issue due to changing contrast against some backgrounds. Unfortunately using DLLS 4 for me is very unstable and I keep getting headset freezes and CDT. I have updated to the latest driver (571.96) and am using prest J. I'll try again after the official release. Hopefully tomorrow!?

It's a known issue and not easily solved. Try keeping your headset on and centred while DCS loads. That can help.

I am tempted too! I keep getting a headset freeze when DLSS 4 is enabled. I want to see if the driver update will help.

I think that's the beta driver. Official driver release hopefully the same day as 5090/5080 release (30th Jan).

Sorry. That one passed me by.

The v63/64 issue didn't brick any headsets. It just meant that some people could not access DCS via meta link for a few weeks. It did not affect my headset (and some others). Those using VD were also unaffected.

I have now reverted back to v72. I had accidentally left PTC enabled . Now eye tracking and calibration work fine.

Discord VD update 27/1/25 "...we’ve had lots of reports of performance issues on the Quest v74 PTC, so make sure to opt out in the Meta Horizon phone app. If you are already on v74, opt out and then perform a factory reset to go back to v72." https://discord.com/channels/564087419918483486/592909523295928340/1333466101119455333

It might be better with the new official drivers.

Update on this. My issues are not related to V74. At least not directly. I had some issues with eye tracking that I have now resolved. I don't know if this was something related to V74 or not but stability is ok and no stuttering. I am still getting some headset freezes though in VD and Meta but I think these might be related to DLSS 4. So I'm waiting for the official NVIDIA driver release.

DLSS 4 with preset J is a massive improvement but not flawless. With the final driver release (hopefully on Thursday) I am hoping this will be better. As Diego999 says I would prefer the official release.

Yes. SSW is terrible compared to ASW but VD handles fps lower than refresh rate better than meta.

VD is a bit faster but still noticeable.

I would suggest trying it again once the update is officially released with the final drivers. By the end of the week is suppose.

Yes. It is annoying. Particularly as dcs shadows and lower resolution can cause "flickering". There must be away.

DLSS 4 is definitely an improvement. Does anyone know if we are likely to see even better performance on 5000 series GPUs? Or will they just benefit from frame generation, which is not much use to use vr uses.

Eye tracking is back on line! Solution is in the other thread. Unfortunately I am now having issues with ethernet connection. I have activated the settings as per this thread but can now only manage about 130 Mbps when I had 400 Mbps only two days ago.