sleighzy

Ran you log files through the DCS log analyzer. Looks like lots of issues identified in the DxDiag report, see below. The DxDiag also says a pagefile of ~64Gb, but DCS log says ~8Gb. Can you drop a screenshot of your page file settings. Some of the Windows errors are memory related. Run a memory test as well. Others can be due to faulty or out-of-date drivers. Windows Error Reporting (WER) Your system crashes with Bluescreens. The following kernel-events have been detected: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY,VIDEO_ENGINE_TIMEOUT_DETECTED,VIDEO_MINIPORT_BLACK_SCREEN_LIVEDUMP,VIDEO_DXGKRNL_LIVEDUMP,VIDEO_DXGKRNL_BLACK_SCREEN_LIVEDUMP,PAGE_FAULT_IN_NONPAGED_AREA Remove any overclocking (including XMP). Run SFC and DISM to check your Windows. Check for any updates of your BIOS or chipset drivers. The DCS log analyzer also said to disable core isolation, although you mentioned you already had. I can't recall off the top of my head if that one is a false positive though and is just a generic suggestion but maybe worth a double-check.

It shouldn’t need a developer account. Drop a DCS log file here. Also install this tool and verify that the Quad Views OpenXR API layer is enabled https://github.com/fredemmott/OpenXR-API-Layers-GUI Confirm also that the Quad Views toggle is turned on under the VR tab in DCS. Check the Quad Views docs for the log file location and make sure it’s displaying what you expect, eg the settings and pixel savings. Sorry, my comments above were based on Quad Views in general. I see you are using a Quest Pro so are you referring to the eye tracking portion of it? Regardless, the other items I mentioned may help with troubleshooting. I’m assuming if you don’t know what the developer account is then this has worked for you in the past with not needing one.

In Virtual Desktop double-clicking the menu button on your hand controller will switch you between viewing your PC desktop (or currently open application) and being in VR (and back again). You just need to make sure that DCS is the open window before double-clicking back to VR on the controller again otherwise you get the Window Out Of Focus message.

Are you logged into the correct account? I'd recommend raising a support request otherwise: https://www.digitalcombatsimulator.com/en/support/ Or send email to the below address, send it from the same email address as the one used to create your DCS account. [email protected]

If you're referring to VoiceAttack as one of those two programs then should definitely work. It just sends key presses to DCS, nothing to do with DCS itself, and zero to do with OpenXR. This is just straight VoiceAttack, i.e. you're not using Vaicom as well? Does VoiceAttack work for other things, has it worked fine before and just stopped now? Is it set up correctly for sending to the active window? Refer to the other questions by Dangerzone as well.

Yup, we're referring to the same thing. Virtual Desktop I linked to runs on the PC, and then you install the one from the Meta Store on the headset which connects to it. Note, the author of the PC streaming app and the headset app are the same people (not Meta), you need both things for it to work. This is the software I use as well. This does not run alongside Meta Link, they're different. You don't even need Meta Link installed.

Which app is that? Do you mean this Virtual Desktop https://www.vrdesktop.net/ ? This isn't Meta, it's a 3rd party developer, and doesn't require a development account. This is an alternative to Meta Link / AirLink.

@Alexified, can you drop your DCS log file here as well after replicating the issue. Is C:\Users\username\Saved Games\DCS\Logs\dcs.log (or text document named "dcs" if your Windows is hiding file extensions).

Could be anything. Please attach your DCS log file (C:\Users\username\Saved Games\DCS\dcs.log) after replicating the issue. Also run the Windows DxDiag tool, save the report, and attach here as well. Is SSW set to Auto in Virtual Desktop? What is the refresh rate set to for the headset? Pixel density in DCS is set to 1.0 under the VR tab, and is Quad Views on or off? (just asking as these won’t show up in the DCS log).

Sorry on the delayed response, you've probably already got past this point. Yes, is as easy as that. Can't really help with the scripts side of things, i.e. preparing one for you as my system is different and has a number of different entries. Based on your previous screenshots it looked like you had nested duplicate folders, which can sometimes happen when unzipping folders and then copying them. Just copy them from your renamed backup, but copy from the lower level of those so you don't get the complete nesting. The lines in the screenshot you posted of your exports.lua file gives a good indication of what the folder structure should look like for it to find those. Yes, you can copy the DCS installation to your D drive, and then just update the shortcut you use to launch DCS to the new location for the exe file and folder path. Alternatively, after you've to the new location you can double-click the <new location>\bin\DCS.exe and within the launcher there is a Repair button. I believe this has an option for fixing up your shortcuts automatically (I haven't tested). Another thought to save you future time as well; once you get everything working again, before trying Streamdeck again, take a backup of that Scripts folder and exports.lua file. Go back through the Streamdeck setup, and you can always put back that Scripts folder backup and try again if you have problems. I'd also hang onto that copy of the Config\Input folder, nothing worse than having to redo your bindings all over again should something happen days/weeks/months from now

Turbo mode also exists (on by default) in Quad-Views-Foveated (QVFR) as well.

Mods and scripts don’t go into the main DCS game folder (they go in Saved Games) so you shouldn’t need to download the game all over again. A reinstall doesn’t touch Saved Games\DCS anyway so wouldn’t solve your problem. You may be better off just renaming Saved Games\DCS to Saved Games\DCS.old (rename and not delete so you can get back your Config\Input folder from within there so you don’t lose your keybindings). DCS will create a new Saved Games\DCS folder, basically getting you back to default state without all the duplicates etc. You can then put the necessary export scripts where they should be. Based on your log file DCS is running from C:\Program Files so doesn’t appear to be on your D drive anyway.

In addition to this you could try adding the below config (made available in the last couple of DCS updates) to use a different preset to see if it helps in reducing the ghosting. Note, as mentioned by Qcumber this will never go away completely unless you can burn through it Add the below line to the C:\Users\username\Saved Games\DCS\Config\autoexec.cfg file, create it if it doesn't already exist DLSS_Preset = 'K' The additional optional line below can also be added to that file. This will bypass the HUD and MFD for DLSS, means greater control if you'd like to use DLSS4 for the game, but hate ghosting on the MFDs and don't want to apply to those. Best of both worlds. HUD_MFD_after_DLSS = true

With no log attached it’s hard to tell what your problem might be. @YoYo posted the below comment on another thread. Don’t believe this is public API but would be interested to know what other folks experience with this config line.

Would need to double check (away for a few days) but it’s definitely a lot higher than 200. I have a good dedicated router beside my head so no network issues

The VD Discord has some info re: Quest 3 and AV1 can have latency issues at higher bitrates. Try h264+ (I do) as can have higher bitrates and better at fast paced things.

As a followup to this from the logs I have reviewed I see that these are also from VR, does the same situation occur when running in 2D? If VR only you could also try installing the tool below and then unselecting both the OpenXR Toolkit and OpenKneeboard layers within there to see whether or not they're a factor in this. https://github.com/fredemmott/OpenXR-API-Layers-GUI

Based on the DCS log analyzer, and the errors in the logs, it appears that there is a GPU related issue here as well. And yes, you do have mods. You also have a dxgi.dll file in the bin-mt directory of DCS, this does not ship with the game. There are only a couple of reasons you would do this, and has been known to cause crashes, so remove that, run a slow repair of the game choosing the option to remove files. There is a GPU-related error Remove any overclocking from your GPU. (some GPUs come with a factory overclock, you can confirm with MSI Afterburner) Uninstall your GPU driver with DDU and install a clean one. This aligns with the log file as well, tons of these errors. 2025-06-06 19:30:42.725 ERROR DX11BACKEND (18892): DX device removed. Reason: 0x887A0005 2025-06-06 19:30:42.725 ERROR DX11BACKEND (12260): failed to create structed buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2025-06-06 19:30:42.725 ERROR DX11BACKEND (12260): CreateShaderResourceView FAILED. Reason: E_INVALIDARG 2025-06-06 19:30:42.725 ERROR DX11BACKEND (12260): failed to create index buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2025-06-06 19:30:42.725 ERROR DX11BACKEND (12260): failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2025-06-06 19:30:42.725 ERROR DX11BACKEND (12260): Failed assert `false && "failed to create vertex buffer"` Also appears in the DxDiag report as well: Windows Error Reporting (WER) Kernel Events The following kernel-events have been detected: VIDEO_ENGINE_TIMEOUT_DETECTED You should run DCS from the bin directory and not bin-mt as well. There is also an access denied error when it is trying to write a track file to Saved Games, do you run DCS as administrator? (You can check the Compatibility tab of the properties menu of your shortcut to ensure that this is not the case). There are other errors in DxDiag report as well, but the above may solve this. Application Errors DCS.exe: was hung for 58.12s and killed SimLogic.exe: c0000005 (WWTHID.dll) WWTStream.exe: c0000005 (WWTHID.dll) Memory Timing Issues Run SFC and DISM to check your Windows. Check for any updates of your BIOS or chipset drivers. Remove any overclocking (XMP) from your RAM. For the SFC and DISM checks open a command prompt as administrator and run the below two commands separately and restart your PC: dism /online /cleanup-image /restorehealth sfc /scannow

Following on from silverdevil's comments if the installing a clean newer driver doesn't work then remove any overclocks on the GPU. Some GPU's come with a factory overclock so you can check that with MSI Afterburner. More info from the DCS log analyzer, looks like a number of issues identified in the DxDiag report, some of them video card related. Windows Error Reporting (WER) Your system crashes with Bluescreens. The following kernel-events have been detected: VIDEO_ENGINE_TIMEOUT_DETECTED,VIDEO_DXGKRNL_LIVEDUMP,IRQL_NOT_LESS_OR_EQUAL,PFN_LIST_CORRUPT,KERNEL_SECURITY_CHECK_FAILURE Remove any overclocking (including XMP). Run SFC and DISM to check your Windows. Check for any updates of your BIOS or chipset drivers. Application Errors DCS.exe: was hung and killed, c00000fd (edCore.dll) There is a GPU-related error (Re-)install the latest GPU drivers. Don't overclock your GPU or RAM. For the SFC and DISM checks 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 Some additional performance tuning tips from the log analyzer as well. Set Water to Medium or Low. Set Shadows to Medium. Turn off SSAO. Turn down Anisotropic Filtering. Turn off SSLR. Advice Verify that this is configured correctly in Windows: Game Mode disabled Hardware accelerated GPU scheduling disabled Core Isolation disabled

No crash in the log, so would imply that Windows killed the process. Appears to align with what's in the video. Run the Windows DxDiag tool, save the report, and drop the DxDiag.txt file here.

The stacktrace shows that this bubbled up from the OpenXR Toolkit. I see you are using both the ReShade and the OpenXR Toolkit api layers. I'd recommend that you install the below tool, and then untick the ReShade and OpenXR Toolkit layers and then try again to rule these out. If this works then re-tick and retry each individually to see which layer may be causing an issue. This tool will also show potential issues with these layers, and may fix them. https://github.com/fredemmott/OpenXR-API-Layers-GUI I'd also recommend the following: run a verify files for Steam for the game to do a repair deleting the Saved Games\DCS\fxo and metashaders2 directories. If it still continues then rename your Saved Games\DCS folder to Saved Games\DCS.old and try again. Rename, don't delete, the folder so that you can get your bindings back from the Config\Input folder in there.

Your issue is unrelated so you probably shouldn't hijack other people's posts on a different topic. Regardless, I've run your DxDiag report through the DCS log analyzer, plus some research on the "DPC_WATCHDOG_VIOLATION" error mentioned there. The DCS log file doesn't have a crash, so this will be Windows killing it. Your system crashes with Bluescreens. The following kernel-events have been detected: DPC_WATCHDOG_VIOLATION Remove any overclocking (including XMP)., Run SFC and DISM to check your Windows., Check for any updates of your BIOS or chipset drivers., Application Errors InstalledPackagesAgent.exe: c0000005 (InstalledPackagesAgent.exe) DeviceSetting.exe: was hung for 63.99s and killed For the SFC and DISM checks, 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 Have a google for the DPC_WATCHDOG_VIOLATION error as there are references there, namely around hardware and chipset drivers. If this continues to happen then raise a new post attaching your updated logs instead of this thread.

Drop your DCS log file (C:\Users\username\Saved Games\Logs\DCS\dcs.log) here so somebody can look at it and offer advice.

What version of DCS was fine prior to this occurring? Your log shows a driver 56633.DLSS Enabler for your AMD card. Seems like a mod of some description for DLSS-like support? Have you tried removing that as well? Probably unrelated. Your log file shows your Preload Radius is at the 150000 max, drop that to 60000. Run the Windows DxDiag tool, save the report, and drop that here as well.

Do you have exactly the same problem as this post and log errors? You probably shouldn’t hijack old posts. If you have an issue then raise a new post and attach your logs. You don’t need to install DCS again. Just remove any mods and run a slow repair of the game.