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.
Comments
A brief history:
iFly 747 (original release) support was built into the GoFlight drivers. You had to use GFConfig and the GoFlight Data Bridge to run it. Last time I checked, iFly released a service pack for their plane and broke the SDK and thus GoFlight driver support. GoFlight never fixed support for the service pack version.
The 747 requires specific SDK support which GIT is not programmed to provide. There are no Bespoke Events available to download.
Thus, as far as I know, there is no support for GoFlight hardware and the 747. If you know LUA you might be able to use FSUPIC and write something yourself.
Best wishes
Steve
Steve,
Thanks for the detailed explanation and quick response. Anecdotally, I need more testing to confirm this, I get a much quicker OOM when running the GF config software. The GFIT does not seem to either use up as much or cause a memory leak. Hence my interest in using it on the iFly 747. I have some crude workarounds, but I may play with a LUA myself. If I do I'll post it. What we really need is some industry standards for everyone. It would make things so much easier for the developers. We both know the chance that has of happening!!