sleighzy

Install this tool and drop a screenshot here of your OpenXR layers that it shows https://github.com/fredemmott/OpenXR-API-Layers-GUI Drop a DCS log file here as well for review. It will be in your Saved Games\DCS\Logs directory. Needs to be a log file containing a crash from this. It may just be that you have multiple OpenXR layers and they need to be reordered, or something else conflicting. The tool can be used to reorder the layers, or disable/enable them.

You are not running the multithreaded version of DCS, this is using ST (and has also two params which are incorrect). Because you are are using Steam you must launch the game from with your Steam client library, and you must choose the Play MT Preview option. Also remove those -force_enable_VR and -force_OpenXR params. They are not required as OpenXR is the default for the multithreaded version. When the game starts you should see the text MULTITHREADED PREVIEW at the bottom of the menu in the game if you have done this correctly.

What version of Reshade? (Install the version with Addon support as it will make it easier to sync with VR). Did it present a screen for selecting shaders (with a couple selected) during the installation process? Did it create a reshade-shaders folder in your DCS bin-mt dir, as well as a ReShadePresets.ini file? Do you get a ReShade.log file created in the bin-mt dir when DCS loads into the game? Anything in there? Tried hitting the Home button from within DCS to see if the menu comes up? And probably a stupid question, but you’re definitely running the MT version aye? (Shows the MULTITHREAD PREVIEW text at the bottom of the menu).

In your DCS control settings make sure you’ve disabled hot plug so DCS isn’t constantly scanning for new devices.

Does it crash, or just not complete loading? Don't see a crash in the logs. One thing you could try is to rename your C:\Users\<user name>\Saved Games\DCS folder to DCS.old and then try again. A new one will be created when the game starts, and as you have renamed and not deleted the old one you can still copy back your config, keybinds etc. if it works. It may be a corruption, but hard to tell, so could be worth a quick shot.

I’ve looked at most of the log files attached to the comments in this post. Almost half of them have the OH6 gunner mod. This is known to have a performance issue. Try removing that and seeing if it has any impact. If unsure search in your logs for the text “gunner_export_hook.lua”.

Unrelated, however running the bin-mt\DCS.exe file on the Steam version will still run the ST version. For the Steam version you have to launch the game from within your Stem library and choose the Play MT Preview option for it to use the multithreaded (MT) version. The next DCS patch will however be removing ST so hopefully shouldn’t be a problem going forward.

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