Philippe TORNE

@haza2 could you feedback our observations to the development team ? Thanks in advance

To illustrate my first post's observations, here is a screenshot made at the ETP, during another flight. As you can see the values are almost all weird (the most obvious ones being the estimated UTCs which should by definition be the sames as we are actually at the ETP (PPOS is the ETP) :

Hello there is an issue with the drop-down WPT selection menu of the STEP ALTS page. I think a short video would be more explanatory than a long text. In this example I wanted to set a step to FL390 at KABAM then a step to FL400 at MIGUG. As you can see the first waypint of the drop-down list is added at the top of the WPT list of the page when the mouse is released from the scrolling bar, leading to a big mess :

Hello there is an issue with the selection of the reference FIX in the FIX INFO page, when the FIX has multiple iterations in the database. Below are some chronological screenshots during the selection of HME as a reference waypoiint. The problem is : first entry of HME on the FIX INFO page is accepted without being prompted to the multiple WPT selection. The rings are not displayed on the ND. Then I enter again HME and this time I am prompted to the multiple HME selection, select the closest WPT and this time WPT and ring are well drawn on the ND. FIRST HME ENTRY, "ACCEPTED" WITHOUT BEING PROMPTED TO SELECT BETWEEN MULTIPLE ITERATIONS : NO RING IS DRAWN : SECOND HME INSERTION IN THE FIX INFO PAGE : AND THIS TIME I GET ASKED TO SELECT BETWEEN TWO HME ITERATIONS OF THE DATABASE ? AND NOW IT WORKS :

I am also experiencing CTDs using the A350 (version 1.0.7) in combination with FSLTL models. I investigated further and found something interesting I would like to forward to the iniBuilds team here : - Flying without FSLTL models: No CTD - Flying with FSLTL models and no traffic display on any ND (TRAFF EFIS switches OFF on both sides, ADS-B OFF in the SURV page) : No CTD - Flying with FSLTL models and traffic displayed on the ND (either TFC or ID selected on the EFIS) : CTD after a random time (1 to 3 hours) I tested on many different flights, different sceneries and always the same behavior. So my conclusion is that there is something wrong with the way the A350 processes data from FSLTL during the ND injection process. I hope this report will help solving this annoying issue.

Hello, I noticed some improvements on the ETP Page, thanks for that. However, there is still a bug regarding the two lower boxes (BRG/DIST/UTC from the ETP to the selected airports). See the attached screnshots that details the situation of an ETP between VVTS and RPLL with a present position south-east of VVTS. The Track and Distance values in the two lower boxes are reversed from what they should be (the arrow in the ETP Page is from the ETP to the selected airport). Regarding time values, they are also weird (9 minutes from the ETP to VVTS, minus 1 minutes from the ETP to RPLL). Edit : after reaching the ETP, I can say that the upper boxes values (PPOS to the selected airports) are also wrong. At the ETP I can see a 175 NM ETP displacement towards RPLL from the upper boxes values with a 090@20Kts wind which is impossible for such leg lengthes (20 Kts means 20 NM/hour so for an about 1.25 hour leg the ETP offset should be arround 25 NM).

I noticed this also. Looks like there is absolutely nothing behind the numbers, sadly...

Hello, despite some improvements, still a long way to go to get a correct segregation between SEC and ACTIVE FPL. Here is an example of trying to modify an ALT CSTR in the SEC, and falling in the ACTIVE (and wrong waypoint BTW ! - EGEMU was one of my active FPL WPTS, very far behind my actual position-) so feature STILL unusable at this point...

Already set at MAX thanks anyway

May I sugest you to read my message again and carefully ?

After one month away from this aircraft, I switched directly from 1.0.4 to 1.0.7. The sounds were one of the satisfying points in my opinion, but with the latest version something has definitely been broken. Flaps sounds from the cabin are almost unnoticeable, external APU sound is very bad quality, packs sounds from the ramp almost unnoticeable, engine starting sounds very quiet from the cabin, even from the closest seats, no reverse sounds. I even made a complete re-install to check, still broken. Audio immersion is definitely killed. Please fix this.

Using 1.0.7. The aircraft has an incorrect behaviour during managed descent (DES). According with the documents, the first part of the descent (from the TOD to the first constraint) should be an idle path. The FMA should display THR DES or THR IDLE | DES | NAV and the A/THR should go the IDLE (or very slightly above if necessary). This is not the case with this product. The aircraft is always descending in MACH/SPEED with a very shallow path (almost never more than -1500ft/min) resulting in a high amount of thrust. This leads to a very long descent and a very high fuel consumption. Could you please fix this as quick as possible thanks.

Hello, Using 1.0.7 but noticed this from Day 1. During manual speedbrakes oparation in flight, the physical panels position of the flight model are directly linked with the cockpit's handle position. That means if I set the handle quickly, say, from 0 to 1/4 the panels are deployed as quickly. Same bahaviour during retraction. This should not happen IRL. As far as I know, there is a damping controled by the flight computers. Could you please consider implementing this ?

Hello, Using 1.0.7. The Cabin Ready message is coming very late, especially during approach. I don't think this message comes as late as 3-4 NM from touchdown IRL. Could you please fix this ? Regards

+1. Aircraft unable to capture an altitude after recovering from AutoSave (1.0.7).