Hollywood_315

TALD support is included in next AIRIO update. Sent from my SM-G960F using Tapatalk

@Mirabelle @jv44bubi Cool, merci for the generous comments :thumbup: @TOViper Good point, will do cheers mate @Mangrove Not reproducible here. Also the plugin doesn't send any keystrokes (like F2) at all. You may want to inspect you're running VA and VAICOM latest versions (2.5.12.2). Grtz

Hi guys The 400 thing is reproducible and confirmed a snag in AIRIO: will be fixed in next update. Thanks for flagging.

You can keep your existing VA profiles and attach (daisy-chain) them to the VAICOM PRO master profile. Also you can use the plugins Exposed Variables to add dynamic module-specific stuff to your profiles i.e. apply different actions depending on the module you're flying. Details in the manual and various mentions along this thread, look here to get you started

@NakedSquirrel I like the idea, we'll have a look to see what can be done.

@stgchamby Addressed in next update. @Kristoffer79 No you use either one or the other. @RichW If needed, reset you custom path to force lua, delete export.lua from Saved Games then restart VA and DCS. @sollymans @FreightDog Not reproducible here, just as reminder you need PRO license activated, plugin Use With Multiplayer option must be enabled and the MP server must have Player Export setting set to ON. Thanks

@Snacks, Greyman The plugin auto-updater requires VA to run as admin. When updating VA that can get reset without being noticed. @Badass Imported items e.g. Action Do Something should be changed into a phrase that works for you using the keywords editor. Sent from my SM-G960F using Tapatalk

Leave small pauses (manual p. 15). Also use Select command a/o Instant Select option. Sent from my SM-G960F using Tapatalk

VAICOM doesn't use the comms menu but it is dynamically aware of all frequencies/modulations the mission recipients can be contacted on. So AWACS, tankers etc. can be reached on UHF just fine. Only with easy comms ON a simplification is made, restricting recipient categories to their default radios (VHF AM for AWACS). Sent from my SM-G960F using Tapatalk

Try disabling SRS mode. Sent from my SM-G960F using Tapatalk

build 2.5.12.2 All, Plugin build 2.5.12.2 has an EA patch for the Viper VHF radio. Auto-updates (reminder: VA must run as admin). Grtz Hollywood

Guys Ground Crew -> "Request Refuel" Aerial Tanker -> "Approaching for Refuel". It's in the ref. tables. Grtz

@Badass The import F10 Menu function is described in the user manual. It includes recursive import of the complete command tree and is by far the recommended option for this. @dburne Thanks Don not reproducible here, SNGL all working fine. Perhaps your Windows application log will give a clue. @MAXsenna It can vary depending on your keyboard locale mappings. @jameslockridge Try with "Approaching for Refuel", see the user manual reference tables.

For the Viper, the sim currently returns incorrect device on/off status for the VHF radio. Presumably an EA thing. Reported here: https://forums.eagle.ru/showthread.php?t=252665&highlight=vaicom Thanks

@Badass Right- not exactly sure though why you'd want to create such a custom command: - All standard commands found in the menus are already available in the plugin keyword set, - You can use the Import F10 Menu feature to add any non-standard menu commands, - The options/take commands are there to navigate the menus if all else fails. That said if you must, you may have some success by sending the '/' keystroke twice instead of once. Grtz

Ah ok thanks. For using a single PTT button for all modules, use the selector to set PTT mode to SNGL. This controls mic listen on/off states as normal. Hope it helps, grtz

Hi guys Ok not sure I could entirely follow the last pieces of this thread, but in any case in relation to the plugin and the Viper module: - The greyed-out VHF radio (and consequently missing squelch and beep sounds, etc.) is caused by seemingly inaccurate values returned by the sim related to the Viper VHF radio device on/off state, - This seems simply an EA loose end which in all likelyhood will be ironed out by ED at some point, - Just in case I added a report in the viper forum section: https://forums.eagle.ru/showthread.php?t=252665 - Let's see if this leads to follow-up by ED dev. which should resolve the issue for VAICOM PRO users, - Only if no fix by ED is implemented, ad-hoc workaround patches in the plugin may be considered for the Viper, - For other modules there is no issue. Thanks, Hollywood

Hi there Calling in an issue which is hidden for many users, however resulting in inconsistent radio behavior as experienced and reported by multiple users using the VAICOM PRO AI Radio comms plugin with the F-16C: https://forums.eagle.ru/showthread.php?t=198297. No doubt this is just an EA loose end, much appreciated if it can be addressed. Many thanks, Hollywood ----- OBSERVATIONS For Viper radio device with displayname VHF Radio AN/ARC-222, device ID 38, the sim always returns "false" for the following lua function call: - GetDevice(data.intercomId):is_communicator_available( 38 ) This is the case even when in-flight with all systems fully powered. This return value is inconsistent with the in-sim radio device actually being switched on, not damaged, and powered in the Viper pit, i.e. return value "true" is expected here. To note this function call does behave consistently for all other DCS Modules. ADDITIONAL INFO - Garmin not used. - No mods or alterations applied. - DCS.log shows no errors. - For the other Viper radio device with ID 36, displayName UHF Radio AN/ARC-164, the returned true/false value is as expected i.e. corresponding to the device state in the pit. REFERENCE -JSON snippet (as used by VAICOM PRO) representing the read sim info: PS issue also reported here, incorrectly flagged as [correct as is] https://forums.eagle.ru/showthread.php?t=252320 Thanks

@Firebird1955 Ok that's interesting. Noted, we'll need to see if it can somehow be reproduced. @Harker By itself that's normal behavior: not all modules support use of appendices (weapon, direction directives). We'll run a check on this re the Viper. In any case the 'Use Appendices' option must obviously be enabled in the plugin.

@Outlaw Download on the website is always the latest build. Build info now added on the download page for clarity, thanks for flagging.

@MAXsenna Yes 2.5.12.1 is latest build and has Viper support. @Firebird If there's been no change to the keywords you will only have those options. @NakedSquirrel It's not a command curently but we'll make a note to see if it can be added. @Manhorne I've seen the sim report Viper VHF radio as switched off (hence greyed out on the PTT page) even though it does appear to be switched on in the pit. Not sure yet if this sim report is in fact accurate (e.g. radio is switched off, not powered..) or not but let's keep an eye on. Could be worth reporting to ED if things are not consistent. It is Early Access so may be one of those things that will get ironed out by ED along the way. @stgchamby Suggest to try with what @Greyman says @kaltokri :D @Bluethornton One of the things you may want to check is the VR Audio Device option in DCS settings. @hreich Good you got it sorted, thanks for updating.

Well there is no problem. The command is in the profile, as said it's not supposed to be in the keywords list. You already have it in your profile so you can just use it, no need for any more steps. Hope that helps grtz.

The Scan Sector command is not in the dropdown, it must be added to the VA profile. Manual page 36-38.

@Greyman It works for Easy Comms ON but you may need to disable other entries in export.lua first (Simshaker, TacView, etc.) Interestingly display shows ' F-5E Tiger II ' for now (will be fixed) but the basic comms seem to work. A plugin update for Viper also supporting Easy Comms OFF will follow. EDIT: Viper hotfix published (auto-update).

You can do both (press and keep holding PTT): - "Options" -> show root menu, - "Darkstar,.. Options" -> show options for Darkstar AWACS unit, - "Mission,.. Options"-> show F10 menu, - "JTAC,.. Options", - etc. The Options command works even when menus are disabled in preferences.