Andy Ross <[EMAIL PROTECTED]> said: > I'm pretty sure we're seeing the same behavior here, actually. I'll
With Dave's change to prefrences.xml I can get up to FL320 before running into trouble. Really tried to go higher...no luck. > take a look at the reduction in climb performance, but I'm pretty sure > you're just being fooled by the slower speed (once you drop below 260 > knots or so, it takes a *long* time to get back to 300, even if you > dive). No, I don't think so and yes I know. But haven't had a chance to verify this with the latest changes. > Here's my plan for testing 747 climb: > > 1.) Set autopilot to runway heading before takeoff, then disengage > with ^H. Verify that all trim controls are zero. > 2.) Throttle up. > 3.) Rotate at 190 knots. Gear up. Engage autopilot heading mode. > 4.) Hold the nose at 15° until the aircraft reaches 250 kias. > 5.) Hand fly the aircraft at 250 knots until 10k feet. > 6.) Reduce back pressure on the yoke as the aircraft accelerates to > 300-310 knots. Trim up very (!) slightly to hold this speed. > Use very small movements of the stick to damp the phugoid. I flew this exact protocol in the last test. BTW I might have mentioned before, but wasn't clear that when I do use the autopilot I'm tweaking the config at various flight levels with the property picker (/autopilot/config). Unfortunately the autopilot's "min climb speed" setting doesn't work quite right, so you have to watch the ias. Anyway this is a lot different than just entering an elevation like we do with the cessnas. In any case, flying very carefully I can barely get it up to FL320 with the change in preferences.xml. Going further just doesn't seem possible. I tried serveral AoAs and just couldn't get it to go up much without falling back. Best, Jim _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
