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.