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.
GoFlight MCP Pro and others stop working after MSFS PMDG 737 Update
So, I got MSFS the day it was released. I never flew in there until PMDG released their 737.
Got this baby and I was so gloriously surprised that GIT eventually released an update that seamlessly connected my GoFlight MCP Pro and other modules to the PMDG 737 without me attempting to program anything (which I suck).
This worked so beautifully, and I did a flight and the joy in my heart cannot be described.
Then on June 3 PMDG released an update for the 737, but I waited and did the update on June 10. Then bam all a sudden my MCP Pro and others are not working. Changing anything on the MCP pro does not affect the sim, however changing something on the sim affects what is displayed on the MCP Pro. One can imagine my disappointment.
I followed all the instructions to enable the modules etc.
I have started the GIT and MSFS in various sequences to see if it would help but nothing. MSFS first then GIT second or GIT first and MSFS second all to no avail.
The EFIS which used to work is not working either.
Please help
I have these modules MCP Pro, EFIS, GF-TQ6 (this still works but it did before I even downloaded the new GIT), GF-46, GF-T8, GF-P8, RP48
None seems to be affect the airplane in the SIM even though they worked before the update.
Got this baby and I was so gloriously surprised that GIT eventually released an update that seamlessly connected my GoFlight MCP Pro and other modules to the PMDG 737 without me attempting to program anything (which I suck).
This worked so beautifully, and I did a flight and the joy in my heart cannot be described.
Then on June 3 PMDG released an update for the 737, but I waited and did the update on June 10. Then bam all a sudden my MCP Pro and others are not working. Changing anything on the MCP pro does not affect the sim, however changing something on the sim affects what is displayed on the MCP Pro. One can imagine my disappointment.
I followed all the instructions to enable the modules etc.
I have started the GIT and MSFS in various sequences to see if it would help but nothing. MSFS first then GIT second or GIT first and MSFS second all to no avail.
The EFIS which used to work is not working either.
Please help
I have these modules MCP Pro, EFIS, GF-TQ6 (this still works but it did before I even downloaded the new GIT), GF-46, GF-T8, GF-P8, RP48
None seems to be affect the airplane in the SIM even though they worked before the update.
Comments
I have been using the GF MCP Pro with PMDG MSFS through the last update about two weeks ago - still awaiting the next B737 update with the new 600 and a working LNAV, VNAV, and FD. I have not had any issue with using GIT. I can use MCP Pro, EFIS, GIT, and the four unit NAV/COM module without much issue. Some nit noids here and there, for example the landing gear handle in the LGT does not detect movement into the center "OFF" position.
Sometimes, you need to start the GIT and load once, then restart again for things to wake up.
Rich Boll
Much discussion over on the PMDG forum. The MSFS version is moving away from the NGXu SDK, and as it does the GIT will stop working. No word from PMDG on the SDK release.
On the one hand, I can't blame PMDG because Asobo is not finished tweaking their simulator. How can PMDG get an SDK current with Asobo changing things. I guess this is one of the things we're going to have to live with during this "open beta" period with both MSFS and PMDG?
Gents,
We have not published the SDK for the 737. It is currently in development and as such we are making some changes here to accommodate the new platform. Any product currently connecting to the 737 is doing so using an SDK for P3D, which is perfectly fine except that the SDK must necessarily change in order to grasp greater functionality for end users.
A few developers who reached out to us to ask “is this okay?” before using the old P3D SDK were informed that the connections will very likely change as we prepare the actual MSFS SDK.
Many of those developers have reached out to us after this update and we have helped them, even during the weekend, because we know how hard it is to have your software break and customers get upset.
So, while I realize it can be frustrating to have your connected software break, let us all please take a deep breath and acknowledge that those developers smart enough to reach out to us early on to ask questions knew this was coming. If a developer chooses not to reach out, there isn’t much we can do- especially given that we have been quite open about the fact that the SDK is not yet published and using the P3D one comes with risk.
Those developers who reached out were given an interim version to keep up to date, and were also told that more changes are pending and to reach out again if we break connections on them again in the next update cycle or two.
This ain’t that complicated, but it is a necessary process that we have communicated to developers who reached out to us for guidance. We cannot be responsible for developers who have not, and frankly it is baffling why they wouldn’t since we actually know what is going on and can serve as their best source of information.
I've been on holiday and only just become aware of this issue. The SDK broke with the update. I have requested access to the interim SDK that PMDG have produced and are providing to developers. Once I have it, I will do an update.
Best wishes
Steve
Expect a new GIT version ASAP.
Best wishes
Steve
Best wishes
Steve