Currently, the designers of

Sean,I believe the problem version was 3.12. 3.125 was the version released to correct the problems with add-on a/c diplay issuesRegardsPaul Gollnick :-coolTechnical Operations/Customer Operational SupportPrecision Manuals Development Groupwww.precisionmanuals.com

Hello,Speaking about compatibility with other products, I'm using Flightdeck Companion and in the latest version there is a feature where you can have the autobrake returned to 'Off' at a predefined speed after touchdown by your virtual co-pilot. But with the PMDG 737NG that doesn't work and according to the team behind FDC that's because PMDG built their own autopilot.Since I love both products it's a pitty they don't work 100% together. The thought crossed my mind whether it would be possible for you (PMDG) to provide the FDC team with the info needed to have your products work together? Think FSUIPC may be involved in the issue as well...Cheers,

Richard -PMDG is making it possible to assaign keystrokes to various autopilot functions and other plane functions in SU2.

Hello Fred,OK, that's great but I'm not sure whether that will help FDC interact better with the PMDG 737. Guess the best would be if PMDG and the team behind FDC made contact themselfs. That is of course if they think compatibility between their products is an important issue.I'm not sure about FDC, but there's no doubt how popular PMDG's 737 is and I belive FDC is quite popular as well so I'm pretty sure lots of people would appreciate such compatibility efforts.All the best,

I always use Radar Contact when I fly and haven't had any problems with it at all when I'm flying the PMDG 737.WilliamP.S. now if your talking about having the copilot drive the plane, no that doesn't work. Radar Contact can only do that with aircraft that use the Flightsim autopilot so that excludes almost any payware aircraft.

RichardI couldn't agree more. The auto pilot is not the only interactivity function addressed in the latest version of FDC. I would heartily second a meeting of minds between PMDG and FDC.Bud

All:Thanks for the quick replies!Sean

Great to hear I'm not the only one with those kind of wishes, maybe someone from the PMDG team could comment?Cheers,

Richard, I just wanted to drop a quick line and let you know that I also have Flight Deck Companion in use with my PMDG 737 and it works great! It does a super job of turning it off when at 60 knots.Best Reguards,James

Hello,That's great news James, but I wonder what's the difference between your setup compared to mine and others with the same problem. I also got the problem confirmed by a team member of FDC who had the same problem when using FDC with the PMDG 737 when he tried it out and thereby gave me the explanation about the PMDG autopilot.So...just to clarify...what you say is that you actually see the autobrake gauge change settings automatically by the virtual co-pilot? In my case, I see the autobrake gauge go from 'RTO' to 'OFF' after takeoff but that has nothing to do with FDC. On the other hand, the autobrake doesn't go from 'OFF' to a predefined setting at a specific altitude and neither does it go from that setting to 'OFF' after touchdown at a predefined groundspeed.Are you aware of anything special you did to have this work for you?Cheers,

Gave it another try yesterday and came up with the following:The co-pilot calls out the correct settings for the autobrake as predefined and it "seems" to work although the gauge for the autobrake is not moving and thus indicating the settings called for. Does your autobrake gauge actually MOVE when the calls for different settings are made?Cheers,

can i get some information on how this is going to work?

Richard, Hello and sorry for being tardy in responding to your question. I took a short hop from my home at KSEA and went to KPDX to make sure I wasn

Hello James,No worries and thanks for your answer. Actually I've had the same experience now that the autobrake returns from '2' for example to 'off' when starting to taxi off the runway after landing. Strange why it happens then and not when it should, that is when your speed drops below the value you've chosen in the FDC settings.But what still doesn't work and I'm not sure if that works for you either is to have the autobrake go from it's 'Off' position to the setting you've set when dropping below a certain altitude before landing? I've heard that the call are made by the co-pilot but the gauge remains in it's 'Off' position and therby I'm not sure which setting the autobrake really has - the setting that is called out or the 'Off' position the gauge shows...Hmm...find all this a bit strange I must say - wish there was a way to fix it :-)All the best and wishing you a nice weekend,