Dunska

For me, by far the best results are from locking at 72 fps in NVCP and leaving DCS at the default (180 fps). I tried leaving it unlimited and also forcing it to 72 fps in DCS (by manually modifying the options.lua to set "maxFPS=72") but still had micro-stutters. Limiting to 72 fps in NVCP and setting that in the headset (Pico 4 with Virtual Desktop in my case) gave me the best results.

Yay! Small thing, but it bugged me a lot.

jdba97 has also started a series of F/A-18, co-op missions (three so far) called "Operation Ceder Shield". I haven't played them yet, but worth a look: https://www.digitalcombatsimulator.com/en/files/filter/type-is-multiplayer/unit-is-fa-18c/user-is-jdba97/apply/

Operation Hormuz is great - I played that with a mate in 2-player co-op and it was fine. We've also played Operation Mountain Lion and Oil in the Water - both cool, but I would recommend opening each miz file in the Mission Editor and saving it, so it updates for stuff in the latest DCS versions. I think we had to enable/disable the carrier deck crew in some missions as the statics on deck messed it up. We also removed the dust from some missions in OitW as the new dust/fog made it very hard to see anything.

Strange - NVPI DLSS override works fine for me with 572.70 and NVPI 2.4.0.18 (on a 4090).

Yeah, I use them for View controls. The analog stick for moving the view around in external camera mode and the upper one for selecting different view (e.g. weapon view, fly-by view, F10 Map view, etc.) in all airframes - jests, helos, props. You need SimAppPro running to have the vibrations working.

I have the Viper stick grip with the EX Shaker Kit (more hats and rumble)

I started with the F/A-18 throttle grips, then later swapped to the F-15 EX throttle grips with finger lifts - much better having more buttons, hats and rumble vibration.

You don't need DLSSTweaks to show the DLSS Hud, just use the registry settings: Set manually or copy this into a .reg file and run it. For me I only see it in 2D, so I run it in 2D to check. DLSS Hud On: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\NGXCore] "ShowDlssIndicator"=dword:00000400 DLSS Hud Off: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\NGXCore] "ShowDlssIndicator"=dword:00000000

Hi All. Does this setting work for anyone in DCS 2.9.12.5336.1? I tried a range of setting for "options.graphics.lights" using a night approach to a carrier and airport, however all settings were the same... airport light first visible around 24.6 miles and the carrier at around 5.5 miles. I could see from my dcs.log that it took the setting... I just did not see any difference in light visibility distance.

There is a new nvidia hotfix driver 572.24 for game crashes. I've read it is aimed at DX11 and DLSS4, so might be worth a try. https://nvidia.custhelp.com/app/answers/detail/a_id/5624

Will be interesting to compare these. Will grab the new DLSSTweaks just released on NexusMods and give it a whirl. So the DLSS override you can do in the nvidia app is only for specific "whitelisted" games? I was hoping to point it at DCS.exe

No for me. TDC holds steady. Maybe something else mapped to TDC as well?

I'll definitely be trying it out today.

Seems to still work ok for me after the 2.9.12.5336 patch. I removed all mods, updated DCS, did a slow repair (just because), then enabled mods again.