VAICOM 2.8.3.3 Release

[PeneCruz]

We are pleased to publish our next release that implements a new way for VAICOMPRO to interact with the the DCS menu system, this will appear no different to the end user.

This release contains fixes to all existing modules that were experiencing issues post DCS 2.8 and returns Vaicom to a more robust state. It also sets Vaicom up for handling the release of new modules without having to code individual work arounds for each module depending on how the developers chose to interact with the DCS menu system. This alone will reduce workload and see new modules added in a shorter timeframe.

The ATC recipients list on some maps can now be updated by selecting Auto-Import Theaters on the Config page. We recommend doing this and following the instruction to update the keywords. this fixes the errors with ATC names not being executed on some maps. You must load into the map for it to update the list.

We have also added many of the popular community modules that are mature as a trial. (Note: Some of these modules do not have full AI comms implemented by their developers, or the radio units themselves have limited functionality.)

We hope you enjoy 2.8.3 the stability patch.

CHANGELOG:

• Implement new DX Gui call loop
• Removed redundant workarounds
• Add F-15E Strike Eagle
• Add KA-50 Blackshark III
• Add MB-339 Aeromacchi
• Add Community A4E-C Skyhawk
• Add Community F-22A Raptor (Grinnelli Designs)
• Add Community C-130J Hercules (Anubis)
• Add Community UH-60L Blackhawk
• Add Community T-45 Goshawk (VANO)
• Add Community A-29B Super Tucano
• Completed AH-64 Apache Implementation (No George Ai)
• Fixed in game messages displaying too low in frame
• Fixed numerous bugs across many modules
• Fixed Auto-Import modules function (Single PTT and Easy Comms only)
• Fixed Auto-Import theaters (Note one detected you must add these using the keywords update routine in the VAICOMPRO UI)
• Enhanced notification if no module is detected ("None Detected" displayed on PTT page)
• Enhanced module hooking and release routine
  
  Download at https://github.com/Penecruz/VAICOMPRO-Community/releases/tag/v2.8.3.3

 

 

[dburne]

Much thanks for all of your hard work on improving Vaicom guys!

It is very much appreciated!!

[dburne]

So got mine updated this morning and been flying most of the day today. In the Hornet everything was fine, just like it has been.

WWII still giving me issues - namely while wingman comms work fine ATC never gets recognized. At least I get no audio feedback from it. This is in the Spitfire in Normandy 2 Map, P-51 in Normandy 2 Map, and Mossie in The Channel Map. In fact in the Mossie, TX1 does not seem to work at all - I do not get an audible beep or anything when pressing it. TX5 does at least give me the audible beep, but no ATC comms there either. In the WWII planes I tried each channel available to be sure. This was pretty much how my Vaicom was doing prior to this latest update.

Procedure I used -  I uninstalled Vaicom and installed this latest version. I also went through the Finish Steps process to paste all the keywords back in.

[PeneCruz]

Have you activated Auto-Import Theatres in config? It will import the ATC recipients when you load into a map for the first time. Then you need to hit finish in the editor and add them to your keywords.

many of the map airfield names have changed over time, now that we have the auto import function working it will fix up the recipients table for you. As new theatres are added it will allow the user to update it without us changing the tables manually. 
 

[dburne]

8 minutes ago, PeneCruz said:

Have you activated Auto-Import Theatres in config? It will import the ATC recipients when you load into a map for the first time. Then you need to hit finish in the editor and add them to your keywords.

many of the map airfield names have changed over time, now that we have the auto import function working it will fix up the recipients table for you. As new theatres are added it will allow the user to update it without us changing the tables manually. 
 

 

Yes I have auto-import theatres selected in the config. I did finish steps but maybe just on the first or last map I loaded can't say for sure, will make another attempt tomorrow and make sure I click on finish steps after each map loads? Do I need to do this procedure for each aircraft when doing this also? Or just the maps?

Thanks,

Edited May 20, 2023 by dburne

[dburne]

Gave it another try earlier today, seems for me still WWII birds are not behaving with ATC, same as before this latest update. Tested both Spit and P-51 in Normandy 2 and The Channel. Behaving exactly same as it was, wingman comms worked fine, no ATC comms working. I made sure to load into each map and do the finish steps procedure to get the  new commands in.

Then flew the Hornet some in the Persian Gulf, it worked properly as it always has. So in effect absolutely no change for me with this latest Vaicom update. 

Edited May 21, 2023 by dburne

[PeneCruz]

Try the Hornet in those maps, you will find the same issues. With ATC names we are working on an update of the tables. But we are writing a script to dump them from DCS to save time. The Auto import theatres only brings in ones that don’t exist in the table. So some will work that are new since DCS 2.7.X there are two seperate issues we have fixed the first and it seems only partially the second. Nevada now works fine with ATC I personally don’t own the WWII maps so I can’t test my self. We will get there.