markom

That does help, but it's still a bit too thick for those of us using unusual screens. Specifically, I have 32:9 screen, and HUD lines are thicker than I would expect them. It's a problem not easily reproducible with track files, but I am happy to take videos and photos to demonstrate.

Home FPAS can be permanently killed by setting it to WP 58, but it's a brute-force approach.

OMG! Will this thing silence the HOME FPAS alert and BINGO as well?

Unless they are destructible. Then it makes sense including them... as either targets, or things to protect, or just... collateral damage.

Can you try it again and do the following: 1. Set left DDI to show HUF 2. Take a screenshot or photo of left DDI 3. Post #2 here

It's a nice song though. We get to enjoy it for ~6 more weeks by the look of it.

Radio menu, ground crew, request takeoff.

You can do it manually... Sadly, it's rather difficult to save the layout for next time... It takes a bit to do it right.

From what I remember, that should not be happening. To preempt the inevitable - can you post a track?

+1 for not derailing the discussion about the already awesome model. it's a joy to use Also +1 for a more detailed damage model. Once in a blue moon, my a/c gets damaged in an exciting and unusual way that makes it still flyable. It's an amazing challenge getting it safely to ground. I'd love to have many more different opportunities like that with a more detailed damage model.

Ohhhhhhh *excitement* /dance!

Oh jeez, that explains painful refueling. I thought I was going nuts. It was awesome though! I may just leave it on :-).

Honestly, I think most of us would just go away if they fixed the bullseye thing. As-is, the map is very unattractive for A/A missions, since all built-in AWACS calls would be nonsensical.

Yeah, not being an actual F/A-18 pilot helps not being on the glideslope, but that really has nothing to do with the touchdown. It is doable was the point.

War sucks, doesn't it?

Thank you for the wonderful surprise. (Pre-)purchased!

OK

Aerobraking is keeping the flaps down, gentle pressure on the brakes, and pulling the stick/yoke back (or similar set of actions to increase aerodynamic braking, *after* all wheels are on the ground). If the nose is up, executing this action may not do what you want in a bad way (porpoising).

One could make an external FLOLS indicator and use it instead of relying on the in-game one (which is invisible on the boat, and looks quite ugly as the overlay).

There are many definitions, but in essence, it's landing at such speed (air, gs, vertical), that the nose of the aircraft remains up after the main wheels have already touched-down. If you take a look the infamous "Air Force vs Navy" video clip, that F-16 did a flared landing, while the F/A-18 pilot did not.

Jogging: Unrestricted: 10km/h Restricted: 15km/h Restriction: must have 5 km/h tailwind. This is how I would rather interpret unrestricted/restricted.

I think that Navy pilot flew my last Delta flight.

You can configure external switch' controller to send two signals on button press: one to operate a virtual guard, the other one to press the underlying button.

Also, make sure your radio altimeter warning altitude is set. If it's not set, RALT won't engage.

My understanding (which is often inaccurate) is that this is an expected and correct, albeit annoying, behavior with Mavericks loaded.