Bugs VA / Vaicom pro

[Magoa]

Hello.
We are several to use VA and VAICOM in multiplayer (on dedicated servers or not).
We encounter different problems in the form but identical in the substance.

• Easy communication switches on or off in an unexplained way and this despite the change of options, knowing that we want it to be on off.
• The commands are not addressed to the right tankers for example com1 set on Arco1-1, the voice command is addressed to shell 1-1 (both tankers are in flight)
• Some commands remain unanswered (taxi request, refueling request, ...) and this while the radio frequencies are the right ones.
• These bugs are random between our configurations (not the same voice command for example, not the same tankers), it can work 5 minutes then rebugger, idem after a reboot.
• Note that when we share the same VA profile and the same Vaicom dictionary the same problems described above appear.

For my part, I have even completely re-installed VA and Vaicom and all my modules, made new VA profile, despite that we always fall back on the same problems that I summarize as follows:

• Impossible to freeze our choice on Easycomm Off
• The commands do not address the "object" defined by the radio frequency
• The commands, objects and radio frequencies with these malfunctions are not identical between players on the same map.

It is frustrating not to be able to fully exploit the VA / Vaicom tool.

Thank you in advance for the leads you could share with us.

Sincerely

[sthompson]

22 hours ago, Magoa said:

Hello.
We are several to use VA and VAICOM in multiplayer (on dedicated servers or not).
We encounter different problems in the form but identical in the substance.

• Easy communication switches on or off in an unexplained way and this despite the change of options, knowing that we want it to be on off.
• The commands are not addressed to the right tankers for example com1 set on Arco1-1, the voice command is addressed to shell 1-1 (both tankers are in flight)
• Some commands remain unanswered (taxi request, refueling request, ...) and this while the radio frequencies are the right ones.
• These bugs are random between our configurations (not the same voice command for example, not the same tankers), it can work 5 minutes then rebugger, idem after a reboot.
• Note that when we share the same VA profile and the same Vaicom dictionary the same problems described above appear.

For my part, I have even completely re-installed VA and Vaicom and all my modules, made new VA profile, despite that we always fall back on the same problems that I summarize as follows:

• Impossible to freeze our choice on Easycomm Off
• The commands do not address the "object" defined by the radio frequency
• The commands, objects and radio frequencies with these malfunctions are not identical between players on the same map.

It is frustrating not to be able to fully exploit the VA / Vaicom tool.

Thank you in advance for the leads you could share with us.

Sincerely

Regarding the tankers. Do you use the "Select" command before trying to contact them. I've found that usually solves the problem, unless there is more than one tanker with the same callsign.

Regarding Easy Comms. Are you saying that this behavior occurs only when running VAICOM, everything else the same? (I've been frustrated when MP missions force Easy Comms on, but that isn't a VAICOM issue, and can even occur in a SP mission if the mission designer choose to enforce easy comms.) If so, can you be more precise about symptoms? Does killing VoiceAttack while still in mission restore normal behavior, for example? It might be helpful to post some examples from the VA log when VAICOM debug is turned on. (I leave it on all the time since it has very low overhead and provides insights into what VAICOM is doing).

Regarding "The commands do not address the object defined by the radio frequency," VAICOM does not define recipients using the radio frequency (and never has). That is not how it works. You need to use the VAICOM "select" functions to choose the recipient, either by using an explicit select command, or by using the "instant select" method. Otherwise there is a default recipient, depending on the command (typically the closest recipient of the correct type at the time VAICOM first started communicating with the mission). If the recipient selected by VAICOM is not on the tuned radio channel you are not going to get a reply. That is not a bug.

VAICOM relies on local network communication between the VA plugin and DCS. I suspect that some problems occur when DCS gets busy, leading to dropped messages. If so, this is not so much a bug as it is a performance issue. Frustrating nevertheless.

 

[Magoa]

Thank you sthompspon for your response and sorry for my late return.  I am going to look at the tracks you mention and come back to give you a feedback with the VA debug logs.

[sthompson]

43 minutes ago, Magoa said:

Thank you sthompspon for your response and sorry for my late return.  I am going to look at the tracks you mention and come back to give you a feedback with the VA debug logs.

If you are referring to DCS track files, don't bother checking them. VAICOM commands bypass the menu system and so are not registered in track files. This means that DCS track files created while using VAICOM do not work properly even if VAICOM works perfectly.

[Magoa]

Hie.

lol, "look at the tracks", it's a French expression tracks = indices / indexes.

1/ Below are the logs of my request for authorization to drive on Batumi:
 

Quote

 

5:36:47.411 Listening suspended
5:36:47.265 Joystick : 'Transmit TX1 release'
5:36:45.871 Done.
5:36:45.869 Constructing message...
5:36:45.859 TX1 | COMM1: ARC-210: [ Air Traffic Controller ] ,  [ Request Taxi for Takeoff ]   
5:36:45.851 Recipient for ATC set by call contents.
5:36:45.851 Identified unit: Batumi with id 5000022
5:36:45.851 Getting selected unit for category ATC
5:36:45.847 Have result, identified as command: Riqouest Taxi for Teckeoff
5:36:45.845 Captured sentence: riqouest taxi for teckeoff
5:36:45.822 Recognized : 'riqouest taxi for teckeoff'
5:36:41.582 TX1 | COMM1: ARC-210 AM 310.000 MHz tuned for AWACS unit Wizard1-1 [AI]
5:36:41.582 TX1 | COMM1: ARC-210 AM 310.000 MHz tuned for AWACS unit Wizard1-1 [AI]
5:36:41.582 TX1 | COMM1: ARC-210 AM 310.000 MHz tuned for AWACS unit Wizard1-1 [AI]
5:36:41.582 TX1 | COMM1: ARC-210 AM 310.000 MHz tuned for AWACS unit Wizard1-1 [AI]
5:36:41.420 Listening resumed
5:36:41.281 Joystick : 'Transmit TX1 press'
5:36:40.941 Joystick : 'Transmit TX1 release'
5:36:40.184 Listening suspended
5:36:40.103 TX1 | COMM1: ARC-210 AM 310.000 MHz tuned for AWACS unit Wizard1-1 [AI]
5:36:40.103 TX1 | COMM1: ARC-210 AM 310.000 MHz tuned for AWACS unit Wizard1-1 [AI]
5:36:40.103 TX1 | COMM1: ARC-210 AM 310.000 MHz tuned for AWACS unit Wizard1-1 [AI]
5:36:40.100 Chatter initialized.
5:36:40.100 Resources added.
5:36:40.100 Adding chatter resources.. NATO
5:36:40.100 Chatter theme set to NATO
5:36:40.100 Adding themepack collections
5:36:40.099 No new ATCs were found.
5:36:40.099 Scanning for new theater.
5:36:40.099 Nearest ATC: Batumi.
5:36:40.098 Player Magoa entered module FA-18C Hornet, unit callsign Enfield31
5:36:40.098 Resetting selected units.
5:36:40.098 DCS mission | AVM_kobuleti_V.3.25
5:36:40.098 ------------------------------------------
5:36:39.975 Listening resumed
5:36:39.761 Joystick : 'Transmit TX1 press'
5:36:24.697 Opening Configuration window
5:36:24.424 Shortcut : 'Configuration'
5:35:32.389 Chatter initialized.
5:35:32.389 Resources added.
5:35:32.388 Adding chatter resources.. NATO
5:35:32.388 Chatter theme set to NATO
5:35:32.388 Adding themepack collections
5:35:32.367 No new ATCs were found.
5:35:32.367 Scanning for new theater.
5:35:32.367 Nearest ATC: Batumi.
5:35:32.367 Player Magoa entered module FA-18C Hornet, unit callsign Enfield31
5:35:32.366 Resetting selected units.
5:35:32.365 DCS mission | AVM_kobuleti_V.3.25
5:35:32.364 ------------------------------------------
5:35:32.076 Plugin 'VAICOM PRO for DCS World' initialized.
5:35:32.059 Ready for commands.
5:35:32.058 Startup finished.
5:35:32.017 Listening suspended
5:35:30.295 Chatter initialized.
5:35:30.294 Resources added.
5:35:30.293 Adding chatter resources.. NATO
5:35:30.293 Chatter theme set to NATO
5:35:30.292 Adding themepack collections
5:35:30.287 No new DCS modules to import.
5:35:30.286 Success.
5:35:30.286 Building master labels table...
5:35:30.285 Success.
5:35:30.275 Building kneeboard tables...
5:35:30.273 Success.
5:35:30.266 Building master keywords table...
5:35:30.265 Setting menu F10 item Action JTAC Status with actionIndex 4 as command 20053 Action JTAC Status
5:35:30.265 Setting menu F10 item Action List Radio Beacons with actionIndex 3 as command 20052 Action List Radio Beacons
5:35:30.265 Setting menu F10 item Action KOBULETTI with actionIndex 2 as command 20051 Action KOBULETTI
5:35:30.265 Setting menu F10 item Action frappe artillerie 2 with actionIndex 1 as command 20050 Action frappe artillerie 2
5:35:30.265 Setting menu F10 item Action frappe artillerie 1 with actionIndex 0 as command 20049 Action frappe artillerie 1
5:35:30.265 Setting menu F10 item Action 3 minutes with actionIndex 127 as command 20048 Action 3 minutes
5:35:30.265 Setting menu F10 item Action 2 minutes with actionIndex 122 as command 20047 Action 2 minutes
5:35:30.264 Setting menu F10 item Action 1 minute with actionIndex 116 as command 20046 Action 1 minute
5:35:30.264 Setting menu F10 item Action 30 seconds with actionIndex 115 as command 20045 Action 30 seconds
5:35:30.264 Setting menu F10 item Action 15 seconds with actionIndex 114 as command 20044 Action 15 seconds
5:35:30.264 Setting menu F10 item Action 10 seconds with actionIndex 113 as command 20043 Action 10 seconds
5:35:30.264 Setting menu F10 item Action 5 seconds with actionIndex 112 as command 20042 Action 5 seconds
5:35:30.264 Setting menu F10 item Action Off with actionIndex 111 as command 20041 Action Off
5:35:30.264 Setting menu F10 item Action Metric (Kilometers,Meters) with actionIndex 110 as command 20040 Action Metric (Kilometers,Meters)
5:35:30.264 Setting menu F10 item Action Imperial (Miles,Feet) with actionIndex 109 as command 20039 Action Imperial (Miles,Feet)
5:35:30.264 Setting menu F10 item Action Bullseye (BULLS) with actionIndex 107 as command 20038 Action Bullseye (BULLS)
5:35:30.264 Setting menu F10 item Action Military Grid (MGRS) with actionIndex 106 as command 20037 Action Military Grid (MGRS)
5:35:30.264 Setting menu F10 item Action Lat/Lon Degree Dec Min (LL DDM) with actionIndex 105 as command 20036 Action Lat/Lon Degree Dec Min (LL DDM)
5:35:30.263 Setting menu F10 item Action Lat/Lon Degree Min Sec (LL DMS) with actionIndex 104 as command 20035 Action Lat/Lon Degree Min Sec (LL DMS)
5:35:30.263 Setting menu F10 item Action Get informtion for Shell1-1 with actionIndex 80 as command 20034 Action Get informtion for Shell1-1

 

 

2/ If I hear and restart VA with DCS running, EasyComm stays on.

Edited December 14, 2021 by Magoa

[Magoa]

3/ Thank you for the "select" command that I did not know.
My settings are on "instant select" so it is handled automatically

And finally the screens of my Vaicom Pro settings

[sthompson]

8 hours ago, Magoa said:

Hie.

lol, "look at the tracks", it's a French expression tracks = indices / indexes.

1/ Below are the logs of my request for authorization to drive on Batumi:
[the rest deleted...]

 

So it appears that the "request taxi to runway" was sent by VAICOM to DCS. Did it appear as a player command in DCS? For example, did you hear the player voice echo the command or was it listed on the DCS screen? If so then DCS did receive the command. Otherwise something is failing in the communication between VAICOM and DCS and you might report it to the developer.

Assuming DCS did receive the command, if Batumi did not respond the most likely cause is a mismatch of coalition. If you are in one coalition and Batumi is another coalition then it will not respond.

EDIT: Looking at your log file again it does not appear that you had Batumi tuned on COM1. The frequencies for Batumi are 40.400 MHz, 131.000 MHz, 260.000 MHz, and 4.250 MHz. You had your radio tuned to 310.000 MHz. If you had Easy Comms on then this wouldn't matter, because DCS would change the tuning for you. Another problem is that you never specified Batumi as the recipient, but it was selected as the default ATC because it was closest at the start of the mission (or when you restarted VA if already in the mission). Instant Select will select Batumi, if you name Batumi in the command (which you did not). However it won't tune the radio for you. "Select Tunes Radio" will tune the radio for you only if you give an explicit Select command. 

Edited December 15, 2021 by sthompson

[Magoa]

Hello.  Yes I do have feedback from my pilot's request, so Vaicom is communicating well with DCS.  But I don't have Batumi's answer.  In the example, I have not set the radio frequency because "instant select" is activated but the result is the same when I select the correct frequency.  Batumi is indeed in the same coalition as me.  I would do the tests again this evening, because at the threshold of the runway, the take-off request command works and the tower responds!

[Magoa]

Hello.

Feedback from the tests carried out.

The “taxi request” response works with hot airplanes under certain conditions.

1 / the plane has to roll !

2 / In the order of the planes allowed to taxi on the taxi (interactions with AI planes).

For the "easy com on / off".

To switch off on the dedicated server, you must first launch a local mission, then launch the dedicated server.

This technique may not be suitable for everyone, but the two of us have solved our worries this way.

Thanks for the help and advice.

[The LT]

Can you try something for me? Do you own NS430 module? If you do, could you try switching it off in DCS module manager and see the behaviour of the Easy Comms?

[Magoa]

Hie TheLT. I don’t have this module, sorry. 

[MAXsenna]

Hi. I've re-read through the thread. I cannot find an answer where you confirm that Easy comms is not enforced in the mission. Can you check again?
Can you also check if you have the issue in single player at Batumi?
DCS can be very finicky about response from ATC depending on where you are when you issue the command. And can change from airfield to airfield. If AI is around, and have started taxiing, you might not get a response immediately too. A while back, I got a "hold position" response every other second, until ATC cleared for taxiing. But I haven't seen that in a while.

Sent from my MAR-LX1A using Tapatalk

[Magoa]

Hello and thank you Maxsenna.

The current solution found is to first launch a single player mission (easycomm appears on), disconnect and launch the multiplayer mission (easycomm appears off).

I'm wondering if the voice attack profile might be corrupted.

[Oban]

I'm having issues after the past couple of updates with the F18C, when I tune the radio in, both UHF and VGH to 127.500 and call "Stenis" .."Inbound" I no longer hear the response, even trying to "call the ball" on finals it doesn't seem to transmit, but the LSO will talk me down, and grade me?

Weird.

[Magoa]

With the latest dcs beta update a new bug appears among users.  The radio menu is displayed on the screen without any prompting from the player (voice or manual).  The radio menu reopens even if you close it.

[MAXsenna]

Hello and thank you Maxsenna.
The current solution found is to first launch a single player mission (easycomm appears on), disconnect and launch the multiplayer mission (easycomm appears off).
I'm wondering if the voice attack profile might be corrupted.

Sorry for the late reply.
No, that cannot be it, as VoiceAttack doesn't know about DCS.
VAICOM talks directly with DCS and only uses VA as a gateway to the Microsoft Speech Recognition.
It does sounds strange though.

Sent from my MAR-LX1A using Tapatalk

With the latest dcs beta update a new bug appears among users.  The radio menu is displayed on the screen without any prompting from the player (voice or manual).  The radio menu reopens even if you close it.

Sounds like you updated DCS without closing VoiceAttack first. That leads to problems, but is usually solved by closing both, and then start VA before DCS.
Do you still have this issue?

Sent from my MAR-LX1A using Tapatalk

[Magoa]

Quote

No, that cannot be it, as VoiceAttack doesn't know about DCS.
VAICOM talks directly with DCS and only uses VA as a gateway to the Microsoft Speech Recognition.
It does sounds strange though. 

yes strange but this no solution works
 

Quote

Sounds like you updated DCS without closing VoiceAttack first. That leads to problems, but is usually solved by closing both, and then start VA before DCS.
Do you still have this issue? 

no, the update was done with the software closed.  The problem persists but a priori only near the bases and aircraft carriers (to be checked with the tankers).  I am not the only one I know at least two people in the same situation

[MAXsenna]

No, that cannot be it, as VoiceAttack doesn't know about DCS.
VAICOM talks directly with DCS and only uses VA as a gateway to the Microsoft Speech Recognition.
It does sounds strange though. 

yes strange but this no solution works
 

Sounds like you updated DCS without closing VoiceAttack first. That leads to problems, but is usually solved by closing both, and then start VA before DCS.
Do you still have this issue? 

no, the update was done with the software closed.  The problem persists but a priori only near the bases and aircraft carriers (to be checked with the tankers).  I am not the only one I know at least two people in the same situation
You misunderstood. I was referring to the "corrupt VoiceAttack profile". That cannot be it, as VoiceAttack does not communicate with DCS. The only way VoiceAttack manipulates DCS in anyway, is if you have standard keybind commands in VoiceAttack, focused to DCS's Window.

As for the popping menus. By any chance, have you un-checked "hide menus" in the VAICOM control panel?
And have you configured PTT buttons in the DCS modules as the same TX buttons in VAICOM? (These are of course in the VA profile, but the "invoke" VAICOM plugin command, goes to VAICOM, not DCS).

I want be able to test for another week, but I anticipated and expect issues when I read the changelog for the latest update to the Voice Chat feature.
But I'm sure it will quickly be solved by @Hollywood_315 if we can drill down and find the similarities about this issue.

Sent from my MAR-LX1A using Tapatalk

[Magoa]

On 12/28/2021 at 9:52 PM, MAXsenna said:

You misunderstood. I was referring to the "corrupt VoiceAttack profile". That cannot be it, as VoiceAttack does not communicate with DCS. The only way VoiceAttack manipulates DCS in anyway, is if you have standard keybind commands in VoiceAttack, focused to DCS's Window.

As for the popping menus. By any chance, have you un-checked "hide menus" in the VAICOM control panel?
And have you configured PTT buttons in the DCS modules as the same TX buttons in VAICOM? (These are of course in the VA profile, but the "invoke" VAICOM plugin command, goes to VAICOM, not DCS).

I want be able to test for another week, but I anticipated and expect issues when I read the changelog for the latest update to the Voice Chat feature.
But I'm sure it will quickly be solved by @Hollywood_315 if we can drill down and find the similarities about this issue.

Hello and thank you for your answers.
"Hide menus": I prefer to see the menus because I'm not expert enough yet. But I will test without.

The PTT buttons are configured identically in DCS and VoiceAttack, I can confirm that.

[MAXsenna]

Hello and thank you for your answers.
"Hide menus": I prefer to see the menus because I'm not expert enough yet. But I will test without.
The PTT buttons are configured identically in DCS and VoiceAttack, I can confirm that.

Ok. If you have not hidden the menus, they will of course show. If the PTT in DCS is bound the same TX in VAICOM, they will of course also show.
Do you have blinking menus? If yes, there are solutions in the stickies.
If you're problem is not related to this, I can only guess it has to do with the new Voice Chat.

Sent from my MAR-LX1A using Tapatalk

[Magoa]

Hello.

Indeed it looks like flashing menus (turns on without prompting) but it does not turn off.

Since this weekend I had to do a full reinstallation (for other reasons) by Saturday I will resume my full configuration of VA and Vaicom.  As such I could tell you if I have the same problem.  But I am interested by stickies.

[MAXsenna]

32 minutes ago, Magoa said:

Hello.

Indeed it looks like flashing menus (turns on without prompting) but it does not turn off.

Since this weekend I had to do a full reinstallation (for other reasons) by Saturday I will resume my full configuration of VA and Vaicom.  As such I could tell you if I have the same problem.  But I am interested by stickies.

Well, if you do the installation from scratch on a new Windows installation. Install an update DCS first. Then VoiceAttack, finally VAICOM and you should bee good to go without any blinking menus. 

Also, for the future, make sure DCS is updated while VoiceAttack is off. And that VoiceAttack is started before DCS. I prefer to use Skatezilla's excellent updater/launcher, which makes me able to choose when I update DCS and not starting it after the update. So I can easily handle when VoiceAttack is on/off in the process. The app has also a lot of other nifty features.