sleighzy

Looking at your DxDiag.txt file I see the following: 4 occurrences of LiveKernelEvent with code 141. This is a hardware failure, generally the video card or power. Good article here with further explanation and areas of investigation: https://answers.microsoft.com/en-us/windows/forum/all/livekernelevent-141-when-playing-games/4485bdee-bb9f-4ef9-97a4-6c1fe5a14ce4#:~:text=The LiveKernelEvent 141 error is,the graphics card or power. 2 occurrences of BlueScreen with code 161. Also indicative of video card issue: Further article here on both error code and the one above in combo: https://answers.microsoft.com/en-us/windows/forum/all/windows-shutting-down-unexpectedly-with-bluescreen/e0bbc619-8689-4f0b-9a01-a3dab29ed01d 3 occurrences of StoreAgentDownloadFailure1. I haven't looked into this one. Let's see whether or not you get further crashes after updating that graphics driver if that is the cause. I also dropped your log file into the DCS log analyser which had further performance tuning advice: Enable Full Screen mode. Turn off SSAO. Turn off SSLR. Set Water to Medium or Low. Set Shadows to Medium. Turn down Anisotropic Filtering. Disable civil traffic. SSAO and SSLR can be performance hits with next to no benefit so advise to just turn off. Just a heads up, I'm not part of the ED team, I'm just another community user who enjoys the game and helps folk troubleshoot problems that crop up (a lot of them are common issues).

Provide your DCS log file regardless, prior to restarting the game. Run the Windows dxdiag tool, save the report and attach it here. This will show the last 10 crashes in your system and the associated processes, codes, etc. You can provide this now. You can also run the following commands to check for, and repair, possible system issues. Open a command prompt (cmd.exe) as Administrator and run each command individually and then restart your PC. dism /online /cleanup-image /restorehealth sfc /scannow

Obviously you're still waiting for screenshots etc. of his OpenXR tools for Windows Mixed Reality config, but just a heads-up that based on the log DCS is attempting to use the WMR runtime if that's helpful. Instance RuntimeName=Windows Mixed Reality Runtime RuntimeVersion=113.2405.31001

Random question, do you use the clickable cockpit mod?

No, games will load the dll that they have in their installation. GeForce Experience can automatically update the dll for registered games, which will replace the dll, but DCS is not one of these. Having the updated driver does not mean that all games will be using the new DLSS version. You can easily test this by enabling the (via DLSSTweaks) the debug overlay and you will see that you're still using the older version and preset.

Yeah if you don’t replace it you won’t be using the new DLSS 3.8.10 version.

Does this mean that other games are great in Reverb, just DCS doesn't work? What games do work? What do you mean by 3D cockpit lookaround view, do you mean DCS in VR headset so you can look around? In your mouse software try setting the polling rate (this is polling rate and not DPI) to 500 or less. What shortcuts are you referring to? What tutorials? Your screenshot of your DCS VR settings does show that the "Enable Virtual Reality Headset" box is ticked. Can you attach a DCS log file for when this occurs. This issue would probably effect 2D as well but install this (choose the repair option if it's already installed) https://aka.ms/vs/17/release/vc_redist.x64.exe Internet should not effect this. To be honest, I don't know what root cause is (attach a log of that failure), but it may just be what others have said...your PC (video card) doesn't support this.

In DLSSTweaksConfig app just disable the GlobalHudOverride setting. It’ll be “Enabled (all dlls)” currently if it’s showing you that debug overlay in the game. You only need that if you’re wanting to confirm that it’s working properly.

To finish answering all your questions. If you do want to use DLLTweaks, i.e. you don't want to use the new dll and get this for free, or if you want to try preset F but on the DCS "Quality" option with the new dll, then follow the 3 steps of the simplified instructions (the second part of my original post) to update the Global Nvidia Profile config using DLSSTweaks No need to put anything in the game folder for DLSSTweaks. Just run the DLSSTweaksConfig.exe file from where ever you downloaded it to. Doesn't need to be launched each time, it's going to update the Nvidia config for your PC so will apply to everything.

Nothing has changed in DCS. If you don't want to use DLSSTweaks you'll need to replace the bin\nvngx_dlss.dll and bin-mt\nvngx_dlss.dll files with the latest 3.8.10 version found here: https://www.techpowerup.com/download/nvidia-dlss-dll/ Don't bother with selecting "Ultra Performance" at this stage. Whilst it will use preset F (if using the new dll) I imagine it will lose some visual aspects vs. the "Quality" option. I need to retest both options to see just how different they are.

Quest 3. Pancake lenses will always be better than fresnel lenses for a start. Even though the PSVR2 one says it has eye-tracking this is not implemented and does not work in DCS. Wifi streaming is also good as you may end up using Virtual Desktop vs. cable and the Meta app at some stage. Foveated Rendering is also supported with DCS even though the comparison linked above says that it doesn't and requires an eye-tracked headset. You can (like many of us) use Quad-Views-Foveated which will use Fixed Foveated Rendering for non-eyetracked headsets. Ability to use passthrough so you can bring outside things into your VR world.

I see you have the Virtual Desktop API layer extension in your log but you are using the Meta link app. Does this same problem happen in Virtual Desktop? Are you connected via cable or using Airlink? Do you use the Oculus Tray Tool or Oculus Debug Tool? Drop screenshots of the settings for those, as well as the Meta app, in here as well. I dropped your log file into the DCS log analyser which had the following to say: Enable Full Screen mode. Set Preload Radius to max. 60000. Disable civil traffic. Consider using TAA instead of MSAA. Also as you only have 32gb of RAM you should add a custom page file. At a custom page file with Initial and Max values of 32768 and click Set, Apply, and restart your PC. Make sure that the page file is on your fastest SSD and that you remove any other page files, e.g. the log indicates you have a standard Windows system managed one.

The cef_log.log may just be related to the new launcher. You could test this by disabling the launcher under the Misc settings in the DCS menu, remove the cef_log.log file and see if it is recreated when you start the game. I also dropped your dcs.log file into the DCS log analyser which had the following to say: Enable Full Screen mode. Set Water to Medium or Low. Turn down Anisotropic Filtering. Set Shadows to Medium.

And just to confirm, you’ve replaced the nvngx_dlss.dll file in the DCS bin and bin-mt directories with the new one? I don’t use Ultra Performance (only looked at it once for testing purposes and did not like it).

Nah, my comment edit came out a bit weird. Both E and F will reduce ghosting. Ultra performance is going to lose quality/clarity (even though maybe still reducing ghosting). Stick with Quality (or whatever you’re using). And you can just download the dll from here https://www.techpowerup.com/download/nvidia-dlss-dll/

If you have a look at my post here (look at the alternative solution of that post re: Nvidia Global Profile as is less steps) you can see how to use DLSSTweaks to easily turn on the debug overlay for DLSS. This overlay will show you the DLSS version as well as the preset that is currently used. Switching between the various DCS options will display the preset in use (shown once you're in your plane).

This log file isn't from launching in VR so it's hard to tell. What I do see (and confirmed by the DCS log analyser) is that you have 32Gb of RAM (excluding your page file but that will be slower) and your preload radius is 150,000. Recommendation is to drop to 60,000. The preload radius is causing a lot of the map etc. to be loaded all at once (unnecessarily) which may explain this.

Selecting the "Ultra Performance" option in the DCS dropdown will set preset F.

DCS will use preset E for Performance, Balanced, Quality. The "Ultra Performance" option in the dropdown will set preset F.

A lot of us VR users use DLSSTweaks to override the default DCS preset of C to E or F, which drastically reduced ghosting. Now with DLSS 3.8.10 all other presets, except for E and F, have been removed. DCS is now using preset E with that new dll for Quality, Balanced, Performance. The "Ultra Performance" option in DCS will select the F preset. This means you get the reduced ghosting without needing to use DLSSTweaks.

Don't know. DCS was always using C if not overridden. I'd only honestly tried E and F if memory serves me correctly (in VR), and stuck with F at the time like a lot of folk. Were you using D?

@BIGNEWY, if DCS were to ship with this later version then my original post here for a request to change the preset would become redundant as we would get this for free. Thanks in advance.

Yup. This release removed all the presets except for E and F. DCS used to use C, but now this is defaulting to E. No more need to use DLSSTweaks to override the preset (unless you still want to use it for updating other values / debug overlay).

It should have picked them up, it reads from the same location, so don't know why if you were noticing large differences.

Your DxDiag file contains the last 10 system/process crashes: DCS (3 times) - you're aware of this one The Oculus Tray Tool (4 times) 3D Mark Speed Way Live Kernel Event (2 times) - these ones have an error code of 141 which can indicate a hardware issue (particularly GPU overclocks in some cases). Even if you're not applying an overclock the manufacturer of your card may have. I believe MSI Afterburner may be able to identify that and remove.