PeneCruz

Hi there I have noticed the Sinai radio.lua is not complete. In that the primary frequencies on most airfields are not specified in the radio.lua. Simple entries of the primary VHF or UHF frequecies (or both) in the script will alow seemless interaction with the Vaicom Pro plugin for Voice Attack. null Example of non completed entries for some airfields and ABR completed. Completing these would align to the airfield comms handling of other terrains. Thanks for a another great expansion.

The A-10C II issue is known, This is due to the Module having 1.png and 2.png files in it cockpit/kneeboard folder. The vaicom kneeboard uses a file called 1.lua that creates the interactive kneeboard. (other module start at 10.png). This sequences the two images ahaed of the Vaicom interactive kneeboard. You can remove them or rename them in the folder, they will get updated every time DCs updates. The Mirage F1 has the same Issue. Custom Campaigns use lots of scripting to get the Ai to do things in the mission that fit the story line. Vaicom interacts with the default DCS Ai commands menu. So I can see it interfering with the behaviour if it's running. There is not much I can do about that as it would be impossible to account for all the possibilities. The only option would be to turn vaicom off for the Mission.

This usually indicates Vaicom is pointing to the C:/ root directory instead of C:/program files/Eagle dynamics/dcs (or dcsworld.openbeta)

I have tested this again. 2. ATC calls worked fine on Both Comm1 (TX1) and Comm2 (TX2) (I have uploaded a video to the VaicomPro Discord (not enough space here) in the Viggen help section. Discord Link 3,4,5 and 6 These sound like Voice Attack issues I can't replicate any of these. With point 6 I have heard other uses have had this happen with Voice Attack, where the mic input volume stops detecting commands. personally I have not been able to replicate this behaviour. I can only put it down to individual sustem performance issues/ installation/ or some conflict with Voice Attack and another program ( Windows Defender?)

Ok go to VOive Attack/Apps/VAICOMPRO and you will see a Extensions folder (it will probably have a chatter.dll in it) this whole folder is not required anymore as the extensions are contained in the main vaicompro.dll. Delete the folder and with DCS shutdown restart Voice Attack. Check the folder does not get rebuit. Check that you can select other themes in the Chatter etensions drop down. Let me know if this fixes it.null null

No worries mate, it's enjoyable at times!

Hi All The latest update will come via your Auto Updater. Or is available at https://github.com/Penecruz/VAICOMPRO-Community/releases/tag/v2.9.3.0 This update adds another Chatter theme targeted for Navy flyers using the NTTR terrain. It was part of my learning journey into the construction of the Chatter Extension. Now that is complete, it will allow the addition of other themes to suit new terrains. Also, some work on the UI and databases. It completes the work to ensure Vaicom Pro remains compatible with future versions of Voice Attack (Gary, Thanks for the help!) Complete Net 7 compatibility assurance. Added option to delete only the Imported keywords from the database. Added new Chatter theme Fallon.(Navy range and ATC chatter, includes some BFM training chatter) Added all terrains to the Kneeboard time zone check. null

UPDATE 03 November 2023 One year ago today a group of us met on Discord to discuss a way forward when the source code appeared on Github, uploaded by the original developer of Vaicom Pro. Could we make it fully functional again in DCS World 2.8.6? For VR pilots that had become reliant on the ability to simply talk to the Ai in DCS rather than use a mouse and menu structure, the loss of Vaicom Pro was a real blow. We were super motivated to just get it working again. Given the complexity of the code and it's extension based functions, with no developer insight or understanding of how it was built we set on 48 hour patching binge and created the first community version that sort of worked for most modules. One year on we have kept refining and simplifying the code to try and reduce the workload of keeping it functioning with each new DCS build. We have had a few hurdles placed in front of us along the way, the introduction of pure client scripts, the reindexing of airfield names on many maps, changes to the comms layer behavior, the list goes on. But overall the plugin has become stable again. Some milestones: - Create a solution based development environment. - Establish a Beta Test team (thank you for your hard work). - Move Vaicom Pro interactions to the DX layer. - Add 3rd party missing modules to the list of supported Aircraft. - Make AIRIO and Chatter dependents of the main VAICOMPRO.dll - Add many of the Community Mod modules to Vaicom pro. - Flesh out Carrier Comms and supported carriers. - Remove redundant UI options and add extension control via the UI. - Establishing an Auto Update function for vaicom Pro with no ongoing costs. - Passing 3000 members on this Discord and 20K downloads on GitHub. (Thanks to our Community Fixers for the endless support to the user base) - New friendships and many laughs amongst the team. The future: - Version 2.9.0.5 is currently in Beta Test This will add more Community Aircraft and fix some bugs. - Work has begun on trying to fully understand the AIRIO extension to allow us to better adapt to changes we might need to make with Jester 2.0 - Try to stay keyboard free! Happy Birthday Vaicom Pro Community Edition, it's been a blast

Hi all VaicomPro 2.8.7.0 is now released, existing uses on the last release can update via the auto update function when you next launch Voice Attack. A new installer and details on GitHub if you need them. https://github.com/Penecruz/VAICOMPRO-Community/releases/tag/v2.8.7.0 cheers

This update returns the Auto Update functionality to VaicomPro and allows a more controlled and user friendly update experience. This will allow us to push out smaller updates more often and make changes without impacting the userbase too much. Fixed AH-64D to Single TX node. (Allows more realistic HOTAS radio controls) Fixed F-5E-3 to Single TX node. Added new recipient “Ground” for ground crew. Added more realistic Tanker communications command set. (see manual) Added Syrian and Cypriot ATC recipients that were missing. (see manual) Added Auto Update check on plugin startup (release and Beta). Added Beta branch update functionality. Added Moose recipients and command structure. (Deactivated in this build) Known Issues F-14 A/B Tomcat, wheel chocks must be set then removed in some cases. https://github.com/Penecruz/VAICOMPRO-Community/releases/tag/v2.8.6.3 This will be the last MSI installer use required until we have a major version change. All future updates will be handled via the Auto Updater. Updates come directly from our GitHub repository and are installed automatically. After running you will need to go to the Editor Tab in Vaicom Pro UI Test>Finish> and paste the new keywords into your Voice Attack VaicomPro for DCS World.vap profile. Cheers The Community Team

It is a fair bit oif work, it's not just a track file that plays, it's a series of short sound files that are databased and sequenced, that is how it randomises the chatter. I have looked at adding another module, or making them thearter specific, however it is really time consuming work so it's on the back burner. Getting Auto Update working again was a higher priority. It's on our road map, but I have no timeframe.

With the desynchronisation, If you disable AIRIO in Vaicom and you select a command via the Jester wheel does it still happen? Sounds like general MP desyc where state gets confused. the map marker might be the same issue if it’s not occurring in single player. If it’s only occurring with AIRIO loaded it maybe the state is not being passed to Vaicom in MP which I can investigate.

I haven’t got to this yet to confirm what is going on. Added to the list of items to work through.

That is a question for ED, it is their product. We have adapted as best we can to keep vaicom functioning. I know I can't fly VR without it.

Hi All We are pleased to publish our next release that fixes some SRS PTT Integration issues on various modules and adds the ability to enable/disable individual extensions using the VaicomPro UI EX tab. This will allow users to customise their VaicomPro experience to only include the extensions they need and use. It also means by disabling AIRIO and Kneeboard in the UI, you can now join a multiplayer server that requires pure client scripts without failing the Integrity Check (IC). We hope you enjoy 2.8.5 The user configuration update. CHANGELOG: Fixed MB339 to return to single TX node. Fixed F-5E-3 TX1 node as primary. Fixed various modules SRS PTT Integration and radio names. Added Chatter enable /disable checkbox to Extension Tab. (hot switchable) Added Kneeboard enable /disable checkbox to Extension Tab. (Requires DCS restart) Removed redundant Extensions folder Removed redundant Setup.exe Updated the VaicomPro Community manual Known Issues F-14 A/B wheel chocks can get out of sequence and require setting in place then removing to remove them. To download head over to. https://github.com/Penecruz/VAICOMPRO-Community/releases/tag/v2.8.5.0 Cheers the Community Team

Sounds like Voice Attack issue rather than Vaicom pro. Try starting Voice Attack with the VaicomPro.exe application. It will stay active in the tray and if Voice Attack crashes it will restart it automatically. null

Yes experienced users like yourself, who understand how Voice Attack and VaicomPro relate can use other methods. I personally have a very different work flow as I'm always uninstalling and reinstalling. The use of Voice Attack export and import functions and the deletion of the VAICOMPRO folder in Voice Attack Apps was to ensure that less confident users got rid of their prevous profile, yet retained their TX and personal commands. All current DCS Commands are in the Vaicom server database. It will be just a matter of activating new ones that had not been implemented by Hollywood.

Hello Vaicom users Now that we have entered a stable period for the software, I thought I would provide an update on what we are working on apart from fixing the last minor bugs with a couple of modules. We are adding the ability for the user to Enable/Disable the three main Vaicom Pro extensions, When it was paid you could easily deactivate the licenses' and turn them off and on that way. One we rolled it into the free version with no activation we lost that ability. One of the impacts of this is that with ED moving to allow multiplayer servers to require clients to have pure client scripts, This has meant on these servers the use of the AI RIO Extension or KNEEBOARD extension caused a failure of the Integrity check (IC) when joining those servers. This is because Vaicom Pro appends some information to some DCS files so it can operate. To return flexibility to the user the Vaicom Pro UI Extensions Tab will include check boxes to Enable/Disable AI RIO, CHATTER and KNEEBOARD. null Due to the deep integration of the AIRIO and KNEEBOARD extensions it will require DCS to be Shutdown and Voice Attack shutdown and relaunched to append the DCS side files. In the case of the CHATTER Extension it can be hot changed with DCS running if desired. The user is notified in the Voice Attack UI LOG if you try to use an Extension that is disabled. When relaesed you will notice some other minor changes to the Vaicom Pro UI to add Tool Tips and some relabling to clarify options. Other ideas I'm personally working on are direct Moose Ops Airboss support to allow voice communications with marshal and LSO, If I get that working as I hope, It could lead to a broader Moose connections. I'm also looking at much the same integration for Hound. nullnull

Hey guys, I understand the confusion, it’s not so much a VaicomPro thing as a Voice Attack thing. The way Voice Attack deals with profiles is via import and export. I needed to wipe out some dead aliases that existed in the old default profile. These caused a conflict with the new keywords and meant that there were two versions of a single command, one leading no where, the other to the recipient. If Voice Attack picked the wrong one the command did not execute. I took the opportunity to update it to include everything so new users did not have to do the finish step. And could learn at a slower pace. I fully understand the want to install over the top and just use your old profile, however it will pay dividends in spades to start fresh. VaicomPro is now fully compliant with the latest DCS command tables and message tables. In the background we have also changed the way it interacts with DCS. Hopefully going forward it means faster work flow for us and faster updates for you. I would like to move to auto updates again, however the old update code doesn’t suit our free model. We are investigating other mechanisms that I have seen like Open Kneeboard uses for instance. I’ll hopefully Hot Fix a few bugs I have fixed once the Beta team confirms I didn’t screw it up more! Anyway I’m personally going to fly more and code less this month as I think we are pretty stable now.

Have you resolved this now? I saw on our Discord Liam helped with it. You need to uninstall VaicomPro using windows uninstall programs or apps. no need to run setup.exe from the zip. If you do a zip install.

We are pleased to publish our next release that fixes issues with many ATC recipients across existing maps and adds ATC recipients for the Marianas, South Atlantic and the Sinai maps. We have also updated the VAICOM PRO for DCS World.vap Voice Attack profile that gets installed in the VAICOMPRO>profiles folder in Voice Attack APPS. Please delete your existing .vap in the Voice attack UI (export it to someplace safe if you have custom commands so you can reimport those commands later to save time) and import the new file that comes with this release. It fixes many broken aliases and adds additional ones for the new ATC recipients. We hope you enjoy 2.8.4 our ATC fixes and theater expansion. CHANGELOG: Added ATC recipients for Marianas Map Added ATC recipients for South Atlantic Map Added ATC Recipients for Sinai Map Fixed ATC recipients for Persian Gulf Map Fixed ATC recipients on Nevada Map Updated Voice Attack Profile (VAP) to reflect latest Keywords list. Updated message commands list to latest DCS open Beta list Updated and compressed the Vaicom Pro user manual Known Issues IC will not be passed for Servers that recuire Pure Client Scripts. (This due to AIRIO and Kneeboard implementation) You can download from GitHub https://github.com/Penecruz/VAICOMPRO-Community/releases/tag/v2.8.4.3

I'm in the process of adding Sinai and South Atlantic to the databases and fixing Nevada and persian Gulf. This way we can control the Keywords used a little better rather than relying on Auto-Import Theaters. Next will be adding Marianas and tiding up the code structure of the databases.

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.

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.

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