sleighzy

Do you have the "eye-tracking" box ticked in the DCS settings (under the VR tab)? Numerous people have had issues with Necksafer and this. Untick that box if you do have it ticked, restart DCS, and try again.

Do you mean OpenXR Toolkit and not "OpenXR"? Disable the OpenXR Toolkit and try again. You can install this tool to see all the API layers and untick the boxes for OpenXR Toolkit and OpenXR Motion Compensation (just leave quad_views) and see if that resolves the issue. https://github.com/fredemmott/OpenXR-API-Layers-GUI

Even after the exclusions and repair? Your DCS directories aren't owned by the administrator or anything and can't be written to? This is still confusing to me as well and should be resolved: " Local source: c:\program files (x86)\steam\steamapps\common\DCSWorld\" Is this via the new launcher, or running the dcs_updater.exe file within the bin directory? What happens if from the commandline you run the bin\DCS_updater.exe manually?

What are the new log files that were created in the Logs directory of the new Saved Games folder? Drop them here for further review in case the problem is different, or still the same.

I've dropped your crash log into the DCS log analyzer which has the attached output. My reference to installing the above files was from the VCRUNTIME error. Try the removal of the RAM overclocking first. Failing that, try the other options listed further down in that screenshot. null Cool, make sure you add the exclusions to Windows Defender as well and restart your PC before running a repair if/when you need to.

Known issue, they’re working on the fix at the moment.

It only does one thing. The button turns on or off Quad-Views if you currently have it installed, i.e. the Quad-Views-Foveated API layer that a number of us have had installed for a while now. More convenient than using Fred's OpenXR Layer GUI tool (for people not familiar with all the tooling available) as Quad-Views-Foveated itself does not have any ui for turning it on or off. Quad-Views can be used by numerous headsets, not just Pimax, and those don't have a UI for turning it on or off. Note that the PimaxXR option would have likely disabled the entire Quad-Views api layer on your system...the DCS setting doesn't, it just disables it in game.

Do you have a headtracker.dll file that you have to copy anywhere? One change between this version of DCS and the previous patch is that DCS will now run the DCS.exe file in the bin directory and not the bin-mt directory (as MT has gone away now). Don't have much other advice, but is one difference between the two.

The DCS nvngx_dlss.dll file will, you'll need to update that back to the 3.7.20 version as DCS ships with 3.7.0.0 so will replace it. All the other DLSSTweaks stuff will be untouched as they aren't DCS files. You can also follow my alternate steps here to set this in the Nvidia Global Profile to reduce some of the effort of dealing with dlls and config files.

@GPatricks (and others): With the latest patch now running DCS from the bin directory by default you'll need to copy your ReShade config files and `reshade-shaders` folder from the bin-mt directory to bin. I also manually updated my `C:\ProgramData\ReShade\ReShadeApps.ini` file to include the path to the bin\DCS.exe file (vs running the ReShade installer and choosing it). You can confirm it works by checking the `ReShade.log` file in the DCS bin directory when you start DCS.

I copied my existing ReShade config files and reshade-shaders folder from the bin-mt dir to the bin dir. I just updated the "C:\ProgramData\ReShade\ReShadeApps.ini" file manually to include the new path to DCS vs. doing a reinstall and selecting it.

I've run your DCS log file through the DCS log analyser. I'd definitely try removing your mods and running a slow repair as mods are frequently broken with new DCS updates. Start with the mods first and then try the other options. When performing the slow repair make sure you add an exclusion to your anti-virus software (Windows Defender if you don't have anything else) for the entire DCS game installation folder and then restart your PC. If it starts working with the mods removed then add each one back in individually and starting the game to narrow it down to which one is breaking things. If it resolves itself after renaming the Saved Games\DCS folder, then you can copy back your config and control bindings from the renamed folder back into the new saved games folder DCS creates for you.null

Download and install this (or repair option) https://aka.ms/vs/17/release/vc_redist.x64.exe It's from here and is a known issue with DCS (a Windows problem and not a DCS problem per se other than causing DCS to crash) https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170 Malwarebytes is also not the greatest, the default Windows Defender is more than enough. Don't exclude just that one file, exclude the entire DCS installation directory as your AV may be quarantining / deleting other DCS files as well.

Also with the latest DCS update both the DCS in the bin directory and the bin-mt directory both run the multithreaded version, ST is no more.

You mean disabling Kapersky? Windows also has its own AV, Windows Defender, which is pretty much all you need. Recommend adding exclusions in there as well as it may kick in as well with Kapersky disabled (possibly even when enabled). I also dropped your log file into the DCS log analyser which has a little feedback re: tuning advice. Not saying that this is going to fix your issues though.null

@Nazgûl, try what Rob said first. I don't recognise that Anti-virus software either, what is it?

Have you ticked the Quad Views box in DCS under the VR tab?

@Nazgûl, can you add an exclusion in your anti-virus for the entire "C:/Users/otavio/Saved Games/dcs.openbeta" folder, as well as the DCS installation folder. Your log appears to show it recompiling the shaders each time. These should be cached and not recompiled every time you start the game.

@xxcosmicggxx, add an exclusion for the DCS installation directory as well. What is really really weird is that it is showing those directories in your Saved Games folder as well. For example: "Can't delete C:\Users\secur\Saved Games\DCS World OpenBeta\bin-mt/edCore.dll:" Can you post a screenshot of your "C:\Users\secur\Saved Games" directory. It should not have the game installation folder in there.

Don't know if you ever solved this, but the crash in your logs is definitely the OpenXR Toolkit. You can install this API layers tool and untick the box for the toolkit to make 100% sure that it is actually disabled. You've said that you already tried with and without, but recommend this tool to confirm. Then try launching DCS again. If it still crashes then drop another log here containing the crash. https://github.com/fredemmott/OpenXR-API-Layers-GUI

I ran your log through the DCS log analyser which highlighted a couple of points. One of them was fairly obvious, you have a preload radius of 150,000 (the max). This is going to hit your RAM, of which you only have 16Gbs. Drop this to 30,000 and see what happens as well.null

Realise this is an old post, but don’t think operator error. I experienced the same problem. I vaguely recall him answering my initial radio once(?), I’ve flown it a few times, but no follow up or laser etc.

Awesome! Glad it's all sorted out for you. Happy flying!

If you're still looking for an answer to this then there's good instructions here:

Do you use Meta Link app or VirtualDesktop? I got this working with VirtualDesktop recently but found the instructions were a little out of date due to some changes in VirtualDesktop, you do need to enable hand tracking in VD (although the HTCC instructions say not to)