I'm going to cross post this in the FDC and PMDG forums in case there are individuals who might not read both forums.Here's my issue/problem:I have created a very simple test checklist for after takeoff. It consists of the following 4 items and default interactive responses:1) Flight director - ON2) Auto Throttle - Armed3) Yaw Damper - Engaged4) Auto Pilot - EngagedI am taking off with all 4 of these switches turned off and then activiting the checklist to see if the "errors" are: a) caught by FDC and then b)rectified when I turn the switches on.On the default MS 777 everything works just fine. Each item is identified as being a problem, and then I can turn the switch to the on position and when I reactivate the checklist there is no longer a problem.However, when I use the PMDG 737 (both 600 and 700) it appears that FDC is unable to tell whether the switch is in the on or off position. Each item in the checklist is identified by FDC as a problem, but even when I turn the switch on it still shows up as a problem and I have to "override" the checklist item to continue.Each of these switches behaves properly within PMDG as far as functionality for the aircraft, it's just that FDC can't seem to "see" what position the switches are in.I'm hoping that someone else who has both FDC and the PMDG aircraft can check this behavior and see what is happening on their machine.Thanks,

Sorry to reply to myself, but I thought I should clarify something about my problem. When I gave the list of 4 items that didn't work I should have mentioned that these were the "ONLY" four that didn't work. All of the other interactive FDC calls (lights, parking brakes, auto brakes, landing gear, etc. etc.) are being handled correctly. My original note was probably misleading in that it may have implied that nothing was working. (I was trying to keep my note short and sweet).

Hi PhilI believe that this has to do with the custom autopilot on the 737NG. Since it does not use the default MS Autopilot, the key commands associated with the default MS autopilot do not corrolate with the functions on the PMDG autopilot.Regards Paul GollnickTechnical Operations/Customer Operational SupportPrecision Manuals Development Groupwww.precisionmanuals.com

Paul-Thanks for the reply. I was afraid that it would be something like that. Guess I'll just have to rely on my own memory to keep things switched as required.Am enjoying your aircraft a lot!!!Phil

Hi Phil,Have you adjusted the checklist around the errors yet? If so I would be more than interested in getting a copy of it so that I too can enjoy the PMDG along with FDC. Could you mail it to matthew(at)fsmagazine.nl Thanks so much!Matthew NiederbergerEditor In Chief / FS Magazine

[a href=http://www.fsmagazine.nl]Visit FS Magazine, the Dutch Flight Simulation Portal[/a]

Dear Phil-after the release of our second Service Update, we will make available an SDK for linking with our internal autopilot etc.Interested organizations can contact us for more information on the SDK, once the release is out.Best,

What I did in the cases where FDC doesn't detect something on the 737 is to use a non-standard prompt. This disables the "interactive" feature in FDC, but will still call out the item so that you can set it correctly.For example, use "engaged" instead of on. This is listed as a work around for aircraft that don't use the standard FS autopilot (and thank God the NG doesn't).I can't figure out how to post an attachment, so let me know if anyone wants my checklist and performance file for the 700. :-)Aaron

HI Aaron,Please send me a copy if you would not mind matthew(at)fsmagazine.nlThanks a bunch!Matthew NiederbergerEditor In Chief / FS Magazine

[a href=http://www.fsmagazine.nl]Visit FS Magazine, the Dutch Flight Simulation Portal[/a]

Leftris,Does this mean that we can build our own MCP, EFIS, CDUs, overhead, etc??? :D :D :D-Shaun