sleighzy

Need an actual DCS log file for when the crash occurs to determine the cause, do not restart the game before getting the log file as it will be overwritten. You may have some dcs-log-<timestamp>.zip files that will contain the full log and crash information as well. Not sure what the information you were provided with previously but crashes are generally due to things that don’t need you to change anything with your core processes.

Also confirm that you aren't running DCS as administrator, can check under the shortcut for the exe as well under the Shortcut and Compatibility tab and make sure that Run as administrator isn't ticked. This was a known issue a while ago with WinWing MFDs. If you have modified the Windows UAC settings then this can also lead to things being run as administrator. Looking for another reference as I believe there is also another app that DCS can be launched from that can cause this issue as well.

It definitely works on Quest 2. Works on pretty much all headsets. It uses fixed foveated rendering for non-eye tracked headsets. Correct. Use Quad Views instead, same author. EDIT: Updating with more info: Install QVFR https://github.com/mbucchia/Quad-Views-Foveated Install Quad Views Companion to configure it https://github.com/TallyMouse/QuadViewsCompanion/releases Turn on Quad Views in the DCS VR settings. You need to restart DCS when making changes to the Quad Views in the companion app.

In which directory? The same one you run your DCS.exe from? Ever used NVPI or Nvidia App to override the DLSS dll, and haven't reverted it back to using the default? Note, I haven't checked in the in game overlay yet myself, just a couple of items that could potentially cause this.

Can you also comment as to when this exactly started happening. Has this just been a problem in the last few days, but was always fine before that? Any PC system updates, or Quest firmware updates (there are known issues with disconnections on the latest firmware when using 3rd party link cables).

Just a heads-up for folk that DCS has native support for this now so no need for NVPI to achieve this, unless you're wanting to apply to all your games. DCS also allows you to not use DLSS on MFD's and the HUD, which is where some of the larger complaints were around the ghosting on those when moving cursors etc. Just add the below to your Saved Games\DCS\Config\autoexec.cfg file (create it if it doesn't exist). DLSS_Preset = 'K' HUD_MFD_after_DLSS = true

The DCS log file shows that there is an OpenXR runtime issue and the session was lost. Don't know at this stage if this was a side-effect of something else in the game triggering this. This is possibly why VR freezes but you continue to hear sound. Does the game continue to play on your monitor mirror as well? 2025-08-26 19:22:34.935 ERROR VISUALIZER (Main): OpenXR xrWaitFrame failed with error: XR_ERROR_RUNTIME_FAILURE 2025-08-26 19:22:34.935 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED 2025-08-26 19:24:11.133 ERROR VISUALIZER (7728): xrEndFrame failed with error: XR_ERROR_SESSION_LOST 2025-08-26 19:24:11.134 ERROR VISUALIZER (7728): xrBeginFrame 12339.069162 failed with error: XR_ERROR_VALIDATION_FAILURE 2025-08-26 19:24:11.139 INFO VISUALIZER (Main): [15:24:11.568][Info ] OpenXR: XrEventDataSessionStateChanged: state XR_SESSION_STATE_FOCUSED->XR_SESSION_STATE_LOSS_PENDING session=3 time=12465287957300 2025-08-26 19:24:11.139 INFO VISUALIZER (Main): OpenXR: request restart 2025-08-26 19:24:11.139 INFO VISUALIZER (Main): OpenXR: request exit 2025-08-26 19:24:11.139 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED 2025-08-26 19:24:11.140 ERROR VISUALIZER (7728): xrBeginFrame 12339.069162 failed with error: XR_ERROR_CALL_ORDER_INVALID 2025-08-26 19:24:11.142 INFO Dispatcher (Main): Stop 2025-08-26 19:24:11.145 ERROR VISUALIZER (7728): xrBeginFrame 12339.069162 failed with error: XR_ERROR_CALL_ORDER_INVALID 2025-08-26 19:24:12.153 WARNING LOG (19056): 1 duplicate message(s) skipped. 2025-08-26 19:24:12.153 WARNING SCENE (7728): Scene was removed with 2 alive objects 2025-08-26 19:24:12.153 WARNING SCENE (7728): Scene was removed with 14 alive lights 2025-08-26 19:24:12.158 ERROR VISUALIZER (7728): xrBeginFrame 12339.069162 failed with error: XR_ERROR_CALL_ORDER_INVALID 2025-08-26 19:24:12.586 WARNING LOG (19056): 1 duplicate message(s) skipped. 2025-08-26 19:24:12.586 INFO TERRAIN (Main): lSystem::CleanScenes() 2025-08-26 19:24:12.586 INFO WORLDGENERAL (Main): TerrainUtility:: updated in parallel: 8791, updated in the main thread: 0 2025-08-26 19:24:12.605 INFO VISUALIZER (7728): Stopped collection of statistic. 2025-08-26 19:02:15.000 ERROR_ONCE (): 2025-08-26 19:24:13.045 INFO VISUALIZER (7728): DCSSceneRenderer initialized 2025-08-26 19:24:13.177 INFO EDCORE (Main): Created boot pool: n:24 2025-08-26 19:24:13.177 INFO WORLDGENERAL (Main): wDetectorWorker:: updated in parallel: 0, updated in the main thread: 0 2025-08-26 19:24:13.249 INFO EDCORE (Main): (dDispatcher)enterToState_:3 2025-08-26 19:24:15.035 ERROR VISUALIZER (Main): OpenXR xrWaitFrame failed with error: XR_ERROR_SESSION_LOST 2025-08-26 19:24:15.054 INFO EDCORE (Main): (dDispatcher)enterToState_:5 2025-08-26 19:24:15.054 ERROR VISUALIZER (Main): OpenXR xrWaitFrame failed with error: XR_ERROR_SESSION_LOST 2025-08-26 19:24:15.056 ERROR VISUALIZER (7728): xrBeginFrame 12339.069162 failed with error: XR_ERROR_CALL_ORDER_INVALID 2025-08-26 19:24:15.058 ERROR VISUALIZER (Main): OpenXR xrWaitFrame failed with error: XR_ERROR_SESSION_LOST 2025-08-26 19:24:15.062 ERROR VISUALIZER (7728): xrBeginFrame 12339.069162 failed with error: XR_ERROR_CALL_ORDER_INVALID 2025-08-26 19:24:15.064 INFO APP (Main): application shutdown 2025-08-26 19:24:15.067 ERROR VISUALIZER (7728): xrBeginFrame 12339.069162 failed with error: XR_ERROR_CALL_ORDER_INVALID Do you get this CTD issue in a basic single player instant mission? Do you get this issue in 2D? I note you're also using the OpenXR Toolkit so recommend disabling this as well to rule our any issues there. Additional information from the log analyzer: You currently have core parking enabled. Use software like ParkControl to disable core parking. You're running DCS from the bin-mt folder. Both executables are multithreaded now and bin-mt will be removed in the near future. Run DCS from the bin folder instead. From the DxDiag report, note some of this is a repeat of one of my earlier comments so apologies for that. Don't know if all are new events. Windows Error Reporting (WER) Kernel Events The following kernel-events have been detected: VIDEO_DXGKRNL_BLACK_SCREEN_LIVEDUMP,VIDEO_MINIPORT_BLACK_SCREEN_LIVEDUMP Remove any overclocking (including XMP). Run SFC and DISM to check your Windows. Check for any updates of your BIOS or chipset drivers. Memory Timing Issues Remove any overclocking (XMP) from your RAM. For the SFC and DISM commands referenced above open a command prompt as administrator and run the below two commands separately and then restart your PC: dism /online /cleanup-image /restorehealth sfc /scannow

There is no crash in this log, was it taken directly after one? What do you actually see when it crashes? Check if you have any dcs-logs-<timestamp>.zip files as well around the time of the crashes. This log only shows some errors from what I'm assuming are your Echo9 mods. Might want to remove those, run a slow repair, and see what happens. It also shows you are running Process Lasso, do you need to? If this is a log after a crash then it is possible that Windows is killing the process. Run the Windows DxDiag tool, save the report, and attach it here.

Your DxDiag report file showed the below: Kernel Events The following kernel-events have been detected: VIDEO_DXGKRNL_BLACK_SCREEN_LIVEDUMP,VIDEO_MINIPORT_BLACK_SCREEN_LIVEDUMP Remove any overclocking (including XMP). Run SFC and DISM to check your Windows., Check for any updates of your BIOS or chipset drivers. For the SFC and DISM commands referenced above open a command prompt as administrator and run the below two commands separately, restart your PC afterwards: dism /online /cleanup-image /restorehealth sfc /scannow Your DxDiag report contains a mix of LiveKernelEvent errors with the codes 1a8 and 1b8, further reference here on these: https://windowsreport.com/hardware-error-1a8-1b8/ Will need the DCS log file to see if anything else shows up.

You have file extensions turned off in Windows. Attach that text document named just "dcs" after you get a crash, the one above the "dcs.log.old" you have highlighted in your screenshot.

No crash in that log, so unless not taken directly after a crash then possibly Windows is “killing” the process. Run the Windows DxDiag tool, save the report, and then attach here as well.

Attach your DCS log file after one of these crashes occurs, don’t restart the game before getting the log. Also run the Windows DxDiag tool, save the report, and attach here as well.

Just caught up with you in the Discord server so looks like we're all sorted. EDIT: for anybody else who sees similar errors, i.e. "COMMAND NOT AVAILABLE" these errors means it didn't find the sentence in the VoiceAttack keywords. For this particular one Vaicom has two different commands for this, one has "wheelchocks" and the other has "wheel chocks". WhisperAttack transcribes this to "wheel chocks" (with a space) so will work depending on which Vaicom command you use. You can workaround this by adding the Vaicom command to the word mappings file with a replacement of "wheel chocks" to "wheelchocks", e.g. "place the wheel chocks" -> "place the wheelchocks". Note, you can do this via Vaicom aliases in their editor as well, so whichever is easiest for you.

If you’re talking about integration with Vaicom, then no. Vaicom has a specific command structure and the required keywords within it so whatever WhisperAttack outputs also has to match this. However, you can use the word mapping replacement functionality in WhisperAttack to achieve this, depending on what you had in mind. For example, if you’re wanting to say certain call signs, ie Vaicom doesn’t support sender call signs, then you could use the word mappings to replace that call sign with a blank. Or even replace with your own different call signs (although changing call signs can also be done using Vaicom aliases) This means you can use it in your speech but it will be removed before being sent to VoiceAttack/Vaicom. The same thing applies to flexible phrasing. As long as you say those in a specific way (or various combinations of them) you can have the word mappings replace that text with the required command for Vaicom.

Have you tried using a VPN as well?

Delete your Saved Games\DCS\launcher.sqlite3 file and start DCS again. Some folk have said switching languages and saving and restarting between each time resolved. You could try that as well, otherwise delete the file I mentioned above.

My PC died a few days ago so I can’t provide any screenshots etc. However, IIRC all I changed was to disable coreparking for all of the power profiles. This is pretty much the only thing you need to do.

Quest 2 via WiFi. You can also use Virtual Desktop with a USBC-Ethernet adapter (still need to connect to a router) for wired connection if your wifi has issues. Not officially supported, but they do have recommendations given the number of people that do this.

For all the reasons you mentioned. (As well as not encountering all the issues the Meta app brings, and breaks, in various versions).

Yup, there’re the same. Follow these instructions by Slughead to setup ReShade for VR, they’re the ones I used ages ago and are still the best I’ve seen yet This will also work for 2D as well. If you launch DCS with VR selected it will automatically use 2D if there is no headset connected, there’s no need to choose VR vs. non-VR. This will mean that ReShade will still be activated no matter if you’re in VR or 2D so this single setup will work for both.

Just use Virtual Desktop.

Firstly, use the DCS in bin and not bin-mt. They’re both multithreaded (and identical) and bin-mt is being removed in the future. Secondly, this issue for 2d or VR?

Hey mate, sorry for the late response. PC died so haven't gotten to it yet, working on getting it back up and running again.

Possibly related to this older post:

There is no crash in this log so is possibly Windows killing the process. Run the Windows DxDiag tool and then save the report and attach here. You also have a huge page file. With 64gb of RAM you don’t need that and could reduce that a lot. Looks like you have core parking enabled as well. You can use the ParkControl program to turn off core parking.