sleighzy

If you have Quad-Views-Foveated installed you now need to enable the Quad Views option in the DCS VR settings, it looks like it’s off in your screenshots. Can you also attach a DCS log file from when you are experiencing this issue.

For the simplified version don't copy any files into "bin" or "bin-mt". This is only required for manual config file changes, if you have stuff in there then it may be overriding the global profile settings (I haven't confirmed this). You only need to run the DLSSTweaksConfig.exe tool for the Nvidia Global settings, no need for extra dlls and ini files, so just go ahead and remove those. When you ran DLSSTweaksConfig and changed the Global preset to F (and the GlobalHudOverride to "Enabled (all DLLs)" and then clicked the Save button did it pop up a message stating that you needed to be an administrative user and when you clicked Ok it closed and then reopened DLSSTweaksConfig, and then you were able to update those settings and click Save again? You need to restart DCS after these changes. The HUD overlay is also only displayed when actually in the plane, not at the main menu. null The "nvngx_dlss.dll" is the one that ships with DCS and is the Nvidia DLSS library file. You can update this to a later version if you like, but this is unrelated to the "dxgi.dll" file. You only need to worry about the "dxgi.dll" file if you are doing manual config, i.e. dropping dll files and ini config files into the bin and bin-mt dirs. DLSSTweaks comes with an nvngx.dll file, so if using the manual approach this is the file you would drop into bin and bin-mt and then rename to dxgi.dll. The reason for renaming that from nvngx.dll to dxgi.dll is that a few DCS patches ago is that the DLSSTweaks stuff stopped working, renaming that file fixed this. You also won't get a log file when using the Global Profile setting approach. This is because it is not using the dxgi.dll (renamed from nvngx.dll) file, which is what produces the log file. You will need to use the HUD overlay to verify it is working, you can turn this off afterwards. Hope that helps, let me know if this still isn't working for you.

Start DCS completely (not just the launcher) and verify that your C:\Users\user\AppData\Local\Quad-Views-Foveated\Quad-Views-Foveated.log file shows your expected settings and the pixel savings it's giving you. If not then drop your DCS log file here, as well as your C:\Users\username\AppData\Local\Quad-Views-Foveated\settings.cfg file.

OpenXR Toolkit is not compatible with Quad Views (only if you "hack" around it by installing the Quad-Views-Foveated API layer). This is because enabling Quad Views ensures that DCS sends 4 views (if requested by the runtime or an API layer), however OXRTK only supports the normal 2 views. You can drop a DCS log file here for confirmation that it isn't something else.

Yes, DCS is in the Steam library, but you're not forced to use their OpenXR runtime. With an Oculus headset you should use the Meta OpenXR runtime as it has less overhead. Using the Standalone version of DCS (the one from the ED website) is better as well (like you pointed out) as you also get free trials of planes and apps, as well as ED miles on purchases to go towards buying other modules.

Warning can be ignored, it just lists your available API layers. Looks like you have Quad Views in that list so should be all good. As long as it’s visible and ticked in the in-game menu (not just the launcher), then it should work fine. I’d put back the Mbucchia one now as the Sandbox version isn’t needed anymore.

Quad Views will only be available, and selectable, within the in-game menu if you have Quad-Views-Foveated installed (or an OpenXR runtime that natively supports this, eg PimaxPlay). The reason this shows up in the launcher is because it doesn’t check if this is present. Even if your friend sees it and can turn it on in the launcher it won’t do anything without QVF being installed. Also the launcher doesn’t hog resources, it just restarts DCS so I’m not sure where that information came from.

The dxdiag report shows that of the last 10 crashes, 4 of them were for "pppd.exe" (internet says this is for your UPS software, so something with the power supply?). There are another 3 for "fsx.exe", so I'm assuming you're using Microsoft Flight Simulator X as well? Do you experience any crashing issues with that too? The final 3 are StoreAgentScanForUpdatesFailure0 which can be related to a few different reasons, including issues with software and corrupted system files. Can you open a command prompt as an administrator and run the below two commands as well to confirm whether or not there are issues and they get fixed. dism /online /cleanup-image /restorehealth sfc /scannow

Not sure what you mean by "steam link". You shouldn't be connecting using SteamLink if connected via cable, just connect your cable and then use the Meta link app with it set to be the default OpenXR runtime if you haven't already. You can drop a DCS log here for reviewing your settings. Drop some screenshots of your Meta link app as well, e.g. what your resolution slider is set to.

This looks like a double-posting of

You're applying resolution multipliers in two different places so may effect things as well, e.g. multiplying things multiple times. Will also cause both GPU and CPU load (QVFR is gonna be more CPU load). Could try dropping the Quest to 1.0 and then bumping up higher in QVFR instead. YMMV. (...my comment above may be a little off-topic for this thread)

Yeah, drop your settings and see if this changes anything. I also ran your log through the DCS log analyzer which only highlighted the following items: drop your preload radius to 60000 change your custom page file to have initial and max values set to 32768 (looks like currently 12288), you should only have one page file on the PC and on your fastest SSD (with at least 10% free space) enable Full Screen mode

This is just a log from opening the launcher. Start the actual game, fly around a bit for the stutters, and then drop an updated log file in here. You also don’t need the “—force_enable_VR” and “—force_OpenXR” parameters on your shortcut.

Yuuurp. I think a bunch of people (myself included) have gone "wow, that's amazing, I definitely wanna do that"... then after 5 minutes of it we realise it's janky as hell and get the mouse out again.

One thing I note in the log, not saying it's the issue, is a few problems around the F14, including messages that it is a different version than the latest build. Can you remove all custom mods from your game, (including the lottafGameGUI.lua from your Scripts/Hooks directory which I'm not familiar with), and then run a slow repair. Delete your fxo and metashaders2 caches from the Saved Games\DCS folder as well, and then see if you can replicate this issue. If this continues to crash can you also run the Windows dxdiag tool, save the report, and attach here as well, along with the latest log.

Classic IT. Have you turned it off and back on again?

Another option is to install the Standalone version of DCS on your new drive. This will give you things such as 2 week free trials of planes and maps, as well as ED miles to go towards purchases of other planes/maps. Any modules that you have purchased on Steam can be transferred to Standalone. Just download the DCS installer from the web site and run it. It should attempt to find an existing Steam installation and copy the files from there so you don't have to do a full download.

The default preset for DCS is C. The default preset for the DLSS 3.7 library is E these days if an application does not set this. However it appears that DCS does actually set to this to C (you can see this when enabling the debug overlay), which at the time was the recommended preset for Performance/Balanced/Quality options.

No reaction in the Discord server?

Try removing your previous firewall rules for DCS and then start the server again so that it asks you if you wish to add rules for it. It’s been mentioned that with the latest patches that DCS will now run the DCS.exe in the bin directly, was previously bin-mt, now that everything is multithreaded and that firewall rules need to updated for the new executable. Give it a shot anyway.

This is out of beta and is available in the current v1.33 release.

Do you also have hand tracking enabled for your Quest, eg developer mode enabled and hand tracking working?

Are you looking at the settings in the launcher, or under the VR tab within the DCS game itself while wearing your headset?

It happens in a layer before it even reaches your OpenXR runtime or headset, so yes this should work for that.

DCS supports OpenXR runtimes and not specific headsets. So, as long as your headset has an OpenXR runtime for it then you should be all good.