Can it be done??!! I have been trying to reconfigure settings through FSUIPC (fully registered version) and the PMDG key assignments but with little luck...especially when it comes to turn dials for CRS, IAS/MACH, HDG, VERT SPEED.I manage to get the commands to move in the PMDG panel but they are far from in synch with what my GF-MCP reads.Radios etc I have no problems with....just seems to be the MCP.Any help would be most appreciated.Kind regards,Justin Cooper

>Can it be done??!! I have been trying to reconfigure>settings through FSUIPC (fully registered version) and the>PMDG key assignments but with little luck...especially when it>comes to turn dials for CRS, IAS/MACH, HDG, VERT SPEED.>I manage to get the commands to move in the PMDG panel but>they are far from in synch with what my GF-MCP reads.>Radios etc I have no problems with....just seems to be the>MCP.>Any help would be most appreciated.>>Kind regards,>>Justin CooperYou cannot get the displays on the GF-MCP to "sync" with the PMDG numbers. what you CAN do is not use the go-flight DLLs at all (or program the MCP to have no function) and then you won't get the out-of-sync displays, but you can use the knobs with FSUIPC.The reason the displays don't sync is because the GF driver is looking at the registers for the default MS autopilot, and most of it is ignored in the PMDG 737.I looked at the MCP and decided I'd just build the GF system from RP48s and P8s, with the only "display" on a GF-46 for the radios and transponder.

Thanks Timothy,Well I guess that was an utter waste of money, as the only aircraft I fly now is the PMDG NG. Not impressed as I was told by the salesperson that it would work correctly.Thanks again.

I wonder why GF developers can't compile a driver to read correct headers from PMDG code. Of course, for this to work, PMDG would have to release source code to GF.Tero

Justin:You beat me to it. I have exactly the same results as you. I had a feeling it was going to be like this, but it's actually more upside down than I imagined. Pity. Don't think it can be resolved properly. There's a workaround in the GF NOTVAM #2, but that's all it is and it has shortcomings too. However, if you have other GF stuff, try that out because some of it works with no keymapping out of the box. I have several GF bits of hardware and their radios work with PMDG NG as do the flaps, gear lever, various lights, and some other stuff. That surprised me pleasantly.'Course, it would be great if the MCP did actually work right, but that's prolly off in the future, unfortunately.JS

JS,Yeah my GF radios and other buttons work fine and i find them great for flying online with VATSIM. It just seems to be the GF-MCP. A real pity because it is a great module (works fine on default aircraft...but who flies those!?! ;) ).Have managed to also incorporate TOGA, VNAV, LNAV, Flight Director and Autothrottle Arm into usable buttons on the GF-P8.I liked the idea of the GF modules because I was able to buid a custom box for them and have them in the positions I wanted.Im very interested in the throttle set up, just hope that works with no problems.Anyway...I might aswell sell the MCP...or stop flying the NG!

Don't give up on the MCP! There are still many great freeware panels with default MS autopilot that work with the MCP that are worth using. I am equally frustrated but am keeping both and using them for different things. This hobby is full of compromises once you get beyond the plain vanilla sim. We expect a lot and get a lot, but not everything.JS

When I asked Doyle at Goflight about something related to this, he said the following: The current version of FSUIPC doesn't do anything with the LEDs or displays on any of the GoFlight modules, but the key mappings should work just fine. You might want to ask Pete about this, as he's recently expressed some interest in the LEDs and displays.So there might be some hope!

Krister:Well, the keymap does work, more or less, but it is confusing and unintuitive because when you push the MCP buttons, while the cockpit MCP lights up in reaction, the GF MCP light then extinguishes!In addition, it is strange and disconcerting to dial in data from the GF MCP that differs from the NG MCP.In addition, the keymap seems to fall asleep or fall out after doing certain things on the NG and needs to be re-set or woken up. Not really a good enough solution to use it.JS

I dont often read the FSUIPC forums as it seems to be a particularly trouble free interface, and well worth every cent. Im pretty sure the problems associated with the MCP and the PMDG are most probably PMDG code related.Thanks everyone none the less. Hopefully if I just hang onto the MCP, one day there will be a fix.

I have every faith in FSUIPC.....!JS