WarthogOsl

This is the only scale model I built that survived to this day. I also got to see this plane perform at an airshow at Point Mugu. Would love to see this specific skin!

This is a show that, when talking about "the mighty MiG," showed a formation of L-39's, and confuses shots of air to ground rockets with air to air missiles.

That's my impression. I've heard a few pilots talk about how the F-14 wasn't super great at high altitude maneuvering due to the wing sweep being based on Mach number.

FWIW, there was a recent conversation on the HB Discord about how the F-14 originally had selectable (via a switch near the throttle) wing sweep programs...one optimized for best L/D based on Mach number, and the other optimized for better turn performance. For whatever reason, the Navy chose to eliminate the later and just keep the former, which is what we have now. Anyway, it seemed like the deleted program had much more bias for the wings being forward, with full 68 degree sweep only happening at around Mach 1.2

I'm not surprised. Haven't seen Airwarriors since I cut the cord, but I always found that show to be rather problematic. Way too much reliance on stock footage that often doesn't even match the stories they are trying to tell. And then, way too much reliance on stories versus actual facts about the airplane and it's development ("Dogfights" did a much better job in this respect). Makes me miss Discovery Wings.

I don't think it was was ever functional. HUD brightness, yes, but not the pitch ladder brightness knob.

There was an interview with F-14 test pilot Kurt Schroeder who got an F-14A to Mach 2.4 and said that was the fastest it ever went. However, speeds were pretty quickly restricted to under Mach 2 due to some issues that the Navy didn't feel like spending money to solve. Of all the Tomcat pilots interviewed in the Tomcast podcast, none said they ever broke Mach 2, fwiw.

FWIW, here's a launch with the elevator trim set to 0.

Is there one for the pitch up yet?

Same here. Its very violent...I wonder if this is a side effect of the landing gear tuning. Seems like maybe the compressed nose gear strut is re-extending way too hard after it's released from the catapult shuttle.

I've mentioned this before, but the pilot body does initially show up in single player just before you click the "fly" button. It will then go away when you click "fly" if you have the option unchecked. In multiplayer, it is also present when the "fly" menu is visible...it just doesn't go away when you click "fly." FWIW, this was mention several months ago in this thread, and it has not changed

I play the F-14 on a Rift CV1...probably the lowest res headset currently in use to play DCS. I do occasionally hit the zoom button to see some gauges, but all the primary flight gauges and navigational stuff are easy enough to see. Granted, not crystal clear, of course.

Usually its best to go to Cat 1 (the furthest right), otherwise the AI wing man will just line up right behind you on Cat 2 rather than go to the free Cat 1. As it is, the AI is still kinda buggy, and even if you launch from Cat 1, your wingman might not move into position on Cat 2 until you actually launch.

This recently posted video on the Air Tales channel shows Tomcats doing a fast-ish fly by with their hooks seemingly only partially extended. I noticed that, according to channel owner (I think he was a RIO), the hook would start to blow back at 300 knots, and the hook transition light might stay illuminated while above 300 knots. Seems like a neat detail, anyway.

Uh, oh...you just gave them more lock wire ideas! Wish there was a pic of the left side panel. I wonder if it got more wear and tear from folks stepping on it accidentally?

You can estimate range using the lines on either side of the TID...each line (and each blank space between the lines) is 20 miles. Otherwise, jump in the backseat really quick and hook the target, and you'll get range and altitude info on the TID.

Maybe? I'm just assuming that's why they haven't provided a bind. We don't have a bind for removing the HUD camera either.

I was wondering about this. It seems pretty hard to get hits with the pipper right on the target unless you are inside of the range where the DONT SHOOT "X" starts flashing.

Bind some buttons to the TID range settings for Jester. I've found that the range settings typically disappear from the Jester wheel after a Phoenix launch for some reason, and Jester doesn't zoom in automatically as your range closes. I also have buttons bound for the Jester aircraft stabilized and ground stabilized mode commands, as I go back and forth between those pretty often. It sucks you can't tell Jester to "soft lock" a target, but it's pretty easy and quick to jump in the back seat and "hook" the target by selecting it on the TID with the hand controller and clicking the full-action button (I have it bound to my trigger).

Sorry to dredge up an old issue, but I just suddenly started having this exact issue tonight. I'm on OB MT, Steam install. Here's part of one of the errors from the log (which is how I found this thread)... [string "./Scripts/UpdateManager.lua"]:64: in function <[string "./Scripts/UpdateManager.lua"]:40> 2023-04-26 05:06:55.136 ALERT LUACOMMON (Main): Error: GUI Error: [string "./MissionEditor/modules/mul_server_list.lua"]:1356: bad argument #1 to 'pairs' (table expected, got string) GUI debug.traceback: stack traceback: [C]: ? [C]: in function 'pairs' [string "./MissionEditor/modules/mul_server_list.lua"]:1356: in function 'getRequiredModules' [string "./MissionEditor/modules/mul_server_list.lua"]:1473: in function 'update' [string "./MissionEditor/modules/mul_server_list.lua"]:832: in function 'updater' I've tried rebooting, verifying files, removing mods, etc. Note: I was able to connect directly via the IP, just as long as I didn't first click on the server list.

AFAIK, you have to jump into the back seat, select a target on the TID, then on the CAP (the funky button thing with the roller display on the left side panel), select "do not attack." That should drop it from the automatic firing order queue.

FWIW, in the majority of pilot interviewed I've heard, they talk about keeping the wings in auto. I heard an interview where Puck talks about sweeping the wings all the way back to disengage/bug out, but this doesn't make a lot of sense to me, since the computer would normally adjust the sweep for the best lift to drag ratio. Sweeping them all the way back at low speed shouldn't be the best way to accelerate. I suppose the exception would be if you are completely unloaded (like zero g), the whole time up to Mach 1, which would negate induced drag. I suppose if you have the altitude that's possible.

Not that I'm aware of. Similar to there be no bind to remove the HUD camera, I guess. Maybe someday? It's been mentioned in the bind request thread, but I'm not sure there was ever an answer from HB.

To clarify "installed", the VDI was dimmed by literally taping a transparent piece of red plastic over the screen. That's where there's no switch to bind.

Do you have the Syria map? I believe it's required for the new campaign.