sleighzy

Can you attach your DCS log file for when this fails to initialize using MT?

@Simonator Did you solve your problem? I notice in your logs it says it's attempting to use WMR for your OpenXR runtime. 2024-08-12 00:35:54.140 INFO VISUALIZER (Main): LAUNCH IN VR OpenXR: Windows Mixed Reality Looking at another user reporting something similar they needed to set SteamVR to be their default OpenXR runtime. Have you tried this as well?

This is because Steam will always run the ST version if you use the DCS.exe file directly, even if using the one bin-mt directory. You can't use shortcuts like that. You have to start it from your Steam library, ensuring that Multithreaded Preview option is set. This is still running the ST version. For Steam you have to run it from within your Steam library. The only reason you're probably seeing a difference is that you're forcing OpenXR, vs. MT which is OpenXR by default.

For DLSS ghosting have a look at this and see if it helps you at all:

The DLSS option in DCS is more performant than MSAA, however has a side-effect of ghosting. The DLSS library itself supports a number of presets for varying graphics qualities/performance. DCS appears to set preset C. A number of DCS users currently use the DLSSTweaks tool (https://github.com/emoose/DLSSTweaks) to override this preset value. A commonly recommended one, at least within the VR community, is preset F which has great performance, image clarity, and removes the ghosting which is otherwise seen with preset C (even when using the Quality mode). Could this be investigated and potentially the default preset used by DCS to be updated to remove the current ghosting that is experienced. Would be good to evaluate the preset with both 2D and VR, as if the experience is much better for VR users, but has no change for 2D users, then a direct change of this should have minimal impact on users across both platforms. For anybody wanting to test this themselves; follow the instructions on the link above, and then rename the DLSSTweaks "nvngx.dll" placed in the DCS bin and bin-mt directories to "dxgi.dll". Set the DLSSPresets to F in the dlsstweaks.ini file, place this in the bin and bin-mt directory as well, and then start DCS and use DLSS. You should see the dlsstweaks.log file created in the bin or bin-mt directory. Additionally if you enable the DLSSTweaks debug overlay you should see this as per the screenshot. You should see less ghosting when using DLSS. Similar config exists within that config ini file for using with DLAA instead of DLSS. Nvidia Global Profile (recommended approach): A more simplified approach to configuring this, will apply to all games using DLSS, is to use DLSSTweaks to set this preset globally within the Nvidia Global Profile. This means you don't need to place the dll file and ini file (or update it) in the DCS/bin-mt directory. Instructions as follows: 1. As per the previous instructions, download the DLSSTweaks.zip file from https://www.nexusmods.com/site/mods/550?tab=files 2. Unzip this and then run the DLSSTweaksConfig.exe file. This requires administrator permissions, but will prompt you and run if you don't 3. Set the GlobalForcedPreset to F (or preset of choice) as per the screenshot and save changes Set GlobalHudOverride to Enabled (all DLLs) to display the debug overlay that will show the preset currently in use. Update 11/14/24: The latest release of the DLSS library (3.8.10) has removed all other presets except for E and F. If you just replace the DCS nvngx_dlss.dll file in the bin and bin-mt directories then DCS will now by default use preset E for the Performance, Quality, Balanced without any overrides. The "Ultra Performance" option will select preset F, however this will mean lowered graphics clarity so you will need to use DLSSTweaks to enable preset F for the "Quality" or other options. Update 24/01/25: DLSS 4 and Preset J: DLSS 4 just became available along with the new J preset. Tried and tested and so far seems awesome. See my comment linked here for instructions and findings. Update 30/01/25: DLSS Swapper: The recent release of DLSS Swapper (use the v1.1.2 version or later) now supports manually adding game folders. You can add the top level DCS installation folder and this will now automatically replace the nvngx_dlss.dll file in the bin and bin-mt folders. You can confirm this by hovering your mouse over the dll files and verifying that the tooltip displays the correct version number. Update 31/01/25: The latest DLSSTweaks release now supports setting presets J and K in the Nvidia Global Profile. This also contains a fix to prevent crashes when using the dxgi.dll wrapper approach. The latest DLSS 310.2.1.0 library now supports preset K NOW AVAILABLE!!!: The latest DLSS dll is now available in DCS and presets can be configured. Add the below line to your C:\Users\username\Saved Games\DCS\Config\autoexec.cfg file to set the DLSS preset, this is still C by default. You will need to create this file if it does not already exist. DLSS_Preset = 'K' You can add this line as well if you don’t want DLSS applied to MFDs and HUD to keep them sharp with no ghosting for greater control. HUD_MFD_after_DLSS = true

@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.