RogerWilco

I’ve found plenty more bugs. Basically, nothing works at all. You can’t enter altitude constraints if you’ve already entered step climbs—they conflict with each other. Entering altitude constraints during the descent wipes previous step climbs from the flight plan; furthermore, once you remove those constraints, you can’t enter any step climbs at all because the system claims there is no cruise altitude—even though it was entered correctly. This aircraft is completely unfit for long-haul flights. It’s ridiculous—after 100 updates and a year and a half of further development following a half-finished release...

From time to time, the A340 incorrectly determines that there is no further waypoint after the next one—but rather a discontinuity—causing it to automatically switch to heading mode and stop following the route. Step climbs are still not being executed correctly in automatic mode.

Still an issue in 1.2.6

I have also frequently encountered situations where, while en route from Germany to the Far East, I simply became stuck somewhere in the middle of the journey. The aircraft was still flying, but all the instruments had frozen, and I was no longer making any forward progress. I had drifted far off the programmed route. This issue could also be related to step climbs, as they remain non-functional. Whenever you make multiple changes in the MCDU, you have to be prepared for the entire system to crash, for incorrect values to be calculated, and for the flight never to reach its destination. This level of inconsistency is completely unacceptable for a long-haul aircraft; consequently—even after more than a year and dozens of updates—the product remains unusable.

I have also frequently encountered situations where, while en route from Germany to the Far East, I simply became stuck somewhere in the middle of the journey. The aircraft was still flying, but all the instruments had frozen, and I was no longer making any forward progress. I had drifted far off the programmed route. This issue could also be related to step climbs, as they remain non-functional. Whenever you make multiple changes in the MCDU, you have to be prepared for the entire system to crash, for incorrect values to be calculated, and for the flight never to reach its destination. This level of inconsistency is completely unacceptable for a long-haul aircraft; consequently—even after more than a year and dozens of updates—the product remains unusable.

Wear and tear doesn´t work for me, too. Sliders also don´t change. Aircraft is flying 12 hours every night, so there should be changes.

There is no 1.2.2. 1.2.1 is latest

Bug is still present!!!!!!!! 1.2.1

Step alts don't work at all. It's the same mess as with the A350. It imports correctly, but when I just checked, it only performed one step climb instead of two, and the entire MCDU was messed up. Times and altitude readings like -123624517, etc. They just can't do it right.

This is also a long term bug, that never gets fixed like one million other ones. Instead from update to update they are again introducing bugs, which where already fixed two times.

1.1.9 BUG IS BACK!!! Cab Press always +50 ft/min

1.1.9 Auto Step Climbs doesn´t work at all.

There are so many old and new bugs with 1.1.9, it doesn´t become better. No cockpit with cabin packs, Cab Press +50 ft/min all the time, Auto Stepclimbs don´t work at all and so on. Since the beginning, every update is one step forward, but two steps back.

Auto Step Climb doesn´t work at all. (1.1.9)

Cabin packs are both completely bugged. Auto step climbs and step climb calculations also don´t work. D-ATIS requests partly hang forever on "Pending request" and can´t be resetted.