ATC Issues: Can not change the airfield recipient

[Skinner]

All these Voice Commands are perfectly recognized: Nearest Airfield, the names of the alternative airfields, Inbound, Request vector, etc. But Vaicom  does not change the airfield recipient of the order. It assumes always that the recipient is the airfield from which I started the mission.

By means of the F10 Menu/ATC I’m able to change the airfield. But it is impossible by means of the vaicom pro. If I departed from Sukhumi, for example, it is impossible to change to another friendly airfield, Batumi as example.

VAICOM does not change the recipient of the order. Nearest Airfield does not work. There is not any voice command able to change the airfield.
I have the kneeboard extension. In the “ATC” I see the list of all the available airfields, arranged from the distance from my position.

 

I have the DCS release version (2.7.5) and I fly the F18.
I have uninstalled Voice Attack from “Program Files(86x)” folder and installed then in the ‘Program Files’ folder but no improvements observed.

I play with easy communications on. However I’ve tried the “select” voice command. Again, no results.

Thanks for help.
 

Edited September 19, 2021 by Skinner

[sthompson]

17 hours ago, Skinner said:

All these Voice Commands are perfectly recognized: Nearest Airfield, the names of the alternative airfields, Inbound, Request vector, etc. But Vaicom  does not change the airfield recipient of the order. It assumes always that the recipient is the airfield from which I started the mission.

By means of the F10 Menu/ATC I’m able to change the airfield. But it is impossible by means of the vaicom pro. If I departed from Sukhumi, for example, it is impossible to change to another friendly airfield, Batumi as example.

VAICOM does not change the recipient of the order. Nearest Airfield does not work. There is not any voice command able to change the airfield.
I have the kneeboard extension. In the “ATC” I see the list of all the available airfields, arranged from the distance from my position.

 

I have the DCS release version (2.7.5) and I fly the F18.
I have uninstalled Voice Attack from “Program Files(86x)” folder and installed then in the ‘Program Files’ folder but no improvements observed.

I play with easy communications on. However I’ve tried the “select” voice command. Again, no results.

Thanks for help.
 

 

Can you please turn on VAICOM debugging and post the VoiceAttack log that shows the incorrect behavior? That would help diagnose why this is not working for you. "Batumi, Select" should switch the recipient to Batumi, for example.

[Skinner]

Dear sthompson,

"Batumi select" does not work. Indeed, given that I have "easy comms on" the command "select" should be unnecesary.

Please find attached the VaicomPro log.

Thank you for your help!

 

VAICOMPRO.log

[sthompson]

First, Select is still necessary with Easy Comms on. Easy comms will automatically tune the radio, but you still need to tell VAICOM who is the intended recipient.

 

Second, looking at your log file, it appears that "Batumi" is being read as one sentence, and "Select" is being read as a second unrelated sentence. So "Batumi" ends up without enough information to make a command, and "Select" does not include the intended recipient.

 

Make sure you keep the TX4 key pressed continuously while giving the "Batumi, Select" command and that the pause between words is fairly short. If this does not solve the problems, please send a log again, but this time also send the VoiceAttack log (cut and paste from the VoiceAttack window to a text file) in addition to the VAICOM log. It's helpful to have both logs so we can make sure they line up. Also, please try to keep both short, with just enough to demonstrate the problem.

 

 

[Skinner]

Dear sthompson,

 

I've tried your kind suggestion. Keeping pressed continuosly TX4 button while giving the command "Batumi, Select", with no good results. It seems that the program after recognizing Batumi does not wait enough time to listen to the recipient.

 

Despite not having any logical basis, I've even tried deselecting TX4 after Batumi and selecting TX4 again and giving select: obviously with no good results.

 

Please find attached both log files. I've intended to keep them short.

 

Thank You for your support!

Voice Attack log.txt VAICOMPRO.log

[MAXsenna]

Can you post screens of your VAICOM settings?

Batumi is 131.000 and from the logs you're tuned to Sukhumi 129.000, and the select command doesn't switch to Batumi for you.

Have you tried other TXs than TX4. I've never used TX4 myself, but I did have some issues with Batumi in the Warthog myself a while back.

Are you trying a stock mission or a self made?

Cheers!

[Skinner]

[Skinner]

Dear MAXsenna,

 

I've post above the screens of the VAICOM settings.

 

This particular mission is self-made. I've noted the same problem in other missions (also self-made) in different maps. Regardless of the airfiled I'm calling Inbound, I've always receive the answer from the ATC of the airfield from I departed the mission.

 

Later, I will try other TXs than TX4.

 

Thank You!

[sthompson]

If I give the command "Batumi, Select" and release the TX key immediately after I say Select then I get the following in the VoiceAttack log (newest messages at the top):

 

 

Notice that the Select command is recognized only AFTER the TX4 release occurs. This is similar to what is going on in your log file, and likely is the cause of the problem. If instead I wait a second or two before releasing TX4 after I say Select I get the following:

 

 

Notice that VAICOM built a correct Select command in this case. (I did this without running a mission, which is why Batumi is not available.)

 

So the lesson is that you need to hold the TX key until you hear the audio hint (a high pitched beep) indicating that the command is complete.  This is documented (sort of) in the manual. On page 16 it says "Note: Commands are executed immediately and you can release PTT almost immediately, hold for another 0,5 second after you finish your voice command." So you can release the TX "almost" immediately, but not immediately.

 

 

[Skinner]

Sounds interesting!

As soon as I would be in front of my computer I would try it.

Thany You!!

[MAXsenna]

Sounds interesting!
As soon as I would be in front of my computer I would try it.
Thany You!!

I switched over to VSPX a long time ago. Might be a little more forgiving.

Sent from my MAR-LX1A using Tapatalk