September 29, 201411 yr PMDG have replied to my ticket. They think they've identified the cause and it should be fixed in SP1c which is currently being tested.cool :-) I think I read somewhere that there is a "force idle after touchdown" option in the CDU. I looked but I could not find it. Otherwise I would have recommended trying without that option. Rob Robson
September 29, 201411 yr Author PMDG have replied to my ticket. They think they've identified the cause and it should be fixed in SP1c which is currently being tested. Correct, I have received the same reply. Nice to see the community working together and using the correct resources to report a issue and get it resolved! As Kyle said, its essential that we report potential bugs to the support team directly, via individual support tickets and not just counting on somebody else doing it. cool :-) I think I read somewhere that there is a "force idle after touchdown" option in the CDU. I looked but I could not find it. Otherwise I would have recommended trying without that option. The option can be found via the FMC. Menu ---> PMDG options ---> Options ----> Simulation ----> Page 2 ----> A/T idle override (I forget the exact wording). Its good to have it on, as in real live u will often see pilots pull the levers to idle as soon as A/T goes from SPD ---> Idle as this is quicker and enables reverse to come in as soon as the mains are on the ground. This has no effect ON/OFF on the reverse thrust bug that PMDG has identified and is working on fixing as we speak. Leo Cal
Create an account or sign in to comment