sleighzy

Might be worth trying Quad Views. You can install Quad-Views-Foveated (https://github.com/mbucchia/Quad-Views-Foveated) and then tick the Quad Views box in DCS under the VR tab. This is somewhat of a replacement of some of the functionality from the OpenXR Toolkit which is no longer supported. Turbo mode is enabled by default. For non-eye tracked headsets it uses fixed foveated rendering and will display a lower resolution image around the periphery with an adjustable multiplier for the main focal area. The focal area can be increased or decreased. This will increase load on the CPU (and remove some from your GPU) but with your 5800x3D you’ll be fine. if you don’t like it then just untick the Quad Views box in DCS and remove it.

OpenXR won’t be the root cause as this is the API used by the game for VR (which is used by all runtimes / headsets). When using Virtual Desktop you should use its VDXR runtime vs. the Steam OpenXR runtime.

One thing that sprung to mind is you mentioned you have 4 sticks of RAM. You could check if you have an XMP profile set in your BIOS for your RAM, and turn it off if so. Four sticks may be more susceptible to timing issues and crashes than two sticks when using some XMP profiles. Worth a shot to rule it out.

Humble apologies for the late response. From the latest log you attached I can see the runtime XR_ERROR_RUNTIME_FAILURE error, no specific cause though. This log shows that the Mbucchia Quad-Views-Foveated api layer was running. Do you recall (been a long time I know) if the crash in this log was when the "OpenXR QuadViews" box was ticked in PimaxPlay? The log also shows a lot of USB unplug/plug events. Can you disable hot plugging in the DCS controls settings (it'll be a big button at the bottom right). This will stop it constantly scanning for devices (and can help with stutters as well). If you plug in a new device you can hit the scan devices button on the controls page.

Oh well, good progress anyway, at least you’ve narrowed down the cause. Small consolation, but you get to play DCS without it crashing on you You could also add a larger page file to help with the loss of RAM. If you do decide to then just add a custom page file on your fastest SSD with initial and max values of 32768, click set, apply, and restart your PC. Make sure you only have one page file, eg remove any system managed ones. Might help with performance where needed until you get your full physical 64gb ram back again.

Really sorry to hear that mate. From that last DxDiag log: Couple more of the LiveKernelEvent 141 errors Some blue screen of deaths which you've noted (don't have a system code, or not seeing it properly, for cause of these) ASUS Armoury software (ArmourySocketServer.exe) Crashes with the Windows login screen (LogonUI.exe) Another one for DCS with the same memory problem If you do manage to get into your system, even if starting up in safe mode, there are some items you could check here, one of them being a memory test. Don't know if you're getting any system codes etc. on your blue screen which may indicate more around the cause. https://support.microsoft.com/en-us/windows/resolving-blue-screen-errors-in-windows-60b01860-58f2-be66-7516-5c45a66ae3c6

The DxDiag report shows that there are crashes for the following: Google Earth (googleearth.exe) Ghost Recon Breakpoint (GRB.exe) - this is an assumption based on a Google search for that process name. This crash indicates the application wasn't properly handling memory(?) DTS Sound Studio (DtsApo4Service.exe) Cinebench DCS (DCS.exe) - possibly not handling memory properly LiveKernalEvent - this has a code of 141 which indicates a hardware issue Based on the above it appears you may have issues across your system and not just DCS. Does the above list sound correct? The "not properly handling memory" ones may be related to system problems. Can you run the below two separate commands from a command prompt (cmd.exe) as an administrative user, restart your PC, and see what happens. Let me know if those commands identify and fix any issues. dism /online /cleanup-image /restorehealth sfc /scannow If you're updating graphics drivers try using DDU to completely clean any old drivers first.

The log file will always be present, but if it doesn't contain an actual crash from the game then this can occur if Windows kills the process or stops responding for some other reason.

I'd recommend removing your custom mods and trying this again. You have a number of them in your Saved Games folder as well. If it still crashes then attach an updated log from the latest crash. Can you also run the Windows dxdiag tool, save the report, and attach it here. This may offer further insight as will contain the last 10 crashes on your system.

DCS uses OpenXR so as long as he (and probably does) have a default OpenXR runtime set then should be all good. You can use this tool as well to see what the default is set to, and if you need to easily change it. https://github.com/rpavlik/xr-picker Glad to hear he's on the Standalone version as well. Makes life easier and get all the good stuff like free trials etc.

Not sure if by "OpenXR" you mean the "OpenXR Toolkit" when you were asking about installing stuff and that's the way to go now? The OpenXR Toolkit is no longer maintained and there are other options. Wouldn't worry about installing it right now. When you say his current setup goes through SteamVR is he using the Steam version of DCS and using SteamVR as his OpenXR runtime, or Mixed Reality Portal / Windows Mixed Reality (which should work for his OpenXR runtime)? Also note that the latest Windows 11 release (24H2) will kill WMR so do not upgrade to that. Best to stay on Windows 10 for now. Might be good to get him on this thread as well if things like DCS logs need to be bounced around or troubleshooting.

Attach a DCS log file for when a crash happens ("C:\Users\username\Saved Games\DCS\Logs\dcs.log" .. or just a text document named "dcs" if Windows is hiding file extensions) and we can have a look to see if it shows anything. You can also run the Windows dxdiag tool, save the results, and then drop that here as well. This should show what the last 10 crashes of applications are in case that shows something as well. IIRC if you try to use the OpenVR runtime of SteamVR (the one that would be used with the `--force_steam_VR` param) DCS should instead state that this isn't supported and will use OpenXR. I'm assuming that this is what you're doing to make that crash happen.

DCS has dropped support for OpenVR (those params won’t do anything) so you will need to use OpenXR. What are the problems you are having which are wanting you to use the previous OpenVR implementation?

Can you download the vc_redist x64 from here and then install it, it may ask for you to do a repair. Once you’ve done that then reenable OpenXR Toolkit and try again. If that succeeds then try with OpenKneeboard enabled again. https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170

Do you use an Ultraleap controller and have installed software for it?

As expected it looks like an OpenXR runtime issue, DCS will open in 2D if it can’t successfully start the runtime. This error is a file access one (I haven’t seen this previously). Can you disable/remove OpenXR Toolkit and OpenKneeboard, these API layers show up in the log. You can also view them and disable them using this tool https://github.com/fredemmott/OpenXR-API-Layers-GUI Try again after disabling/removing those layers. Had you ever added any custom parameters to those Steam launch options?

Can you drop your “C:\Users\username\Saved Games\DCS\Logs\dcs.log” file here after starting the game. Might just be a text document named “dcs” if Windows is hiding file extensions.

My humble apologies, yeah believe that had been for @Omega One as the issue in that posted log looked to be the zip driver issue fixed in the latest patch. It merged my two separate comments into a single one, apparently I’d hit the wrong quote button.

You'd posted this on the DCS Discord server as well. As I mentioned there it looks like Motion Blur is enabled. Can you turn that off and try again. Log doesn't show OpenXR Toolkit in use. This was also not added natively to DCS.

These get posted in the #ed-updates channel of the DCS Discord server, and also this page in this DCS forum Might be easier to check in on those more frequently than needing to fire up the launcher every few days.

You have listed Air link and Meta Quest Link, does this mean that it occurs with both Air link and when you try it with the cable as well? Can you also provide your "C:\Users\username\Saved Games\DCS\Logs\dcs.log" file (it may just be a text document named "dcs" if Windows is hiding file extensions). Do you use OTT or ODT? What is your Meta link app set to for resolution, e.g. 1.0, 1.5 etc.?

I dropped your log into the DCS log analyzer which indicates the below. You have the following mods installed DCS-SRS,UH-60L,Hercules ver 6.8.2,Tacview. Try removing at least the UH-60 and Hercules initially and running a slow repair with the option selected to remove files. The UH-60 is has been known to cause issues with DCS updates. Errors Your DCS has crashed The crash occurred inside DCS core. Remove your custom mods. Try a slow repair. Delete Saved Games\DCS.openbeta\fxo and metashaders2 and try again. Next, delete %LOCALAPPDATA%\TEMP\DCS.openbeta and try again. Next, try renaming Saved Games\DCS.openbeta to DCS.old and try again. Tuning Tips Enable Full Screen mode. Consider using DLAA. Set Water to Medium or Low. Turn down Anisotropic Filtering. The log also shows you have DCS Fiddle server hook being used. I'm not familiar with this so can't comment as to whether or not this is also causing any issues. You could always remove that and try again if the above options don't work. Based on your log this seems to be a different issue than the one posted by the original person on this thread. You should be raising your own issues for things which can be unrelated vs. reusing other posts.

I've dropped your log into the DCS log analyzer and it had the following to say. Note that you do not have a 32Gb page file like you've said, the log analyzer says your page file is 258Mb. Make sure you only have one page file configured for your entire system, and that it is set to a custom size of 32768 for the initial and max values. Click set, apply, and restart your PC. Your System ran out of Memory Increase RAM or page file Your GPU ran out of VRAM Reduce Terrain Textures and Shadows. Doublecheck your page file. Tuning Tips Turn off SSLR. Enable Full Screen mode. Turn off SSAO. There are also some errors with sound scripts, I don't know if related to the ECHO19_CORE_ULTIMATE mod you're using.

@StarLiner, @Omega One can you try this again after upgrading to the latest patch. The patch changelog indicates a fix with invalid zip files, which your logs seem to indicate a crash with the zip driver.

This is just the launcher log. You need the actual dcs.log file (may just be named “dcs” if Windows is hiding your file extensions). Provide the crash zip file if you also have one. Make sure the dcs.log file you attach is immediately following a crash, do not restart the game until you have provided the log file. You can also go to the DCS Discord server and drop your log in the #dcs-log-analyzer channel and it will provide information for you.