I just finished typing out a long message explaining how I feel about not having a fix for the 757-200 landing gear at night issue. But I hit the "reset message" button instead of the "post button" and lost my message, and since I don't feel like making a new one I'll be brief.As a customer of PMDG for both Fly! and Fly!2 products. I feel that it is the duty of PMDG to provide a fix for the above issue. I know that they have tried to put that task on TRI, but it's qutie doubtful that any programmer with TRI would invest their time in making such a patch considering the fact that they won't be compensated for their work. I don't know if any other 757-200 owners feel this way, or if I'm just confused, but either way I have waited patiently for a fix to this issue and now I'm getting impatient. If it is the opinion of PMDG that unless a TRI programmer decides to provide us with a fix theres not going to be one, then I would like PMDG to tell their customers that there will now be a fix. Simple as that, if one is expected then let us know, if one is not expected then that is what I would like to hear.Thank You,JeffLas Vegas

I agree with you Jeff. I hope PMDG will address this matter soon. And also I hope they won't forget to release the paint kit too.chris salviejorpll

Jeff-this must be one of the most unreasonable requests for help that I've heard in a long time:How can we be expected to fix something that is a bug INTERNAL to Fly!2 code? We assure you, we DO NOT have the Fly!2 source code, otherwise there would have been a Fly!3.Had there been a bug within our code, be assured, it would have been fixed.

:-lolLefteris, perhaps Rich could ***accidently*** forget his source code somewhere, it would certainly resolve a lot of issues ...Unreasonable people make up 30 percent of the planet, the other 70 percent is covered in water ;-)BTW: what are you doing posting here during your holidays, get outta here!Ray

Jeff-Nobody would like to see that fix issued more than US!As the explanation in the documentation was apparently not clear enough, let me explain:FLY!II has a problem in its model rendering code that creates anomalous behavior during a transition from light to dark or dark to light.Your 757 is correctly coded in this regard, but the bug within FLY!II causes the gear to become out of phase.I was assured by Rich Harvey during the weeks before out 757 release that a major patch for FLY!II would be released in close proximity to our 757 release. I debated holding our release in ancitipation of TRI's patch- but in the end elected not to.TRI and Rich have, for one reason or another, elected not to release this patch yet. It comes as a disappointment to all of us on the PMDG team because our airplane does not display as well as we would like, especially given the thousands of hours we put into it.Unfortunately- I cannot force Rich or TRI to devote resources to upholding the promise of this patch- and therefor it is completely out of PMDG's control.Hopefully this bit of explanation will help you to understand why we are unable to respond to your demands.Robert S. RandazzoPrecision Manuals Development Group http://www.precisionmanuals.com/images/coolcap.gifwww.precisionmanuals.com

Thanks for the reply. One of the replies to my original question accused me of being unreasonable. Well, my response to that accusation is that, "The customer is always right." As a paying customer, asking for a solution to a problem with a product that I purchased is not unreasonable, especially when it had been talked about and expected.Anyhow Rob I was wondering something that I'm sure you guys have analyzed, and that is how the default planes for Fly!2 don't seem to have that particular "anomoly", is it possible to identify to change to the 757 code as far as gear goes to reflect the code used by the Fly!2 default planes? Like you said the 757 is coded correctly, and that it is a bug within Fly!2, so why does this problem not occur in the default planes?Also, when you said that you had originally elected to not release the 757 until there was a fix for the landing gear problem, that makes this situation a little bit more understandable and, in my opinion however, I think that that probably would have been the best thing to do. I say that because it seems almost certain that we will never get a fix, and that isn't cool.Thanks,Jeff

Lefteris,You can read my reply to Rob if you'd like.Anyway, knowing that this problem had existed you should have never released the product, or at least until the issue was resolved, to me that is unreasonable, after all we are paying customers. $40.00 might not seem like a lot, and for some people it isn't, but you must keep in mind that some of us don't always have extra money to buy goodies. For me it is not often that I can treat myself.Jeff

Jeff-The default models for FLY!II do not include night-lit modeling. That is the difference that is causing the problem. The night lit portion of the model can be removed by the user- but it takes some intimate knowledge- is very tricky- and isn't something I'm able to explain this evening.As for whether or not we should have waited- each is entitled to his own opinion. Rich Harvey felt that he would release a patch within a few days of our release, which influenced my decision to release. Even in view of Rich's inability to live up to his expectation- I stick with my decision.Robert S. RandazzoPrecision Manuals Development Group http://www.precisionmanuals.com/images/coolcap.gifwww.precisionmanuals.com