Monash

I feel pretty foolish. After reading the old thread I turned off OpenXR Toolkit and now the problem appears to be resolved. I really should have thought of this obvious possibility before reinstalling! Going to reinstall the modules and hope the fix remains. Cheers everyone.

I have removed DCS and the Saved Game folder and reinstalled just the base game, no mods, no additional modulus. I have confirmed power saving mode is off for all USB controllers in device manager. The problem is still there. Going to dig into the suggestions in the other thread and see if anything there works. Thanks all for your suggestions.

Thanks, I will try these. Bit embarrassed I missed that earlier post.

That would be tremendously helpful. Thank you!

Understood. I'll give it a try. All drives are SSD. PS. I'm experiencing other VR related issues with DCS, probably related to the recent updates to Oculus Link. As a result, I'm going to step away from this for while. Thanks to everyone who replied with helpful suggestions.

Hi Bignewy, Yes I saw the same thing. I'm staggeringly ignorant about all this stuff, but I can observe that (1) all these problems arose with updates to the Oculus Link software and (2) the log file seems to be point to an error that looks suspiciously like something the Oculus software should be handling. So probably an Meta problem, not a DCS problem. Which means I'm out of luck I guess. Monash

My DCS installation is on drive D. My Saved Games/DCS folder is on drive C. Do I need to set the pagefile to 32 GB for drive C, D, or both?

As the title says: If I am in a mission and I remove my quest 3 headset or simply just raise it up see out, then DCS will immediately freeze and, after 10-20 seconds, crash to desktop. It did not do this before. I do not experience this issue in IL-2 (opencomposite) or Falcon BMS (OpenXR). PS. It is not the headset going to sleep. PPS. I just updated the oculus link software today. dcs.log

Hi Silverdevil The mission will eventually load most of the the time, but can take up to 10 minutes more or less. It is highly variable and can be reasonably quick one time then exceedingly slow the next time. The DCS folder is excluded from my AV software. The DCS folder in Saved Games is not excluded. I've added this to the list of exclusions, but loading times seem unaffected by the change. I have repaired (fast and slow) multiple times. I've deleted and reinstalled the entire Syria map.

I have been experiencing very long (5 to 10 minute) startup times for missions in DCS in VR (Quest3+Link cable). The main menu appears quite quickly, but loading up an instant action mission takes forever. As part of trying to trouble shoot this I submitted my DCS log to an AI and asked it to suggest a cause for this issue. It raised many issues, but key was the following ERROR: 2025-05-12 17:13:55.993 ERROR EDCORE (Main): No suitable driver found to mount mods/terrains/syria/assets/assetstextures.zip There is no such file on my PC at the indicated location. There is however a file called "AssetsTextures.summer.zip". I have reinstalled the Syria map. I have deleted (& backed up) the DCS folder in saved games. I have no mods installed. Can someone shed some light on this problem. I've upload the entire log file in case it is useful. EDIT: I just realised I forgot to change the graphics settings after deleting the DCS saved games folder. They are set to high for VR and that will be reflected in the attached log file. However, that is not the key issue as the problem of extreme loading time (and the strange attempt to "mount" a non-existent file) persists after I set much lower graphics settings. dcs.log

Hello Ozone Thanks for following up. I have "solved" this issue by recognising that changing bindings in the UI layer can affect existing bindings for modules. I'll admit to not fully understanding the issue, but since I really only wanted to map one key (pause/break) from the UI Layer, and now it seems to be working, I'm leaving well enough alone. Thanks for the tip about how to backup the input folder. Cheers, Monash

A solution appears to be to delete the following file: DCS World OpenBeta\Mods\aircraft\Ka-50_3\Input\ka-50_3\joystick\Joystick - HOTAS Warthog.diff.lua. This fix is suggested in the following forum thread:

This sounds just like the issue I was having and posted about here: EDIT The link posted by Insonia suggests deleting the file "Joystick - HOTAS Warthog.diff.lua" saved in DCS World OpenBeta\Mods\aircraft\Ka-50_3\Input\ka-50_3\joystick. This seems to have fixed the issue! Thank you Insonia. I hope it works for you too. Monash.

Thank you for trying. I'll contact support.

Hi Flappie, I think you might have missed my post from 7:43 AM yesterday when I describe how I have already tried what you suggest. I renamed the Saved Games/DCS.openbeta folder to DCS.openbeta.OLD and launched DCS. This didn't fix the issue. I followed this up with a complete re-installation of DCS. The trimmer still does not work.