Thank you.
Well, the 3 Beta tests are nothing comparing to hundreds of in-house tests completed by our team members and the type rated pilots.

So, how the bugs got past testing?
Actually it is not about the testers' "sharp eye". It's not a big deal to find 100 bugs, but to fix them without breaking other things.  

For example the '757 Captain' system programming consist of 1600+ print pages of handwritten C++ and XLM code. Where every parameter in every line is interconnected with hundreds of others. It's just programing.
Add thousands of handmade bitmatps, hundreds of textures, tens of 3D modles (thousands of polys each), hundreds of animations, flight model, hundreds of sounds. Now imagine those MANY THOUSANDS of items must look\feel\sound real and work in accordance with flight manual. IT'S A HUGE JOB.  

Same software for a real aircraft costs hundreds of thousands dollars.  ::)

As for the customers' "pressure" (we call it feedback), it helps to set a priority for what to fix first, last or ignore.


Why other developer made this\that system\feature right?
1. All developers are different, all products are different but nothing is perfect. All products (hamburgers, software or cars) have strong and weak points.  
2. We keep working on our products improvement.