Der Michel Posted April 8 Posted April 8 Departing EDDF07C via MARU5E. The first leg is a CA (course to altitude) one. The FMS is handling this leg-type wrong. This is now an example from a VA-leg and A320, but logic is the same for CA-leg and A350: We see here two important things: 1. the terminating altitude is not a normal constraint!--> no magenta 2430, no asterix 2. without predictions there is an interim position choosen. Later with predictions avail, the correct location is calculated according the vertical profile. Now what is the ini A350 doing: 1. the terminating alt is handeled as regualr constraint -->wrong 2. the location is not updated according vertical profile -->wrong 3. The 800 is indiacted as constraint on ND --> wrong see picture below, from an other example. Specs: CPU-13900K, RAM-64GB-6800, GPU-4090
Der Michel Posted April 19 Author Posted April 19 still an issue in 1.08 Specs: CPU-13900K, RAM-64GB-6800, GPU-4090
Eddie Posted April 21 Posted April 21 Hello, Thank you for the follow-up. I've forwarded this again to the team. EddieCommunity Manager IniBuilds Ltd. | inibuilds.com
Der Michel Posted April 22 Author Posted April 22 and to add...no brackets! Specs: CPU-13900K, RAM-64GB-6800, GPU-4090
Der Michel Posted April 26 Author Posted April 26 And here issues with FA and VA-leg: 1. 700 in blue and no constraint 2. 700 should have the label VAB270 3. 2600 no brackets and no constraint. Specs: CPU-13900K, RAM-64GB-6800, GPU-4090
Der Michel Posted May 11 Author Posted May 11 Still an issue in 1.09. Brackets are gone, but it’s still handled and indicated as a regular constraint. 1 Specs: CPU-13900K, RAM-64GB-6800, GPU-4090
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now