Flamin_Squirrel

The Hornet doesn't approach with speedbrake, but the F14 does. Guess they're just covering their bases.

I've asked here, no responses yet: https://forums.eagle.ru/showthread.php?t=275525

I would normally, except they're doing the same to the radar!

Hello, Please bare with me as I'm a bit of a LUA noob; has anyone found out how (if indeed it's possible) how to output landing scores issued by the LSO? I can't find anything documented, but that might be because it's quite new. Ultimately I'm looking to record scores to a file. Thanks.

I really wish they'd stop making lots of little changes like this; it makes it more difficult than it needs to be to learn, and bug identification harder.

It works fine, however please note: ATC holds TRUE airspeed, not INDICATED airspeed. Therefore changes in altitude will result in an apparent drift away from the airspeed you might be expecting (climb will result in you slowing down, descent in speeding up).

MIL or MAX for Hornet launch, depending on weight. For a bolter, only MIL is needed, so that's what you advance to on touchdown in case you miss the wires.

MIL should be selected rather than A/B according to the manual. As for the video, after they cross the ramp take a look at the ball - it looks like it starts to drop, which is probably why they went to MIL before touchdown.

You've got the right idea in that you're controlling descent with throttle. Where you're going wrong is waiting too long to make corrections. Corrections need to be small and frequent. As soon as you see the nose drift away from where you want it, make a throttle correction. It's not possible to find a sweet spot for the throttle where you can just leave it; you'll need to make corrections all the way through the approach.

Hello! This may provide what you're looking for https://www.lotatc.com/

That S3 getting launched into the back of the helo is going to make a real mess.

OP isn't being mocked for having a different opinion, it's because they're being unconstructive.

Any chance of a break at the bow grading (e.g. within 0.5nm or something)? You have to descend during the break for this to work, but the grading would knock points off for doing that at the moment. Something for the future perhaps :) Still my favourite mission regardless :thumbup:

I understand your sentiment, but that doesn't apply here. OP isn't complaining about a bug, they're complaining about poor fps. This is likely due to either totally unrealistic expectations or incorrect settings.

Sorry, follow up question: the trusty NATOPS bible has the descent to 600ft on downwind. I imagine if you break at the bow, this descent has to be done during the break?

It must be ED's fault. The friendly 'Microsoft' adviser that called him up and got him to install some software told him so.

It's mentioned in the '18 NATOPS, but not very specific.

Thanks GB, appreciated as always.

Document that shall not be named I have here says prior to hooking up to the cat.

I've been trying to understand how to make a 4 ship fit into a Case I approach. Some initial figures: 15+ seconds between each kiss-off 4nm - latest you can make your break 350kts entry speed Minimum spacing of 15 seconds will require #4 to break no less than 45 seconds after the lead. At 350kts you'll cover more than 4 miles in that time, meaning even if lead breaks at the bow this won't work. Am I missing something, or will a 4 ship split up before hand? Thanks.

That's how they're keeping the lights on. Not much point bringing Vulcan to the top of the priority list if you go bankrupt in the meantime.

Pretty sure I've read that requesting start up isn't usually done for fighters on base. Each to their own though!

Whoo! Will be ordering shortly. :joystick:

I think it's both: it is earth referenced stabilised, but that stabilisation has limits. If the pitching is too much, it can't keep up.