Callsign JoNay

So is it safe to assume the removal of the probe door is strictly cosmetic? Or does it affect the drag of the FM?

This is going to be very good for our Phoenix if it's going to do what I think it's going to do. An example of the current parallel navigation, and why it can be a problem:

Oh would you look at that. It's amazing the things I don't notice in a module that I fly almost every day. Yeah, the knob doesn't have any effect on my end either.

Is there a knob that independently controls the pitch ladder brightness? If so, I've never used it. Where is it located? Or do you mean the HUD brightness? My HUD brightness knob works fine, I use it every day.

Also some feet pr0n...

I managed to fix almost everything that was bothering me on my own by deleting the broken commands from the AIRIO command list, and rebuilding them myself as simple button press sequences in regular voice attack. Fixed: -The entire NAVGRID category. -Attack modes Pilot, Target, Manual, and even IP in case I ever use that mode some day. I still can't figure out how to fix "Toggle View" which supposed to toggle the FOV of the LANTIRN. The command works if you're QHUD, but not AREA track or Q any of your WPs or DES. I don't know how they got that to work in the first place since there is no Driver seat command to toggle it, and I don't want to hack up my DCS key file, so I'll live with it for now.

RT or LT is his aspect relative to you. If it said 0 that would mean he's pointing right at you. RT 177 means he is rotated to the right 177 degrees from looking at you. So essentially he's flying away from you, and you can compare that to your heading on the VDI or BDHI which is right around 360. We can conclude that he's flowing North same as you are. You can also verify that by the low closure rate. Your speed is around 440, and the closure rate is +113, so he's doing about 320ish. If he was coming towards you, or flanking in some way, the closure rate would be higher.

CPU temps were definitely running high. I cleaned up the chip and the cooler, re-applied paste, and it's much cooler now. I'll monitor to see if the freezes go away. I still don't understand why my computer freezing would cause others near me to freeze also. I was not hosting the server.

Literally no one. I think people are trying to tell you to let them worry about that. I don't see anyone requesting another AI to take over for the AI they just disabled. For the record, I don't have a dog in the fight. I'm fine with managing Iceman through the wheel. I think people are just confused why it's possible to implement an on/off switch for Jester but not one for Iceman. Is it impossible to just allow the jet to nose dive into the ground with all the switches staying in the last place they were switched to?

But why would that also freeze my wingman's PC?

Hmmmm.... Still getting this odd freeze. Video attached: This was after 1h 7m in flight. These freezes almost always occur a little bit after 1hr of flying, and within 20-ish nm of a tanker. I don't know if the tanker has something to do with it, or it's just coincidental since I'm most likely to be grabbing gas around this time. The strange thing is both myself and my dash-2 who was on the left basket both froze within 3 seconds of each other. We confirmed the server was still up and not responsible for our freeze. A near identical situation happened on June 23rd. A very similar checkride with a couple of new recruits. I was in the RIO seat for dash-1, and we were flying with a solo driver in dash-2. We had both been flying for an hour or so, and were both plugging baskets in a 135 when myself and the solo driver froze within seconds of each other. My pilot was unaffected AFAIK. @IronMike I saw you comment on a Reddit thread about the same issue authored by someone else today. I don't think it's just me. Feels like something funky is going on.

Apply some yaw trim.

Since November/December 2021! Ummm...Is there a way to go about requesting a refund?

Server side tracks are reliable for me. You won't have any in cockpit views though.

Edit: Actually upon further testing, the attack mode commands do not work.

Yeah the HUD and E-bracket are very accurate in DCS. I reference it all the time.

So follow up... I've noticed that almost the entire GRID category is FUBAR. Even when I jump in the back seat to enable the NAVGRID, and jump back to the front seat, setting things like coverage and scan rage after enabling the NAVGRID is a complete mess. Jester is entering all kinds of incorrect values in the wrong places. Anyone know if this will be fixed at some point?

Is it a bug? Bomb mode still automatically sweeps the wings between 55-68 degrees. Maybe it's supposed to be that way?

Are you using a datalink host to an E-2 or E-3? I have not noticed any Link-4 contacts blinking out of existence, unless I use a ship as a host. Then the datalink seems to blink on and off and back on again every 3 or 4 seconds for some reason.

Well 1 usually indicates True, so I assume there is some sort of radar correction mechanic implemented, but as to how it actually functions in the sim, I have no idea.

F/A-18C, F-16C, and A-10C II are all full/waitlist as of the date of this post. Still recruiting for: A/V-8B, AH-64D, F-14B, and LOTATC.

Can we get a binding for the red filter for the VDI? We have one for the HUD, but not for the VDI currently.

Yes, it's all broken again.

I noticed a mistake in the AIRIO PDF: After enunciating "enable grid" for three hours and having the software hear "Able grade, enabled great, enabled grade, enabled a raid, and Mabel grade" and anything you can think of except for "enable grid", I noticed in the Editor Tab that the correct voice command is "GRID ENABLE". So that was frustrating. You know what's even more frustrating? Even after telling Jester to "grid enable" he won't do it, even though he says "Roger". Is this a bug or is there some way to use the NAVGRID that I don't know about? Some other things that could make AIRIO better... If I STT lock a contact I am no longer able to change the scan range. It gives me some text in the upper corner that it's N/A since I have a target locked. That's pretty dumb. The RIO should be able to re-scale the TID regardless of using an STT mode. Can we get that fixed? Also, how do I get Jester to set Manual Mode for bomb delivery? I only see commands for "Attack mode Target" and "Attack mode Pilot". Having access to Manual mode is kind of important for GBU deployment. Is there a way to still have access to the Jester wheel while using AIRIO? Considering that it still has some obvious problems it would be nice to have a way to use the standard Jester wheel to augment it.

When I RIO for a human driver and I'm using a ground stabilized TID mode, or the NAVGRID, I don't just set it and forget it for so long that I allow my driver to fly us off the edge of the screen like Jester currently does. It would be a much appreciated quality of life improvement if Jester could automatically re-center the TID once in a while. Every 10 seconds or so would be . Also, it's annoying to me the player how I have to re-request Jester to center the TID/NAVGRID on the aircraft again every single time after I temporarily switch to an aircraft stabilized mode. Again, it would be much appreciated if Jester remembered that the user likes to have the NAVGRID centered on our aircraft and could appropriately re-center the view automatically when the user requests Jester to use the NAVGRID after using an aircraft stabilized mode.