sleighzy

Hi @macemi. Well I've rebuilt parts of my PC so I'm back up and running again, humble apologies for the delay with this. I've had a dig and believe I've found the issue. We had lost some functionality from what this was originally based on. I have another release planned with new features so I'll look to fix this up and release it at the same time. Thanks for raising this.

Might be easier to troubleshoot in our Discord server https://discord.gg/7J9QAyYA (it's the #vaicom-voiceattack channel there) if we need to do a bit of back'n'forwards. This should just be taking input from the device you've selected as the mic in Windows. Restart WhisperAttack, say some longer sentences, and then drop your C:\Users\username\AppData\Local\WhisperAttack\WhisperAttack.log file here or in our Discord and I'll have a look. If you do go to the Discord you can ping me @sleighzy

What mic are you using? If you test that selected mic in the Windows input settings does it hear you loudly enough? If you turn speech recognition back on in VoiceAttack how well does it hear you?

OvGME is probably the most common one and a lot of mods reference this, it's the one I use as well and is very simple to use. The author of that one also has a later one, Open Mod Manager, but I have no experience with that to comment.

Let us know how you get on. Think that yes this is a "quirk" of OpenKneeboard. I'll dig up the thread that has been had on this before in the OpenKneeboard Discord (or other location where I've seen this discussed).

You should use the one in bin, it’s not single core. Both bin and bin-mt are multithreaded (they’re identical now) and bin-mt will be removed in the future, this is why the recommendation is there.

Another really good one by the Warthog Project guy as well.

That’s correct. What game are you using this with? Basically the push-to-talk will instead take the output from your mic, feed it through WhisperAttack, and then WhisperAttack sends the text to Voice Attack. If this isn’t disabled in Voice Attack then what happens is that Voice Attack will get both the voice input from your mic, as well as the same text command from WhisperAttack and will try to do the same thing multiple times. I believe you can disable speech recognition for just specific profiles so could do it with the profile you use for your game you use WhisperAttack with and leave it on for your other profiles.

You're probably better off upgrading to Windows 11 anyway, you'll find it's recommended for DCS due to better performance, especially with Intel chips. I'm not sure if your plan is to bring your MFDs into the game with you, but I have never heard Windows Mixed Reality Link being used for this (don't know if supported for OpenXR games). Do you have sources for that information if that's what you were intending? Folk who normally do this do it via OpenKneeboard (creating coloured sections for chromakey passthrough) and Virtual Desktop.

AH-64 (the whole reason I got into DCS all those years ago), A10CII, F-16. Recently discovered the new UH-60L v2.0 mod and been really enjoying that.

Two of those logs show you've added Quad-Views-Foveated, recommend removing OpenXR Toolkit if you're running that in general. The logs don't show a crash itself so it's more likely that Windows is killing the process. Can you run the Windows DxDiag tool, save the output, and then attach it here as well. I'd highly recommend you remove your mods, run a repair, and delete your Saved Games\DCS\fxo and metashaders2 caches. Mods can cause issues so may be something conflicting with that module and not others. Additional items: You can remove the "force_OpenXR" parameter from your shortcut as the game is entirely OpenXR. I'm assuming your other params are so you can have both VR and 2D shortcuts? You have core parking enabled. You can use the ParkControl software to disable core parking for your power management profiles. Having this enabled can cause stutters. I'll wait for the DxDiag report as that will likely have more info re: system issues and if/why Windows is terminating this.

What do you mean by this? Windows Mixed Reality (WMR)? Can you clarify what you mean by that. Not sure what you're trying to do, there's no reason to send it back.

DCS isn’t a Quest game so won’t be in the app library. How are you currently connecting your headset to your PC and running games? Connect your headset to your PC via link and then start DCS on your PC using the normal shortcut you always use. Make sure that you have enabled VR headsets in the VR settings of DCS.

Can you tune the radio to a frequency they're not on?

Attach your Saved Games\DCS\Logs\dcs.log file (will just be a text document named "dcs" if your Windows is hiding file extensions). Was the previous card also an AMD? Recommend you use DDU to remove the drivers and reinstall fresh stable ones as well just in case.

No worries All good now? Shouldn't be a lot. Some mods can cause issues though so a good troubleshooting start is to always remove them and run a repair just in case. Yeah this cleans up the shader caches. These can grow over time, and end up containing a bunch of redundant stuff which can still all be loaded. You should always delete them after any DCS upgrades as well to make sure all the cruft is removed and they're nice and clean. There's a handy screen for it in the DCS launcher as well under Files > Cleanup > Shader caches.

silverdevil's change would have disabled the launcher completely, you can turn it back on again in the game settings, might be under the Misc. tab. My solution was to delete the broken file causing this, if you turn the launcher back on again it should work as expected now.

No worries. Yeah dcs.log file in there is good enough to attach here after a crash.

Delete your Saved Games\DCS\launcher.sqlite3 file and start DCS again.

Looks like there's a 4 minute gap here around terrain and completed loading of the F15C. You running on a fast internal SSD? 2025-10-03 17:27:34.912 INFO Dispatcher (Main): load terrain done 2025-10-03 17:27:34.913 INFO LUA-TERRAIN (Main): Init done 2025-10-03 17:27:34.913 INFO INTER (Main): ITerrainGraphicsEntryPoint::close() 2025-10-03 17:27:34.913 INFO INTER (Main): ITerrainGraphicsEntryPoint::createTerrainGraphics() 2025-10-03 17:31:36.419 INFO EDCORE (24528): Loaded J:/DCS World/Mods/aircraft/F-15C/bin/F15.dll 2025-10-03 17:31:36.419 INFO WorldPlugIns (24528): loading "F-15C": 256.909 Ran your DCS log through the DCS log analyzer which highlighted a few things. You have heaps of mods. Can you try removing those and delete your Saved Games\DCS\fxo and metashaders2 caches. You can put them back afterwards, but lets at least rule out any issues there. You have core parking enabled. You can use the ParkControl software to disable core parking for your power management profiles. Drop your preload radius down to 60000. It's currently 100000, this will save some of the load time along with reducing VRAM and RAM usage. If you haven't already then you can also add a folder exclusion to your anti-virus software, e.g. Windows Defender, for the entire DCS installation folder, and then restart your PC. This may help if it's scanning the DLLs while loading.

Nah, OpenComposite takes OpenVR games (not OpenXR like DCS) and "converts" (like a bridge) them to OpenXR. So basically is intended to "allow" SteamVR games to run using OpenXR. Because DCS is already OpenXR none of that is needed. You just need to set your runtime of choice (PimaxPlay or Mbucchia's PimaxXR) as the default OpenXR runtime and it'll use that. If you have set SteamVR to be the runtime for OpenXR it will open SteamVR. Drop another crash log zip file from one of those occurrences. If the system is rebooting then this means a Windows issue and not the game itself. Typically an issue with drivers or memory. Unless I misunderstood your comment and these are reboots you are doing manually. If Windows is rebooting and not a game crash then there likely won't be a crash zip. Run the Windows DxDiag tool, save the output, and drop that here as well as a DCS log file from a crash.

This log is just from the launcher and not a complete boot into DCS. This log is also from the DCS in bin-mt and not bin. This post has also been solved and you're responding to something from 4 months ago. You should raise your own new post if you're having issues.

Humble apologies, I misread that as referring to the video on core parking, vs. your Process Lasso one I see as a link now. Needed more coffee.

Any reason why you're using OpenComposite? DCS is a native OpenXR game so shouldn't be used with that. And yes, Pimax should ideally be used with either the PimaxPlay OpenXR runtime or Mbucchia's Pimax runtime and not SteamVR.

Reinstalling DCS is hardly ever the option. Please provide the information that MAXsenna requested along with a screenshot of the exact error.