sleighzy

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.

“C:\Users\username\Saved Games\DCS” ”C:\Users\username\Saved Games\DCS\Config\options.lua” If editing configuration files make sure you use an editor like Notepad++ and not the default Windows Notepad application. Note, turning off the launcher isn’t going to solve your problem though based on your log file. You should start by removing all you mods and running a slow repair with the option checked for removing extra files.

Can you also attach your dcs.log file for when this crashes. Can you also disable OpenXR Necksafer and retest. And then try with OpenKneeboard disabled and retest. There have been known issues with Necksafer breaking things. If it is Necksafer then there are a couple of options for fixing this, but let’s confirm first. You can use this tool to easily enable and disable these layers https://github.com/fredemmott/OpenXR-API-Layers-GUI Just to confirm, your second screenshot says PimaxXR (incl. Pimax QuadViews). Does this mean it includes the Pimax Quad Views option checked in PimaxPlay, or that it means QVF is installed and the Quad Views box is not ticked in PimaxPlay? I ask this because that screen also shows the QVF is enabled… if using the Pimax OpenXR QuadViews one then QVF should be disabled.

A very similar issue has been reported in the bug reports channel in the DCS Discord server. There is a comment there that it may be fixed in the next upcoming patch. I have added a comment there with a link back to this forum post to have the dev team confirm whether or not this may be the same issue, and if potentially resolved in the next patch. I'll drop a further update here once I hear back.

You can overlay colors using OpenKneeboard, approach taken by most folk and examples, see YouTube. The Warthog Project is probably the most impressive for full simpit, but can do individual things.

It’s also interesting you mention Quad Views and MSAA. Does this mean that if MSAA is left on but you disable Quad Views (in DCS settings) that this works? Does this mean that when Quad Views is enabled and you use DLSS or something else (or nothing at all) it works as expected? I mention motion blur above as another user was able to replicate a very similar issue and stack trace with this on as well.

Virtual Desktop has native support for hands pass through without needing chroma key for them now. The best implementations I have seen have been people using VirtualDesktop with OpenKneeboard. This can be used as an overlay, with the kneeboard pages containing the coloured section you want for pass through. This could also potentially work for different aircraft as you could have a kneeboard page per plane.

You can safely ignore that error, it shows up in every body’s logs, may be related to when there were two different textures to the DCS gloves at one stage. Your log shows an OpenXR API layer for Ultra Leap. Is that the hand tracking module you’re referring to?