Most of the commonly reported issues and questions are answered in the Frequently Asked Questions (FAQ) option under the Support menu of this website.
*** PLEASE NOTE ***
Your forum account is not the same as the account used in the shop. They are completely separate accounts.
1st December: A new version of the GoFlight Interface Tool for MSFS is now available.
12th November: A new version of the GoFlight Interface Tool for X-Plane is now available.
6th June: A new version of Virtual Flight Sim Hardware is now available (huge update)
21st November: A new version of the GoFlight Interface Tool for FSX/FSXSE/P3D is now available.

MCP-PRO issues with PMDG B747 in P3Dv5

Hello to all:

PMDG has finally made the B747 available for P3Dv5 and the testing has begun.

All of my GF modules, except one (other than the LGT II still malfunctiuoning as it id in v4.5) appear to be working OK.

The MCP PRO, however, is not. All the rotaries appear to be working OK. The numbers/values in the sim's windows are changing correctly when I turn the device's rotaries, however, the numbers/values in the MCP PRO device itself are not working correctly. Only three windows are lit and the values are not correct. For example, turning the ALTITUDE knob, changes de values in the VERT SPEED window as feet altitude in 100's

I also noticed that, when I pressed the APP button to intercept the ILS, the lights in the LNAV and VNAV buttons, came on.

Finally, although the lights of the CMD A, B and C buttons were lit in the sim, the ones in the device (A and B) were not.

If anybody else is experiencing these issues, please chime in, so that Steve can determine what needs to be corrected (unless this is an issue specific to me).

Many regards,
Roberto

Comments

  • Seeing exactly the same thing here.

    Graham
  • I installed the new version of PMDG 747 today (09th May 2020) and it seems that my MCP Pro doesnt work with this new version. I run the new GFIT 3.8.0

    Please can you have a look on that???

    Best regards,
    Dimitris
  • edited May 2020
    Hello Steve,
    I only recently installed the 747 (yet to fly the aircraft) and today installed the update into P3DV4.5 (I do not have P3DV5 installed). I am also seeing similar issues between the PMDG update, GFIT, and the Modules. Here's are some examples of what I've observed thus far:

    GFT8: - Assigned toggles seem to work correctly, however, Light Data is incorrect.
    (Switch Event "Evt_OH-Lghts_Wing" triggers the led for Strobe).
    - A LED Engine 2 for "Fuel Control Run" is always on, regardless of the switch setting.

    RP48: - OH_Lights Storm assigned to a push button, triggers the assigned Landing lights led on the T8 switch.

    EFIS: - The Range knob does not seem to work.

    MCPPro: Some additional observations (all the windows are lit (not Course).
    Pushing the Altitude knob button will light the "B CMD" led.
    Pushing the IAS/Mach knob will light the "A CMD" led.
    Pushing the Heading knob will light both "CWS" leds.
    The leds for the 2 F/D toggles and the A/T Arm toggle do not light.
    The IAS knob changes the MCPPro heading window (in sim-changes the IAS/MACH).
    The Heading knob changes the MCPPro Vert Sped window (in sim-changes the HDG.)
    In the sim, using the mouse to turn Altitude knob Alt has no effect anywhere on the MCPPro.

    Not exhaustive, but hope it helps your troubleshooting.

    Stay safe,
    Claude

  • I'm running P3Dv5 and just installed the new release of PMDG 747 (for v5) and Im also experiencing issues with EFIS and MCP PRO.

    With MCP PRO, the values in the sim readout, and values displayed in MCP PRO are different, and some of the rotaries appear to be changing the wrong functions.

    My EFIS also seems to have issues with the range function.

    Regards
    David
    Regards
    David
  • edited May 2020
    Over in the PMDG Forums, they said they inadvertently broke the data output for external tools and a fix is coming "probably tomorrow".
  • Great catch frantzy.
    It might not be a GFIT issue at all!
    Regards,
    Roberto
  • The problem is at PMDG's end as the SDK hasn't changed.

    Best wishes
    Steve
  • On the PMDG forum, several posters referenced simular problems interfacing the PMDG 747 with flight control hardware and the SDK variables. Yesterday, May 10, Robert Randazzo posted the following encouraging news -- "We broke the SDK output accidentally. An update to correct this is pending. Don't do anything on your end, the fix is entirely ours."

    Regards, Claude
  • PMDG have pushed out the micro update, problem is fixed.
Sign In or Register to comment.