Hollywood_315

@Max The effect has not been reproducible in any module mode or setting. Suggest to confirm testing with a clean profile with MP Only selected on the MP tab, Release Hot set to off. Grtz

"Command disabled for this session and was not executed" This is a normal message you get when the Release Hot feature is active (check light on PTT tab) and you issue a recognized VAICOM command with PTT key not pressed. However the screenshot suggests you run some kind of customized TX config where TX1 and TX6 are pressed/release at the same time. Suggest to use Config tab/Export button to obtain a standard stock .vap profile file and test with that.

Build update 2.5.25.1 has hotfix for Interactive Kneeboard CASE II/III Thanks

@Nickentik On the MP tab, inspect your VoIP Control slider. If it's on TX Link mode, select MP Only and restart. Alternatively select one of the other two modes with the slider. For details on the TX Link feature for VoIP see manual page 26. Grtz

Hi there people Just to make you aware that the loss of some Interactive Kneeboard notations in DCS 2.7 has been flagged. ED is still making changes to 2.7 openbeta at this time. Once 2.7 moves out of beta and into stable release version, a plugin update will be planned. All Interactive Kneeboard functions work in DCS 2.5 release version. All the best Hollywood

Hi guys just to add that the supercarriers all have callsign aliases in the default database. If a particular unit name gives you difficulties you may want to give them a try. For Stennis, callsign is Courage. See manual page 75.

Hi everyone - all the best wishes for the new year! This week we'll be rolling out plugin update 2.5.24 with some tweaks for the Interactive Kneeboard including added support for CASE II/III carrier recovery. Also, we'll have AIRIO update 2.5.10 with improved TACAN support and new commands such as for target size selection. Stay tuned! Hollywood

Good to hear! Cheers

Excellent - thanks for sharing.

What you see is normal - you can't use a radio before it's powered on.

Update with FINISH and use the corect syntax e.g. ' JTAC,... Page'. See manual. Carrier CASE I works, CASE III doesn't: known issue.

Good to hear you got it working

With VSPX you need to use a shortcut for calling up the kneeboard, this is known. Check the Easy Comms setting with a mission running and bear in mind the actual EC setting can be forced by mission design.

Ok noted for the wishlist thanks.

CASE III is not working atm for the Interactive Kneeboard, will be addressed in next update.

To see the module name, add a 'Write to log' command to one of your TX press commands using the token {TXT:vaicompro.playerdata.currentmodule.name}. Start a mission and press the TX.

Each F10 command has a unique ID that is stored by VAICOM. Location of the command in the menu tree is irrelevant.

Hi all Just to add that there is another elegant option to consider which uses the plugins exposed variables. Exposed variables are there to cover exactly these types of scenarios. Let's assume you already have configured a default 4-hat setup for TX/PTT on your throttle, which you use for all aircraft. But for a specific aircraft, let's say the Mig28, you want TX2 mapped to a hw button on your stick instead of the throttle. This can be achieved in two steps. Step 1 Edit the TX2 Press and Release command in the profile (which are mapped to a throttle button) Create a conditional block around the plugin call using the exposed variable for the active module name: - Go to command edit menu Other -> Advanced -> Begin a Conditional (If statement) block -> Single condition -> Text - Variable/Token {TXT:vaicompro.playerdata.currentmodule.name} Does Not Equal Mig28 - Move the 'execute external plugin 'VAICOM PRO 2.5' line down to sit between Begin and End so result looks like this Begin Text Compare {TXT:vaicompro.playerdata.currentmodule.name} Does Not Equal ' Mig28' 'execute external plugin 'VAICOM PRO 2.5' End Do this for both the Press and Release command. The effect is that the default TX2 Press/Release combo is now no longer used with this module. Step 2 Commands in the VA profile can be duplicated. Continue by making a copy of the TX2 Press command that you just edited by using right-click -> Duplicate. The command edit window opens. - In the command edit window, doubleclick on the Begin Text Compare line and change 'Does Not Equal' to 'Equals' - Tick the 'When I say' textbox and change the command name to 'Transmit TX2 press (Mig28)' - Important: after editing the name, untick the 'When I say' checkbox again! - Edit the When I Press Key/Button with the ... button and map the command to the stick hw button you want to use with the Mig28. Finish with OK/Apply/Done. Now do the exact same steps with the TX2 Release command copy. Important: when changing the button binding for Release this item must be checked: 'Shortcut is invoked only when all keys are released'. Done. If you've executed the above steps carefully, the stick hw button will now be used as TX2 press/release combo for the Mig28. For all other modules, the TX2 button on the throttle is used instead. Needless to say you can repeat this recipe for as many module/button scenarios as you want. This means you will not need multiple profiles but can handle it all in a single one. I hope this will be helpful. Grtz

Can you check either one of the following - Uncheck Instant Select in preferences, - Call just "approaching for refuel" i.e. without the "Texaco", - Set PTT mode to NORM/MULTI instead of SNGL. Thanks

@Chaz Noted, thanks for flagging. If there's a mismatch there we'll fix in next update.

That is correct. With easy comms off you need to tune the radio before making the call to the recipient, either manually or using the Select command.

Disable Garmin in DCS Module Manager.

@INFIDEL 1-1 It appears you have some mod interfering with kneeboard bookmarks. Suggest to run a DCS Repair and test without mods. Disable Auto Browse on the EX tab to disable the automated page switching.

The plugin doesn't send any keystrokes so it looks like your problem lies somewhere outside. In any case nothing like this has been reproducible. Suggest to start with a full DCS Repair, disable all mods. Use Reset tab to reset keywords database and enable Debug Mode. Then import a fresh VAICOM PRO .vap profile in VA (using Config tab/Export button and import in VA, FINISH steps) and try again.

What Hornblower says, also confirm Use Appendices is enabled in preferences.