bug FMS issues - F-PLN A page - 1.03

[Der Michel]

This will now be a longer post, as the F-PLN has many issues. Maybe I will do follow on post in future.

1. at LSK1R show only 5 dashes ----- and move 1 column right

2. removed

3. Line 1 is missing TIME 0000

4. LSK1R is missing the airport refference altitude rounded to tenth

5. for the leg length the unit NM does only appear at line 2

6. all dashes have to be large font

7. the color and size of the / is always defined by the following text or numbers (just a general remark)

8. LSK1L is missing the label for the SID name

9. The CA leg is indicated wrong. Already mentioned in the A350 topics. An CA leg is somehow a "pseudo" constraint. For the VNAV it'S mandatory to met it, therefor the position is adjusted along the track according climb performance. Initial there is a assumed distance and when performance calculations are avail, that position is refined.

But: It's not indicated as magenta constraint in F-PLN, ND or VERT REV page! Also there can never be a missed or match asterix next to it.

This also relevant for FA (in the reference photo) and VA legs.

10. We see here 2 magenta asterix without predictions avail. that cant be! Also there a no alt CSTR, so for what are they there? The speeds 230 and 250 are constraints, they have to be magenta.

11. Also the arrival airport is missing the altitude

12. And as already mentioned in the A350 topics. The ALTN F-PLN is missing the destination of the active F-PLN as origin for itself. Without that it's not possible to built a ALTN F-PLN.

13. If there is a window alt constraint in F-PLN, display WINDOW in F-PLN

14. The arrival altitude has to be green.

15. The GS intcpt altitude has to be green

16. TRK and BRG are missing the °

17. HOLD SPD has to be in the TIME column and different  spelling

18. place the HOLD speed value in the speed column, but it's not in line with the other speeds

 

 

 

Edited Sunday at 08:39 PM by Der Michel

[Der Michel]

And the same error as always:

1. The speed at the departure is the V1 !!!! If it's not entered it has to be dashed!

2. The from wpt TIME and SPEED has to be large font

 

 

Edited Sunday at 08:41 PM by Der Michel

[Farlis]

You are on a roll again. 

I admire your tireless effort to document everything that IniBuilds gets wrong in their Airbus fleet.

However given the snails pace at which they correct them and carry them over from product to product, I also admire that you still hold out the expectation that they will fix all of these.

[ArtAir]

Absolutelly great remarks. Looks like my old topic about FSLabs A320 FMGC on their forums (for P3D).

Hope inibuilds will correct it.

[ArtAir]

And BTW, most of your remarks are correct, but it needs to be checked with latest A340 LCD MCDU and firmware. Because your real photos made with old CRT MCDU and probably this MCDU has less functionality.

Edited Monday at 07:30 AM by ArtAir

[Swisspilot1986]

thank you Der Michel for all your observations. Thanks to you I decided to put it into AOG until further updates. It has no utility to spend time with a half-finished product. 

Edited Monday at 09:44 AM by Swisspilot1986

[Der Michel]

3 hours ago, ArtAir said:

And BTW, most of your remarks are correct, but it needs to be checked with latest A340 LCD MCDU and firmware. Because your real photos made with old CRT MCDU and probably this MCDU has less functionality.

I tried to get the correct versions. I can rule out any P4 or non Honeywell references.