*Solved* Vaicom Pro and SRS / TX Link

[AyeEe]

Hello,

I looked at the FAQ sticky and couldn't find an answer to my question.  I am trying to use TX Link in Vaicom so I can use SRS with it.  I want to make sure I understand how the TX Link function works.

TX1 - short press = enables vaicom to hear commands for AI

TX1 - short press again disables vaicom listening commands

TX1 - long hold = push to talk SRS activates, vaicom should not be active and listening

My problem is when I do the short press command for AI commands.  It is not consistent.  Sometimes the listening will resume and sometimes it stays suspended.  I also noticed in the VA program, the "Chatter Initialized, Resources added." lines keep popping up.  I asked a friend who uses VAICOM and they said that doesn't happen to them.  It triggers when I press TX1.  I also notice that this behaviour only happens when VOIP Control is set to "TX Link".  When TX Link is active, every other short hold command of the TX1 button does not resume the listening.  When I have VOIP Control set to Dynamic Switching, no problems whatsoever.  Here is a logfile of my VA.

Spoiler

6:53:44.182 TX1 | AN/ARC-210 - 1 AM 305.000 MHz: no tuned units.
6:53:44.180 Adding chatter resources.. Navy
6:53:44.180 Resources added. 
6:53:44.180 Chatter initialized. 
6:53:44.179 Resetting selected units.
6:53:44.179 Player UnLiBoG entered module FA-18C Hornet, unit callsign 131
6:53:44.179 Nearest ATC: Andersen AFB.
6:53:44.179 Adding themepack collections
6:53:44.179 Chatter theme set to Navy
6:53:44.178 ------------------------------------------
6:53:44.178 DCS mission | BZ_Training_MODS_Marianas_v033
6:53:44.060 Listening suspended
6:53:44.031 Joystick : 'Transmit TX1 press' (Long tap-coordinated)
6:53:44.030 Joystick : 'Transmit TX1 release'
6:53:42.234 TX1 | AN/ARC-210 - 1 AM 305.000 MHz: no tuned units.
6:53:42.097 Listening resumed
6:53:42.075 Joystick : 'Transmit TX1 press' (Long tap-coordinated)
6:53:40.631 Joystick : 'Transmit TX1 press' (Long tap-coordinated)
6:53:38.654 Listening suspended
6:53:38.637 TX1 | AN/ARC-210 - 1 AM 305.000 MHz: no tuned units.
6:53:38.634 Adding themepack collections
6:53:38.634 Chatter theme set to Navy
6:53:38.634 Adding chatter resources.. Navy
6:53:38.634 Resources added. 
6:53:38.634 Chatter initialized. 
6:53:38.633 DCS mission | BZ_Training_MODS_Marianas_v033
6:53:38.633 Resetting selected units.
6:53:38.633 Player UnLiBoG entered module FA-18C Hornet, unit callsign 131
6:53:38.633 Nearest ATC: Andersen AFB.
6:53:38.632 ------------------------------------------
6:53:38.494 Listening resumed
6:53:38.478 Joystick : 'Transmit TX1 press' (Long tap-coordinated)
6:53:36.751 Listening suspended
6:53:36.724 Joystick : 'Transmit TX1 press' (Long tap-coordinated)
6:53:35.082 TX1 | AN/ARC-210 - 1 AM 305.000 MHz: no tuned units.
6:53:34.956 Listening resumed
6:53:34.930 Joystick : 'Transmit TX1 press' (Long tap-coordinated)
6:53:33.463 Joystick : 'Transmit TX1 press' (Long tap-coordinated)

 

 

 

I followed the instructions and changed the bindings of TX1-TX6  to correlate with the TX Link, as shown in the instructions.  I changed long press joystick in VA to 100ms.

I've tried resetting everything in VAICOM.  I've tried re-installing both VoiceAttack and Vaicom.  I've tried repairing DCS. And I've also tried to delete export.lua.

 

I don't know what else to do, please help.

Edited August 25, 2022 by AyeEe

[sthompson]

What else are you running? I've seen reports of symptoms like this when incompatible software has been installed, like the NS430 module, or DICE.

 

[AyeEe]

40 minutes ago, sthompson said:

What else are you running? I've seen reports of symptoms like this when incompatible software has been installed, like the NS430 module, or DICE.

 

Hey! thanks for the reply! Oh yes, I do have DICE.  The dispenser auto program thing ?  How do I test if it's that ? how do i turn off DICE or remove it?

 

Edit: Okay, I removed DICE i think and I will try out Vaicom now.  Thanks again!

 

EDIT 2 : Okay, everything works properly now I think.  So if that is the case then it is DiCE for sure that was causing my problems.

 

Thanks so much sthompson

Edited August 24, 2022 by AyeEe

[Whistler_RIO]

thanks for reporting back. its helpful when folks do that. maybe even edit title with SOLVED if you like

[AyeEe]

3 hours ago, Whistler_RIO said:

thanks for reporting back. its helpful when folks do that. maybe even edit title with SOLVED if you like

Great Idea, I've actually tried to message hollywood to maybe put it in his FAQ.

This was a very frustrating problem, to say the least

[MAXsenna]

57 minutes ago, AyeEe said:

Great Idea, I've actually tried to message hollywood to maybe put it in his FAQ.

This was a very frustrating problem, to say the least

The FAQ is useless as it's corrupted by discussion. But it is documented somewhere that a previous version of DiCE is incompatible with VAICOM. I was so sure that was fixed. Alas.