Callsign JoNay

Yes, it has been proven in the FM Development Status pinned thread that adding or removing phoenix pallets has no effect on the aircraft gross weight and drag. Either the weight of the pallets is permanently baked into the clean weight of the jet, or they don't weigh anything when attached.

Sure, and I would argue all those things are less important than properly modeling the weight/drag of the pallets and fairings, but I'm not going to mention that in a thread about AP heading hold.

Is the oxygen gauge going to be getting instrument/console lighting eventually?

So correct as is. Thanks for the verification guys.

So helpful. The question is... Is this intended/realistic behavior, or not? Im looking for an answer from HB, or someone in the know.

Right, I know what happened. I'm just surprised Grumman couldn't program something into the system to adjust the sequence so the plane stays as balanced as possible. Like if the crew shoots a Sparrow first, have some programming that changes the Phoenix order so it deploys from right to left. Or an even easier solution, just program the Phoenix to deploy left to right, and the Sparrow to deploy right to left. Problem solved. Just trying to confirm if this is really how the Tomcat was, or if it's something still being worked on by HB.

I'm sure this has probably been brought up on the forum before, but I couldn't find a thread about it. Is the F-14 supposed to shoot all the missiles off the same side of the jet in this way? Is this how it was in real life? I know you can somewhat manage it by pressing the weapon select switch on the sidewinder before shooting, but at best you're still left with the two heaviest missiles on the same side of the jet.

Great interview from start to finish. That IRST sounds like it was incredible. I was surprised at 18:00, I thought the Phoenix had a PD RADAR. If it's pulse then I wonder if it should be more susceptible to chaff than it currently is, and unnotchable.

Yeah, so for example, I deleted the VAICOM/AIRIO "Grid Center", and just made my own in regular Voice Attack to complement the stuff in AIRIO that actually works. It looks like this... I did the same for almost the entire NAVGRID category and some of the busted A2G stuff. The only one I haven't been able to figure out how to fix is the "Toggle View" command to toggle the LANTIRN FOV. I don't know how VAICOM was getting that to work in the first place since there is no Jester wheel command for it.

deleted

Am I losing my mind, or did you guys add a new shaky effect to the VDI now? Is that to simulate an old CRT effect?

I deleted the broken commands from VAICOM/AIRIO and rebuilt them in the regular base Voice Attack. They work with the same voice commands that AIRIO was programmed to recognize. To the user there is almost no difference... just a missing subtitle in the upper right to confirm what you just asked for.

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?