Flamin_Squirrel

Totally agree. I asked for this and was told we'd get it. *drums fingers* https://forums.eagle.ru/showpost.php?p=4290129&postcount=489 Yes, you are right. Should be done for every project. We'll do! Thank you.

:thumbup:

To be specific, I was referring to the idea that no rudder input was required from the pilot; this is not the case: I did not mean to imply there was no FCS input at all.

Anyone know what the New and updated HOTAS functions is all about?

It does not.

Thanks for all the great info GB. Slightly academic at the moment as marshal is around BRC/FB, but is there a prescribed method to make the turn from assigned radial to FB when marshal is say 30 degrees off? e.g. turn so many degrees on reaching platform (or other point in the approach).

This Wednesday I believe.

Really sorry for the confusion guys, they've changed something as what I described was how it used to work, but having just checked, it doesn't any more. When caged it's locked to the centre (it used to move with yaw). When uncaged it shows where you're heading, which while does take into account yaw, can't be used to determine sideslip as it's also affected by wind as has been previously mentioned. Apologies again.

It works fine. Fly in NAV mode with a crosswind. Cage the VV. You'll see pitch ladder and a solid VV align to the centre of the hud, and a ghost VV off to one side. The ghost VV is corrected for wind, the solid one is not. Kick the rudder, both will now shift left/right, indicating sideslip. If you fly in AA mode, the VV is always caged, in AG mode it's always uncaged.

If the VV is caged it will be an indicator of slip. If it isn't caged, it's a combination of wind and slip.

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?