VoiceAttack-profiles/docs/troubleshooting.md

Troubleshooting

This will fill up gradually with Troubleshooting tips as people run into common ones.

VoiceAttack does not understand me / mishears me / fires random commands

There is a thread on the VoiceAttack forums on how to set up your microphone and the speech recognition engine to work best.

If your microphone is bad and you still get erroneous recognitions when you are not speaking it is probably going to recognize the same command every time. You can remedy that by blocking the voice trigger. One-syllable triggers are especially prone to misrecognition.

1. Create a new command in your custom profile.
2. Set the “when I say” field to the trigger that gets misrecognized.

Adding the “Other” → “VoiceAttack Action” → “Ignore an Unrecognized Word or Phrase” action will also hide it from the VoiceAttack log when it is (wrongly) recognized. You might or might not want that.

Example for the “cruise” voice trigger of the Supercruise command:

!

Alternatively you can raise the minimum confidence level and call the underlying command to make misfires less likely:

!

There are a few examples in the Custom Profile Example.

VoiceAttack recognizes a command, but doesn’t do anything in game

Make sure you have a keyboard bind for whatever the command is supposed to do as outlined in Installing#Set Elite Keyboard Binds.

VoiceAttack talks over the COVAS voice

There is no way to know for sure when the ingame COVAS is talking to you, so there is no way to always prevent the two from speaking over each other.

You can however either disable TTS responses for events that you know will clash (or file a feature request if one is not optional yet). Alternatively, if you prefer the info given by VoiceAttack over the ingame COVAS, you can deactivate its response to these events in the ingame Audo settings:

!

While you’re in there you might as well get rid of the spoken FSD countdown that is off by one second …