Is there a problem with Case III commands currently?

[TimSell75]

I have problems with the Supercarrier Case III commands which I did not notice before. The commands "Commencing" and "Checking In" are not recognized anymore. Others like "Plattform" or "Established" are though. If I give the commands via the "Options" Menu, they are working, so it seems to be related to the voice commands. Any ideas how to fix this or a a workaround?

Many thanks in advance!

[MAXsenna]

I have problems with the Supercarrier Case III commands which I did not notice before. The commands "Commencing" and "Checking In" are not recognized anymore. Others like "Plattform" or "Established" are though. If I give the commands via the "Options" Menu, they are working, so it seems to be related to the voice commands. Any ideas how to fix this or a a workaround?
Many thanks in advance!

What does the log say? You say the commands are not recognised?

Sent from my SM-A536B using Tapatalk

[TimSell75]

vor 8 Stunden schrieb MAXsenna:

What does the log say? You say the commands are not recognised?

Sent from my SM-A536B using Tapatalk
 

VA does process the commands as far as I can see and I can hear the beep sound, but they are not being carried out on DCS side. Works for other commands as before though (like Plattform or established). Strange

[TimSell75]

Just found out that the "See you at 10" command also is not processed. Vaicom does recognize it, but it is not accapted by the game. Only when I give the command via the normal Radio Options. Anybody else sees this error?

[MAXsenna]

Just found out that the "See you at 10" command also is not processed. Vaicom does recognize it, but it is not accapted by the game. Only when I give the command via the normal Radio Options. Anybody else sees this error?

Well, IF the correct audio is passed from VoiceAttack to the Microsoft Speech Recognition, which does the recognition, passed back to VoiceAttack and matches the keywords in the VAICOM VoiceAttack profile. (As you say, the log shows this). Then the VAICOM plugin is invoked and should trigger the command in DCS. If this does not happen, something is either wrong in VAICOM or DCS. Wouldn't be the first time they change something in DCS.

Sent from my SM-A536B using Tapatalk

[TimSell75]

vor 15 Stunden schrieb MAXsenna:

Well, IF the correct audio is passed from VoiceAttack to the Microsoft Speech Recognition, which does the recognition, passed back to VoiceAttack and matches the keywords in the VAICOM VoiceAttack profile. (As you say, the log shows this). Then the VAICOM plugin is invoked and should trigger the command in DCS. If this does not happen, something is either wrong in VAICOM or DCS. Wouldn't be the first time they change something in DCS.

Sent from my SM-A536B using Tapatalk
 

Yeah seems the updates are slowly breaking all the carrier commands. Which is a pitty as you are normally in a time critical situation and fiddeling with the comms menues is kind of "dangerous"

Edited December 7, 2024 by TimSell75

[MAXsenna]

Yeah seems the updates are slowly breaking all the carrier commands. Which is a pitty as you are normally in a time critical situation and fiddeling with the comms menues is kind of "dangerous"

I'm not sure you are aware. One can map a hat, (or buttons), to browse the radio menu while it's open now. So you won't actually lose a hat. Very convenient for stuff that "can't" be used with VAICOM.

Sent from my SM-A536B using Tapatalk

[TimSell75]

vor 16 Minuten schrieb MAXsenna:

I'm not sure you are aware. One can map a hat, (or buttons), to browse the radio menu while it's open now. So you won't actually lose a hat. Very convenient for stuff that "can't" be used with VAICOM.

Sent from my SM-A536B using Tapatalk
 

No did not know this. Will try to figure it out. Thanks!

[TimSell75]

vor 4 Stunden schrieb MAXsenna:

I'm not sure you are aware. One can map a hat, (or buttons), to browse the radio menu while it's open now. So you won't actually lose a hat. Very convenient for stuff that "can't" be used with VAICOM.

Sent from my SM-A536B using Tapatalk
 

Tried to do this. But unfortunately could not figure out how?

[MAXsenna]

58 minutes ago, TimSell75 said:

Tried to do this. But unfortunately could not figure out how?

 

I'll get back you with screenshots. Can't ever remember the "module"/category!

EDIT: Here you go. "Command Menu". I keep forgetting that

The red rectangle just point out a keybind conflict in the UI Layer. ED please fix. That's a default from you!  @NineLine@BIGNEWY

 

Sent from my SM-A536B using Tapatalk
 

Edited December 7, 2024 by MAXsenna

[TimSell75]

vor 13 Minuten schrieb MAXsenna:

I'll get back you with screenshots. Can't ever remember the "module"/category!

Sent from my SM-A536B using Tapatalk
 

That would be really nice

[MAXsenna]

Just now, TimSell75 said:

That would be really nice

Refresh the page. I just edited the post above.

[TimSell75]

vor 1 Stunde schrieb MAXsenna:

Refresh the page. I just edited the post above.

Thanks so much! I need to figure out how to bind these best with my controls, but might be a temporary help until Vaicom addresses these bugs

[MAXsenna]

Thanks so much! I need to figure out how to bind these best with my controls, but might be a temporary help until Vaicom addresses these bugs

Much obliged Tim! Just bind any hat like I did, up/down/sideways. It will only function with the menu when the menu is open. When the menu is closed it will work normally!
Cheers!

Sent from my SM-A536B using Tapatalk