Jump to content

1009 not working with VAICOM


Al-Azraq

Recommended Posts

Hi!

 

Yesterday I have been trying to use VAICOM with the 109 and it wasn't working. Voice command were being recognised, but no inputs were being sent to DCS. Is the 109 supported?

 

Thanks

i7 12700KF | MSI Z690 A-PRO | Corsair Vengeance 2x16 gb @ 3200 Mhz | RTX 3070 Ti FE | Acer XB271HU 1440P 144HZ | Virpil T-50 CM throttle | Virpil WarBRD Base + MongoosT-50 CM2 Grip | MFG Crosswind | TrackIR 5 | HP Reverb G2

Bf 109 K-4 | Fw 190 A-8 | Spitfire LF Mk. IX | P-51D | Fw 190 D-9 | P-47D | Mosquito FB VI | F/A 18C | F-14 A/B | F-16C | MiG-15bis | MiG-21bis | M-2000C | A-10C | AJS-37 Viggen | UH-1H | Ka-50 | Mi-24P | C-101 | Flaming Cliffs 3

Persian Gulf | Nevada | Normandy | The Channel | Syria

Link to comment
Share on other sites

The 109 is supported by the plugin.

As Lt_Jaeger says, there is a known issue with this module where it does not respond correctly to the ED API commands, specifically LoSetCommand(1591 and 1592).

This compatibility error cannot be addressed by the plugin and needs to be solved by the module dev.

Probably best to try with Easy Comms ON atm.

There is no spoon.

 

Avatar_old_80x80.gif.0c105925ce4b9f5b87697ea37cbde317.gif

VAICOM PRO plugin for DCS World

www.vaicompro.com

Link to comment
Share on other sites

There is a bug with the 109 using vaicom.

 

Did you check inside the COCKPIT, it pops the FuG 16 CB so the radio won't work.

 

 

Gesendet von meinem LYA-L29 mit Tapatalk

 

That explains a lot! I wasn't able to hear anyone on SRS.

 

The 109 is supported by the plugin.

As Lt_Jaeger says, there is a known issue with this module where it does not respond correctly to the ED API commands, specifically LoSetCommand(1591 and 1592).

This compatibility error cannot be addressed by the plugin and needs to be solved by the module dev.

Probably best to try with Easy Comms ON atm.

 

Thanks, I'll try.

i7 12700KF | MSI Z690 A-PRO | Corsair Vengeance 2x16 gb @ 3200 Mhz | RTX 3070 Ti FE | Acer XB271HU 1440P 144HZ | Virpil T-50 CM throttle | Virpil WarBRD Base + MongoosT-50 CM2 Grip | MFG Crosswind | TrackIR 5 | HP Reverb G2

Bf 109 K-4 | Fw 190 A-8 | Spitfire LF Mk. IX | P-51D | Fw 190 D-9 | P-47D | Mosquito FB VI | F/A 18C | F-14 A/B | F-16C | MiG-15bis | MiG-21bis | M-2000C | A-10C | AJS-37 Viggen | UH-1H | Ka-50 | Mi-24P | C-101 | Flaming Cliffs 3

Persian Gulf | Nevada | Normandy | The Channel | Syria

Link to comment
Share on other sites

  • 1 month later...

Since the 07-15 Update the CB doesn't pop any more but for me the 109 and the 190 A8 is no longer recognised by vaicom. No chance to contact anybody (Wingman, ATC etc...) via VAICOM.

 

 

Since this happend AFTER the update, I assume ED changes something for the warbirds.

 

 

 

Could someone confirm ?

Link to comment
Share on other sites

Yeah, see my post about the Fw190D9. ED did something. As suggested by others, enabling easy comms worked ok for me. But when you go to the trouble of setting up hi-fidelity hardware and software to enjoy the realism that is possible with DCS, VAICOM, and SRS, it is disappointing to encounter a bug like this :(

 

I was going to try to become a Fw190D9 ace, but this one little glitch just drove me back to the jets.

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

Not at my sim PC atm, but there is a check box in the DCS options, called something like "Easy Communucations" and all you need to do is check that,

 

Thereafter, you won't need to manually tune radios and will be able to press just one PTT rather than the one appropriate for a specific radio.

Link to comment
Share on other sites

  • Recently Browsing   0 members

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