Hollywood_315

All, For info: latest versions plugin 2.5.11 and AIRIO extension 2.5.3 are available on the website http://www.vaicompro.com/downloads.html If you want, you can download these for manual dll replacement (update your plugin first before updating AIRIO). These updated versions work with current DCS openbeta. The plugin auto-updater will be switched on once ED has propagated the latest ob changes into their release version i.e. later this week.

Fair question: it's yet to be determined. We've only put some preliminary groundwork in place for the carrier comms. However in the end this comms upgrade will also involve ground ATC and potentially other areas, and at this stage the scope is not yet entirely clear. So we'll make that assessment as we go along. In any case it's great that ED is putting their attention to communications as an important part of a realistic sim experience. Definitely stuff to look forward to :thumbup:

AIRIO WIP update As a WIP update: dev work on AIRIO 2.5.3 is done and it will now go through testing. This update includes the following Jester stuff: - Added commands for Radar Mode selection, - Added commands for Radar Stabilize, - Update for changed Ripple quantities, - Update for changed for relative turns (Iceman), - Translation fix for manual radio tune, - Added commands for F10 map markers, - Added command for LANTIRN, - Misc tweaks and finetuning. Grtz

Thanks rogue. When using the NORM push-to-talk mode these switches are indeed mapped as you say. Question was more on the slot allocations i.e. for the Hornet COMM1 is on TX1 but you may want to have it e.g. on TX4 instead in some cases for example because you have mapped that one to the UP switch on your controller. There's a lot you could do with the Exposed Variables but let me have a think on potential other options and get back on this one.

@Spartanic :rotflmao: @Andrew @Rogue That's a good point. Can you let me know if this is specific to the FA-18C or does it also apply to some other aircraft. @Home Fries Cheers mate, much appreciated. You're right of course. Let me have a chat with the forum admins and see what can be done. @all Thanks for your support! :thumbup:

@KewlerMouh Thanks for the generous comment. The Map Markers feature is work in progress for next AIRIO update. @Greyhound Try run a DCS repair and restart VA. @Ares63 Not sure I follow. You may want to inspect your keybinds in dcs options, manual page 10. @Shane45 CB UHF is normal. Make sure your apps are all up-to-date (VA, VAICOM, 3rd party apps) and inspect dcs.log for clues. Run a DCS Repair and restart VA, for testing disable other app entries in export.lua. Feel free to PM. @bucketeye Make sure you're using the correct profile and that your database is updated with the AIRIO keywords. Also HB have made several Jester changes in latest DCS OpenBeta. These will be addressed in next AIRIO update after the changes have propagated to Release version. DCS Release works normal. @Spartanic There's no API in place atm for keybinding those functions. It is a nice idea though, may be considered for feature roadmap.

@Wayan For MP you need to have the Use with Multiplayer setting enabled in preferences and the MP server needs to have Player Export enabled. @Aeons No these are profile commands i.e. not in the editor. @sohei All right thanks for the update.

@Aeons You need to add the command, check manual page 37.

@Kaos OK not entirely clear what's causing it but suggest to try with disabling Audio Redirect and removing Config and Database subfolders. Then restart and try again. PM me if you get stuck.

Quite a few questions around this lately: of course the upcoming new Carrier Communications (and to be updated ground ATC comms after that) has our full attention. Stay tuned! :thumbup:

@christianholmes There's quite a few other settings you need to take into account. Look here http://forums.eagle.ru/showpost.php?p=3819172&postcount=1776 @stretch Suggest to run a DCS Repair. @hreich No new commands were added afaik. If you know of a specific one missing make sure to clearly point them out. EDIT: Radar Ground Stabilize is planned for next update. @Schlapperklange Thanks for flagging, added to the list for review. @jasonbirder What @astrospud says: use Training Mode for keywords, and observe the micropauses in your calls (page 15) eg. 'Kobuleti,... Ready for Departure.'.

You'll need to configure your board so that all PTT buttons are of the press-and-hold variety. Sent from my SM-G960F using Tapatalk

Ok the plugin reads the radar lock state directly from the sim. There could be a snag in some particular missions perhaps. It hasn't been observed at any time during testing. A link to a miz file where this is consistently reproducible would be good to have thanks Sent from my SM-G960F using Tapatalk

By itself Radar lock state behavior is normal, you will have the same when using the traditional menu wheel instead of AIRIO. When locked to a contact (STT) you cannot change certain radar scan parameters such as range. The 'break lock' voice command is used to have Jester release the STT state and then these parameters can be changed again. Sent from my SM-G960F using Tapatalk

@rocketeer When using your own commands you need to use a TX for PTT. Can be any TX but when you want a dedicated key for your own commands use TX6 making sure press/release are properly configured. @biselvon Make sure your VA version is current i.e. 1.7.5 @Maddog Translation support for the new AIRIO manual tune commands will be in next update @onslawt Ok good you got it to work @Requiem The simple way is using the SRS radio slot mapping for the F-14 @overalien The delay hasn't been reproducible, perhaps check if the log gives any clues. For the F14 confirm your menu setting in DCS/Special is set to default. By @snacks' suggestion also inspect your export.lua in Saved Games. Grtz Sent from my SM-G960F using Tapatalk

@Badass Use the 'Take 1' to 'Take 12' voice commands for menu items selection, see reference tables in the manual. Alternatively go with @SgtCoyle's suggestion for F10 menu commands import.

@Glass_zero Did you update your keywords database (editor tab)? @Wulf Do you have Link to Radio Power setting on @agathorn Inspect the Audio tab and switch off Audio Redirect. Also make sure your Rift device is configured to playback Windows audio. @TheFlyGuy Good that you got things to work. Your mic device problem seems to be some USB driver thing (perhaps power scheme setting). @Rennes We'll have a look. The F-5E radio is modelled differently than other modules so could be something specific. You may also want to check if you can solve it by changing your SRS PTT config.

@FlyGuy Suggestions 1) You're on DCS Steam version. Try with unchecking the ob box in the Config tab custom path. 2) If no improvement run a DCS repair first 3) Then clear export.lua in Saved Games, i.e. making sure no other apps are interfering, 4) Do a manual lua code install per page 35. If you get stuck PM me. Grtz

@tspencer227 The log shows a problem in VoiceAttack, not inside the plugin. You may want to flag it with VA support. @Mojo That goes with the plugin master volume so you can set the desired balance in Windows audio mixer. @steve The plugin is at 2.5.10. The lua code blocks may still say 2.5.9 but that's fine.

@JG13~Wulf Ok as said this is a bug in the Bf109 itself, not in VAICOM. For reporting: there are unwanted side-effects when processing the 1591/1592 external input commands for PTT. @Gunterlund21 If your menus pop up when using PTT: make sure to clear all key / button bindings in DCS config, user manual page 10. If you see a blinking menu: this means the lua files in Saved Games are properly installed, but the ones in the DCS program folder are not. Specifically it points to RadioCommandDialogsPanel.lua not being configured properly. The standard way of approaching is 1) run a DCS repair, 2) confirm VA runs as admin, and 3) set the custom path in the Config tab. On manual page 35 there's a listing of the lua files involved and their locations for manual inspection. Also make sure no other apps are interfering in export.lua. @Linkage Assuming you're on Win10 with VA latest version 1.7.5. For Steam it can be a matter of trying without the ob option checked. PM me if you get stuck. @Fries Much appreciated mate. Yep that TARGET profile looks like a pretty elaborate piece of work for testing as well. We got our hands on a temp replacement box we'll probably keep that for the Win7 reference so should be OK. Cheers :joystick:

@sc_neo Hey mate many thanks for updating on the UDP snag for Windows 7. It's being looked into for a fix in next update. Generally: Windows 7/8 is becoming ever harder to support. Pretty much all support time is spent on Windows 7 cases these days, it is prone to very specific oddities (like the UDP packet case) which are just not a factor in Win10. The old Win7 test machine has died recently and specific testing for Win7 in reasonable timeframes is becoming an issue. Already there are a massive number of testing and support axes to work against for this plugin: DCS Release or OpenBeta, Singe Player or Multi Player, Easy Communications On or Off, plugin Free or PRO version, Extensions installed or not, 30+ different aircraft modules, combinations of settings, and then Windows of 7 8 or Windows 10,.. you get the picture. While I will still try to support for legacy Windows versions where I can, win10 will become the only officially supported OS going forward. PM me in any case of more questions and thanks again for you determination with tracking down the UDP thing :thumbup: @Highwayman-Ed Can you try using the Select command without call Jester first, e.g. just say 'Batumi,.. Select.' @overalien See answer to @Ed @Linkage Looks like you may need to point to your DCS install folder with the custom path option. Run a DCS Repair first. Look here for the 2 mins install fix: youtu.be/LchLOQxKfXY?t=722 http://www.vaicompro.com/faq.html

@Fries That's certainly a possibility. Any unexplained snag recently has turned out to be Win7 related somehow. No such issues on Win10 it seems. If GhostDad is also on Win7 it would at least point in that direction. In any case plugin support for Win7/8 is scheduled to be discontinued. @Wulf Thanks, the 109 has been looked into before and this is actually a bug in the DCS module itself. Specifically it responds inadvertently to a 179 external input command. So it would need to be fixed there. You could try switching Easy Comms On/Off, may help as workaround. Cheers

@HomeFries It's not entirely clear what could be causing this. Suggest to try this: set import new modules to OFF, then close VA, delete Config and Database subfolders and restart.

OK seems like you may have a stuck auto-update somehow. In DCS options/Special/VAICOMPRO you can check if your dlls are up to date (2.5.10/2.5.2/2.5.2) Confirm VA is latest version 1.7.5. and is running as admin. If you find an Updates subfolder and/or an update.cmd file, delete them and restart VA. Alternatively get the latest dll files from the website and replace manually: http://www.vaicompro.com/downloads.html

@Kaos Thanks mate @Phantomflyer65 The license is one per machine. @GhostDad Did you try clearing the Config subfolder? @zionid This is described on manual page 38.