PeneCruz

The latest Vaicom release is available on your Auto Updater, or you can find the latest version on GitHub. This update fixes a major bug with the F-5E-3 Flaming Cliffs module and adds a new approach for community support via the new more expansive Help tab in the Vaicom UI. This should allow new users to access the manual directly from the UI and also locate the tutorial videos on YouTube via a playlist view. The inclusion of Vaicom log file access directly from the Help tab in the UI should assist the community support team to help new users (Remember you need Debug enabled on the Config tab of the UI to log activity). It also sets the frameworks for future proofing the pending removal of Windows Speech Recognition (WSR) from Windows 11. This is disabled for now on the Preferences tab of the UI as at this time Microsoft have not provided any public API in the new Voice Access application for grabbing and using the detected speech like WSR does. I'm hoping this gets rectified and API's are provided prior to the removal of WSR completely. This only impacts our Keyword Training module, not Voice Attack's use of SAPI 5.4, which remains in Windows despite the impending removal of WSR. - Fixes DCS crash with F-5E-3 Flaming Cliffs version. - Add keyword training mode Windows Speech Recognition detection and logging enhancements. - Add option for Voice Access use with keyword training (disabled for now). - Change DIAG tab on Vaicom UI to Help tab. - Add Help tab button for direct log file access. - Add Help tab button for direct Vaicom PDF manual access. - Add Help tab button for direct YouTube tutorial access. - Other minor bug fixes with UI and module database. Known Issues - None null

It uses an F-16 tabulated data set for performance calculations. Fuel planning is pretty rudimentary at the moment using interpolation at a single drag index. I have already added a full data set of cruise tables and will add drag index and a proper vertical interpolation based on the imported route rather than the selected profiles.

Yes that's how I use it works really well with my Wacom tablet in VR.

Sharing my data card generator for the DCS F-16C. Built for my personal use, but happy to share with the community. - Based on the Excel Data Card builders used in real squadrons. - It imports the DCS Route Tool saved routes from you Saved Games folder and converts to usable LAT/LON route information to automatically allow for Stores & Weight Planning, Fuel Planning, TOLD computation and a function to export the data inlcuding the route directly to the printable 2 page data card. - The workbook has an Attack Planner for both Pop-Up and Dive Attacks that are also exported to drag and drop shapes and datablocks to speed up Data Card generation. - The datacard has a bunch of configurable data blocks (via a block editior) to suit different mission sets. - Also configuarle shapes and symbols to allow plans to be visualized and understood. I see this suited to muliplayer users where co-ordination and planning is important and also allows better use of the Route Tool function built into multiplarer DCS. The Cover is completly unlocked to allow it to be customised to your own squadron. Video on how to use it and what to expect. How to Use It Link to the workbook F-16C Data Card Generator And a payload config file that matches the Mission Planners STD Stores configurations (goes in your Saved Games\DCS\MissionEditor\UnitPayloads folder) Not required but makes things very quick from panning to mission execution. Payload Config File Built for my personal use but sharing with the community as is. It uses macros and VBA Code to run many of it's functions, you will get a security warning from Excel. It will NOT run in Google Sheets for the same reason. I use Excel 365 and many of the Macros are quite modern so may not be backward compatible. Happy Viper Flying.

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.