Ghost Dad Recon

Awesome! Been waiting for this to try out Jester LANTIRN!

In my experience it doesn't actually matter what tanker callsign you say if there are multiple tankers on the same frequency, it selects the nearest one. Ie. if both Texaco and Arco are on the same channel, you can say "Arco, approaching for refuel" and if you're closer to Texaco the message will be interpreted as "Texaco, request rejoin". This is obviously not ideal, but it seems to be how it currently works (as of last time I checked at least).

Yeah, it's less-than-ideal that the aircraft disappears, but it's a technical limitation apparently. You would say "Take 5" to go into Navigation, then select whatever option is for map marker to waypoint the same way ("Take #").

You can do it using "Jester, options" and navigating the menu. That's how I've done it.

I have also had this issue in multiplayer, "map marker to waypoint" doesn't seem to like to play nicely in most multiplayer scenarios.

Ok, I have a Valve Index and I thought I was going crazy because I was getting eyestrain in DCS VR, but it appears that this could be the cause. To confirm, I forced IPD to 0 in DCS in order to minimize any parallax error, then compared a horizontal datum rendered by DCS (like a menu or the edge of a cockpit instrument) against the steamVR overlay menu, and it seems like the right eye viewport DCS is rendering is slightly higher than the left. Not enough to be obviously wrong at a glance, but enough to give me painful eye strain. Hopefully I can trim it out with the debug tool, but this definitely seems like it's a problem and not limited to WMR headsets. Edit: I just tried the debug tool linked previously: You can 100% reproduce this on my headset if you set the IPD in DCS settings to 0 (which I think everyone will agree should make both viewports identical) and then use the debug menu "swap eyes" option. If you close one eye then toggle swap eyes, the image you see will jump up or down each time you toggle. Unless I'm completely off-base, it should not change at all. Edit 2: Using "Make symmetric" seems to have resolved this for me, there is a noticeable difference in comfort level.

I have also had this issue in the F14. It's like it is caching the command and not actually sending it to DCS until I hit ptt again.

Hey Hollywood, Any chance we can get a command for the "spot" function for Jester (to tell him to look where you're currently looking)? Unless I'm missing something, I don't see it in the editor (the "spot" command in the editor appears to be for JTAC). As an aside, this is maybe beyond the scope of AIRIO, but it would be great to be able to tell Jester to defend when he's on manual CM modes. Probably needs additional functionality from HB, though. Great stuff, keep it coming!

Great! Thanks, Hollywood!

Is it possible to have the "hot mic" setting respect the position of the ICS switch in the cockpit? Ie. if switch is set to hot mic, hot mic is on, otherwise PTT as normal. In my experience it doesn't appear to care (if I have hot mic enabled in the VAICOM settings, I get hot mic behaviour even if I set the ICS switch to cold). It'd be great to be able to switch this behaviour right from the pilot seat.

Happening to me as well today. Glad it's not just me, was losing my mind.

Hey Hollywood, didn't get a response to something I posted a while back so I figured I'd resurface it. I can't even imagine using Jester without AIRIO at this point, and DCS without VAICOM would be a huge step backwards for me. Real good stuff!

Hey Hollywood, The manual tuning stuff works great, although I have one issue that seems to be coming up and I'm having a dog of a time resolving it. Any frequency that starts with a '2' is tripping up the voice recognition, and I'm not sure how best to handle this. ie. "Radio tune two two five decimal zero" will get interpreted by VA as somthing like "10:52:13 AM - Unrecognized : 'radio 2225 decibels are'" whereas "Radio tune three two five decimal zero" will (usually) get correctly identified as "10:55:48 AM - Recognized : 'radio tune 3 2 5 decimal 0' (Confidence 81)" Normally I'd just remap the command phrase to something else to avoid the "tune/two" mixup, but that doesn't seem to be possible with these extra phrases. Any suggestions? Also, would it be possible to add "Radio tune channel #" or something similar, ie. to tell Jester to tune to a specific channel in addition to selecting by frequency? This would be helpful to have when dealing with SRS in a complicated radio environment (ie. if you have a common channel and an ATC channel already programmed in the radios for the aircraft, it would somewhat simplify keeping track of who is tuned to what). E: Also just remembered an issue I encountered, when trying to contact a tanker, regardless of what callsign you actually specify, the message seems to go to the nearest tanker to your position (if the tankers are on a common frequency at least). Not something that comes up particularly often, but it does seem like undesired behaviour.

Bang on. This resolved the issues, good call! Thanks a million! @hollywood, not sure if it's possible to incorporate the UDP datagram packet size into an update? Seems very likely this was the compatibility issue for both the extended commands and the module display on the config screen.

@sc_neo @Home Fries @Hollywood I too am a W7 holdout. I'll wait for your packet size workaround @sc_neo, hopefully that addresses the issue in the short term.

Not running Chatter. Something thing I noticed, the behaviour is a little different between normal AIRIO commands and the extended commands in how they show up in the log. Regardless of if I have DCS running, I still get the normal command set recognized, but the extended command set says "AIRIO commands are not available". So the behaviour I'm seeing doesn't appear to change if DCS is running or not. It almost seems like the functionality implementing the extended command set is not present in the version I have (which is why the first thing I did was make sure the DLLs were up to date). The command is definitely recognized, it just doesn't have a valid command to execute. I grabbed a screenshot of the actual command config from VA for your review, in case something looks off here.

Ok, I'll run through these in order. -Was using SNGL, but I tried all other modes, no joy. -ICS HOT MIC does not appear to do anything for me (on or off doesn't make a difference, I have to use PTT to talk to Jester). In any case, having it off or on did not change the behaviour. -Easy Comms was on before, but turning it off does not seem to have made a difference. -This is openbeta standalone. -AIRIO license is listed and appears valid on the About page. -Auto-import was enabled when I installed F-14. -After reset Keywords and Settings, HOT MIC starts working but no joy on the manual tune commands.

Right, which is confusing because all the other AIRIO commands are recognized and work fine. It's just these additional ones that don't work (even in the same mission when everything else is working, so it shouldn't be any issue with the dll loading, license activation, or mission/module recognition).

Doesn't appear to be the case, the command is getting recognized but it reports "not available" in the log (and there is no response at all in DCS) regardless of how long I depress the PTT. 10:40:31 AM - Listening suspended 10:40:31 AM - Joystick : 'Transmit TX4 release' 10:40:30 AM - AIRIO commands are not available. 10:40:30 AM - Recognized : 'tacan tune x-ray 0 7 4' (Confidence 92) 10:40:26 AM - Listening resumed 10:40:26 AM - Joystick : 'Transmit TX4 press'

Hi Hollywood, Still fiddling with this, can't seem to get it working. 3:11:05 PM - Listening suspended 3:10:58 PM - AIRIO commands are not available. 3:10:58 PM - Recognized : 'radio tune 2 5 7 decimal 0' (Confidence 96) 3:10:57 PM - Listening suspended 3:10:57 PM - Joystick : 'Transmit TX4 release' 3:10:53 PM - Listening resumed 3:10:53 PM - Joystick : 'Transmit TX4 press' 3:10:49 PM - Unrecognized : 'Radio Tune 257.0' 3:10:48 PM - Listening suspended 3:10:48 PM - Joystick : 'Transmit TX4 release' 3:10:45 PM - Listening resumed 3:10:45 PM - Joystick : 'Transmit TX4 press' 3:10:41 PM - TX4 | SEL/AUTO: [ F-14 AI RIO ],[ ],[ ] TACAN Tune TAC [ ] [ ] 3:10:41 PM - Recognized : 'TACAN Tune X-Ray 79' (contains 'tacan tune') (Confidence 78) 3:10:41 PM - Listening suspended 3:10:41 PM - Joystick : 'Transmit TX4 release' 3:10:37 PM - Listening resumed 3:10:37 PM - Joystick : 'Transmit TX4 press' This is all with DCS running and in focus, I have no issues getting any other commands to register. Any suggestions? E: I ran again with debug enabled in case there's anything interesting in the logs, but it doesn't appear so. You can see that the commands are recognized but don't go through (and the other commands "wake up" and radar hot/cold are recognized and accepted). 3:53:38 PM - Listening suspended 3:53:26 PM - Constructing message... 3:53:26 PM - TX4 | SEL/AUTO: [ F-14 AI RIO ],[ ],[ ] Switch Radar Transmit [ ] [ ] 3:53:26 PM - Unspecified recipient called: using default unit for this category 3:53:26 PM - Have result, identified as command : Go nose hot 3:53:26 PM - Captured sentence: go nose hot 3:53:26 PM - Recognized : 'go nose hot' (Confidence 95) 3:53:25 PM - Listening suspended 3:53:25 PM - Joystick : 'Transmit TX4 release' 3:53:24 PM - Listening resumed 3:53:24 PM - Joystick : 'Transmit TX4 press' 3:53:22 PM - Constructing message... 3:53:22 PM - TX4 | SEL/AUTO: [ F-14 AI RIO ],[ ],[ ] Switch Radar Standby [ ] [ ] 3:53:22 PM - Unspecified recipient called: using default unit for this category 3:53:22 PM - Have result, identified as command : Go nose cold 3:53:22 PM - Captured sentence: go nose cold 3:53:22 PM - Recognized : 'go nose cold' (Confidence 93) 3:53:21 PM - Listening suspended 3:53:21 PM - Joystick : 'Transmit TX4 release' 3:53:20 PM - Listening resumed 3:53:20 PM - Joystick : 'Transmit TX4 press' 3:53:15 PM - AIRIO commands are not available. 3:53:15 PM - Recognized : 'tacan tune yankee 0 9 8' (Confidence 95) 3:53:15 PM - Listening suspended 3:53:15 PM - Joystick : 'Transmit TX4 release' 3:53:11 PM - Listening resumed 3:53:11 PM - Joystick : 'Transmit TX4 press' 3:53:10 PM - Listening suspended 3:53:10 PM - Joystick : 'Transmit TX4 release' 3:53:09 PM - Listening resumed 3:53:09 PM - Joystick : 'Transmit TX4 press' 3:53:04 PM - AIRIO commands are not available. 3:53:04 PM - Recognized : 'radio tune 2 5 2 decimal 0' (Confidence 96) 3:53:04 PM - Listening suspended 3:53:04 PM - Joystick : 'Transmit TX4 release' 3:53:00 PM - Listening resumed 3:53:00 PM - Joystick : 'Transmit TX4 press' 3:52:56 PM - (awaiting additional input) 3:52:56 PM - Have result, identified as recipient : Jester 3:52:56 PM - Captured sentence: jester 3:52:56 PM - Recognized : 'jester' (Confidence 95) 3:52:56 PM - Listening suspended 3:52:56 PM - Joystick : 'Transmit TX4 release' 3:52:55 PM - Listening resumed 3:52:55 PM - Joystick : 'Transmit TX4 press' 3:52:48 PM - Constructing message... 3:52:48 PM - TX4 | SEL/AUTO: [ F-14 AI RIO ],[ ],[ ] Reset [ ] [ ] 3:52:48 PM - Unspecified recipient called: using default unit for this category 3:52:48 PM - Have result, identified as command : Wake Up 3:52:48 PM - Captured sentence: wake up 3:52:48 PM - Recognized : 'wake up' (Confidence 94) 3:52:48 PM - Listening suspended 3:52:48 PM - Joystick : 'Transmit TX4 release' 3:52:47 PM - Listening resumed 3:52:47 PM - Joystick : 'Transmit TX4 press' 3:51:33 PM - Plugin 'VAICOM PRO 2.5' initialized. 3:51:33 PM - Ready for commands. 3:51:33 PM - Startup finished. 3:51:33 PM - No new DCS modules to import. 3:51:33 PM - Success. 3:51:33 PM - Building master labels table... 3:51:33 PM - Success. 3:51:33 PM - Building master keywords table... 3:51:33 PM - Adding 0 imported menu commands. 3:51:33 PM - Adding 0 imported ATC aliases. 3:51:33 PM - Success. 3:51:33 PM - Loading F10 menu items... 3:51:33 PM - Success. 3:51:33 PM - Writing updates. 3:51:33 PM - Loading keywords database... 3:51:33 PM - Done. 3:51:33 PM - Importing RIO extension pack... 3:51:33 PM - Checking VA profile. 3:51:33 PM - 4/5 DCS-side files were updated. 3:51:33 PM - Reset: TabSheetBar.lua 3:51:33 PM - Reset: speech.lua 3:51:33 PM - Reset: RadioCommandDialogsPanel.lua 3:51:33 PM - Reset: VAICOMPRO.export.lua 3:51:33 PM - Unchanged: Export.lua 3:51:33 PM - Saved Games folder = C:\Users\Mark\Saved Games\DCS.openbeta 3:51:33 PM - DCS World installation path = E:\DCS\DCS World OpenBeta 3:51:33 PM - Using Registry entry for 2.5 OpenBeta 3:51:33 PM - DCS World installation found: version 2.5 OpenBeta 3:51:33 PM - 4/5 DCS-side files were updated. 3:51:33 PM - Reset: TabSheetBar.lua 3:51:33 PM - Reset: speech.lua 3:51:33 PM - Reset: RadioCommandDialogsPanel.lua 3:51:33 PM - Reset: VAICOMPRO.export.lua 3:51:33 PM - Unchanged: Export.lua 3:51:33 PM - Saved Games folder = C:\Users\Mark\Saved Games\DCS 3:51:33 PM - DCS World installation path = E:\SteamLibrary\steamapps\common\DCSWorld 3:51:33 PM - Custom install path used for 2.5 3:51:33 PM - Executing automatic lua code installation. 3:51:33 PM - License: PRO 3:51:33 PM - Plugin version 2.5.10.0 (release) 3:51:33 PM - Initializing.. 3:51:33 PM - Press LCtrl+LAlt+C for config. 3:51:33 PM - VAICOM PRO for DCS World. License: PRO 3:51:32 PM - Plugin support enabled. And just to confirm, I am running the latest versions of both VAICOM and AIRIO. (I just checked to make sure I hadn't missed an update!)

Hi Hollywood, I'm trying to get AIRIO to recognize manual tune commands. They seem to be recognized at least at face value by the VA profile, but they don't seem to go through to DCS. TACAN Tune [...] just seems to get recognized as "TACAN tune" and displays the hint cues for that root command. Link tune and radio tune don't go through at all (although radio tune will get recognized in the log, it says "AIRIO commands are not available" as if DCS wasn't running at all. Not sure if I'm doing something wrong here, I believe I have the commands imported correctly (they ended up under "Extension packs" in the profile and did not add any command phrases to the dictionary). Any ideas?

Hi Hollywood, Fantastic stuff! VAICOM really improves my immersion when flying, and generally works impressively well. I've been playing with AIRIO since you released it, and it's good enough that going back to playing without it is kind of a non-option, but I do have one major reservation right now (that I have seen other people bring up) which is regarding control over the RIO's UHF/VHF radio. Particularly when using SRS it is important to be able to tune this to a specified frequency, which there is currently no way of doing without the Jester menu. Can you look at addressing this?