Problem using TX6 for my own voice command

[sthompson]

I've found that I often cannot use TX6 to issue one of my own voice commands. For example, I have a command "Gear" to toggle the landing gear by transmitting a keypress G. It also writes a message to the log before and after the keypress. This works fine if I am running in hot mic mode, or if I use one of the TX1, TX2, TX3, or TX5 keys to open and close the mic. But it is hit or miss --mostly miss-- with TX6. The VA log shows that "gear" was recognized with high confidence (95-100 usually) and the appropriate messages get written to the log, but there is no response from DCS.

 

I wondered if it might be a timing issue, so I've tried pausing before saying "gear" after the mic is open. I've also tried increasing the time the G key is held to one second. These made no difference.

 

I've tested this in the Tomcat and the Mig-15 with similar experience in both.

 

Any thoughts about what might be causing this or how to debug the issue will be appreciated.

[Weegie]

It MIGHT be your timing, could be something else

 

First make sure there is nothing in Vaicom that uses the same word or phrase, or Vaicom will grab it and it won't get passed thru to your (appended) profile. If that is happening you'll see it registered in the log as Vaicom

 

Personally I used to have a lot of problems when using TX6 and what worked for me was issuing the command then immediatley coming off the switch/button/hat, keeping the PTT pressed seemed to cause problems and the command didn't get executed.

 

On a similar note if you then need to input further data (via voice) inside the command you don't need to press the PTT once the command is executing.

 

I thought that Hollywoood had fixed this via a recent update, to the best of my knowledge, but I haven't extensively tested it.

 

That might not help but perhaps worth a shot

[lxsapper]

10 hours ago, Weegie said:

It MIGHT be your timing, could be something else

 

First make sure there is nothing in Vaicom that uses the same word or phrase, or Vaicom will grab it and it won't get passed thru to your (appended) profile. If that is happening you'll see it registered in the log as Vaicom

 

Personally I used to have a lot of problems when using TX6 and what worked for me was issuing the command then immediatley coming off the switch/button/hat, keeping the PTT pressed seemed to cause problems and the command didn't get executed.

 

On a similar note if you then need to input further data (via voice) inside the command you don't need to press the PTT once the command is executing.

 

I thought that Hollywoood had fixed this via a recent update, to the best of my knowledge, but I haven't extensively tested it.

 

That might not help but perhaps worth a shot

I think a lot of the issues with TX6 come from when assigning the command to a button by default the "Execute this command when all buttons are released" seems to be checked for TX6 press (for joysticks). You must uncheck it! It should only be checked for TX release commands.