![]() While the investigation is ongoing, thanks to data gathered during the beta we were able to narrow down the search. For example, we now understand the issues are not limited to specific regions or locations. With the global release of AAU 02 this week, we’ll have the opportunity to gather data on a larger scale and continue working towards a solution. We’d like to thank the community, as always, for your desire and appetite for testing out the AAU_02 aircraft. Having such a wide breadth of systems, simming styles, and viewpoints really creates a test force that is simply impossible to replicate with even infinite flight hours in QA. The community brought forward all manner of issues, some big and some small, that made it possible for the team to locate things deep in complex systems logic only surfaced via the specific actions of a given user at a given time. Because of the complexity of these aircraft, an issue that has only a 1% chance of happening really showcases the law of probabilities thousands of simmers trying their best to break it certainly makes those issues much more likely to show their face. ![]() ![]() ![]() We caught massively important issues with VNAV, flight modeling, FMC behaviors, and would not have been able to track down some critical hardware sensitive optimizations without the tireless support and generosity of the community. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |