Describe the bug
neither the zip not the msi install

the zip fails with
"Unable to locate application file 'VAICOM PRO for DCS World.msi'.

See the setup log file located at 'C:\Users\dream\AppData\Local\Temp\VSD44E4.tmp\install.log' for more information."
D

the msi fails with :
unable to write to D:\Program Files\VoiceAttack\Apps\VAICOMPRO

install.log

Describe the bug
While on the ground, you can use the Vaicom commands to talk to ATC, JTAC, AWACS etc fine. However, once you are in the air, you will only get confirmation from the recipients if you have the F10 menu up (either initiated before or after issuing the voice command).

To Reproduce
Easy Comms Off
Vaicom - Disable Menus unchecked
In an Apache - using PTT Norm mode
issue the Vaicom test, communicating with ATC (e.g. Request Hover). It will work fine because you are on the ground
next go into a hover, and then try to communicate with ATC (e.g. Inbound). ATC will only acknowledge you if you first toggled the F10 menu on (call radio menu keybind)
Because its buggy, you may need to initiate the call radio menu multiple times before it actually appears

Expected behavior
Regardless of whether you are in the air or on the ground, the radios should work without requiring the F10 menu to be displayed

Screenshots
not applicable

Additional context
running Vaicom Community download 2.8.0

Is your feature request related to a problem? Please describe.
When viewing a Kneeboard and Viacom senses an incoming AI transmission, the DCS KB view automatically switches to the interactive Viacom KB page. This is frustrating if you're using another KB page and you have to constantly switch back from the Viacom KB

Describe the solution you'd like
An option in the settings to select KB to jump to Viacom pro or stay on current KB Page

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

When tuned to the correct tanker frequency, Vaicom correctly identifies that I am on a given specific tanker. However, when making the call "Approaching for refuel," Vaicom contacts the incorrect tanker. This was broken some months ago, perhaps as long as when the Apache released. It's not worked for me properly since, and does not work in this latest build.

Here is a copy paste of the log:

12:47:19.371 Listening suspended
12:47:19.354 Joystick : 'Transmit TX1 release'
12:47:18.983 Constructing message...
12:47:18.983 Done.
12:47:18.983 Identified unit: Arco2-1 with id 17490688
12:47:18.983 Recipient for Tanker set by call contents.
12:47:18.983 TX1 | AN/ARC-164: [ Tanker ] , [ Intent to Refuel ]
12:47:18.982 Have result, identified as command: Approaching for Refuel
12:47:18.982 Getting selected unit for category Tanker
12:47:18.982 Have result, identified as recipient: Approach
12:47:18.981 Captured sentence: approaching for refuel
12:47:18.978 Recognized : 'approaching for refuel'
12:47:17.015 F10 entry Action Activate SA-8: action index updated to value 8
12:47:17.015 F10 entry Action Activate SA-15: action index updated to value 9
12:47:17.015 F10 entry Action Disable All: action index updated to value 10
12:47:17.015 F10 entry Action Remove all Convoys: action index updated to value 5
12:47:17.015 F10 entry Action Activate SA-2: action index updated to value 6
12:47:17.015 F10 entry Action Activate SA-3: action index updated to value 7
12:47:17.014 F10 entry Action TGT 7513 Activate M113 Convoy (17 mph): action index updated to value 3
12:47:17.014 F10 entry Action TGT 7513 Activate Humvee Convoy (34 mph): action index updated to value 4
12:47:17.014 F10 entry Action TGT 6208 Activate 4x4 (46 mph): action index updated to value 0
12:47:17.014 F10 entry Action TGT 6208 Activate Truck (23 mph): action index updated to value 1
12:47:17.014 F10 entry Action TGT 6208 Activate T-55 (11 mph): action index updated to value 2
12:47:17.013 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:17.013 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:17.013 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:17.013 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:17.013 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:17.012 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:17.012 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:17.012 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:17.012 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:17.012 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:17.012 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:17.011 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:17.011 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:17.011 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:17.011 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:17.011 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:17.010 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:17.010 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:17.010 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:17.010 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:17.009 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:17.009 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:17.009 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:17.009 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:17.009 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:17.008 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:17.008 TX1 | AN/ARC-164 AM 342.150 MHz tuned for AAR unit Texaco3-1 [AI]
12:47:16.782 Listening resumed
12:47:16.764 Joystick : 'Transmit TX1 press'

In the next issue of the manual, could the column headers of the Keywords Reference be repeated on every page, please?

The A-4E-C community mod works with Vaicom when on the ground. Once in the air Vaicom no longer works. This includes kneeboard functions. If transmit button is pressed approximately half a dozen times the requested transmit message will sometimes go through.

Allow user to set text output font size for message log.

Basic font size selector + up + down size buttons.

Also enable word wrap so long msg like Marking Moms can be seen on narrower window.

Feature is nice to have where multiple monitors are being used and the VA msg window is far away from primary screen.

Describe the bug

VAICOM does not appear to utilize the custom path config option correctly. When checked VAICOM does not load/log loading of modules and other information to the tables.
When Checked VAICOM does log that these modules are being loaded and loading correctly but does not seem to function. It may correctly function I was not able to test this extensively.

To Reproduce

Use the custom path checkbox to set a custom path note the log shows nothing loading to the tables. Uncheck the box and note in the logs that modules are showing as loaded, this case may be using the registry key and therefore nonfunctional if you use a path different than what is in the registry key.

Expected Behavior

Respect the 'custom DCS path' checkbox correctly and show correct module loading log messages.

Workaround

Setting the DCS path correctly in the registry appears to fix this issue but may be undesirable for some users.

Describe the bug
This is a known VAICOM bug for some users where after a DCS update, the communications menu will cycle open and closed repeatedly.

To Reproduce
Happens for some, launching VAICOM and DCS after an update and loading into an aircraft.

Expected behavior
The communications menu should only react to in game/VAICOM commands and not cycle on its own.

Screenshots
N/A

Additional context
A workaround seems to be for some just resetting the lua script in VAICOM. However I find consistent work around results by clearing the lua, closing voice attack, launching and exiting DCS, and launching voice attack to clear the lua once more. Not sure if this is overkill but it works to resolve the flashing.

MSG box (top right corner) go down with Vaicom. If vaicom is not loaded, it will stay up right.

Describe the bug
Error will pop up stating that pure client is required to join server.

To Reproduce
Install VAICOM Community, join multiplayer server

Expected behavior
Uncertain - may be normal now as its no longer official.

Screenshots

Additional context
I also have a problem where I cannot select the DCS install location. I am using the Steam Edition of Voice Attack and DCS Open Beta. When I try to set the path, it simply shows my desktop folder, but will not allow me to navigate elsewhere. VA is in admin mode.

The "Jester ... options" command brings up a simplified Jester dial. "Take #" navigates the dial. This works as described in the manual in PTT mode and the simplified Jester dial closes once the PTT button is released and the cockit is renderted again. In "hot mic" mode, "Jester ... options" activates the simplified Jester dial but there is no way to abort and even if a Jester command is issued, the Jester dial disappears but the cockpit is not re-rendered. You're left in view looking out of the plane without a cockpit render.

Requested features:

1. Replicate the "Jester ... options" function in "hot mic" mode as it operates in PTT.
2. Allow navigation to the next Jester dial screeen (where avaialble).
3. Provide the option to abort the "Jester ... options" command (and return to the cockpit) via "hot mic" mode (same as releasing the PTT button).

Describe the bug
In the AJS-37 Viggen, Vaicom recognises the command and sends the correct menu command however no action is recieved and actioned within DCS,

To Reproduce
Fly a section flight with an Ai wingman and issue flight or section commands. If you sned the command via the F10 menu and the mouse or function key the command is sent within DCS and actioned.

Expected behavior
Expect when the Flight Command is sent Ai will respond and perform the action.

Screenshots
N/A

Additional context
Possible change to Viggen Menu structure in klast update?

The test was made before 2.8 and now with this new 2.8 community Vaicom. Same result, different installation plugin.
Only tested to show menu and navigate to select something through them. Mostly all the planes works good, but this list:

1. AH-64 Apache - On Ground (OK - QMission=HotStart) - On Air (sometimes when takeoff from quick mission on ground. On Mission editor airborned start NO WORK (menu don't show up)
   with Easy Comms = All works ok.

2. AJS37 Viggen - No problem With Menus, but they don't do anything when choosen the option. They have to be selected with mouse to interact. This problem even with Easy Comms on.

3. F86F - On Ground Don't work (The menu appears but disappears inmediatelly) - On Air, the menu appears, but once selected an option that has other options nested, it disappears as on ground, so no possible selection. Works on ground and air with Simple Coms on.

4. Fw190A8 and FW190D9 - No Problem with Menus, but they don't do anything. They have to be selected with mouse to interact. This problem even with Easy Comms on. With easy Comms it can accept orders as "anapa, inbound" with realistic comms those type of orders won't be "heared"

5. i16 - Works on Ground,but on air the menu don't show. With Easy Comms on, the menu appears on air, but after first second selection on nest options it dissapear

6. K50 - On Ground the menu disappears as soon as it it called - On Air, the menu appears, but after first selection in options, the second selection the menu disappears. With easy coms on it is worst, as in air, the menu just disappears once called.

7. Mi24 - On ground no problem - On air the menu don't appears when called with Vaicom - With Easy Comms on, no problem.

8. mi8 - On ground the menus disappear just when called - On Air they are ok - With easy Comms on the menus on air also disappears as the ones on ground.

9. Mig15 - On Ground the menus disappears just when called - On air, the menu appears, but after first selection it disappears. Have to be operated with mouse or keys - With Easy Comms on, no problem with menus.

10. P51D - On Ground the menu disappear just when called - On air it appears once but if I choose anything it disappears - With Easy Comms no problem.

11. Mosquito - on ground menus appears, but as soon as takeoff thyey disappears when it is called.

12. Spitfire - On Ground the menu disappear just when called - On air it appears once but if I choose anything it disappears - With Easy Comms no problem

13. UH1H - On Ground the menu disappear just when called but can do direct voice orders - On air it seems no problem. There was a problem in the past on air with menus.

This bug was reported with the previous DCS update. I had read that RAZBAM acknowledged the issue but were unable to release a patch to make it into the last DCS update but said it would be in the folloing DCS update. The latest DCS update arrived today. I checked the "Remove Wheelchocks" command using VAICOM Pro and the bug persists. The command is acknowledged but the wheelchocks remain in their place.

Is your feature request related to a problem? Please describe.
The issue with the current behavior is only for someone flying in a multiplayer environment who is trying to get Vaicom to recognize the keywords in a normal human-to-human radio message. It works well if you plan our your micro-pauses carefully, have good recognition fidelity.

When trying to do this, particularly with "Marking Mom's", vaicom transmits the mm call to the carrier and the carrier starts responding before I'm done with the call. The mm call is somewhat long... approximately "marshall, 101, marking mom's [pause] 100 for 50, angels 10, low state 8.0

Describe the solution you'd like
AI Transmission should be held until I release PTT when using "Broadcast Parallel" and "Hold AI Transmission". Currently "Hold AI Transmission" option is grayed out with "Broadcast Parallel" selected. I believe it becomes an option with the other Tx modes.

Describe alternatives you've considered
Speaking quicker is an option, but it's still difficult for the longer examples like marking mom's, and it reduces the likelihood of capturing the keyword and increases the likelihood that I have to throw out another "marking mom's" on the radio, which is disruptive.

The other Tx modes help solve the problem, but at the expense of immersion.

Additional context
N/A

Easy communications is OFF in DCS settings. It is OFF in mission settings. VAICOM PTT window still says "Easy Communications ON."

I have master zeroized the entire program, uninstalled VAICOM, deleted all related folders in VoiceAttack, Saved Games, and ensured the export.lua is clean. I made a 100% fresh install via the community 2.8 version .msi installer from Github, no avail.

dcs-05NOC-easycoms.log
VAICOMPRO-05NOV-EasyComs.log

I'm flying Huey.
Everything works fine when EasyComm is ON

When OFF the communication menu doesn't appear when I press TX6 and say Options.

After clicking many times TX1, TX2, ..., TX6 it appears but if I say Take 1 (for instance) it disappears again and entire process of managing Comm Menu via Options, Take 1, ecc. is disrupted.

I've cleaned the system, uninstalled VAICOM and then reinstalled but no joy.

Thanks

Describe the bug
When requesting jester to switch lantirn, he acknowledges it and doesn’t switch to TV

To Reproduce
Steps to reproduce the behavior:
Be in A/G mode and have a lantirn onboard
Jester automatically switches to the pod
Per the manual, say “Switch Lantirn”

Expected behavior
Jester should be switching back and forth between the Lantirn and TV. This also is an option In the jester wheel.

When using Hot Mic in F14 with a human RIO, VP is now in a hot mic status and trying to execute commands

provide an option to disable hot mic from the settings menu rather than have it a baked in function tied to the ics mic switch

I've noticed in recent checkins that the Assembly Product Version and Product Name are referenced as instanced strings in many places within the code-base. This necessitates code-reuse and raises the possibility of typos across the project. I'm recommending that these strings (and any others) be centralized into static class properties that can be referenced across the program.

Describe the solution you'd like
Product Name and Product Version should be set only 1 time in a centralized class (or other method if preferred) and referenced across the project as needed. Perhaps an AssemblyInfo class with static members instanced as a singleton and then referenced whenever desired so scrutiny of strings across the project are greatly reduced.

Describe alternatives you've considered
Global Variables - Ick
Extending the Assembly Class and referencing it widely - Possible
Centralized String collection that references internally - Allows for flexibility and centralized extensibility + language support. May not be instantiated when needed. Has fallen out of favor.

Additional context
Example change from recent Commit:

Describe the bug
The Mirage F1CE shows up in VAICOM as the Christen Eagle aircraft with only the AUTO radio option.

To Reproduce
Load into a Mirage F1 variant with VAICOM running and easy communications OFF.

Expected behavior
The Mirage F1 should show as its own module with its two built in radios (forget the exact ones, will add once I'm home and can reference documentation).

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Is your feature request related to a problem? Please describe.
Jester can tune to frequencies via "Radio Tune" however he still is unable to tune to preset channels in the aircraft. Apparently there is a set channel ability that works if you hold a radio selected down but it does not function when using a single PTT for Vaicom.

Describe the solution you'd like
Add something along the lines of "radio tune button one" or "push button one" etc (comm parlance for a preset channel) to allow preset selection instead of reading off the frequency or recipient.

Describe alternatives you've considered
N/A

Additional context
Quality of Life feature adding another one of jesters abilities to Vaicom. This feature should be added in a future release as part of completing jesters abilities commanded by Vaicom.

I also see the commands are already in the code, but they seem to not be functioning via plugin.

Hello!
Here I leave some problem I have since long with AIRIO.. Just for testing when is possible and no rush at all (incredible job about this community)

1. If I command Jester to be silent,He continue giving "nails" rwr callouts or enemy position. With Yester Wheel no problem. It doesn't work for making him silent and alowing him to speak again.

2. Switch LANTIRN doesnt work. Even it is is TCS or Lantirn, it won't change between both. With the Yester Wheel no problem

3. Don't know if this one is in this update. Toggle PDSTT/PSTT do not change from PD STT to PSTT. I go back to the RIO cockpit and always is set PDSTT

4. Command MAP [1-10] to point 1-3, fix initial etc, works with only some points: (Defense, home base and danger zone). Don't work for points1-3, fix, IP, or surface target. No problem if done in Yester Wheel

5. None of the RIO Grid options works. Only Radar Stabilize, and Map Mark [0-10] to Grid function. No sectors, no orientate grid, etc... Tested with Yester Wheel and the navigation options works in stabilize grid mode.

Users with Supercarrier module installed have Supercarrier communcations enabled for freeware carriers (Forrestal, Stennis). Expected behavior is that Supercarrier commands in VAICOM work with as normal with Forrestal and Stennis.

Currently user is unable to proceed with other communications after initial inbound call because VAICOM does not detect unlocked Supercarrier communcations on non-Supercarrier units.

Describe the bug
If I issue any kneeboard page voice command, the phrase is recognized but either the kneeboard remains on the Note page or it leaves the VAICOM page and goes to the first default game kneeboard page (HOTAS cheat sheet).

To Reproduce
Assign voice commands to kneeboard contexts like kneeboard.tab.log, kneeboard.tab.awacs. Launch any A10C II mission. Open kneedboard in cockpit. Navigate with keypresses to the VAICOM kneeboard page (it opens to the "Notes" tab for me). Issue "log" voice command. See that kneeboard resets to the default primary kneeboard page (HOTAS cheat sheet).

Expected behavior
Kneeboard should have switched from the "Notes" tab to the "log" tab.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
VAICOM community edition version 2.8.1.

Describe the bug
When on carrier, a new change by heatblur has the wheel chocks automatically applied to the aircraft. The Vaicom command "Remove the wheel chocks" functions as it always used to, and even gets a "copy" response from ground crew and a confirmation! However, the wheel chocks remain. User must use the conventional radio-text-input system to get chocks to actually be removed.

To Reproduce
Vaicom command: "Remove the wheel chocks" and then observe ground crew response. Go external view to confirm that chocks remain nonetheless.

Expected behavior
Wheel chocks should be removed as if text-menu commanded

Issue Description
I forked the repro and tried with both VS 2019 and VS 2022 to get the solution to compile. It seems to complaining about Fody being missing but I installed the latest 6.6.4 and changed the csproj to match and still the same error.

Request
As a C# developer with over 30 years experience in software development I would be very grateful if you could post build directions

Supplemental Information
I want to try add some RIO commands and maybe even build my own extension for other A/C functions. I own all the modules except I-16, Christen Eagle and F-1 Mirage. I also have some ideas for a newer version. :-)

Closing
Thanks for taking the time to review this request! I have been a DCS fanatic since it came out and even before with Falcon (all versions), Flanker, Flanker 2.0, Flaming Cliffs etc. etc.

Vyper [VAF-111]

Chatter does not play audio after installing the latest version post DCS 2.8.

I can press the 0 key and hear a beep as well as see chatter started, but never hear audio
Log shows chatter loading and chatter starting.

Tried to replace chatter.dll from my original backed up viacom install as well as from community files.

Describe the bug
The "Select Channel" command is not working in DCS, though VAICOM is registering is as a command.

To Reproduce
Tested in F14 F18 and F16 powered up on the ground, the command is registered in the vaicom log however nothing happens in DCS

Expected behavior
Should select a channel preset on the radio

Screenshots
N/A

Additional context
This "should" be implemented in VAICOMPRO but appears not to hook into DCS properly in any aircraft and should be investigated.

Hello everyone,

after updating to the community fix 2.8.0., I get this VoiceAttack message after any voice commands:

Command 'xxx' is currently disabled for this session and was not executed.
For example:
6:58:27.499 Command 'navigate steerpoint 1' is currently disabled for this session and was not executed.
6:58:27.489 Recognized : 'navigate steerpoint 1'

This seems to be an older problem that apparently must have been introduced after VAICOM version 2.5.24, I personally never experienced it until now.

A "workaround" is to keep pressing the (any) TX button until the "confirmation beep" can be heard, after which the command is being executed.

So, press TX -> speak command -> wait for "beep" -> release TX -> command is being executed.

"Normal" behavior would be either press TX -> issue command -> release TX -> beep and execution. Or, with ICS set to "hot", VAICOM is "always listening".

Could the community please have a look at this so that it works as it used to, especially WRT the ICS hot mic function to interact with Jester without the need for PTT?

Thanks.

Is your feature request related to a problem? Please describe.
Add a list (dedicated, maybe not in the changelog) of added commands in each version.
When a new release of vaicom adds new commands, it is difficult to the translator to find the new commands to translate.

Describe the solution you'd like
To help translator, it can be good to know (if keywords are added) what keywords has been added to what version.

Describe alternatives you've considered
It can be a csv table with the following lines:
VaicomVersion; module; voice command phrase; category; command segment

Is your feature request related to a problem? Please describe.
Currently, VAICOM reads text in the OS System language setting, no matter what additional speech packs are installed.

Describe the solution you'd like
Being able to select the output TTS Synthesizer language

Describe alternatives you've considered

Additional context
Currently, the build in Crystal Palace feature in VAICOM reads the briefing in the OS Language. E.g. mine is set to German and VAICOM reads the English text in German, which sounds funny to say the least. No matter which language is set in VA, the read-back is always in the OS language. If I switch my OS language to english, everything works as intended.
This is an issue as long as I use VAICOM (+ 2.5 years). I never found a workaround and stopped using this feature (Crystal Palace) at all.
Would be nice to be selectable somewhere.

Apologies if this is actually already a thing but i've been unable to find such on the documentation

Currently you can set up your bindings for either the Pilot or RIO seat, but not both. Making binding for users who usually RIO in MP much harder

{TXT:vaicompro.playerdata.currentmodule.name} should have the options:
"F-14AB" to maintain legacy support, independent of your current seat selection
"F-14AB PILOT" for the front seat
"F-14AB RIO" for the back seat, RIO seat should use Radio 1 and 5 in VAICOM with easy comms off, with Radio 1 servicing whichever radio is currently selected by the RIO's radio select switch in the cockpit.

Only apparent alternative is to go in and change bindings manually depending on what you're flying that day, with no ability to select the radio being used in cockpit

When VPC is running, friendly contacts on the SA page (only tested in F/A-18) do not reflect the unit/number designation as defined in mission editor.

To Reproduce
Start any mission in F/A-18 and inspect friendly aircraft callsigns via the SA page. Without VA/VPC running, the callsigns will reflect the flight/unit designation (such as PC11 for "Pontiac 1-1" or DE21 for "Devil 2-1".

If you inspect the same with VA/VPC running, the same callsigns will be some arbitrary numbers like "0511" or "0321"

Screenshots
Without VPC/VA Running:

WITH VPC/VA Running:

Additional context
Add any other context about the problem here.

Issue: Config sliders create extra folders on desktop.

My setup:

• Running DCS Open Beta on Steam.
• Vaicom Community Release

Working Config options:

With this setup the community release works well, even if the sliders don't match my setup. If I change the sliders to represent my setup, it still works in DCS. but I get extra mods and script folder on my desktop. If I delete them they get replaced. If I keep them they get overwritten.
This happens if I select either Open Beta or Steam or both.

Thanks for all your good work!

If you travel to Oslo I will buy you all a beer.

Previously to community update 2.8, if I was taking from Kobuleti and wanted to change recipient to Batumi I had just to say:

"Batumi" pause "select" and the Batumi airport was selected in Vaicom so frequency was automatically changed (with easy comms off) in my plane, and I didn't need to say the recipient before the command, so I could just say "inbound" or "abort approach" and DCS would know I was talking to Batumi.

Now it doesn't do it. It will remain in the recipient I was starting the mission and if I say "inbound" it will talk with the first loaded recipient. This is very bad specially for multiplayer, were we can find several Jtac, or tankers to choose.

STILL works if I say "batumi inbound" or "batumi cancel aproach" but I have to be saying always the recipient before. Of course that doesnt't change the freq.

I tested this is the F18, F14 and F5. None of them are working. Only the frequency is changed... but not selected the new recipient. Will remain in the old one.

Here you have the options choosen. I made a clean install as the instructions to install the community 2.8 says. Also in Vaicom editor I have "select" under special commands category and segment is (undefined) Select recipient

Describe the bug
With "Aircraft Carrier Comms" and "Suppress Auto" selected, the CV responds to an overhead call when I am close enough, but I believe the audio call from my aircraft is successfully suppressed. If this is a bug, it is that the CV is still registering that I'm overhead when I haven't made the call, or that the audio is being suppressed but the actual message isn't.

To Reproduce
Follow the case 1 procedure in an F-14. Marking moms, see you at 10, then fly overhead CV (w/i like 3 nm). Listen for "[num] overhead angels [num]" from your pilot (you shouldn't hear it). Listen for the response from the carrier, you should hear it.

Expected behavior
The carrier should not respond until I have made an "overhead" call with Vaicom.

Screenshots
N/A

Additional context
N/A

When calling inbound to a carrier, the voice only reads off the numeric values for vector, distance, altitude and fuel. It does not use the full text which is displayed when the inbound is called (or when using the comms menu to announce inbound).
This issue was around in previous builds.

Describe the bug
PTT tab-> PTT selector up and down arrows don't work

To Reproduce
Open PTT tab-> click up || down arrow

Expected behavior
PTT mode hast to change

Additional context
May be we can just remove those arrows and leave the switch only?
If yes then could we change mouse click event over this selector to mouse wheel events up and down?

Describe the bug
As per the title.

Describe the bug

When I try to send the order to mount the NVG goggles, the ground crew instead rearm the plane. The plugin give a diferent order.

Describe the bug
Kneeboard - interactive bit is gray, other normal kneeboard pages work ok

To Reproduce
Open kneeboard, check if interactive kneeboard pages can be opened

Expected behavior
Interactive kneeboard pages should open

Screenshots

Additional context
I tried in DCS AH-64 module, but probably its not related to module. I installed MSI version over existing one - VAICOM.PRO.for.DCS.World.msi

F-14 module (both A and B) are not being hooked by the viacom plugin, as evident by the PTT menu in the viacom config app (see below). Due to this, commands do not execute in-game even though they have successfully been recognised by Voice attack. All other modules do hook and work correctly with viacom as expected in my case. Commands tested include the requesting of ground power, ground air and request for rearming/refueling.

PTT menu with F-14 (Instant action Cold & Dark Caucasus)

PTT menu with F-16 - working (Instant action Cold & Dark Caucasus)

DCS Log (before repair):
dcs.log

DCS Log (after repair):
dcs (1).log

DCS Log (without DICE & after repair):
dcs.log

Viacom log:
VAICOMPRO.log

Describe the bug
The command "Look for SAMs" it doesn't seem to work althoug is recognized. Others commands like "Look for Tanks" are working fine.

To Reproduce
Any mission with F14B with GBUs and Lantirn loaded, also with different units including SAMs. Order Jester to look for sams.

Expected behavior
RIO should move Lantirn searching any SAM and designate it when found one. In voice attack window should be a confirmation of the command.

Screenshots

The current kneeboard has multiple tabs and it has never been clear how to navigate to each one via voice command. I know that one can find the action and then create a voice attack command to go to it but this is not something which everyone wants to do or even can figure out how to do It's frustrating when I need to go to a tab, that I can't for the life of me remember what the command is. Is it show (tab)? Is it (tab) page? Is it show (some different name all together)? (i.e. to get to the JTAC page).

I would propose standardizing on all of these tabs with a clear and obvious command structure.
LOG - Show Log
AWACS - Show AWACS
JTAC - Show JTAC
ATC - Show ATC
AAR - Show Tanker (rename tab to TANKER)
AOCS -Show (Something more concise) and rename this
FLIGHT - Show Flight
NOTES - Show Notes
REF - Show Reference (Rename tab to Reference)

I would also ask that things such as next tab and previous tab be included for easier tab navigation for those who do not edit their voice attack to manually add these.
Add new command keywords to main kneeboard page to show that they are available.

Describe the bug
A lua Script using the DCS Scripting Engine (not MIST/MOOSE) can only send messages via five functions:

trigger.action.outText()
trigger.action.outTextToUnit()
trigger.action.outTextToGroup()
trigger.action.outTextToCountry()
trigger.action.outTextToCoalition()

When a text message is sent via these, with VIACOM enabled, the message is suppressed and not displayed to the player.

To Reproduce
Either from a script or from a tigger in the mission editor run any of those commands and try to send a text message.

Notice that nothing is displayed.

Disable VIACOM and reload mission, and notice that the text is displayed.

Expected behavior
VIACOM should not surpress these types of messages that mission designers and script programmers use to add richness and additional AI communication to players in-game.

Screenshots
N/A

Additional context
N/A

Describe the bug
As discussed in discord, having a high module count (38) will cause vaicom behavioral issues such as reinitialization with PTT press, PTT getting stuck open or closed, and failure to read in game easy comms.

To Reproduce
Install 38+ DCS modules.

Expected behavior
No change in behavior.

Screenshots
See Discord

Additional context
Issue being tracked via thread in discord and actively worked on. Fixes in PRs should be mentioned here for tracking.

Naturally this will be down the road, posting this "issue" for tracking and visibility, and so others don't post it all over the place here as well.

Similar to Jester, commands to control Petrovich in the Hind & George in the Apache need to be researched and implemented. This issue can be used to track progress on those updates as they are researched, added, and tested.

If any PR's with this functionality are added to be tested, please comment and link them in this issue.

Describe the bug
In VR mode Kneeboard opacity not working.

To Reproduce
1 - VIACOM config-EX tab - down "KNEE" slider to max pos(DIM) means max transparency
2 - DCS F-14 any mission: "Kneeboard" -> opens kneeboard window and no opacity applied

Expected behavior
It is expected that VIACOM config-EX tab - "KNEE" slider changes is change opacity of showed Kneeboard window in VR