The problem with anything this complex is that it is not always “buggy”. Yes, I have seen the ridiculously overdone haze in places it should not exist or clouds sitting on the ground, but I have done three flights in the past two days where the weather was next to perfect. No clouds sitting on the ground, and either very light haze, or no haze at all. Based only on those flights, I would say “it works fine”.
A limited set of developers can only do so much when it comes to testing a new, highly complex technique that has never been done before, and the only way to find all the potential bugs is to have as many people as possible use it and report problems. Making the new system optional for those willing to put up with potential issues, while leaving the ability to opt out for those who do not want to bother is the best solution IMO.
I have been running MSFS since Alpha 4, and in all that time, I have never had a CTD. Not one single time. If I were an official tester reporting to the development team, I could honestly say “I have found no CTD issues whatsoever”.
Yet, we all know that CTDs are an issue in MSFS. Some users are plagued by them constantly. Some are due to external problems on individual computers (hardware issues, corrupt drivers, incompatible add-one etc.), but some are clearly due to bugs in MSFS itself.
I know now that if I had tried spawning at KADW in SU6 I would have gotten a CTD (for the very first time), but knowing that in advance, I avoided going to that area. I am not an official tester, and saw no reason to deliberately crash the sim for no good reason. Many other users found the bug “the hard way”.