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.
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.
PMDG MSFS GIT - MCPPro Altitude scrolling and display in sim and on the MCP display window lagging
Hi Steve,
Thank you for getting the update to GIT for MSFS supporting PMDG B737 for MSFS. Things are working pretty good. However, I noticed that when setting the MCPPro Altitude, both the in simulator PFD display and the digital display on the MCPPro lags by a few seconds. If example, you have turn the knob real slowly or you will overshoot your desired altitude setting. The MCPPro setting knobs, e.g. heading, speed, course, etc. appear to be working normally.
Also, I noticed with the GF-LGT II Landing Gear module, the raising the gear to the full UP position on the module only raises the gear lever to the OFF position. You have to move it a second time to the UP position to get it to raise to the UP position. I noticed this in XP Zibo as well. Any fix for that?
Finally, and I'm not sure this is a GIT issue, but when setting the NAV radios using the GF 166 and GIT, when you rotate the small MHz knob, i.e., the .00 to .95 setting, as you pass through the ".00", for example from .00 to .10 or in reverse from .00 to .95. the big value for MHZ changes. For example if you have 110.10 set and rotate the small knob through .00, the frequency changes to 109.95. Make sense? Is this a GIT issue or is it a MSFS/PMDG issue?
Thanks again for your help!
Rich Boll
Thank you for getting the update to GIT for MSFS supporting PMDG B737 for MSFS. Things are working pretty good. However, I noticed that when setting the MCPPro Altitude, both the in simulator PFD display and the digital display on the MCPPro lags by a few seconds. If example, you have turn the knob real slowly or you will overshoot your desired altitude setting. The MCPPro setting knobs, e.g. heading, speed, course, etc. appear to be working normally.
Also, I noticed with the GF-LGT II Landing Gear module, the raising the gear to the full UP position on the module only raises the gear lever to the OFF position. You have to move it a second time to the UP position to get it to raise to the UP position. I noticed this in XP Zibo as well. Any fix for that?
Finally, and I'm not sure this is a GIT issue, but when setting the NAV radios using the GF 166 and GIT, when you rotate the small MHz knob, i.e., the .00 to .95 setting, as you pass through the ".00", for example from .00 to .10 or in reverse from .00 to .95. the big value for MHZ changes. For example if you have 110.10 set and rotate the small knob through .00, the frequency changes to 109.95. Make sense? Is this a GIT issue or is it a MSFS/PMDG issue?
Thanks again for your help!
Rich Boll
Comments
Having debugged the altitude window, it appears that the PMDG SDK simply takes a long time to update the value. This must be a bug that PMDG need to fix.
The LGTII issue appears to be a timing bug that had crept in, because if you move to each position slowly it works correctly. I will resolve.
I have updated GIT to fix the flaps problem and have removed the COM/NAV INC/DEC CARRY events to be none carry, so hopefully that will solve your GF166 issues. Remember to click the NAV button on the GF166 to get the updated config.
Best wishes
Steve
Do I need to re download GIT for MSFS 2020 to get the update?
I'll share the Altitude window bug with PMDG on their forum and post a trouble ticket on it.
Thanks again!
Rich
Best wishes
Steve
So, I believe that I have reason for the lag in MCPPro. This is from PMDG's B737 MSFS Introduction book. It appears the folks at PMDG added a new "realistic" feature of the simulator:
"The magenta target altitude setting on the PFD lagging:
You may notice the magenta target altitude setting on the PFD lagging
behind the MCP selected altitude. This is in fact a feature and not a bug and it does resemble the real
aircraft's behavior."
I guess in the real aircraft the altitude preselected altitude shown in the PFD lags from that shown in the MCP selected altitude. True enough, if I spin the Altitude select knob on the MCPPro, there is no lag in the altitude window on the MCP. It keeps up nicely with the MCPPro knob turns. However, the altitude window in the MCPPro does lag and it lags the same amount and speed as does the PFD altitude selected display.
Is that data that provides the altitude shown in the altitude window of the GF MCPPro the same data that is going to the PFD? If so, then that accounts for the lag. Is there any way you can get the data on altitude data from the MCP altitude window in the simulator and have that fed to the altitude window in GF MCPPro? If so, that would fix the problem.
Thanks!
Rich Boll
Best wishes
Steve
Thanks for your help!
Rich