Agent_wolf

When you move from pilot seat to CP/G you use a "pilot" keybind command. To move back to pilot seat from CP/G you must use a "CP/G" keybind command.

NEVERMIND: Did the "Finish ctrl v" thing again. Works now :thumbup:

Realistic ATC plugin extension The command "Request Launch" comes up as unrecognized in VA. 7:23:34.607 Unrecognized : 'request launch' Just me?

I belive you can copy your "input" folder in "C:\Users\NMD\Saved Games\DCS\Config" and paste it and override the "input" folder in "C:\Users\NMD\Saved Games\DCS.openbeta\Config. Hope this made sense :music_whistling:

THIS! plus slingloading, troop insertion/extraction in the same mission with the upcoming multicrew for the huey = Fantastic :thumbup: Thank you for posting this.

@lbellouny From the latest VA 1.8.2 Bug Fix. Fixed issue with minimize on startup and minimize to system tray not working together. Could this be the fix?

@lbellouny and emc. VA1.8 with latest vaicom works fine for me :noexpression:

Use command "Select Stations 3 4 5 6"

Hmm....

I get this when I have a target locked. Use the command "break lock" and try again

Hi Maestro What do you mean by Menus? Do you mean the F radiomenu (F1-F12) With Vaicom Pro you can use the "options" voicecommand to open the F-menu and the "Take" command followed by the F number you like to select. "Take 1" selects the F1 option in the menu. "Take 10" = F10 Other. Im not sure what you ask though :( If you have the F-menu popping in and out all the time then Vaicom Pro did`nt recognized the module/plane you are useing. Sorry.. shooting in the dark here :music_whistling:

No :)

Use command "Select Stations 3 4 5 6"

I had this issue for a long time too without thinking to much about it. I vent in game just now to test and found it to work this time, both single player and multiplayer. VA v.1.7.5 - VAICOM.DLL v.2.5.9.10 - AIRIO.DLL v2.5.1.0

I have the same behavior. The autoupdate seems to work but when I open Ctrl + Alt + C it shows the old version number, even after manually restarting VA. My VA shows this when autoupdating: 20.57.36 - Plugin 'VAICOM PRO 2.5' initialized. 20.57.36 - Ready for commands. 20.57.35 - Installing... 20.57.35 - Package download complete. 20.56.35 - Downloading package..... 20.56.35 - Executing automatic update. 20.55.01 - New update available! 20.55.01 - Initializing.. 20.55.01 - Press LCtrl+LAlt+C for config. 20.55.01 - VAICOM PRO for DCS World. License: PRO 20.55.00 - Plugin support enabled. This goes back to before AIRIO came out. I have gotten into a habit of downloading the latest .DLLs and replace the old ones after every update.

Try with ACM off at long range locking. AIRIO default command is "track single bogie ahead"

Voice Attack v1.7.5, Vaicom.dll v2.5.9.8 and AIRIO.dll v2.5.1.0 works fine for me

@Gannon. Try setting your radio on manual, not preset in cockpit. Then try the "select" command. That works for me. I use TX2 for my cockpit radio.

C:\Program Files (x86)\VoiceAttack\Apps\VAICOMPRO\Extensions

Downloaded latest Vaicom plugin and the AIRIO Dialog Extension. The changelog and the updated manual is in the .zip Edit: Here is some of the new commands. Link Host (show options) Link Host Stennis Link Host Darkstar Link Host Focus Link Host Magic Link Host Overlord Link Host Wizard --------------------------------------- TACAN Tune (show options) TACAN Tune Stennis TACAN Tune Arco TACAN Tune Shell TACAN Tune Texaco ------------------------------------- Align Fine

From the latest AIRIO Update :pilotfly: 01/04/2019 version 2.5.1 - Added INS Alignment commands for startup - Added TACAN tuning for Stennis/Air Refuel - Added DL host selection for Stennis/AWACS

Hi. Yeah that works fine. The issue is getting AIRIO to input and select player placed MapMarker in the F10 map as a Surface Target Waypoint. :)

Hi RedeyeStorm. I tested this last night with no joy. The Mapmarker waypoint should be part of the "Surface Target" waypoint. The command is "Navigate Target". I tryed all the different waypoint options (FP, IP, ST, HB, DP, Steerpoint 1-3) and I tried the "Restore" commands witch just reset the coordinates from the kneeboard or set coordinates to zero if not in the mission. This issue + not being able to set Datalink Host to Carrier/Awacs is the reason I`m not useing the AIRIO atm.

@P3CFE. Some of my squadmates had a similar problem. They had to go to LCtrl + LAlt + C window, Audio Tab and turn the switch from OPER to OFF. That gave them the ATC sound back.

Same here. If I run Vaicom Pro with AIRIO it brakes all inputs for the F-14B module except mouse. No keyboard, trackIR, Warthog Hotas. To get controls back to the F-14B I had to uninstall the F-14B module and reinstall it. As soon as I run VA with Vaicom again it brakes it again. So definetily a Vaicom AIRIO problem EDIT: Hollywood is aware of the problem. Hotfix pending