flyingflatfour

I pretty much tried every fix that I could find but I'll have a look at your link above ;-)

that's exactly what doesn't want to start

Well I just discovered that it does... as I perform the check-in call to the SuperCarrier, as soon as I say "marking moms" I hear the beep sound in the background and the command is sent to DCS. Indeed the SC responds when I am still talking (fuel state)

By the way, is there an option to tell Vaicom to wait until you release the PTT to send the commands to DCS?

Hi everyone, I've had some help in the VA discord channel. Turns out I had chosen the option "use installed speech platform speech engines" under the VA "system/Advanced" options tab. This is I guess because back when I installed VA for the first time, having a french version of Windows, I had no built-in engine in english. I turned it back to "use Built-in SAPI Speech Engines" and now, since I installed the US english voice and language pack under the windows settings panel, I can have access to the proper engine. I can even, from the VA "recognition" options tab, under "utilities", open up training mode and add/remove dictionary words. But I can still not launch the native MS app (the blue bar) either from the windows control panel nor from the Vaicom config panel... see images attached. Could someone please confirm that if I can access training and word editing from VA instead of the native blue bar, it still works as intended?? Thanks!

Thanks, I’ll do that

Thanks for the reply, but it seems it's not the problem. Just trying to start the speech recognition app directly from the control panel doesn't work either. Please see some screenshots of my setup. I have tried setting up a new Windows account to see if I had something corrupted in my account, but I still get the same message. I wonder if I could have deactivated a service needed for this to work? What I don't understand is that VoiceAttack still seems to work? :doh:

Hello, I have been trying to use the training mode to work, but when I click on the microphone icon under editor, this error message pops up. I have checked and English - US is checked everywhere. I tried finding a solution elsewhere on the internet, no joy.. I fear this may be due to some windows debloater program I used in the past. Any ideas?

Hi Hollywood, I have read the manual concerning keybinds but it's not that clear in my mind. I use the TM HOTAS Warthog with the CTS profile system, which is setup to be compatible with VAICOM PRO and SRS together. I have assigned VAICOM PRO nodes TX1, 2, 3 and 5 to joystick buttons DX20, 22, 23 and 21 respectively (I do not use easy comms) and have checked that they work as intended (press/release). I have checked that these are not assigned to any command within DCS controls menu. Still the problem persists... So I have tried another module, the Su-33, and there seems to be no problem there. I suspect there is a conflict with the CTS profile, which simulates the pinkie switch on the stick as a PTT when airborne, but in a non-conventional way through complex TARGET programming... I am in contact with the programmer to try to sort this out. Best regards!

Delayed commands Hi everyone, I've been having a very annoying issue lately using VA + VAICOM PRO with the F-5E (haven't tried using another aircraft): Even though the software recognizes my commands properly (as shown in VA window), they will very often be blocked from being passed right away on to DCS, when airborne. It took me some time to figure out that they would eventually be passed on when opening up the COMMS menu manually (in the F-5E, either using the throttle mic switch, the stick pinkie switch in flight or RALT+\). Strangely enough, the first press to open the COMMS menu doesn't work. The second press works and seems to "unblock" all commands that were queued up by VA+VAICOM. On the ground everything works normally and landing has the same "unblocking" effect on pending orders. Using the COMMS menu manually works everytime. In the VAICOM PRO settings I don't have the COMMS menu hidden option activated and I am using realistic comms in the DCS options. All nodes are properly showing up in the VAICOM status window and respond appropriately to joystick inputs. Using latest version of DCS stable, VA and VAICOM PRO with paid licences, under Windows 10 1903. HOTAS is Thrustmaster Warthog with CTS profile. I wonder if this has anything to do with the F-5E's pinkie switch: on the ground it acts as a NWS button, in the air as a PTT. Any help appreciated as it has been a deal breaker quite frankly :cry:

Thanks, can’t wait for the next stable release :thumbup:

Thanks

Thanks for the information, didn’t know about that. Will report further !

Sometimes the weapons release stops working, even though everyting is properly configured in the cockpit. Bombs or rockets just won't drop or fire no matter what. Restarting DCS fixes the issue... until it happens again randomly. Exiting/rejoining a MP server is not enough to clear the fault.

Sometimes the reticle settings will have no effect on it, as if it stays frozen in MSL mode. Depression doesn't affect the reticle either in MAN... This tends to happen in Multiplayer after some time in the session.