VAICOM/VA Broke BROKE Broke!

[Fang333333]

First off,

Yay subforum! we NEEDED this!

 

Now,

I have basically been reporting MAJOR issues with VA/Vaicom over the last few months. It should be noted that all of this ran fine before Feb for me. Now VA is a big mess. I am copying and pasting some of my posts from another thread at Voice Atack that was started by somebody else having the same issues....

 

In the previous posts I could not officially say if it was the older version of DCS causing the problems with the current version VA. (Before DCS OB 2.6 for those who know what I am talking about). I have installed the latest DCS patch and VA is constantly disabling my mic before a command is given. Same as other DCS versions. This happens in all modules as I happen to own them all.

 

NOW

 

Voice attack does not like my mic, I have tried setting default in windows, frequencies nothing helps. It seems like Voice Attack maybe fighting to share the mic with other programs but that is really a complete guess. That is just the best way to describe problem #1.

 

When it does share the mic it still turns itself off after one second or crashes 95% of the time. When no module is loaded it seems to stop listening one second after mic activated. When module loads (F-18 for example) Mic starts to shutoff as described.

 

Also having F-14 Jester command issues as already reported.

 

ITS A MESS! MESSY MESSY MESS!

 

Also I now have a lot of sound crackling issues when VA and DCS and everything is running, but I assume that is also Windows Update.

 

I have disabled hotplug, (no_device_hotplug = true), tried every version of every software combo, reinstalls, some other ideas I am probably not thinking about, everything.

 

Visit the Thread reported by another user on VA's site here:

 

https://forum.voiceattack.com/smf/index.php?topic=3198.new#new

 

Please help, I used to LOVE using VA/VAicom/VP

 

Fang

Edited May 4, 2020 by Fang333333

[hornblower793]

Does this happen even if the Vaicom profile is not loaded in VA?

 

Sent from my SM-T835 using Tapatalk

[sthompson]

Fang, the VoiceAttack administrator has closed your thread on their site because you have never answered the question as to whether VoiceAttack behaves incorrectly when you disable Voiceattack plugins, which is a completely separate thing from disabling the DCS hotplug feature. You were asked this multiple times but never gave an answer.

 

If I were in your shoes I would completely uninstall DCS, Voiceattack, and VAICOM, then start reinstalling one thing at a time. No one can help you unless you can accurately and completely describe an installation procedure that produces a failure.

[Fang333333]

Fang, the VoiceAttack administrator has closed your thread on their site because you have never answered the question as to whether VoiceAttack behaves incorrectly when you disable Voiceattack plugins, which is a completely separate thing from disabling the DCS hotplug feature. You were asked this multiple times but never gave an answer.

 

If I were in your shoes I would completely uninstall DCS, Voiceattack, and VAICOM, then start reinstalling one thing at a time. No one can help you unless you can accurately and completely describe an installation procedure that produces a failure.

 

Hmm. Well if DCS hadn't stopped working completely I could answer them. Lol thank you for the heads up. I have tried reinstalling in several versions, pre 2.5.6 as well as mentioned the versions on the VA site. Only a week and they closed it lol...

[MAXsenna]

Hmm. Well if DCS hadn't stopped working completely I could answer them. Lol thank you for the heads up. I have tried reinstalling in several versions, pre 2.5.6 as well as mentioned the versions on the VA site. Only a week and they closed it lol...

 

Did you get this working?

[Fang333333]

Did you get this working?

 

Hello all,

 

I am extremely sorry that I have been away, honestly this problem has been getting the better of me and I had to walk away for a few. Thank you so much for asking because I have not got it working at all. Actually Vaicom has broken more for me...

 

I have made 2 videos showing the horrors I am dealing with Vaicom right now. Basically one is a full flight showing a typical day in Vaicom and the second video discuses the latest problem where as of 2 days ago Viacom stopped recognizing F10 commands. Basically midflight "Take 3" became "Take Three". Other commands "Take 4" Worked. I reset Luas in Viacom and say, "Take 4" works but then "Take 3" is recognized as "Take Three" And thus the option does not work. More on this in video: "DCS - Terminator 4.5: Viacom Day - Voice Attack/Viacom Broken!"

 

I HAVE PAINSTAKENLY TIMESTAMPED EVERY OCCURENCE IN THESE VIDEOS!

Please look in the descriptions and click on the timestamps so you do not have to hear me endlessly complaining lol. Sadly the full flight lost half of its timestamps, but it still shows almost every problem in Vaicom with the timestamps it has.

 

Long Flight video Showing EVERY OTHER Problem besides one where Viacom stops recognizing the xmit button and I need to restart it to work.

"DCS Vaicom/Voice Attack Less Than Steller"

 

Short video Showing new F10 problem.

"DCS - Terminator 4.5: Vaicom Day - Voice Attack/Vaicom Broken!"

 

 

Remember all of this has worked before...

 

 

Please help me Voice Attack Vaicom people! I love your product and I just want it to work like it did back in DCS OB 2.5.5 (Around Feb 12?)

 

Sorry for length of everything

Thank You so much

 

Fang

Edited May 29, 2020 by Fang333333

[hornblower793]

The realistic ATC extension licence issue at 8:52 in the first video is because there is a separate, low cost, VAICOM licence for all the new comms associated with the Super Carrier (option 2 at https://www.vaicompro.com/get-license.html)

 

 

For the rest, what other software are you running and have you installed the latest VAICOM version and set the new sliders on the VAICOM Config tab (bearing in mind that if you are running the new standalone stable version released today you will currently need to say it is OB and point the custom path to your install).

 

 

Could you post images of the various VAICOM and VA config screens so that we can see how it is setup?

[Fang333333]

Could you post images of the various VAICOM and VA config screens so that we can see how it is setup?

 

I did purchase the ATC license and figure that out at least...

Yes Thank you very much for looking at this and I hope it is what you are looking for.

 

 

I have a screen of task manager with the open tabs but generally

On a standard, non recorded, bare of the bone's setup I am running:

 

X-55 software for the HOTAS

X-65 Software for HOTAS

Simshaker for Aviators (2Buttkickers)

Voice Meter Banana (VB) to (Voice attack is set to receive straight from The Mindframe Headset Mic (I wear this over the rift). Voice attack playback sound is mixed through VB which is the computers default output for sound.

Strategic commander (For Microsoft game commander controller)

(Note) I do show in the bigger video that no ghost commands are being detected, in case you wondered.

 

I am using standalone, I own all the modules and Tacview

 

any ideas?

I tried playing today and it is just terrible...

Edited May 30, 2020 by Fang333333

[hornblower793]

I did purchase the ATC license and figure that out at least...

Yes Thank you very much for looking at this and I hope it is what you are looking for.

[ATTACH]237832[/ATTACH]

[ATTACH]237833[/ATTACH]

[ATTACH]237834[/ATTACH]

 

 

I have a screen of task manager with the open tabs but generally

On a standard, non recorded, bare of the bone's setup I am running:

 

X-55 software for the HOTAS

X-65 Software for HOTAS

Simshaker for Aviators (2Buttkickers)

Voice Meter Banana (VB) to (Voice attack is set to receive straight from The Mindframe Headset Mic (I wear this over the rift). Voice attack playback sound is mixed through VB which is the computers default output for sound.

Strategic commander (For Microsoft game commander controller)

(Note) I do show in the bigger video that no ghost commands are being detected, in case you wondered.

 

I am using standalone, I own all the modules and Tacview

 

any ideas?

I tried playing today and it is just terrible...

At a first look you seem to be pressing 2 TX buttons simultaneously each time - what HOTAS system are you using for this and how is it set up?

 

I will have a better look in the morning

 

Sent from my SM-T835 using Tapatalk

[Fang333333]

At a first look you seem to be pressing 2 TX buttons simultaneously each time - what HOTAS system are you using for this and how is it set up?

 

Thanks.

Unfortunately I highly doubt there is any kind of double press. I have had the x-55 software "test" window open during the glitches and it shows no inputs while it happens

 

I am using the x-55 HOTAS mainly. It is recognized by VA through the keyboard input, not joystick. The comms assignment is "right shift"+ 0/1/2...etc" depending on radio. Specifically this is assigned to the nipple switch using banding.

 

To put this to a test I have also tried holding shift 0 with no emulators running and the xmit still cuts off after 1 second.

 

Its strange becuase this literally became an overnight problem after update feb 12th. The person who originally posted the issue in VA forum claims they reinstalled an old version of vaicom then reinstalled the later feb 12th update and the problem ended. (At least somehing like that)

 

Of course thiis solution did not work as well for me

 

Thanks for looking at this

[hornblower793]

The problem is that the log window is clearly showing 2 presses at the same time - could you post a picture of your VA \ VAICOM PTT mapping - I am not saying that there is any issue it is just I work better with pictures :-)

Edited May 31, 2020 by hornblower793

[Fang333333]

Is this what you mean?

[hornblower793]

Yes

 

 

In one of your earlier posts you said that you were using keyboard mappings in the X55 software to map to VA and not joystick buttons. The VAICOM window is showing that you still have joystick buttons mapped to the PTT inputs and I wonder whether that might explain some of what you have been seeing (if you use the buttons for something else they may be triggering VA / VAICOM when not meant to). Try clearing the button mapping and see if that works (back up the profile first so you can swap back)

[Fang333333]

I did completely remove the joysticks' assignments from each transmit. It looks like this. Sadly this has had no effect. :cry:

[hornblower793]

What does the VA log now look like - is it still showing 2 TX buttons being pressed at the same time?

[Fang333333]

What does the VA log now look like - is it still showing 2 TX buttons being pressed at the same time?

 

I guess so I would say it largely remains unchanged. I the xmit turns on and off within a second.

[Fang333333]

Should I make another video or is there a log or something that could help finally move past this.

 

I would have never thought the first time I installed that update it would be the last time any of this worked properly.

[hornblower793]

I don't think another video will help - looking again at your log screenshot I notice that TX5 always seems to be pressed first - what do you have this mapped to, and is it mapped in any different way to the other TX nodes?

[hornblower793]

Fang,

 

 

A thought has just come to me - in one of the VAICOM updates there was a bit about removing Start / Stop VoiceAttack Listening commands from the VA commands for the TX Push and Release commands as this is now done inside VAICOM. I wonder whether you still have these in there and it may therefore be confusing the system.

 

 

To check this, open the VAICOM profile in VA using the pencil icon and then double click on each TX command in turn and delete any Start / Stop lines

[Fang333333]

To check this, open the VAICOM profile in VA using the pencil icon and then double click on each TX command in turn and delete any Start / Stop lines

 

Hi Hornblower, thanks for your response, I apologize but I had a few Windows Update bugs to tackle and had to take a break from this issue.

 

What you mentioned sounds like something interesting, this was broke after an update.

 

I am still having major issues, same issues as before

PLUS:

I started a new campaign in the P-51 Blue Bastards campaign.

In the missions it seems Vaicom will work before takeoff, than after takeoff voice commands are recognized, beeps, and than the command is delayed.

The delay becomes longer as mission progresses until by the time I reach the target, the command delays are MINUTE/S behind!

 

"Form up"

(Confirmed command beep)

Minutes later.

Computer = "Flight Close Formation"

 

This is similar to an issue in the f18 where Vaicom works 80% ok, until I reach carrier and it crashes and has issues. If I am landing Vaicom seems to be basicaly nonfunctional.

(I do have a recording of this if needed)

 

I eagerly looked at your recomendation,

And this is what I see. Sadly I am not seeing what you describe.

 

 

Thank you for looking at this,

I'm really losing hope with this so the forum is helping me keep going.

 

Fang

[Fang333333]

VAICOMPRO.log

VAICOMPRO.export.lua

[MAXsenna]

Are you using keyboard and not joystick/HOTAS?

 

Sent from my ANE-LX1 using Tapatalk

[Hollywood_315]

Hi there

 

Your log shows a few very strange audio inputs

of fish off of offf off off off off

This suggests some major audio input problem.

 

Couple of recommended steps:

 

- Check your mic routing disabling any driver enhancements and things like banana voicemeter

- Disable options: Import F10 Menu, Import new theaters, Import new modules

- Reset keywords database with Reset page

- Use Config/Export to get a fresh VAICOM PRO for DCS World.vap profile and import

 

Then test again.

Grtz

[Greyman]

Asus Sonic Studio can be a PIA too

[Fang333333]

Are you using keyboard and not joystick/HOTAS?

 

Sent from my ANE-LX1 using Tapatalk

 

Hi max, thanks for asking I am using the keyboard with "shift" keys "0-5) for TX 1-5.

 

This is emulated through the Saitek X-55 software. The softwware shows no ghost input on my end if you were curious.