sleighzy

For anybody else coming here. You don't need to update registry keys manually. Install this tool and it will list all OpenXR API layers that you currently have, along with the ability to enable/disable them for troubleshooting purposes, or remove them completely. https://github.com/fredemmott/OpenXR-API-Layers-GUI

I don't know what your fps is, but if dropping to 72 Hz means that you're now able to meet that refresh rate within the game then it's possible that ASW (Meta Quest's motion-smoothing) isn't kicking in now. If you can't meet the refresh rate, e.g. previously 90 Hz, then ASW will cut your frames in half and inject "fake" frames which can cause some artifacting (may look like a bit like ghosting in the game).

Did you select "F" for the global nvidia option, or "F" for all the individual preset options? If global then yeah, the nvngx.dll rename probably not needed as it won't look at that.

Preset E was the shiny new one that was introduced in DLSS 3.7 as the default for games. I'm a VR user and have tried both, but honestly couldn't say which was better than the other. Would be curious how people find E vs. F, especially with higher end headsets or 2D, as to whether or not one is noticeably better than the other to get some more informed decisions if this was to be changed within the game permanently. Some internet comments are that E is smoother than F, although the ones I've run across are for 2D and games other than DCS.

The DLAA preset? That I don't know sorry. The debug overlay only shows preset C as the default, even when I'm using DLAA, so I'm presuming this information is based on DLSS. Various comments on the internet (not everything can be believed of course) is that the standard defaults for the library prior to 3.7 (not saying that this is what DCS does, but may be why it is C for historical reasons ) are F for DLAA and C for DLSS. The DLSS default changed to E in DLSS 3.7, unless being set to something different by the game. I'll drop an update if I find anything further out.

You can extract it to the bin-mt folder if you just want to just have it wrap DCS and apply settings for DCS only (note you'll need to rename the `nvngx.dll` to `dxgi.dll`). Otherwise, yes, just extract to your desktop and use the second approach. No, don't need to run each time, the exe file is just used to update the config in the .ini file. Only need to run again if you're wanting to play with other settings, e.g. try preset F and then update it to try with preset E, or play with DLAA instead.

Another alternative is the Moving Map from the DCS Web Editor. It's essentially a dynamic view of the F10 map that can be displayed in a browser, so you can use another monitor, phone, iPad etc. to have it always visible. You can also integrate it with OpenKneeboard to have it brought up as a kneeboard within the game via keybind, or for VR just glance at it.

Not so far as I'm aware, the two are independent of each other. One thing you can do with OpenKneeboard though is combine it with the Moving Map from the DCS Web Editor. This means you have a realtime moving map (essentially replacing the F10 map) as one of the pages in the kneeboard so you can glance at it whenever you need it. Youtube vid (shown for VR but can be used in 2D as well, you can also display it on another monitor or phone/iPad etc. if you want)

For folk choosing to use DLSS/DLAA see my post re: modifying the preset used, i.e. overriding the preset of C that DCS sets by default to reduce the ghosting that you can get. I've updated that post for simplified instructions to update this in your global Nvidia profile.

You only see additional options for the VR controllers when actually viewing the settings from within VR.

You can still use your shortcut for the updater (this is what the default shortcut for DCS is) as by default this will now start the MT version. A separate shortcut to the bin-mt\DCS.exe file is not needed.

Issues with the map normally mean you’re running the ST version and not the multithreaded version (MT). Ensure that you chose the Play MT Preview option when launching the game in your Steam library. You should see the text MULTITHREADED PREVIEW at the bottom of the main menu when DCS has loaded.

@WipeUout Your custom QVF settings under the [app:DCS World] section you posted earlier may possibly no longer be being applied. You can check your QVF log file while starting DCS to double-check. DCS changed the app name to "DCS" a little while ago so it might not be finding a match for that. Check your log to confirm, and then test again using [app:DCS] as the section name and see if that produces a different result.

Just a heads-up that you shouldn’t use that tool unless you’re using an eye-tracking headset, for fixed foveated custom config (which should be provided in your own custom file) this will be overwritten any time you click the apply button in that app. The config docs also mentioning adding custom config to a section named [app:DCS World] if you only want them to apply to DCS. This is not accurate anymore based on my testing as DCS recently changed its process name from “DCS World” to “DCS” so would need to be [app:DCS] instead. Not a big deal, if like me, you’re are just config’ing “global” settings in the custom config file.

Just a heads-up that you shouldn’t use that tool unless you’re using an eye-tracking headset, for fixed foveated custom config (which should be provided in your own custom file) this will be overwritten any time you click the apply button in that app.

Yeah sounds about right. Same thing somebody highlighted in another post on this problem

I've updated the instructions for using DLSSTweaks to set this preset globally in the Nvidia global profile. Removes a number of steps for placing updated dll and ini file in the DCS\bin-mt directory. Note, the preset will apply to all DLSS games if this approach is taken, and not all additional fine-grained config will be possible. Not a big deal when looking to achieve these results in DCS.

Thanks for that, I'll see if I can find it again, previous references had been modifying XML files for it. The DLSSTweaksConfig tool provides an option in that screen as well for updating the Nvidia Global Profile to use the preset across everything. I'll have to give this a go to confirm, but at least simplifies the config (as long as folk don't care about it applying to every game).

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: