Thrustmast T Flight HOTAS + VA + HCS voice pack --- anybody using the same?

So I have got VA plus the HCS voice pack and Thrustmaster T flight HOTAS (awesome stick for the cash)...

Does anyone use the same and how have you got the profiles setup? I am having loads of trouble getting some voice commands to work even when the key is bound correctly.

For instance - Balance power work but power to engines doesn't. Anyone come across that before and can point me in the direction of what I have done wrong as that is bound to be the problem :)

Thanks in advance Commander's
 
Last edited:
So I have got VA plus the HCS voice pack and Thrustmaster T flight HOTAS (awesome sick for the cash)...

Does anyone use the same and how have you got the profiles setup? I am having loads of trouble getting some voice commands to work even when the key is bound correctly.

For instance - Balance power work but power to engines doesn't. Anyone come across that before and can point me in the direction of what I have done wrong as that is bound to be the problem :)

Thanks in advance Commander's

I have the same joystick, am i missing out on something? ;')
 
Yes, have the same set-up as this as well and all working fine.

As BrewerGeorge says, training the Windows Voice Recognition system, at least 3 times, seems to solve most of the problems of unrecognised commands
 
Same HOTAS, VA is a huge part of my operation. Don't use any voice packs, I just make my own through TTS.

In addition to training Windows a number of times as mentioned, try to add different variations to the commands that give you trouble. For example, I changed mine to "Full engines" or "Full shields" because it was less words and quicker. The more you add to the command, the more likely it might miss a piece and not work at all. Too short a command can have the opposite problem, it fires off at noise that sounds like a match.

Open up like Notepad for the focus app, and try the different commands while watching the VA console, and see what it "thinks" you're saying. Some people with thicker accents have added or substituted the command with what VA thinks its hearing. It doesn't have to be right, it just has to be accurate as a trigger.
 
Assigning one of the buttons to be a switch mode button, so it doubles the amount of key binds you can have.
Before I started using VA, I had both button 3 and button 9 set up as switch buttons, to change what happened on the other hand's buttons. #3 is a really good one for shift because it's easy to hit by mistake, and using it as shift prevents you from doing something accidentally. But it's hard to hold it down and use the other buttons adroitly with the same hand. Then I hit on the idea of the opposite hand thing, so the shifted commands on the throttle take affect when #3 is down and the shifted commands on the stick are active when #9 is also down. #3 and #9 together are my Flight Assist Off.

I don't use most of those complicated bindings any more, though, since I started using Voice Attack.
 
...
Open up like Notepad for the focus app, and try the different commands while watching the VA console, and see what it "thinks" you're saying. Some people with thicker accents have added or substituted the command with what VA thinks its hearing. It doesn't have to be right, it just has to be accurate as a trigger.

When you say something on the log, and it give the "Unrecognized" command, you can double click on that line item and use that sound as the trigger. It will open the new command dialog. If you do this, definitely also make a compound command with the correct command so you'll remember what it is supposed to be not just what VA thinks it is.

Honestly, though, training Windows more is the best option.
 
Yep done that the command says its recognised in VA but nothing happens. Even though others do. Something to do with command bound to keys plus hotas maybe?
 
When you say something on the log, and it give the "Unrecognized" command, you can double click on that line item and use that sound as the trigger. It will open the new command dialog. If you do this, definitely also make a compound command with the correct command so you'll remember what it is supposed to be not just what VA thinks it is.

Honestly, though, training Windows more is the best option.

Yes, compensating should be if other things don't work well. Another key thing is your mic quality, it will make all the difference in the world.

But making multiple version of a command isn't just for misunderstood stuff, often times you might in the heat of battle or rushing say something close but not quite right, or pluralize something. I finally realize one of my commands, half the time I was saying "drives" and not "drive", and it was just enough to not work.

- - - - - Additional Content Posted / Auto Merge - - - - -

Yep done that the command says its recognised in VA but nothing happens. Even though others do. Something to do with command bound to keys plus hotas maybe?

Maybe in game it's not set right? If VA is recognizing your command, then do what VA is supposed to do. Maybe something in the controls setup for the game isn't right.
 
Back
Top Bottom