Jump to content

VAICOM recognizes command but dont send to DCS just after another PTT push


Recommended Posts

Posted

Hi,

 

I use this extremely good tool for a few months now, it works flawless for me except for one thing. After a few hours (sometimes minutes) of flying (not all the time...) VAICOM (or VA) stops sending the command through to DCS. I have the beeps, command is perfect, just nothing happens. I have already tried the 'push PTT a little bit longer' but this does not help.

However after I release the PTT and push it again, release again, the command goes through. It is enough to push it for like a fraction of a second. It is a bit annoying as I have to pause, switch to VA, close it and restart. Only that helps. Or restarting the mission helps in most of the cases. 

 

Do you have any ideas, what to try? I have checked the log and found nothing special. 

  • Like 1
  • 2 weeks later...
Posted

This has been happening a ton with WW2 planes lately especially in the instant action and built in missions. I've figured out that when this behavior starts happening, if I look at the config window in Vaicom (LCNTL LALT C) it doesn't recognize the aircraft I'm flying - in other words no aircraft is identified in the config window. If I load the FWA8 training mission and go to the config window it will show the FWA8 as it should and vaicom works. Something in these new WWII missions that were just released is definitely blocking VA/VAICOM from working and I can't figure it out - but it is definitely with these newly released missions.

Posted

Just flew mission 2 of reflected Horrido campaign in the FWA8 and I cant get Vaicom to work. It'll work fine on the ground, but as soon as I get airborne I lose functionality. I can say kneeboard and I get the beeps - but no kneeboard. When I want to bring up the comms menu with "options" - I get the beeps but no options... It's weird but it seems like its related to a script running or something, because it works fine on the ground.

  • Like 2
Posted

Sorry to keep updating this thread.. but after more testing I can get the WWII birds to work by selecting easy comms to on in the DCS options menu... Everything works as advertised when I do that.... something weird is going on with the WWII birds...

 

Posted

Same with P47. Airborne, not connected to DCS (vaicom). Once landed again, Vaicom connected. 

thanks for the easycoms tip, but hope it is fixed soon in the normal comms. 

  • 3 months later...
Posted
16 minutes ago, horstweihrauch said:

Have the problem too in FW190A8 and Instant Action/SP😢

You need to have EasyComms on for the warbirds at the moment to make it work. It will be fine on the ground otherwise, but not when you are in the air

 

  • Like 1

Windows 11 Home ¦ Z790 AORUS Elite AX motherboard ¦ i7-13700K ¦ 64GB Corsair Vengeance DDR5 memory @ 5600MHz ¦ Samsung 990 Pro 1TB SSD for OS, Samsung 980 Pro 2TB SSD for DCS ¦ MSI GeForce RTX 4090 Gaming X Trio 24GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk4 and MCG Pro ¦ Thrustmaster Warthog Throttle ¦ VKB STECS Throttle ¦ Virpil TCS rotor base with Shark and AH-64D  grips ¦ MFG Crosswinds ¦ Total Controls Multi-Function Button Box ¦ Pimax Crystal

Posted

Thanks mate

21 hours ago, hornblower793 said:

You need to have EasyComms on for the warbirds at the moment to make it work. It will be fine on the ground otherwise, but not when you are in the air

 

 

Darkstar: Merged

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...