WHAT CHANGED, WHAT REMAINS OPEN, AND HOW TO READ THE NEXT ARGUMENT
Across these releases the recurring questions are recognisable: does detail justify the workload; does the aircraft respond as expected; can the owner complete a flight reliably; and does support turn an observation into a reproducible report? Answers changed with release, computer, controller and priorities. This history keeps dates and viewpoints rather than assigning one permanent score. The developer's own performance account illustrates why system-dependent outcomes must stay visible. [22, 5 August 2023; acknowledged workload and system-dependent results]
The DOOR/OXY page and central pedestal are visible together; the left MCDU identifies an A320-200 with V2527-A5 engines. [1, Presentation chapter: Final Thoughts]
Some complaints have a recorded change of status. The August 2022 reviewer assessed the font issue as addressed. The expansion received corrective patches. A V3 user explicitly marked the door-texture case solved. Other first-week V3 concerns remain reports or disagreements at this cutoff. They should not be marked resolved without the relevant release note, a controlled reproduction or a clear retest by the affected owner. [7, Glass Cockpit Display; font correction] [34, 29 August corrective update] [44, Post 8580: door-texture case marked solved in 3.0.0.7454]
The positive case is a detailed aircraft many owners wanted to keep flying and learning. The critical case is that detail does not substitute for smooth operation, predictable controls and clear support. These judgements can coexist. The BFU crash discussion demonstrates that affection, frustration, successful flights and unresolved attribution can appear together. Preserving that complexity records the actual conversation rather than producing either an advertisement or a prosecution brief. [40, Opening post, subsequent edits and contrasting reports]