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.
MSFS2020 - GIT Stopped Loading FBW A32NX for MCPPro
I have been running the GIT using the FlyByWire A320 successfully in the MCPPro and EFIS for many months now with no issues.
However, after recently starting GIT, no aircraft information is seen in the Aircraft section of the status page, where is typically shows FBW A320 loaded. It just says None, and while the green light below is blinking, no tabs or buttons work in the GIT.
I recently updated FSUIPC7 to 7.2.8, and have not been able to power up the MCPPro with any lights or knob functionality.
Attached is a snapshot of the GIT, and a copy of my log file. It appears the log file stops at the same point each time.
Any assistance or guidance is greatly appreciated.
Steve G.
However, after recently starting GIT, no aircraft information is seen in the Aircraft section of the status page, where is typically shows FBW A320 loaded. It just says None, and while the green light below is blinking, no tabs or buttons work in the GIT.
I recently updated FSUIPC7 to 7.2.8, and have not been able to power up the MCPPro with any lights or knob functionality.
Attached is a snapshot of the GIT, and a copy of my log file. It appears the log file stops at the same point each time.
Any assistance or guidance is greatly appreciated.
Steve G.
Comments
I have:
1. Removed and reinstalled GIT from my account
2. Removed and re-added the WASM module to the Community folder
3. Tried moving the MCPPro USB to another port location, although it had been running without any issues in the original location.
Not understanding why the log shows the load stops at specific LVAR's each time.
Steve, any thoughts or suggestions would be greatly appreciated.
The FBW A320 development version will not operate, however, and still appears to halt during the load of LVARS in the same exact line every time. And like before, the buttons and tabs in the GIT interface will not operate.
Can you post the Log.
Best wishes
Steve
Yes, the log is attached above in my first post. The initialization appears to stop at the same LVAR/line every time.
What's odd is that I see LVARs in the log for other aircraft as well as the A32NX, such as the Aerosoft CRJ, DA62, 747-8, etc.
My KnownLvars is VERY long, over 14000 lines.
Much appreciation for your help.
Steve G.
I've been using GIT with the A320NX for months and its been solid, no issues.
It would be interesting to see what happens if you remove all the late lvars for this aircraft in KnownLvars. Start GIT with this aircraft in VC mode, wait a minute, quit GIT so that KnownLvars is updated and then start GIT again and see if the problem remains.
Best wishes
Steve
OK, thanks.
But get this: after update to MSFS 2020 and installing World Update IV, the GIT and MCPro appear to be working. I am baffled by this, but happy nonetheless...!
Attached is the log file AFTER the update. Look toward the bottom where it loaded all LVARs and then created the Bespoke Vars. It continued passed that last LVAR and completed initialization.
11:47:57 Late Lvar Detected: XMLVAR_Cabin_Heat_2_Position
11:47:57 Creating Bespoke Vars
Bizarre...
I'm going to keep testing to ensure this occurs every time GIT is loaded.
Thanks,
Steve G.
Following Steve's advice, I began to remove LVARs associated with the A30NX in the KnowLvars XML file. I soon realized its an impossible task since (1) it is 14000 lines long, and (2) there are LVARs that are difficult to tell whether they are associated with the A320NX. So I stopped and went to the extreme, deleting the KnownLvar.xml file and let it rebuild itself by loading up the A320NX in the sim. It seems to have reset itself and now I'm able to get GIT to initialize complete each time. I will continue to test this evening and advise on my results.
Thanks for all assistance....
Steve G.
Best wishes
Steve
Best wishes
Steve
Much appreciation for your help and support....
Steve G.
Just letting you know that all is working well after the most recent update to GIT and the WASM module. I have tested with a few flights using the FBW A32NX, on the EFIS and MCPPro. I will continue to test with other aircraft as well and advise of any issues.
Thanks again for your wonderful support....
Steve G.