jzakrzeski

Never used easy comms with vaicom, only for a few flights initially when I started DCS. The LOS angle is interesting, come to think of it that holds water. Often commands don't work immediately then suddenly do, say, when I get closer to the airfield or when I'm near my squad again. Odd that it would affect an "Options" calls to open the menu but it could be a factor. I'll experiment with this next time I get a chance.

I am having this exact same issue with the P-51 and Vaicom Pro. It affects only the P-51, and not just in the Blue-Nosed Bastards of Bodney campaign, it's in every mission you might fly with the P-51 module. I can, in the same session, fly the F/A-18C and Vaicom works flawlessly. When in the P-51, commands are only instantaneous while on the ground, once airborne, they are massively delayed. Even saying "options" to bring up the on-screen menu will sometimes take upwards of 2 minutes to appear, whereby I will usually just fumble for the F-keys to select commands instead of waiting for Vaicom to send them to the sim. The commands are sent instantly when doing so, it's something about the interface between Vaicom and comms with the P-51 module that appears to be borked. To be fair, I can't be sure it has ever worked myself, as I started flying the P-51 a couple weeks ago, and I installed/purchased Vaicom in May of this year. I am fairly new to DCS (since April), but I'm reasonably sure my install is correct and my configuration in Vaicom is working, as evidenced by the perfect functionality in other DCS modules/campaigns/missions. I'm using the Steam version of DCS on the openbeta branch. EDIT: You can see in VoiceAttack that the commands are registered and ostensibly being sent, and they do eventually reach DCS and are interpreted, just after a very significant delay.

FWIW using Vaicom I call ESTABLISHED on holding entry, COMMENCING at approach time, CHECK IN during initial decent to PLATFORM at 5000, respond to "say needles" with NEEDLES, and I usually start faintly seeing deck lighting just before BALL/glidepath intercept. I have found on my first one or two CASE III that the lights weren't at all visible if I missed any calls in that segment leading up to BALL, but I could be wrong. I was shocked by how dim they were but the LRLLS was clearly visible as far back as marshal pattern and I was on instruments anyway. EDIT: that is to say I must manually call "NEEDLES" and "BALL" for the process to work and the lights to show up, nothing was automatic about those triggers.