Just to clear up a couple misconceptions posted here on the PMDG 737NG:1. They are not going to make you pay for bug fixes - the SU2 update fixes nearly every outstanding issue and adds a TON of functionality to the FMC. (transitions, approaches, missed approaches, CRZ decents/climbs, keystroke mapping for home cockpit builders, improvements to the ND screen etc) As a member of the SU2 beta team I can tell you with 100% certainty that PMDG cares VERY much about making the 737 a great product and have admitted their mistakes regarding the initial release. I can't imagine anyone being disapointed with SU2 when it comes out unless you're expecting a perfect level D simulator, which not even 767PIC is. They've listened to and implemented almost everything myself and the other testers have requested. REPEAT - you will NOT need to pay for the SU2 update!!! The 800/900 is adding additional things like the TCAS system, the EFIS LCD option and the new visual models - all of this was very clearly stated before the 600/700 was released. PMDG also stated that anyone who purchased the 600/700 right after release will be entitled to a discount on the 800/900 addon.2. I'm not sure if you've had to use the PMDG registration system since the initial release phase, but they changed it to an entirely web based method that allows you to get new keys as many times as you want on your machine. There's no more emailing them and waiting for a key etc... It's incredibly easy and non-intrusive.Ryan

"As a member of the SU2 beta team I can tell you with 100% certainty that PMDG cares VERY much about making the 737 a great product and have admitted their mistakes regarding the initial release."One of the fundamentals of safe navigation is proper FMC programming, i have been told the altitude contraint restrictions in the upcoming patch does not address this issue. I.E you cannot program the FMC for the plane to cross BSR at or above 15000 or /15000A. You can only put in 15000 and the plane will level off at 15000 till meeting that intersection. It was programmed in the PSS777 and 747 for FS2000!What a joke.

I never had any problems with the installation or their security, and I invite anyone to come and see that the PMDG performs fine on my computer. I just think there are too many complaints from people regarding these add-ons. If you look at the forums, they request the most ridiculous features you could put on an add-on. One person wants visible fire on an engine, another wants an animated co-pilot to work the flaps and other switches. The list of nonsense some simmers want on these planes is beyond silly. The bottom line is, if you go to a forum you have so many simmers begging like children for a release. Then when the release comes out, they moan and groan because the stab override switch doesn't do anything! If you aren't happy then simply stop buying pay ware products, or think about the fact that these add-ons take some time to program, thus getting the bugs out. As far as PSS is concerned, they released the 330/340 first because they new they'd sell more for those who are dying for FS9 add-ons, then they can patch the other planes that they've already sold. I don't dislike PSS, however, making someone pay close to ten bucks for a paint is gouging, IMO. There products have problems as well, and there forum is set up so that any serious complaints are stricken from view. Don't act like PSS is better because they might work better in your eyes, when in reality they're only modelling 35% of the planes functions, so you can't compare them to PMDG, PIC, DF, or any other company who tries to model 80% or more of a planes realistic ability. You also have to understand the limitations of MSFS, especially FS9. The program just came out, so of course there will be problems. Most people have lousy frame rates in FS9, but then can't understand why a graphics intense add-on won't work at 20+ FPS! Look, I don't care who buys what or who complains. I'd complain if I spent money on something that didn't work, however, I think there's more latitude for me when it comes to complaints. Nothing is perfect, and therefore I'm happy just to have something better than the default planes. I guess I've been lucky so far and haven't had any real issues. I also believe that a complaint against PMDG when the plane doesn't do something or won't even install isn't entirely their fault. If I got the program to install and work, then it's not simply a PMDG problem.

No contridiction here.A developer must be prepared to hear the complaints of his customer. The man has a full right to vent. I did not say he didn't. But I also informed him of his right not to purchase product.I work in technical support. I will ALWAYS help the customer to solve their problems. Yet whether or not I help them does not absolve them from the responsibility to do some due dilligence prior to making their purchase.If they buy a product for an application that the product was not designed for, I can't make it function the way they want. I can empathize with them, and tell them I am sorry even credit them for their purchase, but in the end, they bought the wrong product. I am not trying to contradict anyone.I am saying that both the vendor and buyer have responsibilities. A vendors willingness to support or not to support a product does not excuse a purchase that was done either in impulse or without due dilligence.I told the original poster that I knew how he felt, and how frustrated he was. But that in the future, he should make sure to research and only buy from companies that have a reputation for good product and good support.If all companies worked to satisfy the customer, then "buyer beware" would not be in our vocabulary. I can urge companies to provide good service and good product, while at the same time urging consumers to be smart about their purchases. I do not see this as a contradiction in any way.