sleighzy

What anti-virus do you use? You should add an exclusion to your anti-virus software for the entire DCS installation folder and then restart your PC. It is taking 3 minutes alone for a single dll to be loaded. It then starts on the next dll but doesn't complete...presumably because you are ending this? See below where it starts loading the rwr.dll at 13:32:14 and doesn't finish until 13:35:42. There is something wrong with your system, try anti-virus exclusion first, for it to take this long. 2024-12-29 13:32:14.871 TRACE SECURITYCONTROL (Main): preCheckResource(mods/aircraft/f-4e/bin/rwr.dll, ) 2024-12-29 13:32:14.871 TRACE SECURITYCONTROL (27260): do_check_resource(mods/aircraft/f-4e/bin/rwr.dll, ) 2024-12-29 13:35:42.795 INFO EDCORE (Main): Loaded D:/Program Files/Eagle Dynamics/DCS World OpenBeta/Mods/aircraft/F-4E/bin/RWR.dll 2024-12-29 13:35:42.802 TRACE SECURITYCONTROL (Main): preCheckResource(mods/aircraft/f-4e/bin/lua51.dll, ) 2024-12-29 13:35:42.802 TRACE SECURITYCONTROL (27260): do_check_resource(mods/aircraft/f-4e/bin/lua51.dll, )

Based on reports this can occur when using the "Broken Preset 3" clouds setting. Try one of the other ones and see what happens.

@casserole The difference between those two logs is significant. The first play after virgin saved games contains no mods, however the restart one does. In addition to this the preload radius goes from 150000 to 90300. Are you sure you aren't doing something between those two actions? These are all your custom mods that it is trying to use after the restart: WW2 V1 German Rocket Launcher V1.3,UH-60L,Civil Aircraft Mod,DCS-SRS,VNAO_T45,ESCA-8ECV

@casserole Definitely drop the preload radius to 60000 as mentioned by @aceviper. In addition to this because your RAM is only 32Gb you should add a custom page file. Add a custom page with Initial and Max values of 32768. This must be on your fastest SSD, and remove any existing ones (there is a currently a tiny system managed one in use). Click Set, Apply, and restart your PC. Additional tuning tips from the DCS log analyser: Set Preload Radius to max. 60000. Set Water to Medium or Low. Enable Full Screen mode. Consider using TAA instead of MSAA.

Please raise a new issue. This post is about a VR issue and unrelated to yours.

Windows Defender, not Windows Defender Firewall as this has nothing to do with your firewall. Send a screenshot of your Windows Defender that shows the DCS installation folder as one of your excluded folders. https://support.microsoft.com/en-us/windows/add-an-exclusion-to-windows-security-811816c0-4dfd-af4a-47e4-c301afe13b26#ID0EBF=Windows_11

What anti-virus software do you use? Have you added the entire DCS installation folder as an exclusion to it, restarted your PC, and run a slow repair of the game?

It’s probably non-existent as your anti-virus software has probably quarantined it (or deleted). Have you added the entire DCS installation folder to your anti-virus software as an exclusion? What anti-virus software are you using?

Drop a DCS log file here after a crash has occurred. Will be C:\Users\username\Saved Games\DCS\Logs\dcs.log ... may just be a text document named "dcs" if your Windows is hiding file extensions). Run the Windows DxDiag tool as well, save the report, and drop that here too.

What Rudel_chw said. Once you've added the antivirus exclusion for the entire DCS installation folder, restart your PC, and then run a slow repair of the game.

Download the latest DLSS 3.8.10 (https://www.techpowerup.com/download/nvidia-dlss-dll/) and replace the nvngx_dlss.dll file in the DCS bin and bin-mt directories and this will remove some of the ghosting. The 3.8.10 version will use preset E by default, which is better than the current version in DCS. You can additionally try using preset F as well which may help further by using DLLSTweaks to update your Nvida Global Profile to force preset F. The steps for updating the preset in the Nvidia Global Profile can be found here: You could also try using Quad Views to increase the resolution (will push more of the load from your GPU to your CPU so will need to balance that) vs. the pixel density setting in DCS. Depending on your CPU this may offer you the increase in clarity with less performance drops than you're seeing right now. Have you also tried dropping your sharpening from 1.0 down to something like 0.6?

I've dropped your logs into the DCS log analyser which has the following to say for the crash: Your DCS has crashed. Errors Memory Timing Issues Remove any overclocking (XMP) from your RAM. There is a GPU-related error (Re-)install the latest GPU drivers. Don't overclock your GPU or RAM. The crash occurred inside dx11backend.dll. Try running a slow repair for the game including removing extra files. Delete C:\Users\username\Saved Games\DCS\fxo and metashaders2 and try again. Next, delete %LOCALAPPDATA%\TEMP\DCS and try again. Next, try renaming Saved Games\DCS to DCS.old and try again. In addition to this you only have 32Gb of RAM so you can create a custom page file to give you more headroom and reduce the chance of out-of-memory problems. Create a custom page file, just a single one on your fastest SSD, remove any system managed ones. Create it with Initial and Max values of 32768, click Set, Apply, and restart your PC. Additional tuning tips: Turn down Anisotropic Filtering. Set Water to Medium or Low. Enable Full Screen mode. Set Preload Radius to max. 60000. You currently have 150000 set for your preload radius which is really high for your RAM and you will be unnecessarily loading in a bunch of textures and other items when not required and may be redundant. Advice for Windows if not already done. Note that these are general items to help with performance and not to resolve your issue: Disable Game Mode Disable Hardware accelerated GPU scheduling Disable Core Isolation Disable Core Parking

Won't solve your overall problem, however if you download the latest DLSS 3.8.10 version and replace the nvngx_dlss.dll file in both the bin and bin-mt folders with that then it should reduce the ghosting. This is especially true of DLSS, but should apply to DLAA as well. https://www.techpowerup.com/download/nvidia-dlss-dll/

For an alternative map use the DCS Web Editor Moving Map. It’s a dynamic F10 map replacement. For VR this can be displayed within OpenKneeboard.

No. The DCS log will tell you that the Quad Views layer is there, but not if it is activated or not. You need to turn on Quad Views in DCS settings as to enable this. If you are using Mbucchia's QVF layer then you will need to check the "C:\Users\username\AppData\Local\Quad-Views-Foveated\Quad-Views-Foveated.log" file to verify this. This should display the settings that you have configured and the pixel savings it is giving you.

No, those line are common to all DCS VR launches regardless of the runtime used or whether or not Quad Views is used. EDIT: I see views 0-3 listed here so yes looks to be Quad Views with the calculated values for each of the 4 views. Other logs without Quad Views show only views 0-1. I'll retest mine with Quad View disabled to verify that mine also drops from 0-3 down to 0-1.

I've dropped your DCS log file into the DCS log analyser which has the below information. Note that this may not resolve your issue. Hot plug Events Disable hot plug in your DCS CONTROLS section, it's the button at the bottom right of the controls settings. If you plug in new controllers in the future you can click the "Scan devices" button. This will prevent DCS from constantly scanning for new USB devices, which can lead to stutters. Advice In Windows: Disable Game Mode Disable Hardware accelerated GPU scheduling Tuning Tips Disable civil traffic. Consider using DLAA. Errors Error attempt to index local 'accel' (a nil value) Line 69 Script C:\Users\game\Saved Games\DCS\Scripts\Export.lua Can you expand a little on "pausing and loading". Do you mean like lengthy stutters? How long are the pauses? After the initial take off does the game become smooth again, or this continues to happen throughout the flight? You could also drop your preload radius down as well, it's currently 100000. You could drop to 60000 so that it is loading less map and textures (possibly unnecessarily) into RAM when you first start. Have you also tried removing your custom mods, deleting your Saved Games\DCS\fxo and metashaders2 folders and seeing if this makes a difference?

There is apparently a fix in the latest v1.9.12 beta release for this you can download. Additional comment here re: config setting that can also be updated that may help: https://github.com/OpenKneeboard/OpenKneeboard/issues/658#issuecomment-2395163358

My humble apologies. I’d thought at the time that only Varjo and PimaxPlay had native support in their runtimes for Quad Views. So yes Somnium does too.

Numerous forum posts on this. Index controllers are still broken.

If you want to try Quad Views (may help you with performance but will also depend on your CPU as it increases the load there) then yes. You will also need to install https://github.com/mbucchia/Quad-Views-Foveated as well.

There are a few script errors to do with sounds, which may be related to your Echo19 mods. Remove all your custom mods and run a slow repair of the game. Delete your "Saved Games\DCS\fxo", "metashaders2", and "%LOCALAPPDATA%\TEMP\DCS" folders and try again. There is an OpenXR runtime crash message as well, although this is post the initial DCS crash in the log. I've also dropped your log into the DCS log analyser which has the following to say: Additional items: Set Preload Radius to max. 60000. Your preload radius is currently really high at 150000 for your RAM, and not necessary. Turn off SSLR. Turn off SSAO. Enable Full Screen mode. Consider using DLAA. In Windows: Disable Game Mode Disable Hardware accelerated GPU scheduling

You should probably be raising this as a new post. vs. adding to this one. However, try installing the latest version of the Microsoft C++ distributables, https://aka.ms/vs/17/release/vc_redist.x64.exe (which come from here https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170). Failing that remove all custom mods and run a slow repair of the game, or verify files if on Steam. A number of mods are now broken with later releases of DCS. If it still doesn't launch then upload your "C:\Users\username\Saved Games\DCS\Logs\dcs.log" file (may just be a text document named "dcs" if your Windows is hiding file extensions) here for review. This should probably be done as a new post.

Changes almost of them, except for the Horizontal focus size and Vertical focal size for non-eye tracked. Changing the sliders in the Companion app for those will update the "horizontal_focus_section" and "vertical_focus_section" values (for DFR), but not the "horizontal_fixed_section" and "vertical_fixed_section" values needed for FFR. EDIT: sorry, saw you just responded with an edit as I was writing this. All good.

Just a heads-up that changing the focal areas in the Companion app only works for eye-tracked headsets. The config file needs to updated manually for the horizontal_fixed_section and vertical_fixed_section values to change these on non-eye tracked headsets. Saving any changes in the Companion app will also overwrite those.