Der Michel

1. As long as long as no Radio is tuned at RAD NAV (will happen after alignment of IRS), - no FREQ has to be displayed at SEL NAVAIDS (just keep blank). - no FREQ has to be displayed at ND (just keep blank). - no MORA has to be displayed at ND. 2. SEL NAVAIDS: frq has to be 1 column left 3. SEL NAVAIDS: AUTO has to be 1 column right 4. SEL NAVAIDS: Display LSK1-4 only, if something related is tuned.

1. keep page dashed as long as ADIRS are OFF. The GPS signal is routed through them. 2. The GPS position is not instant avail with ADIRS ON, it requires some time. For IRS INIT page it is stated <1min that GPS pos is avail. 3. Indicate the mode of ops at LSK3R and 6R

1. move titel 3 columns right

1. Dashes have to be ALWAYS !!! white (large font) and the correct format is: ----.--/-----.-- 2. LSK6R: SEL has to be in small font 3. Line 5: OFF, ALIGN, NAV x.x has to be in small font 4. LSK3L label depends on availability of GPS

1. Only 2 pages, not 4 2. P3 doesn't support RADIUS, so remove it. Edit: This report assumes that ini is doing a Honeywell P3. With 1.02 they changed several pages including IRS INIT from P4 to P3. So it‘s a pre Release1A standard.

1. VIA and AVAILABLE label are not in line with the columns/matrix structure 2. Runway length is too far right (keep it in same colun) 3. Runway unit has to be small font 4. ident/freq is too far right 5. NONE has to be at the end of the list, if it exists in reality (I have no source) 6. ERASE also with <-- 7. display NONE at LSK2R if there are no TRANS and keep the list empty. 8. Refference is from SEC, so no yellow items. 9. VIA page should have a RETURN and no ERASE/INSERT 10. selecting any LSK1-3L item should directly switch back to ARRIVAL page. 11. NO VIA has to be at the end of the list

1. AVAILABLE RUNWAYS is not correct arranged in the column/line matrix 2. dashes for SID and TRANS are both missing an additional one 3. CRS has to be moved 4. length unit has to be small font 5. ILS has to be large font 6. END is missing 7. NONE has to be at the end of the list, if it really exists (have no source) 8. EOSID NONE is missing 9. ERASE has an <-- and no * 10. just a another refference

There will maybe follow more posts to this topic. 1. LSK5L is missing <ALTN page access

Please enable MCDU 3 so we can use it for AOC/ACARS operations, just like it's done in reality.

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

1. The LSK2L and 2R have to be blue, as the values can be edited by pilot. 2. Whne LSK1R is pressed, the values have to vanish 3. The logic need to be adapted. The ini A340 has GPS, so this logic has to be implemented: "The preferred way of initializing the ADIRS is to use the GPS position, because this does not require any flight crew intervention. Less than 1 min after setting the ADIRS to NAV, the INIT page displays the GPS position without displaying the ALIGN IRS prompt. If the flight crew enters a CO RTE or FROM/TO, the INIT page displays the departure airport reference-point coordinates, and the ALIGN IRS prompt appears. If this prompt key is not pressed, the ADIRS is initialized to the GPS position at the end of the alignment time. At any time during the alignment, the flight crew can manually adjust the coordinates displayed on the INIT page. The ALIGN IRS prompt reappears. If the ALIGN IRS prompt key is pressed, the coordinates displayed on the INIT page are sent to the ADIRS for initialization. This is the alternate method for ADIRS initialization, when the GPS position is not available. A normal alignment takes between 5 and 10 min (depending on the local latitude). At latitudes between 73° and 82° (North or South), the alignment takes about 17 min. The ADIRS cannot be aligned beyond 82° (North or South). A fast alignment takes about 30 s, and it is used for improving the ADIRS initial position accuracy, when time is limited."

1. As already mentioned, the page layout is just wrong. 2. The Titel will change to INIT FUEL PREDICTUION, when ZFW and BLOCK is entered. ZFWCG is not required for that.

1. When LSK2R INIT request is pressed, only the asterix has to disapear, not the whole text. 2. LSK1L and LSK1R becomes green after engine start, prior it's blue text. 3. When CRZ ALT is reached, the CRZ TEMP has to be dashed

Hi, this will be the start of a series of topics regarding issues with the FMS pages. Still the work assumes that ini switched from P4 to P3 since update 1.02. Please change the menu layout. You already replaced ACARS with ATSU at LSK2L. But if ATSU is used it has to be at LSK6L. Also add LSK5L SAT for airplanes equipped with SAT.

Here are now two correct pictures for the P3:

The lat post contains pictures from wrong version. Stick to FCOM images from first post.

and the next page: FIX INFO should now have only 2 pages and no support for RADIUS

Yes, that's correct. They downgraded from Honeyell Release1A P4 to Honeywell P3. Only the Release1A versions have the more complex page design.

Hi ini Team, after my still open long list of A350 reports, I did the step and also bought your A340. I was happy to see, that you did the step and decided to model a Honeywell FMGS instead of Thales because most out addons have a Thales FMGS. Now I noticed that you changed with the update from 1.01 to 1.02 also the modeled FMGS version. You downgraded from FMS2 HONEYWELL Release 1A P4 to FMS2 HONEYWELL P3 and adapted the page layout to the older system. What I noticed, that this step is incomplete. You have still to change: INIT B FUEL PRED P.S.: I also noticed plenty of bugs in your A340 FMGS. I'm still not sure if should takle it and report these bugs. A350 bug report was/is still useless. It takes a lot time to test and report. Take one obvious one: It's still not possible (like in A350) to enter a departure in the ALTN-FPLN. You have to copy the active FPLN destination airport as origin in the ALTN-FPLN.

still an issue in 1.1.0

still not fixed in 1.1.0 - naming of Anchor Point is still wrong - the achor point (it's avirtual one) has to be displayed on ND - during descent the FLS glidepath was going up and down during last few hundred meters. (magenta double diamond)

CDA looking good so far

With 1.1.0... So, we have now the VIEW ALONG ACFT TRK message, but the logic during cockpit preparation is wrong. Magenta part according changelog implemented....I don't see any. Radioaltitude: check The rest of the issues still to do. I would say...still a long way to go.

The ILS and HDG overflow box at ND and PFD is not updated with correct value in TRUE mode: