sleighzy

They’ve said they’ll look at it after Vulkan.

Restart your PC in case the process is already running. Add an exclusion in your anti-virus software, e.g. Windows Defender, for the entire DCS installation folder, and then restart your PC.

Without your DCS log file after a crash there's no way to tell the cause.

People having numerous problems with the new Nvidia app in general. Based on feedback I'd avoid it at this stage. You need it for anything specifically?

Router is the way to go for official support, or if Meta change anything that prevents the steps in the below guide from working. It may be enough just to use a usb-c to ethernet adapter for VirtualDesktop and Quest 3 (it does for some folk), however if you need the extra steps to get it working (note that these may only be needed for a Quest Pro ) then you can try them here:

Can try putting tape over the sensor as well. A few people do that to stop it sleeping for that very reason (although in your case it hasn’t actually gone to sleep).

If you haven't already then also add an exclusion in your anti-virus software, e.g. Windows Defender, to exclude the entire DCS installation folder. This can speed things up as won't be scanning everything downloaded and unpacked.

You mean the Nvidia nvngx_dlss.dll file (and others)? Nowhere. With the NVPI config change to enable the override and set the preset it will automatically use the DLSS version that ships with the driver. The one in DCS is ignored. So no dlls need to be put anywhere.

If you followed the steps to rename "DCS.openbeta" to "DCS.openbeta_old" then the "DCS.openbeta_old/Config/Input" folder contains all your bindings. Just copy that folder back to DCS.openbeta to get them back again.

This is expected and can be ignored. It just lists other API layers you have installed so you’re aware of them in case of problems. Nothing to worry about, we all get this. You maybe shouldn’t have done it the way you did though as there are registry keys associated with these two. In future, and if you experience problems, use the https://github.com/fredemmott/OpenXR-API-Layers-GUI tool to disable those layers. Hopefully you still have those in case you need to put them back in those directories again.

If using NVPI like you mention you don’t need to copy any dlls in. Does it still work fine if you don’t copy/replace those dlls in DCS?

Using a second GPU for this is not something we've looked at. Our default model is small.en however you can update your settings.cfg and change this to use smaller models which will use less VRAM, e.g. tiny.en whisper_model=tiny.en

You can't. Use DLSSTweaks. Select Enable (All DLLs) from the ForceOverrideHud drop down.

You can use VAICOM PRO a plug-in for VoiceAttack for this.

What headset do you have? Please attach your C:\Users\username\Saved Games\DCS\Logs\dcs.log file (may just be a text document named "dcs" if your Windows is hiding file extensions). The F10 map is a known issue for VR with massive fps drops. There are some workarounds which may help: Use the Empty VR hangar for less VRAM usage and faster F-10 ingame map which will save VRAM as otherwise the hanger is always there, including when viewing the map. Make sure to recenter the map and zoom in on your plane before entering the cockpit again Alt-tab out of the game, wait a few seconds, and then alt-tab back in again Try using the DCS Web Editor Moving Map with OpenKneeboard for an ingame dynamic map without needing the F10 map Lower your texture settings As you only have 32Gb RAM I'd also recommend create a custom page file. Create a custom page file, just a single one (removed any other system managed ones) on your fastest SSD. Set the Initial and Max values to 32768, click Set, Apply, and restart your PC.

This one has still come back as a memory timing issue (C00000005 access error I believe is what the log analyzer uses to determine this). Did you have any existing overclocks, XMP / EXPO profiles on your RAM that you removed? Maybe run a memory test as well to see if that identifies anything, Windows has a tool for that. Memory Timing Issues Remove any overclocking (XMP) from your RAM. Further items referenced by the analyzer. Your DCS has crashed The crash occurred inside ARF.dll. Try a slow repair of the game, select remove other files option as well. Delete Saved Games\DCS\fxo and metashaders2 and try again. Next, delete %LOCALAPPDATA%\TEMP\DCS and try again. Next, try renaming Saved Games\DCS to DCS.old and try again.

Presumably you clicked "Appy changes"? What profile did you make the change to, e.g. _GLOBAL_DRIVER_PROFILE (there's a dropdown at the top of the screen)? Check what you have for the "Digital Combat Simulator: Black Shark" profile in case it's overriding the global profile. You've never used DLSSTweaks in the past, so have none of those files in DCS? If you don't know what I mean then it likely means you haven't, which is good. Note, I haven't upgraded to 572.42 yet so don't know if any change between 572.16 and that, would have thought others would have complained if that was the case. Maybe drop a screenshot of NVPI as well.

I've also run your log through the DCS log analyzer which had the following to say: Note that your preload radius is at the 150000 max setting. You will be loading a lot of redundant stuff into RAM, and you have very little RAM. Set it to 30000. Your page file is also only 27648 MB. I'd increase that to at least 32768 MB or higher. Set Preload Radius to max. 30000. Turn down Anisotropic Filtering. Set Water to Medium or Low. Enable Full Screen mode. Some additional items. Upgrade your RAM to 32 GB for complex multiplayer missions. Your game resolution (1600 x 900) does not match your current GPU resolution. If you are not using VR or external MFDs, please check your settings. Your Windows version is outdated. Consider upgrading! Verify that this is configured correctly in Windows: Game Mode disabled Hardware accelerated GPU scheduling disabled

I see you are using the SteamVR runtime for your VR as well. Recommend using the Meta Link app (or VirtualDesktop) instead of SteamVR. In the Meta Link app in Windows set the setting to make it the “Default OpenXR runtime”. It will probably display a banner if it isn’t. Note that this will likely not solve your problem. If the log doesn’t show a crash then more likely Windows killed the process. Run the Windows DxDiag tool and attach the report to this ticket.

I’ll enquire further, they may have mistaken for a previous mod of this, vs an actual official module.

Dropped your log into the DCS log analyser which had the following to say. Process Lasso detected Process Lasso can cause issues with DCS MT. Consider disabling it. Your DCS has crashed The crash occurred inside edCore.dll. Remove your custom mods Try a slow repair of the game, tick the option to remove extra files Delete Saved Games\DCS\fxo and metashaders2 and try again. Next, delete %LOCALAPPDATA%\TEMP\DCS and try again. Next, try renaming Saved Games\DCS to DCS.old and try again. Some additional information it provided. Upgrade your OS to Windows 11 to better support your CPU or change your affinity mask to 11110000000000001111111111111111 Verify that this is configured correctly in Windows: Game Mode disabled Hardware accelerated GPU scheduling disabled

This tool may also help identify which runtime it's attempting to use. https://github.com/rpavlik/xr-picker I don't use the Steam version of the game, but from within Steam can you try just using one of the other options to run the game, i.e. not one that mentions OpenXR. DCS is OpenXR by default so no need to select a specific OpenXR option in Steam. It may be trying to force it to use the SteamVR runtime with that option, which is not installed.

You can only have one runtime set to be the default OpenXR runtime. It sounds like you have Mbucchia's PimaxXR installed as well as the PimaxPlay one. This is fine, however, go into Mbucchias' PimaxXR app and check to see if you have the SteamVR option selected in there. This may be why it is attempting to use that runtime (which doesn't exist as you aren't using SteamVR). Change that to instead be PimaxXR and restart your PC. That same error is in your dcs.log file so it's definitely trying to use a non-existent runtime: 2025-02-15 16:17:02.603 ERROR VISUALIZER (Main): OpenXR failure XrResult failure [XR_ERROR_RUNTIME_UNAVAILABLE] Origin: xrEnumerateInstanceExtensionProperties(nullptr, 0, &instanceExtensionCount, nullptr) Source: Projects\Visualizer\Source\OpenXR\openxr_program.cpp:225 null

First DCS Forum post on this I've seen. Looks like he's put this warning on all his other repos as well. https://github.com/mbucchia/Quad-Views-Foveated/blob/main/README.md https://github.com/mbucchia/OpenXR-Toolkit/blob/main/README.md

The one on your left hand controller that makes the VD menu slide out when you're not in VR.