Der Michel

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:

still an issue in 1.1.0

still an issue in 1.1.0 sorry, but this is basic stuff for the F-PLN building logic!

still an issue in 1.1.0

still an issue in 1.1.0

1. With the ADIRUs off, there can't be any GNSS position at the GNSS page of the FMS. "For initialization purpose and GNSS position validation, the MMRs receive the last valid A/C position from the ADIRS through the Aeronautical Radio Incorporated (ARINC) 429 bus. Once initialized, each MMR sends the GNSS calculated data (GNSS A/C position, etc.) through the ARINC 429 to each Air Data/Inertial Reference Unit (ADIRU)." 2. The altitude of the GNSS should indicate the AC altitude. Currently at EDDL it should be ~ 148ft

FIXED, can be closed!

Ok, the big update is released. Thank you! I will cross check all my reports during the next days…may take some time. I already missed some really big issues in the fix list. We will see…

You can delete discos, except the one behind a manual leg.

@Eddie did you also forward this one?

And how is selecting just NONE ? Won't you leave by that the beta and be automatically in the stable SU2?

It's a large scale SU3 Beta problem. Not related to the A350 in first place... CTD loading into 1.5.10.0 - Sim Update 3 Beta | MSFS 2024 / CTDs - Microsoft Flight Simulator Forums