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.
Ms2020 Experience Feedback
HI Steve,
Downloaded GIT for MSFS2020, ran installer.
After some usual hit and misses, was able to get my MCP PRO and dual 166's to work. However, I have made six test flights today and on each flight I get a CTD when using GIT after about 20 minutes of flight, almost right on schedule time wise.
Some observations and feeback.
I did see the instruction to wait until MSFS2020 was loaded and had a menu before starting GIT. However, repeated attempts with NOT loading the existing GFConfig drivers via my task bar (what I do when using P3D), the GoFlight modules always remain dark, dead. So... I loaded the GFConfig drivers as my #1 program after rebooting each attempt at doing all this (learning from experience!). That brings the modules to life.
When I load the GFConfig drivers, then MS2020 to the intial menu, then GIT and follow the directions above I get my MCP Pro and the 166's fully functional.
Two items to note from the first 20 minutes of each of the six flights before I get a CTD:
The altitude rotary only runs in 1000's, same issue as another user recently posted. Also... to engage NAV the LNAV button would not do the trick. However, after mouse clicking the NAV button in the VC, the VOR LOC button lights and the NAV function executes.
I must confess to not noting the Exception Error dialog Steve. My bad for not writing it down. I will find some time to do this agin over the next few days and keep written notes on the crashes and what ever else ufolds. I'm hopeful my efforts will help your efforts. With 10 GoFlight modules I am keen to see the bugs worked out.
Thanks for all you do. Patience is going to be required, I get it. It's promising it's being worked on. THANK YOU!
Downloaded GIT for MSFS2020, ran installer.
After some usual hit and misses, was able to get my MCP PRO and dual 166's to work. However, I have made six test flights today and on each flight I get a CTD when using GIT after about 20 minutes of flight, almost right on schedule time wise.
Some observations and feeback.
I did see the instruction to wait until MSFS2020 was loaded and had a menu before starting GIT. However, repeated attempts with NOT loading the existing GFConfig drivers via my task bar (what I do when using P3D), the GoFlight modules always remain dark, dead. So... I loaded the GFConfig drivers as my #1 program after rebooting each attempt at doing all this (learning from experience!). That brings the modules to life.
When I load the GFConfig drivers, then MS2020 to the intial menu, then GIT and follow the directions above I get my MCP Pro and the 166's fully functional.
Two items to note from the first 20 minutes of each of the six flights before I get a CTD:
The altitude rotary only runs in 1000's, same issue as another user recently posted. Also... to engage NAV the LNAV button would not do the trick. However, after mouse clicking the NAV button in the VC, the VOR LOC button lights and the NAV function executes.
I must confess to not noting the Exception Error dialog Steve. My bad for not writing it down. I will find some time to do this agin over the next few days and keep written notes on the crashes and what ever else ufolds. I'm hopeful my efforts will help your efforts. With 10 GoFlight modules I am keen to see the bugs worked out.
Thanks for all you do. Patience is going to be required, I get it. It's promising it's being worked on. THANK YOU!
Comments
The 1000's issue is an old FSX bug. There is an option in FSUIPC to fix it (Fix Control Acceleration).
The MCP is configured exactly as GoFlight configures it, so its either a bug in Simconnect or the aircraft doesn't use the standard event.
Please report the error details when you have it.
Thanks
Steve