markom

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.

Doh. This is the one I meant

You push the castle switch (TDC priority) forward, that moves the diamond to the HUD. If you don't have it mapped to your controls, there is a keyboard shortcut that I can't recall from memory.

TDC up, and you can slew it there.

Are you, perhaps, using an external tool that could be mapping axis input to keystrokes or something like that?

This looks like an ME issue, not F/A-18 one.

Not in the last few days, no

I love AAR - it's a learning that's incredibly rewarding. Here's a bit long video of one of mine (if you are bored with just flying, AAR is at 10m10s:

Similarly to the S3 bug here: I noticed that F/A-18C also seem to disregard statics. Screenshots and track attached. Statics.trk

I could be wrong, but isn't JDAM alignment just making sure they're on for 90 seconds?

I was unable to reproduce this. I tried a few times at various VS. Perhaps it only happens on the carrier? Gear Smash.trk

Aye. The assumption is that they are being worked out. While, of course, they may be, we as users have little to no evidence that, in fact, they are :-). That being said, noone here will persuade anyone else, and the conversation is likely no longer constructive. I have my wallet to voice the opinions with :-).

Honestly... not the way to talk to paying customers, you know :-). Especially the ones who are not too unreasonable. I even called out a specific bug that remains unfixed since... well... the actual release. It's not an obscure or invisible one. It's a very tangible one. Not cool, man. Not. Cool.

That's why we, the consumers, can vote with our wallets

That's what "early release" implies... At least monthly updates, until glaring bugs are ironed out. For example... the one where you cannot place bullseye, because it's way off the map.

You totally can:

Interesting. All the docs relating to ED's F/A-18 that I've seen refer to the 33,000. I have not seen the 34,000 number anywhere.

For me, the bar for "is there damage" in the game is whether it beeps at me... I don't believe external visual inspection yields the same result as it would have in real life. In other words, thank you for confirming the damage

What do you mean no damage... you can quite audibly hear the wheel damage alert on that carrier trap.