sleighzy

@Qcumber, still works fine for me. It's just not starting for you, e.g. it's not creating the dlsstweaks.log file, or you aren't noticing a difference? Don't know if you've solved this yet but have you renamed the DLSSTweaks dll to dxgi.dll yet? DCS "broke" this a few patches back and you have to rename the dll for it to work.

@Blinde, yes DCS broke this a few patches ago. See my post here however for the DLSSTweaks workaround to resolve this issue, and how you can verify that it's working:

This no longer runs the wrapper using the default instructions in the DLSSTweaks README. This was "broken" in DCS a couple of patches ago. You can confirm this by checking if the dlsstweaks.log file was created in your bin-mt folder, or if it contains the expected date time stamp when you start DCS. As per their GitHub issue https://github.com/emoose/DLSSTweaks/issues/134 the workaround is to rename the DLSSTweaks nvngx.dll file you place in your bin-mt folder to dxgi.dll. Once you've done that then the log file will be created, and have the expected date time stamps, when you start DCS. This can also be verified by enabling the debug hud overlay in the DLSSTweaks config and ensuring that this is displayed in DCS.null

Hi @Taz1004, awesome work!. What's the recommended practice when performing DCS updates? Disable all these mods, delete the shader caches, update DCS, start DCS to ensure it works fine, reenable these mods and then delete the shader caches again? Thanks heaps in advance.