PeneCruz

Yes I’ll keep them seperate but also create a full map version template as well.

I did have plans it seems LOL null

Awesome, just looking at it looks like a cool area, I'll do the OP's too if I haven't done them yet.

I can I can release a combined one, I kept them seperate to allow people to keep their object count low if they need to. DM me the pictures and I can add it. some places have stock commercial/industrial textures at the location whick makes it hard to work around but I'll take a look.

Awesome work mate! now you just need to add the Aerostats

Export.lua, however I think if it’s not updating to the new version you may have two installations of Voice Attack? Or the wrong release? Yeah some missions maybe using scripts that interfere with the operation of Viacom, like work around DCS lua tables and provide their own. I won’t have a fix for this unfortunately.

Ok it's not updating for some reason, go to the GitHub relase Release V3.0.5.3 and download the zip file and manually copy the vaocompro folder to Voice Attcak/Apps folder and overwirite the existing. Then start Voice Attack. You version should be 3.0.5.3 then you will need to do a Lua Code reset via the Vaicom UI Reset tab and then restart Voice Attack then start DCS.

Are other Jester commands working? Other wepon types etc? Nothing was changed in the AIRIO module so it should operate the same. Also try cycling AIRIO off the rerstarting Voice Attack Then Back on and restarting. also check Use Appensicies is checked. I'll be traveling for a few days if you still have issues jump onto our Discord for support. nullnull

I would say that the auto update is not downloading? when you accept the update offer on the popup do you see in yellow in the Voice Attack window Doenloading then installing befor Voice Attack retarts?

VAICOM RELEASE 3.0.5.3 I'm excited to say the latest release update is now available on GitHub or via your auto updaters. A lot of work has gone into this patch and I think you guys will like it. This update adds a new hooking method for DCS and a major lua optimization, which brings a faster communication rate between Vaicom and DCS. Along with better logging of message construction and passing when set to debug and new file handling routines. It also makes many fixes, brings better Kneeboard data management and stops the phantom Scripts file that was being generated in the root directory during file writing. - Fixes the rearming command to ensure the Mission Resources dialog pops up. - Fixes NVG, HMD, Inertial starter commands and other special commands. - Fixes “request taxi for takeoff” bug - Fixes Supercarrier verification bug - Fixes lua code reset behavior and expands to cleanup legacy export.lua hook if present. - New Kneeboard frequency priority for recipients UHF>VHF>FM. - New faster two-way communications rate between DCS and Vaicom. - New safe handling of export.lua and better logging. - New lua code optimization for many appended files. - New Vaicom UI window handling now will not remain on top of other windows. **ALL USERS NEED TO DO A RESET OF THEIR LUA CODE USING THE RESET TAB OF THE VAICOM UI.** This is important, If you do not perform this reset the legacy entry will remain and Vaicom will not connect to DCS KNOWN ISSUES - None

No as I don't have access to the lua files in the F4E. They are encrypted with Jester 2.0, so the current metthod used with the F-14 can't be employed (this makes perfect sense for HB to do this given their investment in that IP). I do have another idea which is in works for passing DCS icommands, which would allow the passing of Jester 2.0 commands from their new API, this would also pick up George for the AH-64. But alas time is short at the moment as I have many RL commitments, so it's slow progress.

Sharing my work on a Google Earth overlay for Iranian Military Sites. I was unhappy with what was publicly available so I decided to make my own based on open source research and some serious map searching. The KMZ contains almost all Air Defence and IRIAF locations and many more locations for IRIA, IRIN, IRGC, storage, production and underground facilities in Iran. I have been building this overlay for some time, I guess many sites have been destroyed by now but it is useful for creating realistic missions and placing units in their correct locations in the southern region that lines up with the Persian Gulf Map. I'm still slowly working on this overlay as my research continues so If you add the link as a network link in Google Earth you will get the updates as they occur. I will eventually hyperlink references to the more prominent sites once the overall collection is completed. https://drive.google.com/uc?export=download&id=1Ps4ir_uKS4T_PRvlwBl-bnhvDJLWt_mY

Wrong forum?

UPDATE 17 May 2025 The thing that keeps me going with DCS is the passion of it's user base, as Nick from ED often lets us know. Truly though, it is amazing the level of commitment to improving the usability of the game, from the great ideas to drive Vaicom forward and make it even more accessible to DCS pilots, to the awesome scripts and mods that continue to make the experience better for everyone. VSPX export has always been a little broken and thanks to some ideas from @sleighzy we now have a complete and expanded keywords export function for VSPX users that mirrors the regular Vaicom use case. So here comes Vaicom 3.0.3.0. on your auto updaters and GitHub. Vaicom Releases This update adds a feature request for VSPX/Whisper Attack users to have imported F10 menu items copied to the clipboard during the Editor finish steps; this allows an updated keywords list including these commands to be easily pasted to the Vaicom for DCS World.vap keywords section. It also makes many backend changes to the code including a general clean up and database reorganization to make my life easier. - Adds new VSPX keywords export function. - F10 and dynamically matched F10 keyword export for VSPX. - Update DCSMessageTable to the latest version. - Update all DCS core lua files to ensure return to original on Voice Attack exit. - Tidy up Database to make DCS Modules more logically ordered. - Remove code notes that are no longer relevant or fixed. VSPX USERS NEED TO DO FINISH IN THE EDITOR AND PASTE THE NEW KEYWORD SET TO THE PROFILE AS DESCRIBED IN THE MANUAL. Stay keyboard free!

Go to your Reset Tab and do a keywords reset. Then with DCS shut down restart Voice Attack. Then do the finish steps again. That should work.

Howdy guys, another update is available via your auto updaters and on GitHub if you need an initial download. VAICOM 3.0.2.0 Community Edition. This update adds the awesome Germany Cold War map to the ATC recipient’s database. Removes some old code that I was trialing during the Moose integration work, Changes the AOCS text to speech default volume and fixes the incorrect use of elevation vs altitude. There are also some database ID changes to clean the code up a little and allow for future expansion with new maps. Adds Germany Cold War ATC recipients. Remove old Moose trial code. Tidy up Database unique ID's. A few Database fixes Increase AOCS TTS volume. Change AOCS elevation to altitude. YOU WILL NEED TO DO FINISH IN THE EDITOR AND PASTE THE NEW KEYWORD SET TO THE PROFILE AS DESCRIBED IN THE MANUAL. Known Issues Rearming Request with Ground Crew will not open Rearming UI, only rearms last selection (Use Options Command to access menu for now). Happy flying and good luck with those German airfield names

Awesome, Thanks @intruder11 love this application!

Also noticed with the latest update 1.3.0, the bot is ignoring the auto-picture: false config.yaml setting. It is still broadcasting at the set auto-picture-interval: I have tried a few restarts of the bot without effect.

Love the latest update, awesome. Getting better all the time. SkyEye has been running great on our Public Server for a few months now without issue. I would like to try and run another instace on that box for a second AWACS on another server instance. Apart from the Admin documentation on second instance limitations and possible load managment switches is there a guide somewhere on how best to install a second instance?

I have created a three part series of videos on how to Install, Configure and the basics of using Vaicom Pro with Voice Attack. Hopefully this takes some of the mystery out of it and helps get people up and running faster. Installation Configuration Basic Use in the Aircraft. Get keyboard free and up the immersion!

A super brief look at the upcoming changes to Vaicom Pro that use preconfigured keywords to control F10 Other menu items, in this case being used with the brilliant Moose Ops Airboss. Functional Range and Ops AWACS have been coded as well. No more random commands when importing F10 Menu Items, Pre configured keywords are matched with dynamically scanned command endpoints to provide a more seemless integration. Please ignore the quality of the video, it's just a dirty grab of my VR mirror. Stay keyboard free!

UPDATE 17 March 2025 Voice Attack Version 2 Gary has released version 2 of Voice Attack, it offers some cool new features and a better UI. As a plugin developer I was invited to participate in testing the new Version during it's development. Any changes required to keep Vaicom Pro working in Voice Attack 2 have already been made and Vaicom Pro is fully compatible with Voice Attack 2. Do I need to upgrade to Voice Attack 2? The short answer is NO, Vaicom pro will continue running with Voice Attack Version 1. Is there a benefit to upgrading to Voice Attack 2? Version 2 brings some new things to the UI in particular UI scaling which is cool if you ever need to fit it someplace, I quite often use it in OpenKneeboard for instance. However the real benefit is Version 2 will receive ongoing updates to ensure it works as intended going forward and at $10 it's not a bad way of supporting a great developer. How do I move to Voice Attack 2? It's really simple, just Install it following the instructions on the Voice Attack website, Get your new Voice Attack 2 registration key and enter it. - Copy your VAICOMPRO folder located at Voice Attack/Apps and paste it into the same location in the Voice Attack 2/Apps folder. - Check the Profile Vaicom Pro for DCS World is selected in Voice Attack. - Check you Settings are configured in Voice Attack Options (they are the same as Version 1) - Check your preferences in the Vaicom pro UI (they should not have changed) - Start using Voice Attack 2 Other Vaicom Pro News Work on the next release is underway and will fix a few things, ensure compatibility with some upcoming changes in DCS and add a much awaited feature of better keyword control of scripted F10 Other Commands. I have been working on this addition for over a year, The approach I ended up taking after many failed attempts and unsatisfactory trials was to leverage the existing Vaicom Pro Import F10 menu feature, allowing it to add the menu endpoints to the database while coding known endpoints to have pre configured Keywords. What does this actually mean? Well it means things like Moose Airboss, Range, AWACS etc can now have their own Keywords which you can train, have written down on a kneeboard or can be provided by the script developer in their documentation. How it works, when the Import F10 Menus function scans the menu tree and discovers a know command, for example the Airboss command "Request Marshal" it adds the command "Action Request Marshal" to the database then automatically applies the new, pre configured command keyword to this database entry as an alias. "Inbound Mother Request Marshal" This all happens dynamically as scripts are loaded or updated. This approach allows scripts that dynamically add menu items as the mission runs or the situation dictates to add the Actions to the database but already have an alias in the users profile. There are a couple of limitations to this new feature, a mission can't have multiple Airboss, Range, AWACS objects of the same type. As the keywords target a menu endpoint, multiple objects of the same type introduce endpoints with the same database name which are then filtered out by the code to avoid issues. Secondly, I will only be adding code for the more commonly used community scripts and will only add commands that you would use in flight generally not configuration commands. Anyway have a great week and stay keyboard free

Watching with interest