Wolf359

Ok, thanks. I will have two installs. I thought it strange when I noticed the combined thing that happened via the utility. I will configure the utility to point to each install.

I notice that when sing the Updater Utility, all the files are combined into one directory. Whether I update to OB or the Stable Release. Is this a recipe for something bad to happen, or is this designed to streamline switching between the two? I'm upgrading my system this week; it will have a 2TB M.2 PCIe NVMe SSD. I am leaning to simply install both releases separately - no switching via Updater Utility. However, if the combined folder is no big deal, no issue, then I won't use up the extra space on the drive.

I look up the airfield on the kneepad or F10 map, get the frequency, and tune the com appropriately.

I'm an F-18 driver as well. Make sure the OB box is checked in Vaiccom config custom dcs path, turn off the redirect, then go to dcs audio and set up in the headphone/default settings. You may have to do a repair, but it should take care of it all.

And this actually sounds better.

True, it was probably mentioned a million times, but YOUR mention of it finally clicked in my dense brain. That worked! Thanks buddy. Now, I am not getting any voice responses. The text come up on the screen just fine. I'll read back through some of the entries to see if the fix has already been posted.

WADR, Vaicom is the only app causing this. It's the only app we reset, we run repair, we get things running, and then it falls to crap. Vaicom is the common denominator in this issue. Whether it's Vaicom or Voice Attack - it's all the same where this issue is concerned, at least for those using both. So how about we focus on that. DCS OB runs fine when Voice Attack is never started. That pretty much says it all. I, for one, don't have any mods.

Stop VA and close it down completely (check your task bar). Run repair via DCS Updater Utility. This will get you flying. Run DCS. Just don't run VA until this gets figured out.

That didn't work either.

It hangs at 10% again. I've deleted the vaicompro.export.lua file, ran reset...the whole thing over again. It was working ok prior to the patch. Now it appears broken again.

Same thing is happening to me, even after I enter the custom location. I am having to run repair every time I start OB. Is this the appropriate thread to report?

I have a mission built, launching from the carrier, and I can launch fine since 2.5.6. Haven't tried today, since the patch. I will try when I get home.

Upgrade must be in the water! Mine is due to arrive between the 21st and 26th. Lunar Light chassis with High-Performance CPU Liquid Cooling and 850W Power Supply NVIDIA® GeForce® RTX 2070 SUPER 8GB GDDR6 (OC Ready) 9th Gen Intel® Core i7 9700K (8-Core, 12MB Cache, Overclocked up to 4.6GHz across all cores) Killer Wi-Fi 6 AX1650 (2x2) and Bluetooth 5.0 2TB M.2 PCIe NVMe SSD 32GB Dual Channel HyperX(FM) FURY DDR4 XMP at 2933MHz Windows 10 Home 64bit English

That did it for me as well.

NVM, found it

I have no such file in any Vaicom folder in saved games.

Excellent. I will try this when I get home this evening.

Yep, I just did the same.

Same here. I am unable to use Voice Attack/Vaicompro in 2.5.6. Hangs at 10%. I have to run repair and NOT open VA at all in order to run 2.5.6 successfully.

I need to purchase the KA-50 first?

Has anyone tried uninstalling and reinstalling VoiceAttack? FYI: VaicomPro IS already in the saved games folder structure.

I did it through the DCS Updater app. The advanced update options tab, right side button to "delete pre-compiled shaders".

It's a voice attack issue. Closed it and ran repair, now I'm in.

Ok, that's what i thought. I'm in! Closed VA and ran repair.

How do I disable it?