dectenor1

Really sorry, but point 2 has been reported a while back. I think there are improvements needed on bug tracking. There are so so so many bugs with this aircraft that the system needs to be more robust. Many thanks for the continued work, and I am looking forward to the reported bugs being fixed in the next update.

Yeah sadly this is not the case. I only use Navigraph data from the OIS for both sims, and it is still broken. Thanks for pointing that out though.

When you cross the Managed SPD LIMIT Pseudo-Waypoint for when the aircraft wants to slow to 250kts when descending when in Selected SPD, the magenta dot bug on the speed tape remains at the ECON DES SPD rather than changing to 250kts.

Yep, again here, absolutely no reason for it to want to be so low at IZS38. And it thinks it can get to the (incorrect) altitude by losing 2600ft and slowing down in 6nm... Just borked. One can also see here that the time predications are messed up for the FLAP pseudo-waypoints. Bit of a mess really.

The calculated descent path logic still needs work. There is absolutely no need for the aircraft to be planning to descend below the altitude constraint here at PRN25. If the aircraft needed to slow down, then it is possible it would be above an AT constraint, but there is no need for the aircraft to descend lower.

BKPR35 should be part of the main route and in green not blue This issue also affects things like distance remaining of the route, as it won't take into account the part from the final fix to the runway.

On this video you can see an issue with the Cabin VS constantly fluctuating.

Why has suddenly the arrival runway become part of the missed approach procedure? This is completely wrong and messes up the flight plan and various things on the F-PLN page associated with it. Looking at the changelog, it seems like this was done on purpose....

I'm afraid issues with the flight plan and the F-PLN page are a total mess since the last update. Just look at all those altitude predictions at 10ft... I think it is something to do with the path not being drawn on the ND from the FAF to the runway as we have both reported elsehwere, it is like the flight plan ends at some waypoint on the approach. I would do more testing, but it's not my job and frankly I have better things to do.

Yeah I have to agree here. I usually do a few flights after a new version, and see the same old bugs and then also new bugs, and so the aircraft goes straight back to the hangar. Again, as @Der Michel says, these are basic things, I don't really understand why they were incorrect in the first place or have not been fixed. For those of us who enjoy realism, there is just no desire to fly this aircraft when there are others that simply don't have these basic errors. It is very disappointing for an aircraft that is marketed as offering unparalleled immersion and realism . One can see how the frustration builds as well, when we constantly see new features, snow accumulation, printers etc., and yet the basic core functions still do not work. I do not mean to be negative, it is just so frustrating when you spend hours and hours of your own time testing and making reports, reading the FCOM etc., and you just wonder if anyone from the team is also actually doing this, given that all the basic errors and bugs are still there after all these updates. Of course it goes without saying that I thank all the team for the continued work on it, we'll get there eventually. It is just a shame that the release was, and still is, so far off what was promised.

Seeing this also, and also with ILS approaches. Included it a few bugs I added at the weekend.

Yes also seeing this!

2020 or 2024? Do you have GSX set to auto reposition? I think since the last a350 update, when the aircraft does this reposition it removes the GPU and you then can't get power.

Also incorrect placement of DECEL FLAP1 and FLAP2 pseudo-waypoints I mean there is a lot wrong with this. CHLF is 5nm from the runway and the aircraft wants be at 10ft.... And it is not connected to the rwy on the ND. Something odd with this approach. Again flown regularly with other aircraft and never experienced this.

I should add that I am now using 1.0.12, but the same applies as was only a hotfix update, and didn't address these issues, so these (including the original post) relate to v1.0.12 as well.