To PMDG Developers,I bought and installed the 737 on Tuesday - the day it came out. Prior to that I flew almost exclusively with the 767PIC and to control it I'm using Aerosoft's MCP747 unit.I've discovered this evening after several worrying hours of investigation that the PMDGOptions.DLL is causing a conflict between the MCP and the 767PIC preventing any of the units controls from communicating with the aircraft's autopilot. To prove this I've moved the DLL from the MODULES folder and the problem disappeared.This is potentially very serious for me. Although I like the 737 I cannot contemplate not being able to fly the 767 and control it via an expensive piece of hardware. I know you are in touch with Andrew Mclean at Aerosoft so I'm hoping a solution can be found. I posted a message earlier this evening on his forum asking for help as I've only just discovered what is causing the problem. I'll advise him of the problem too.I know Leferis is working with Andrew to link the two products but unless a reasonably quick solution can be found I may have no alternative but to remove the 737 from my system.Regards,

bumpguys, this is an important one!

Lenny, thanks for bumping this. I'm doing it again as it's gone down to page 3 overnight. PMDG please at least acknowledge you've read this. It's a critical issue for those of us with the MCP and the 767PIC!! :-( Thanks.

As a temporary solution you could remove the DLL when you want ot fly the 767 and then put it back when you want to fly the 737.RegardsRussell Jourdain (NZL007/ZK-RHJ)

Hi Ray,I'm sure the guy's are looking into it for you, and should reply when they have the answer :-), those Aerosoft MCP's look an awesome bit 'o kit.Regards,Bob JonesPrecision Manuals Development Groupwww.precisionmanuals.com

Hi Russell,That's precisely what I'm having to do but it's a major pain. If I don't move the DLL back in and then choose the 737 it tells me I don't have a valid installation (or words to that effect).Cheers,

Hi Bob,Thanks for your reply. It gave me several hours of real worry last night as I feared the MCP had developed a fault. Here's hoping for a quick resolution so I cna enjoy both aircraft.Thanks,

I thought you might be - it was only a suggestion until the guys get a chance to look at it :)RegardsRussell Jourdain (NZL007/ZK-RHJ)

We've had another user report this. It *seems*, though I have NO way of verifying it, that there are conflicting WM_ type messages that are used by the 767PIC DLL.What happens, though, is that these are not documented anywhere, so it's quite the guesswork to find out what they are.In our upcoming service release, I will look for ways to make the PMDGOptions.DLL read an .INI file for settings in terms of its WM_ messages. Then, it'll be easier to provide different values, in case we discover a conflict somewhere.I just *WISH* that other developers would actually publish their WM_ codes, so we don't step on eachother's toes...

Hi Lefteris,Many thamks for your comments on this problem - one you can't have anticipated. I do have an e-mail address for Laurent Crenier if that would be helpful although the team have more or less withdrawn from supporting the 767PIC.Is it still your hope that the MCP and PMDG737 will be able to communicate with each other?Thanks,

Ray,Were you able to get the 747MCP to work with the 737 even if it meant having to move the dll? If so could you tell me how and which dll as I am not using the 767PIC at this time.Thanks for whatever information you may have.Tom

Hi Tom,Please see my reply in the Patch thread anchored to Page 1.Cheers,