flushi

Hi there again, Found this possible issue while playing around with different loads. Something seems wrong here. The Vr of the plane is ALWAYS above 160kts for me, no matter if the plane is completely empty or well loaded. Even stranger, it just gave me a Vr of 161 kts for a load of 160t - and a Vr of 168 kts, significantly higher, for a weight of 92t (no load, 2,5t of fuel, basically empty) which just can't be right. It lifts off by itself at about 130 at that weight at the correct trim, no way to realistically keep it on the runway to 168 empty in that situation. I attached the Perf Calc images as proof. Also, changing between Force TOGA on/off as some user in Discord suggested had no effect at all on speeds. Difference between 15/0 and 15/15 is neglegible at a few kts difference, still way too high. V speeds all tend to get lower the higher the weight is at the same CG? Greetings, Felix

+1 on this one. Had this on all three different departures i did so far, FD doesnt follow the entered SID/lateral path on takeoff. It just continues straight on the runway heading forever - or until you enter a direct to another waypoint. Reproducible at EDFH's NVO3S out of 21 and LIML PEPA1J out of 35 for example as well.

You colleague there (apparently deleted the response) asked me if i was using Add On scenery. So actually i was -> which i didnt think would be a problem, since both builtin (787) planes and external (737) still showed the correct SIDs and runways. The A300 didnt - until i tried without the Addon now. So apparently the A300 is the only plane that uses the very old, scenery supplied data - instead of the current Navigraph and Builtin data like all the other planes do - at least on that particular airport. Strange

Hi there ini Staff🙂 Found a little problem with the A300, reproducable for example at the Airport Milan Linate. The runway designations there recently changed from 18/36 to 17/35. My Navdata is kept recent by a Navigraph subscription, which works perfectly - checked in the Builtin 787 (builtin Navdata) and the PMDG 737 (Navdata installed seperatly). The runways and SIDs are correct for the new 17/35. The A300 however still shows me the old 18/36 - and no SIDs. I also deleted and updated the builtin MSFS navdata via the Navigraph hub and tried again - same result. The A300 doesnt accept/use the current data Cheers, Felix