sleighzy

Given the way that Quad Views works (it's generating 4 views each frame vs 2) it is doing significantly more things than just the turbo mode. This puts more load on your CPU hence why you may be getting micro-stutters depending on where your bottleneck is.

No worries. Just had noted the install instructions had a different folder name, but looks like maybe they're out of date. I downloaded and checked it and appears unzipped it matches what I would have expected from a mod, i.e. this is the contents of that folder. So yes, still a mystery, sorry I don't have an exact answer for you at the moment.

VirtualDesktop can be more performant than Quest Link (it has a lot smaller overhead for VRAM) for a lot of folk, and is less prone to the issues you can get with Quest Link app at times. Easier to setup and configure items, more encode options, and has additional features like pass through for bringing things into your VR environment.

Are you slaving and/or unslaving George at the time this occurs? Your log errors seem to be identical to the same ones reported by myself and others on other forum posts with slaving and unslaving George causing crashes in campaigns. This started occurring after the latest patch. In particular this one:

So DCS is installed under "E:\DCS World" then? What's inside that "RAF_M2000D_V1_PUBLIC RELEASE" folder in the "E:\DCS MOD" folder?

I don't know if related at all but there are some really long loading times taking place here as well. From the below log snippet there's a 5-7 minute gap (goes from 08:41:50 to 08:43:21 and then to 08:48:37). 2024-12-28 08:41:50.469 INFO EDTERRAINGRAPHICS41 (8900): instancer factors has been changed. Update lod buffers. 2024-12-28 08:41:50.469 INFO EDTERRAINGRAPHICS41 (8900): distanceFactor = 1.000000 2024-12-28 08:41:50.469 INFO EDTERRAINGRAPHICS41 (8900): instancerDetailsFactor = 1.000000 2024-12-28 08:41:50.469 INFO EDTERRAINGRAPHICS41 (8900): forestDistanceFactor = 0.440000 2024-12-28 08:41:50.469 INFO EDTERRAINGRAPHICS41 (8900): forestDetailsFactor = 0.530000 2024-12-28 08:41:50.752 ERROR_ONCE DX11BACKEND (4896): texture 'f-5e3_cockpit_normal.bmp' not found. Asked from '' 2024-12-28 08:41:50.752 ERROR_ONCE DX11BACKEND (4896): texture 'f-5e3_cockpit_spec.bmp' not found. Asked from '' 2024-12-28 08:43:21.848 WARNING BACKENDCOMMON (10260): Need to reprocess [DDS] image '/textures/F18C_1_DIFF_STAY_nm.dds'. Reason: Conversion requires - expanded pixel size, setting alpha to known value. Source is an 8:8:8 (24bpp) format 2024-12-28 08:48:37.800 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED Do you get long loading times in those other instant action missions as well, e.g. these should only take 1+ min? Is DCS on a fast SSD? Can you, if you haven't already, try adding an exclusion to your anti-virus software for both the entire DCS installation folder, and your entire Saved Games\DCS folder, restart your PC, and then try again. Just curious if there is long times being taken loading stuff if anti-virus is scanning these as well.

Is this also the Mirage 2000D mod you installed, and followed the PDF installation tutorial on that mod website for installing it via OVGMe? https://splitair-dcs.com/language/en/downloads/?lang=en Not sure I understand, you said when you installed the mod that DCS vanished from your computer? But in this comment you say the mod does not show up in the game.

Please post screenshots of your OVGMe config, and the directory location of where DCS is supposed to be installed based on right clicking the DCS shortcut and selecting properties to see what the target is. Send a screenshot of the mods folder you unzipped this mod into, and the top-level folder structure of the unzipped mod What happens when you disable the mod again in OVGMe?

Me too. Only occurred once, late into one of the missions of the MAD campaign (I had been slaving/unslaving fine within this mission prior to the crash).

This is likely a duplicate of this issue which has been reported by a number of folk: Drop your logs on that one as well.

This is likely a duplicate of this issue: Please attach your logs (and crash zip if one available) to that other post from when this has occurred.

Same issue here on the DCS MAD AH-64 campaign on the Persian Gulf map. Same errors for the George slaving sound files (although do recall hearing "Slaving" "Deslaving" in the game so is getting those sounds from somewhere). 2024-12-29 04:06:01.697 ERROR ED_SOUND (10524): can't load wave: "speech/eng/ah-64d/george_cpg/slavin.ogg" ... 2024-12-29 04:08:39.700 ERROR ED_SOUND (10524): can't load wave: "speech/eng/ah-64d/george_cpg/deslavin.ogg" Log snippet of crash showing consistency with the others in this thread (full log is attached): 2024-12-29 04:13:04.041 INFO EDCORE (Main): try to write dump information 2024-12-29 04:13:04.129 INFO EDCORE (Main): # -------------- 20241229-041304 -------------- 2024-12-29 04:13:04.130 INFO EDCORE (Main): DCS/2.9.11.4686 (x86_64; MT; Windows NT 10.0.26100) 2024-12-29 04:13:04.131 INFO EDCORE (Main): G:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AH-64D\bin\AH64D.dll 2024-12-29 04:13:04.132 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ffac97e375c 00:00000000 2024-12-29 04:13:04.133 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'G:\Eagle Dynamics\DCS World OpenBeta\bin;', symOptions: 532, UserName: 'simonl' 2024-12-29 04:13:04.134 INFO EDCORE (Main): OS-Version: 10.0.26100 () 0x100-0x1 2024-12-29 04:13:04.134 INFO EDCORE (Main): 0x000000000045375c (AH64D): ExternalFM::AH64::AH64FM::setImmortal + 0x1D3C 2024-12-29 04:13:04.135 INFO EDCORE (Main): 0x0000000000453a24 (AH64D): ExternalFM::AH64::AH64FM::setImmortal + 0x2004 2024-12-29 04:13:04.136 INFO EDCORE (Main): 0x0000000000442c07 (AH64D): ExternalFM::AH64::AH64FM::getSensorsSystem + 0xB7B7 2024-12-29 04:13:04.136 INFO EDCORE (Main): 0x000000000000e2e0 (edObjects): Evoker<LandObjectDestroyNotifierBase,Link<LandObjectDestroyNotifierBase> >::onStartEvoke + 0xD0 2024-12-29 04:13:04.136 INFO EDCORE (Main): 0x0000000000011412 (edObjects): viSearch::TestAndInsert + 0x52 2024-12-29 04:13:04.136 INFO EDCORE (Main): 0x000000000001d528 (edObjects): DamageInfo::GetDamager + 0x15A8 2024-12-29 04:13:04.136 INFO EDCORE (Main): 0x000000000001d5fe (edObjects): DamageInfo::GetDamager + 0x167E 2024-12-29 04:13:04.137 WARNING LOG (20428): 15 duplicate message(s) skipped. 2024-12-29 04:13:04.137 INFO EDCORE (Main): 0x000000000000b77f (edObjects): viObjectManager::GetObjects + 0x9F 2024-12-29 04:13:04.137 INFO EDCORE (Main): 0x000000000000c1fb (edObjects): viObjectManager::GetSegmentList + 0x9CB 2024-12-29 04:13:04.138 INFO EDCORE (Main): 0x000000000045b3a8 (AH64D): ExternalFM::AH64::AH64FM::setImmortal + 0x9988 2024-12-29 04:13:04.138 INFO EDCORE (Main): 0x000000000045cb7b (AH64D): ExternalFM::AH64::AH64FM::setImmortal + 0xB15B 2024-12-29 04:13:04.138 INFO EDCORE (Main): 0x000000000046015f (AH64D): ExternalFM::AH64::AH64FM::setImmortal + 0xE73F 2024-12-29 04:13:04.138 INFO EDCORE (Main): 0x000000000021f70e (CockpitBase): cockpit::avDevice_BasicTimer::NextEvent + 0x1E 2024-12-29 04:13:04.138 INFO EDCORE (Main): 0x00000000000045eb (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x3EB 2024-12-29 04:13:04.138 INFO EDCORE (Main): 0x0000000000004c12 (World): wSimCalendar::DoActionsUntil + 0x262 2024-12-29 04:13:04.138 INFO EDCORE (Main): 0x000000000091459a (DCS): SW + 0x427ACA 2024-12-29 04:13:04.138 INFO EDCORE (Main): 0x0000000000914271 (DCS): SW + 0x4277A1 2024-12-29 04:13:04.138 INFO EDCORE (Main): 0x0000000000939b72 (DCS): SW + 0x44D0A2 2024-12-29 04:13:04.138 INFO EDCORE (Main): 0x00000000008f3fb4 (DCS): SW + 0x4074E4 2024-12-29 04:13:04.138 INFO EDCORE (Main): 0x00000000008f56e3 (DCS): SW + 0x408C13 2024-12-29 04:13:04.138 INFO EDCORE (Main): 0x0000000002265047 (DCS): AmdPowerXpressRequestHighPerformance + 0x11D2043 2024-12-29 04:13:04.138 INFO EDCORE (Main): 0x0000000000cd4182 (DCS): SW + 0x7E76B2 2024-12-29 04:13:04.138 INFO EDCORE (Main): 0x000000000002e8d7 (KERNEL32): BaseThreadInitThunk + 0x17 2024-12-29 04:13:04.360 INFO EDCORE (Main): Minidump created. 2024-12-29 04:13:04.360 INFO Lua::Config (Main): stack traceback: 2024-12-29 04:13:04.364 WARNING LOG (20428): 3 duplicate message(s) skipped. Yes, there are a couple of mods mentioned there, I will need to retest with those removed. However, this was fine prior to the most recent patch, and my log has the same stack trace and crash experienced as others on this thread so I'm assuming that the mods are unrelated. dcs.log

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/