I have a deep Texas accent. Hard for ANY Yankee to understand me. LOL
One of my friends has a pronounced Missouri accent and uses Voice Attack. He needed to train the software several times before it started to get reliable.
Some tips I've found helpful:
1> To Thud's point, enunciation is very important -- try to emulate newscasters with that flatter Midwestern sound if you can (or keep training the software til it understands your accent).
2> Speak evenly and clearly, and in the same tone. Esp. in combat situations, getting excited (or too loud) can spoof VA into not understanding
3> Use a PTT for VA. Think what you want to say, then, PTT and say only that... VA actually can pick up extraneous noise(s) well enough to mess up a command
4> Use full words for commands over abbreviations. For Example: "ILS button" may, or may not work well for you (it did not for me), but "Landing System button" works very well.
5>One of my biggest troubles is remembering the exact commands. I've found that following a "standard" tends to help, as does allowing more optional words. For instance, I tend to create my commands in a specific pattern when possible --> System, Action, Parameters. Easy Example: "Battery On". That's about as simple as it gets, but in actual practice, I also tended to say "Battery Switch On" or "Turn Battery Switch On" -- which, of course, wouldn't work... The fix? Allow optional words. So, my Battery command actually looks like this:
[Turn; Toggle;] Battery [Switch;] [On; Off]
In this case, *any* of the above commands will work as expected -- the only required parts are Battery and On or Off. The one caveat to that approach is that it can make your command file quite a bit larger in memory usage as it stores each possible command permutation. If your system is on the edge of being marginal, this could present problems. For me though, I've found that the flexibility far outweighs that risk. YMMV.
Hope that helps!
Cheers,
4 ~S!~
