did multiple flights this week with Live weather without having this problem. just did a quick test(with Clear Sky preset) and it took 50 seconds to make the final 200’ to FL450.
Took around 15 sec from 44 800 to 44 900 than VS decreased steadily for the final 100’
Ok, Ill post a video tomorrow
did a 2nd test, with live weather this time, with ISA +8 it struggled to keep 500’/min for the last 2 000’ but it took 14 seconds from 44 800 to 44 900 and 50 seconds total from 44 800 to FL450
With default weight & fuel
ISA +8 at ceiling - might explain the slow climb.
Normaly i would’ve stop earlier, but it was for testing purpose
Well I don’t really think it’s an altitude issue. I usually don’t fly above FL440. I’ve seen this at FL420 too. Ironically, if you change your altitude 1000 higher and hit FLC the vertical speed will greatly increase. Until you get to within 200 feet of the new altitude…
It’s weird. Other planes slow down right before altitude capture too, but not as much. I’m wondering if it’s a tunable quantity somewhere.
Thank you for your hard work on this mod. I’ve been flying the Longitude for the last few days and I have to say the mod really helps with the flight dynamics. Just to encourage you to keep up the good work.
What speed / Mach number are you holding during these climbs?
What speed /Mach number are you holding during these climbs and are you using FLC or VS hold?
I usually use FLC. In this case I was using FLC. This last time I initially hit mach hold right at the bottom of the “red” zone. mach 0.77. In the last ten thousand feet or so I adjusted it to 0.80. I was monitoring v/s the entire time and v/s never dropped below 500 so I thought I was good.
Like I said, I don’t think it’s an issue of not enough power. V/s stays fine right up to 200 feet before capture altitude (no matter what that is). Then it goes into Altitude Hold mode. You can tell because the engine power changes and there is an audible tone. I’m about to try anther test soon.
And is this behavior new since the last Asobo update or had you noticed this previously?
I am not sure. I was flying other aircraft a lot prior to the update
Okay. I appreciate the testing and feedback. This is an interesting issue. I haven’t changed anything in the autopilot or PID configurations in several versions, other than as relates to autothrottle. I can only guess that Asobo adjusted the altitude hold function recently.
.76 with flc with autothrottle
If its hotter than Isa +5 i’ll use .78
I’ll have to share a dropbox with you Dakfly. My movies are too big. This is a sample. The Longitude has been trying to reach cruise altitude for 3 minutes now. I can force it but I don’t understand why this is happening. ATC is mad at me…
I just stumbled on something that may explain it, but I don’t understand. When I get above 18,000 I click the baro knob to set STD (like you do). The baro indicator changes to 29.92 (as it should). I just pressed the ‘B’ button for no reason and all of a sudden the aircraft starts climbing and levels out at 44,000. Apparently, clicking the baro knob does not actually set STD, it just changes the baro indicator to 29.92. 
Look at the altitude indicator above the center screen. You are still flying with a baro of 30.16. You need to STD that display to.
Look at the altitude indicator on the PFD. It shows a baro of 29.92. You’re saying that the PFD baro is ignored?
The baro in the little box has the impact on the plane. The baro on the PFD is more like cosmetics.