WhisperAttack - OpenAI Whisper Voice Recognition and injection into VoiceAttack

[macemi]

Yes, same result when pasting text from other sources, so this behavior is not normal? However, I’m experiencing the issue regardless of the settings, whether VR or fullscreen on a monitor. Changing the monitor resolution also doesn’t have any effect.

[sleighzy]

6 minutes ago, macemi said:

Yes, same result when pasting text from other sources, so this behavior is not normal? However, I’m experiencing the issue regardless of the settings, whether VR or fullscreen on a monitor. Changing the monitor resolution also doesn’t have any effect.

Yeah doesn't sound like a WhisperAttack issue. I'll test it on my end in the coming days when I get a chance to see if the notepad is just broken in DCS, or if it's something else.

[macemi]

@sleighzy have you got around to testing it yet?

[sleighzy]

On 8/10/2025 at 10:08 PM, macemi said:

@sleighzy have you got around to testing it yet?

Hey mate, sorry for the late response. PC died so haven't gotten to it yet, working on getting it back up and running again.

[macemi]

Hey mate no worries! Hope he will be well soon. 

[j9murphy]

For those of you using WhisperAttack... do find it to be a significant upgrade?  Does it enable more flexible speech input - like liberal use of callsigns and more flexible phrasing?

[sleighzy]

16 hours ago, j9murphy said:

For those of you using WhisperAttack... do find it to be a significant upgrade?  Does it enable more flexible speech input - like liberal use of callsigns and more flexible phrasing?

If you’re talking about integration with Vaicom, then no. Vaicom has a specific command structure and the required keywords within it so whatever WhisperAttack outputs also has to match this.

However, you can use the word mapping replacement functionality in WhisperAttack to achieve this, depending on what you had in mind. For example, if you’re wanting to say certain call signs, ie Vaicom doesn’t support sender call signs, then you could use the word mappings to replace that call sign with a blank. Or even replace with your own different call signs (although changing call signs can also be done using Vaicom aliases) This means you can use it in your speech but it will be removed before being sent to VoiceAttack/Vaicom. The same thing applies to flexible phrasing. As long as you say those in a specific way (or various combinations of them) you can have the word mappings replace that text with the required command for Vaicom. 

Edited yesterday at 04:25 AM by sleighzy

[j9murphy]

9 hours ago, sleighzy said:

If you’re talking about integration with Vaicom, then no. Vaicom has a specific command structure and the required keywords within it so whatever WhisperAttack outputs also has to match this.

However, you can use the word mapping replacement functionality in WhisperAttack to achieve this, depending on what you had in mind. For example, if you’re wanting to say certain call signs, ie Vaicom doesn’t support sender call signs, then you could use the word mappings to replace that call sign with a blank. Or even replace with your own different call signs (although changing call signs can also be done using Vaicom aliases) This means you can use it in your speech but it will be removed before being sent to VoiceAttack/Vaicom. The same thing applies to flexible phrasing. As long as you say those in a specific way (or various combinations of them) you can have the word mappings replace that text with the required command for Vaicom. 

Thank you for the reply, very helpful!

[sleighzy]

47 minutes ago, j9murphy said:

what does it mean when I see this message in VoiceAttack?

9:11:38.804 UNABLE TO EXECUTE EXTERNALLY INITIALIZED COMMAND. COMMAND NOT AVAILABLE (Chief place the wheel chocks)
 

Just caught up with you in the Discord server so looks like we're all sorted.

EDIT: for anybody else who sees similar errors, i.e. "COMMAND NOT AVAILABLE" these errors means it didn't find the sentence in the VoiceAttack keywords. For this particular one Vaicom has two different commands for this, one has "wheelchocks" and the other has "wheel chocks". WhisperAttack transcribes this to "wheel chocks" (with a space) so will work depending on which Vaicom command you use. You can workaround this by adding the Vaicom command to the word mappings file with a replacement of "wheel chocks" to "wheelchocks", e.g. "place the wheel chocks" -> "place the wheelchocks". Note, you can do this via Vaicom aliases in their editor as well, so whichever is easiest for you.

Edited 9 hours ago by sleighzy