Der Michel

Since we didn't get an update last week, I assume you are working towards the large scale update? With all bugreports being logged I also hope that this update will not only cover ULR and HUD, but also a very, very long list of bugfixing. Please take your time with the update, especially testing the fixes and new features.

@Eddie also this one, please.

@Eddie is this one also logged?

No, when I pressed instant loading (set ZFW) refresh doesn’t change anything. I think the AOC is a preliminary ZFWCG. What’s missing is a message with the final ZFWCG. So the OIS/EFB one might be the correct one. But some clarification by ini would be welcome, if its a bug, if a final loadsheet is missing and what is the correct value.

And some info what speed is relevant for what to compare with:

Yeah, correct. I was talking about RNP AR. But you will get exactly the same picture if you try to fly a RNP AR. And deselecting FLS is not working (which shouldn’t be necessary).

There is another big bug I already reported. A RNP appr can’t be flown with FLS. It shouldn’t be avail at all for that type of appr.

NO. Last picture from my last post. FCU alt 5000. CRZ ALT is definitely higher, you also see the dashed vertical profile. And here the vertical line at the end of the scale is solid, not dashed. And the other photo....FL400 pretty sure the current CRZ Level...dashed when arrow is displayed. Now this photo: Also FL400 and pretty sure the current CRZ level...solid without arrow.

Performing flight at CRZ FL FL370, 4000NM+ to go. Set FCU to 36200. Aircraft is switching to vertical mode DES. FMS remains in CRZ. When reaching the new Altitude ALT* the FMS suddenly switches to DES. That's wrong. It has to remain in CRZ !!!! The distance to the destination airport has to be equal or less then 200NM for the FMS to switch to DES in this case.

Auto import of STEP CLB does only import CLB and not STEP DES. Simbrief Steps and what was imported:

just as addition to my first point in opening topic. The last vertical line is done vice versa currently. It has to be dashed when the arrow is displayed top right and solid when there is no arrow.

Just to add more info: A CA, VA or FA can never be at an other altitude in the vertical profile as it's name indicates, because it's vertical fixed. Never indicate constraint values, circles or asterix (magenta, amber, white) in F-PLN or ND. At VD the wpt symbol can only be a regular white diamond.

With the T.O SURV button at OVHD it should be possible to deactivate all TOS2 checks. That are the ones reported with the topics: T.O Surveillance issue #2 T.O Surveillance issue #3 T.O Surveillance issue #4

ECAM warning is missing:

Warning is missing:

The following FMS message is missing during Cockpit Preparation. This TOS2 check is performed a second time at engine start. Based on the TORA (selected RWY and entered T.O Shift) the FMS will cross check with the calculated Lift Off Distance (LOD) and trigger the message. The LOD is also required to corretly display the starting point of the vertical profile at the VD. The associated T.O Config test ECAM is also missing: And the ECAM warning at T.O Power is missing:

The following FMS message is missing during Cockpit Preparation: I assume VMU and VS1G are known, because they are used to calculate T.O speeds and VLS for example. A350-941: A350-1000: Also the associated T.O Config test ECAM is missing:

The Runwaylength is not necessarily the max TORA. As in this EDDL example. EDDV for example has a TORA extension larger then regular runway length. EDDL has a 23L Runway of 3000m with 300m stop margin. So the max TORA is 2700m. Not all charts offer ASDA and TODA, but TORA. The import of the correct TORA would be fantastic. Do we need to indicate ASDA and TODA? EDDL23L example: ASDA with 2998 almost correct -> Chart 3000 TORA with 2998 wrong -> Chart 2700 TODA with 2998 wrong -> Chart 2760 When I manually enter TORA 2500 for L2 int the system calculates wrong T.O SHIFT, TODA and ASDA. Correct T.O SHIFT is 200 (TORA full - TORA L2) Correct ASDA is 2800 (ASDA full - T.O SHIFT) Correct TODA is 2560 (TODA full - T.O SHIFT)

I had baro at Std, then FL is correct.

Also the APPR was somehow a wild ride up and down, while the airplane was trying to keep speed and glideslope. Is GSmini implemented?

Some more items during APPR: - DME distance is not indicated - GA is green instead of blue at the ND (maybe because the system thinks I'm doing a GA, but then PERF should show the GA page and F-PLN should also an activated GA F-PLN, no longer blue and with predictions.) So the GA logic is also somehow not working correct.

During CLB it was then indicated....at FL119....it's set at FL100 at the CSTR page !?!

SIM DEFAULT navdata. RWY part of GA, is wrong as already known. But where do the 3000 for HAD54 come from? If it's a WINDOW constraint...in F-PLN has to be a magenta "WINDOW". But to my knowledge it's coded with "at 1460" in navdata. At the ND the ALT constaitns shouldn't be indicated after the FAF for ILS APPR At the APPR selection page the ILS freq and IDENT is not shown note: I changed the constraint type at HAD54 manually

After loading (Set ZFW) LOADSHEET we have 31.75 ZFWCG According AOC message we have 29.88 ZFWCG What is correct?

After I deleted the not required "CI09L" The FLAP appeared, but SPDLIM still missing.