Underscores and Teamspeak

[bonesvf103]

I seem to recall hearing that VAICOM PRo has problems if your profile name uses spaces in it instead of underscores.

I also recall that it is recommended to start Vaicom Pro as administrator and waiting for it to load completely before you start Teamspeak or it might not  work.

Were either of these true, or still true now?

v6,

boNes

Edited October 30, 2023 by bonesvf103

[MAXsenna]

I seem to recall hearing that VAICOM PRo has problems if your profile name uses spaces in it instead of underscores.
I also recall that it is recommended to start Vaicom Pro as administrator and waiting for it to load completely before you start Teamspeak or it might not  work.
Were either of these true, or still true now?
v6,
boNes

You mean your Windows username, so spaces in the username profile? Never heard of that.
About admin, you mean VoiceAttack, right?
VAICOM is not an application per say, while VoiceAttack is. VAICOM is a plugin for VoiceAttack, and is started by VoiceAttack. exactly is your issue?
Cheers!

Edit: VoiceAttack might complain when other programs, like TeamViewer, are using the Microphone.

Sent from my SM-A536B using Tapatalk

[bonesvf103]

BY profile name, I mean within VoiceAttack, when you select via drop down menu which profile you want to use, which in this case is the VAICOM Pro one.  I had heard that the VAICONM Pro profile had to use underscores not spaces, but wasn't sure about that.

And yes, I misspoke and when I said starting VAICOM Pro, I meant Voice Attack.  So I remembered reading in the VAICOM Pro manual over a year ago that you had to wait for Voice Attack to start up completely and load your VAICOM Pro profile before starting Teamspeak or it might now work.

One more thing I wanted to add:  I have VoiceAttack set to run as admin, yet whenever I run it, it still brings up that dialogue box asking if I want to allow it to make changes to my computer.  Why is that?

Thanks.

v6,

boNes

[MAXsenna]

20 minutes ago, bonesvf103 said:

BY profile name, I mean within VoiceAttack, when you select via drop down menu which profile you want to use, which in this case is the VAICOM Pro one.  I had heard that the VAICONM Pro profile had to use underscores not spaces, but wasn't sure about that.

Never had any issues with that, would be a VoiceAttack issue in any case. The VAICOM profile "is all VoiceAttack" related and doesn't do anything except to trigger the plugin if the correct commands (keywords) are used. 

22 minutes ago, bonesvf103 said:

And yes, I misspoke and when I said starting VAICOM Pro, I meant Voice Attack.  So I remembered reading in the VAICOM Pro manual over a year ago that you had to wait for Voice Attack to start up completely and load your VAICOM Pro profile before starting Teamspeak or it might now work.

Again, this is all VoiceAttack. VAICOM in it itself only sends commands to DCS, and does neither listening nor recognition. Like I wrote, VoiceAttack might give a warning when other applications use the microphone, because they can be in conflict. Personally I have never had any issues. VoiceAttack needs to load a profile on startup. Doesn't need to be VAICOM, and you'll get the warning anyhow. 

24 minutes ago, bonesvf103 said:

One more thing I wanted to add:  I have VoiceAttack set to run as admin, yet whenever I run it, it still brings up that dialogue box asking if I want to allow it to make changes to my computer.  Why is that?

Yet again nothing to do with VAICOM as the application is VoiceAttack. Can't remember if I ever saw that one, and maybe checked "don't display again" or similar. You're better off asking in the VoiceAttack Discord, (those guys are really helpful), as the only changes on the computer VAICOM does, will be in DCS. The VoiceAttack manual might be worth checking out too.

Hope this helps! 

Cheers! 

[bonesvf103]

Thanks!

[sthompson]

I run VAICOM PRO within VoiceAttack with VA not running as administrator. It works just fine provided you make sure VA/VCP can modify the files they need to modify. If DCS is installed in a user changeable directory this is not a problem. If DCS is installed in The Program Files directory you may have to change its permissions to allow updates by an ordinary user. In my view this is a safer solution than giving VoiceAttack full admin rights on my computer.