Dave,I have a number of GoFlight modules, but not so extensive as yours. My set up includes two GF P8s, a GF T8, the GF 45 and the GF-LGT. These work quite well with the NG. Pitch wheel, lndg gear and flaps all work. Pretty well all of the GF 45 functions work. As for the rest, it does depend on what you have allocated. My toggle switches are set for landing gear and lights - all function. Oddly, tho' only one of the two fuel run/cut-off switches work. The push buttons I allocate to various miscellaneous functions and all are working OK. Obviously, however, a number of the P8s are allocated via the new G/F key allocation facility.I have my own MCP unit so I've never bothered with G/F's offering. I'm pretty sure that it will not work with the NG, however. All in all using the GF modules with the NG in my cockpit set up has been a very positive experience.Bud

What mcp are you using and any issues with it?

I'm using the GoFlight GF-MCP and none of the functions seem to work. All I've tried to do is set the course, heading, IAS, and altitude on the GF-MCP and none of the settings show up on the NG. I heard that they may actually show up in the PFD, but the MCP doesn't reflect the changes which is key to using the unit, obviously. I still have some more testing to do and I'll report back with my findings... as you can tell I caved and bought the NG despite my concerns from my original post ;)Thanks for your replies and any advice would be helpful. Especially from someone using the GF-MCP together with the NG.Cheers,Dave

Hi That would be really neato.Ted

Sad to report that there is nothing about the GoFlight MCP Module that works with the PMDG 737NG. I didn't attempt to map any commands via FSUIPC but doubt that it is possible with the current software, but please correct me if I am wrong.PMDG -It would be great if we could at least use the GF-MCP to set the values for the course, heading, altitude, vert spd, and IAS/Mach. There is also buttons for holds, master AP, disengage, appr, and bc. I understand that there is additional functionality on the NG that isn't anywhere on the module, but at least we can use some of the features to add to the overall experience. Thanks!Dave

Well - it doesn't as if PMDG is eager to adress this issue. PMDG has given some reply here and there, but they tend to blame Goflight for the incompability. This is a little disturbing as Goflight modules seems to work with most panels, not only the default ones - and where they do not, it's ussually (to my experience) minor thing as autobrake and decision height, which cannot be set by the RP48.I'am wondering, if PMDG in their persue of the finest panel with maximum "as real as it gets" are doing some tricks that essentially is "not MSFS compatible" thus straying away from the FS SDK - I could be afraid that this may lead to even more incompabilities in the future. In posts regarding this issue, PMDG states that Goflight hasn't contacted PMDG so they could find a solution to the problems - this (in my mind) is the wrong approach. Obliously it seems unlikely, that Goflight should be compatible with 3rd party products - they should be compatible with FS (and so should PMDG). And its up to the 3rd party producers to make sure, that their product are compliant with FS. If they all are, then the products should work together.Now as I see it, the producer, who is "most" uncompatible in this case is PMDG, as GF modules seems to work with FS, so I urge PMDG to try and find a solution to this matter.If a solution cannot be found, I regrettably most decline in buying more PMDG products, as they are not compatible with FS. If you only use a mouse, keyboard (and perhaps yoke/joystick) then I trust you can use PMDG products without noticing any problems, but more and more people are using different hardware - and these people will have problems.Please PMDG please find a solution!!!!!Torben AndersenDenmark

Hello Captains!I have done some research, at least as best I possibly can, into the potential to use GoFlight modules with the 737NG. I have not been able to find a definitive answer about the such and was wondering if anyone could enlighten me as to the level of support with the GoFlight interface. I have multiple modules from the MCP to the throttle quadrant and other switch and dial modules. Has anyone used them with the 737NG? I noticed some unanswered questions similar to this one earlier in the board, but hope this one will not be the same.I don't want to spend the $ until I know for sure that I can use all the GoFlight stuff with the NG. I know that the SU2 should include some key mapping abilities and better integration with FSUIPC, so I have hope that it should all work out. The quality of the product looks second to none and I can't wait to spool up those engines in my cockpit as soon as I find out the answers to my questions. Thanks for any help/support that can be offered!Best Regards,Dave

Torben-There is an SDK coming out soon that all hardware manufacturers will have the choice of buying. This SDK will provide exactly the compatibility they require.Hope this helps!

Hello mr. KalamarasThank you for your response - thou I don't think it will do much good. You are not adressing my point, which is, that no software- and hardwaredeveloper is able to ensure that their product can work together with other addons unless you stick to the "normal" way to use and make inputs to FS.I have tested GF-MCP with other 3rd party panels and only found problems with yours, PSS B747, Olegs DHC8 and to a minor extend Dreamfleets B737, PSS DHC8 and Bill Grabowskys ERJ-145. Seems to me we have problems whenever we want a bit more than the default panels can provide (espescially in regard to the ALT setting).To have Goflight make special drivers for these products or have you to make "drivers" to all kinds of inputdevices is in my mind the wrong attitude - this MUST go wrong - naturally you can't (and Goflight can't).So this is why I ask you to "go back to basics" to ensure compability with the rest of the industry. If this is not an option then we have problems. You have given a very small hope to us, telling about your SDK and naturally I hope GF will buy it - on the other hand - GF has given a SDK about their product for free(!). I don't know wether or not it includes the new GF-MCP, but at least it's free.This said - thou I still hope for a solution - I think it is too late regarding the B737TNG. You have (more or less) finished the development and are concentrating on new products (like the B1900). I don't know if the B1900 works with the GF-MCP, as the autopilot on this kind of aircraft normally isn't as elaborate as on the FMC equipped B737, but if you don't consider the ways you implement your panels in FS, I think this is not the last time, we, the consumers and your costumers(!), will have invested in products, which do not "talk" to each other. And this tends to lead to unhappy costumers, which noone can live with in the long term.And selling a SDK to hardwarecompanies is not the "road to happiness" - I don't think many will buy it and then we're back at square one. Torben

What you are asking then, is for PMDG to "dumb down" their products by going back to the basics as you put it. It's my understanding that they can't produce the level of realism as it pertains to nav/com issues by using the basic FS9 nav/com standards. I would bet that I'm not far off the mark by saying the majority of people who bought the 737 want the high level realism that their 737 provides. The last thing I want is for them to go back to using the default FS9 AP system. I hope you find a solution to your problem, but what you are suggesting sure isn't the way to go. They would be just penalizing the overwhelming number of people who are using the PMDG 737 without the GoFlight units. John Fitzpatrick

This has nothing to do with 'dumbing down' (nice term) anything. How about we 'smart up' the PMDG unit... (love message board grammar). All is requested here is that the PMDG AP system respond to the default AP commands via an API alias (default AP command interception) of some sort so that the GoFlight unit (MCP) would at least be able to manipulate the basic settings, i.e. hdg or course, alt, spd, v/s, cmd A, disengage/engage. This would change nothing on the 737NG for those without GoFlight units but would allow those seeking a higher level of realism something more than the keyboard and mouse jockeys experience.I understand it is difficult to please everyone, but by supporting the default commands from a mapping perspective may help PMDG avoid these kinds of threads time and time again and place the burden squarely on the hardware manufacturers (it is 50/50 right now). The SDK is nice if someone wants to build something specifically for a particular aircraft, but general built hardware (such as GoFlight) is supposed to work out of the box with a majority of aircraft since it supports most of the default FS commands.

I seem to recall about 2 or 3 weeks ago, a keyboard mapping routine for FS9 similar to what PSS offers with their Airbus. Would something like that help and does the GoFlight AP unit work with PSS products? John Fitzpatrick

Could not have putted it better my self - thank you.Torben Andersen

Could help if the Goflight MCP module had keymapping routines like the other GF modules, but right now it has not. Maybe when GF updates their driver we will have. Cross my fingers.Torben Andersen