VAICOM PRO plugin for VoiceAttack

Missing Configuration tab

Is anyone having problems calling up the Configuration tab? Pressing LCTRL, LShift and C brings another tab into the task bar but is blank and the Configuration tab is not present on the screen. Is there some means of reacquiring it please.

Is anyone having problems calling up the Configuration tab? Pressing LCTRL, LShift and C brings another tab into the task bar but is blank and the Configuration tab is not present on the screen. Is there some means of reacquiring it please.

Not having issue here.

However it is LCTL LALT C.

Is anyone having problems calling up the Configuration tab? Pressing LCTRL, LShift and C brings another tab into the task bar but is blank and the Configuration tab is not present on the screen. Is there some means of reacquiring it please.

If you hit Alt+Space, then select move, then use the arrow keys on your keyboard, you'll be able to bring the VAICOM window to where you want it. It's something that's been happening to me for months

This is my first visit to the VAICOM Pro forum, so I'm hoping you kind folks can help me.

Configuration:

DCS/FA-18C

Helios

SSA via onboard Realtek Audio Console

TrackIR

Logitech G35 headset/Logitech Gaming Software

Default audio output, eClaro 7.1 sound card/speakers

Default audio input, G35 mic

G35 selected as headset in DCS sound settings

Chatter redirected to G35 headset in VAICOM Audio Tab

I run all non-radio DCS sound to my 7.1 sound system so I can feel and hear the cockpit/world sounds while I have the headset on to simulate actually sitting in the aircraft with a helmet (headset) on.

I had VAICOM Pro and all extensions working great and was loving it until last night when I started everything up and then fired up DCS. Here are the problems that seemed to come out of nowhere:

1. Chatter is no longer audible.

2. Audio command cues/beeps no longer audible.

3. Mic switch on/off effect no longer audible.

VAICOM commands are recognized and acted upon by VA and responses from ATC, etc.. come through the headset, but no audio cues or chatter present. Even when I start VA, I no longer hear the beep when the profile is initiated at startup.

All VAICOM licenses are validated, no error messages apparent in the VA console.

I performed a DCS repair, no help.

I shut down DCS, cycled chatter redirection to the headset off and back on, shut down and restarted VA, restarted DCS, no help.

When this all started, my headset was not recognized by my system for some unknown reason. Unplugging and re-plugging the headset remedied that, but then all these other problems started.

I'm hoping I'm just missing something simple being a nube at all this, so I'm attaching screen prints of configuration settings. I REALLY don't want to reinstall/reconfigure all this all over again, but if that's what you guys say I need to do, then I guess I'll have to do it. Any suggestions other than that would be most welcome! Thanks! :smilewink:

This is my first visit to the VAICOM Pro forum, so I'm hoping you kind folks can help me.

 

 

 

Configuration:

 

 

 

DCS/FA-18C

 

Helios

 

SSA via onboard Realtek Audio Console

 

TrackIR

 

Logitech G35 headset/Logitech Gaming Software

 

Default audio output, eClaro 7.1 sound card/speakers

 

Default audio input, G35 mic

 

G35 selected as headset in DCS sound settings

 

Chatter redirected to G35 headset in VAICOM Audio Tab

 

 

 

I run all non-radio DCS sound to my 7.1 sound system so I can feel and hear the cockpit/world sounds while I have the headset on to simulate actually sitting in the aircraft with a helmet (headset) on.

 

 

 

I had VAICOM Pro and all extensions working great and was loving it until last night when I started everything up and then fired up DCS. Here are the problems that seemed to come out of nowhere:

 

 

 

1. Chatter is no longer audible.

 

 

 

2. Audio command cues/beeps no longer audible.

 

 

 

3. Mic switch on/off effect no longer audible.

 

 

 

VAICOM commands are recognized and acted upon by VA and responses from ATC, etc.. come through the headset, but no audio cues or chatter present. Even when I start VA, I no longer hear the beep when the profile is initiated at startup.

 

 

 

All VAICOM licenses are validated, no error messages apparent in the VA console.

 

 

 

I performed a DCS repair, no help.

 

 

 

I shut down DCS, cycled chatter redirection to the headset off and back on, shut down and restarted VA, restarted DCS, no help.

 

 

 

When this all started, my headset was not recognized by my system for some unknown reason. Unplugging and re-plugging the headset remedied that, but then all these other problems started.

 

 

 

I'm hoping I'm just missing something simple being a nube at all this, so I'm attaching screen prints of configuration settings. I REALLY don't want to reinstall/reconfigure all this all over again, but if that's what you guys say I need to do, then I guess I'll have to do it. Any suggestions other than that would be most welcome! Thanks! :smilewink:

Sent from my SM-T835 using Tapatalk

Is anyone having problems calling up the Configuration tab? Pressing LCTRL, LShift and C brings another tab into the task bar but is blank and the Configuration tab is not present on the screen. Is there some means of reacquiring it please.

I had this happening for a while...not sure what caused it since it had been working fine for over a year of usage. I think what I did which solved it was to go into the vaicom pro subdir in the voiceattack apps folder and deleted the config dir...after making a back up copy.....after making a back up copy...did I mention about making a backup copy first?....the config dir in there then restarted voiceattack and the config screen was coming up again... Say...did I mention the part about making a backup copy first in case it doesn't work? Yeah...you should definately make a back up copy first. Can't stress that enough...LOL...Hope it helps! Heck....back up the whole damn VoiceAttack directory first!

Away from computer at the moment, but a first step might be to select Run in debug mode on the Vaicom Config tab and see if there are any additional messages given in the VA log window.

 

Sent from my SM-T835 using Tapatalk

VA Console output and VAICOM log attached illustrating what I described. Commands recognized and acted upon, but no audio command cues, no chatter. Unfortunately there doesn't appear to be anything in the VA console output or VAICOM log that would indicate a problem.

Edit: Attached files were created with debug on as requested.

VA Console.txt

VAICOMPRO Log.log

VA Console output and VAICOM log attached illustrating what I described. Commands recognized and acted upon, but no audio command cues, no chatter. Unfortunately there doesn't appear to be anything in the VA console output or VAICOM log that would indicate a problem.

 

Edit: Attached files were created with debug on as requested.

This issue comes up from time to time. I've had some issues myself when trying to have a look at it.

My feeling is that it's "a conflict" between VA and Windows. Emphasis on "feeling".

Some have had luck in VAICOM selecting different outputs, as Windows/VA seems to mess it up.

That said, maybe start a new thread?

Cheers?

Sent from my ANE-LX1 using Tapatalk

This issue comes up from time to time. I've had some issues myself when trying to have a look at it.

My feeling is that it's "a conflict" between VA and Windows. Emphasis on "feeling".

Some have had luck in VAICOM selecting different outputs, as Windows/VA seems to mess it up.

That said, maybe start a new thread?

Cheers?

 

Sent from my ANE-LX1 using Tapatalk

Hey MAX, I'm inclined to agree, especially since Windows 10 now has its own mechanisms in place to redirect output on a per application basis (Settings->Sound->Advanced sound options). My gut tells me as well that it has something to do with a conflict in that area after I've tried everything I know to get the system back to operational status. Another clue is the fact that my headset was suddenly no longer recognized by Windows when this all began, indicating "something" initially happened in Windows 10 that persists even after reacquiring the connection to the headset. Based on that, I'm not even sure if a re-install of VA and VAICOM will fix it, but I don't know what else to try at this point so I'll give it a shot and cross my fingers.

Edit: Right after I wrote this, it got me thinking, maybe trying to beat Windows at its own game was indeed the issue causing the conflict. I turned off ALL redirection in VA and VAICOM, and instead relied solely upon letting Windows redirect the VA output to the headset. BOOM! Working again!

Good to know - i am aware that i have similar issues sometimes with Discord being overridden by windows

Sent from my SM-T835 using Tapatalk

 

Snip...

 

Edit: Right after I wrote this, it got me thinking, maybe trying to beat Windows at its own game was indeed the issue causing the conflict. I turned off ALL redirection in VA and VAICOM, and instead relied solely upon letting Windows redirect the VA output to the headset. BOOM! Working again!

Good find! I'll test myself next week. I guess any redirection in DCS will work as well then?

Cheers!

Sent from my ANE-LX1 using Tapatalk

Good find! I'll test myself next week. I guess any redirection in DCS will work as well then?

Cheers!

Yes, the headset redirection in DCS works fine, responses from ATC etc.. come in loud and clear along with chatter and command cues from VAICOM.

Yes, the headset redirection in DCS works fine, responses from ATC etc.. come in loud and clear along with chatter and command cues from VAICOM.

Sent from my ANE-LX1 using Tapatalk

Well, Max, the bad news is I shut everything down and unplugged my headset to do some other stuff on the PC. Got ready to fly again so I plugged them back in and started everything back up, and everything was all jacked up. Redirection for the headset in DCS was pointing to "default" and Windows had lost all its redirection settings for VA, pointing all the VA output to "default" as well. Reset the Windows and DCS redirection and Windows reverted back to default again after I started VA. Reset it again and it stayed set the second time through. There still seems to be some contention going on. Possibly related, but I haven't the foggiest idea how, my centering key bind for TrackIR was set but no longer working. Restarting TrackIR fixed it, but that's never happened before. Definitely some funky stuff going on under the hood here.

The good news is that I know how to get it working now when these issues happen, but it's just a bit of a hassle is all. Sorry my "solution" didn't live up to expectations...

Well, Max, the bad news is I shut everything down and unplugged my headset to do some other stuff on the PC. Got ready to fly again so I plugged them back in and started everything back up, and everything was all jacked up. Redirection for the headset in DCS was pointing to "default" and Windows had lost all its redirection settings for VA, pointing all the VA output to "default" as well. Reset the Windows and DCS redirection and Windows reverted back to default again after I started VA. Reset it again and it stayed set the second time through. There still seems to be some contention going on. Possibly related, but I haven't the foggiest idea how, my centering key bind for TrackIR was set but no longer working. Restarting TrackIR fixed it, but that's never happened before. Definitely some funky stuff going on under the hood here.

 

The good news is that I know how to get it working now when these issues happen, but it's just a bit of a hassle is all. Sorry my "solution" didn't live up to expectations...

You know the difference between admins and users?

The admin doesn't mind problems as long as there's a solution/fix/workaround. Users don't want problems at all. I'm an admin!

Cheers!

Sent from my ANE-LX1 using Tapatalk

so with the airio extension i cannot get the "Radio Tune" commands to show the hell up in the editor. Im trying to train the voice recognition so i can actually use the command. How do i reset the keywords so i can start from scratch on this

so with the airio extension i cannot get the "Radio Tune" commands to show the hell up in the editor. Im trying to train the voice recognition so i can actually use the command. How do i reset the keywords so i can start from scratch on this

If you are struggling with recognition you may need to change the command phrases (I use freak instead of tune and say Oh instead of zero). There is a separate thread about this in the Vaicom sub forum.

Unlike the normal command words, try to read these phrases without micropauses

Sent from my SM-T835 using Tapatalk

Hey All,

I am having an issue with Vaicom, when I am in game and I can say Options and the menu pops up but when I say "Take x" nothing in DCS Happens..

I have read the troubleshooting and it said to delete the Export.lua which I had done multiple times and restarted Voice Attack. I also tried pointing to the default DCS folder and it still does not want too work.

Now I can do other commands in Vaicome like Request Taxi and such, I just can not issue any "Take" Commands well I can issue them and VA responds but in DCS it does not work..

Well I am pretty sure the lua file is correct because I get the module showing up in the PTT screen and the voice commands are recognised by VA. so I am really unsure why the "Take" commands are not working in DCS..

Going to post a couple screenshots here so you can see the PTT screen and VA Accepting the commands..

I did a recent Windows re-install and didn't re-download DCS, so there is no registry entry. The sim works straight off my DCS SSD.

My Viacom however, while it recognises my commands in VA, does not work in game and the aircraft does not show in the PTT screen.

I have set the custom path, registry fix and deleted the export LUA in the scripts folder but nothing works.

Is this due to lack of DCS on Windows registry?

Do you own the AIRIO extension and have it installed? If not, this is a known issue with this version and the workaround from @Hollywood_315 is to download the AIRIO dll and install it in the Vaicom directory (you do not need to purchase it)

Sent from my SM-T835 using Tapatalk

Do you own the AIRIO extension and have it installed? If not, this is a known issue with this version and the workaround from @Hollywood_315 is to download the AIRIO dll and install it in the Vaicom directory (you do not need to purchase it)

 

Sent from my SM-T835 using Tapatalk

Hi are you talking to me or the other poster? If your post was aimed at me I tried inserting that dll and it still did not work.

Just tried it too. No joy.

Just tried it too. No joy.

For your issue, try doing a repair of DCS - I use Skatezilla's graphical updater to do this

Well I did a Windows Upgrade from my USB disk and now the "Take" Commands are working.

so it was basically like reinstalling windows but it keeps all my programs in place.

https://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html

Well I did a Windows Upgrade from my USB disk and now the "Take" Commands are working.

 

so it was basically like reinstalling windows but it keeps all my programs in place.

 

 

https://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html

Sent from my SM-T835 using Tapatalk