Well, it’s not unheard of to have known bugs that are not addressed until after a release (perhaps the fix was complicated and there were strict deadlines). But at the very least these should be flagged as Known Issues in the changelog so that customers may be kept up to date and they’ll surely appreciate the effort.
Some beta testers claim that the bug was reported but was largely ignored, so if that’s true then that’s borderline criminal negligence because there are people who are heavily dependent on standalone WASM stuff like AAO, SPAD.next etc and have super-expensive equipment that relies on these apps. These people simply can not use MSFS at the moment.
Also it begs the question how many of these 300 beta testers actually tested stuff like WASMs, because it’s not all eye-candy and fluffy clouds and trees LODs.
ps: obviously if this was the first time that a major bug made its way into a major release, people would be more understanding. But we’re several months after the initial launch date and we’re seeing the same QA issues reoccurring again and again after each update.