frank_m

Yes. As I said, the TCAS is a known issue, and there are even more threads, and also statements from the team you asked for. If try your best, you will find it. Yes, you can! Your other thread is regarding a VNAV issue and not regarding TCAS, and it is in the 2024 version, while we are here in the 2020 section. I recommend to take care about your posts, otherwise people will get the impression, you are somehow confused. If you are using the plane in the same uncoordinated way like the forum, then your problems are most likely no bugs...

You are ALSO NOT, GOT IT? As you can read here, nobody except you has tie problem. Guess what, this is an individual thing, but no bug. Thats what I tell you with 40 years experience in software development.

But the same lasts for you. I'm just seeing the facts: no other users complainig about the issue, and I can't confirm it at all. Therfore I tell you: it is a bug when it is confirmed, but not before. You are perfectly right. And what is missing? The other users joining. If you ever have developed only one line of code, you know, that this is impossible on systems you can't control completely. Otherwise you have absolutely no clue about SW development.

Yes, there is a problem and a recommended configuration to circumvent it as long as they are working on it. What else do you want? Oh, I have. In particular, people using outdated Navdata in Simbrief are creating invalid flightplans. Oh, that problem occurred for the large majority of the users. Additionally it was confirmed by the team. Your "bug" is observed by only one user and not confirmed. It becomes a bug if enough people are complaining about it, and it is confirmed by the team. Which both is not the case for your problem. No, that is definitely not the case. There may be problems caused by addons causing problems in specific other addons, but not in all. Think about the problems caused by addons having no "package_order_hint" entry in particular with Navdata. It looks like a problem of the plane or the scenery, but finally it turned out to be a problem with the Navigraph Navdata caused by old MSFS2020 sceneries not involved at all in a specific flight. It is enough if the old addons were installed to disturb the navigation. Oh, I'm sorry about that. Then you have never developed software for Operating systems the user can configure in an open way and install other software. Otherwise, you would know, how external components can influence the behavior of your software. Just let other tasks consume the resources like CPU or memory and lets see, how good your software performs with missing resources. A problem of your software or of the user not providing a clean environment?

That is not true, there have been several statements from the team regarding TCAS in the past. Regarding your VNAV Problem: I can't confirm it. During the Christmastime I did a lot of flights with the A350 on random connections (chosen with https://where2fly.today/). There was never an issue with VNAV, neither in occupied areas (Europe, USA), nor in lonely regions (Asia, Africa). Neither with handcrafted airports, nor with standard airports. I think, either your navdata is not correct installed, or there are conflicts between your flightplan and your navdata. Maybe you are using outdated waypoints somewhere in the chain? Well, it is definitely not a bug of the plane, since otherwise a lot of people would complain about this issue, and you are the only one.

An empty folder means an empty folder: Delete all (other) add-ons except the A350. In particular liveries, sceneries and tools.

Remove incompatible addons and liveries.

Please show Screenshots from the OIS Setup while computing the T.O. Performance. The performance is not calculated if one of the parameters has no valid value, e.g. too short runway or similar.

Please learn at first, how to write a post in a forum. Who should read this mess with horizontal scrolling? Then maybe someone will read the question and answer more than a "RTFM" (which would help, btw.).

Incompatible addons. Please use the search function, the question was already asked several times.

It depends on your used Navdata, if the values are correct or not. If you use outdated material, you have to enter it manually. The plane itself works flawlessly. I did a testflight to EKCH ILS04L, and everything was perfect, as well with current Navigraph data as with the simulator data. So it is up to you and your settings, if you have to enter it manually. Waiting for an update of the plane will not help, since there is nothing wrong or buggy.

The frequency is wrong. EKCH ILS04L is 110.50, not 110.70.

This is no surprise. You should REMOVE the liveries. I didn't mention that the critical addons are FOR THIS AIRCRAFT. I just wanted to help. I like to do that for people who are overwhelmed by the search function.

Seriously? There are at least 15 threads in this forum dealing with the same problem. You are now waiting several days for an answer the search function would have delivered within seconds. You have incompatible addons installed. Cabin packs, third-party liveries or similar. Clean your Community Folder. BTW: why are you asking a MSFS2020 question in the 2024 section?

You have followed the takeoff procedure required for Autothrottle? MCDU programming, Thrust Levers, Flaps, Gear, Autopilot, Glareshield, ... For me it engages at 1000 Feet as foreseen. Please show screenshots from the cockpit if the Autothrottle does not engage as foreseen.