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.
GF Module tabs not bold and unclickable
Hi Steve,
Thank you for your efforts with this module. My problem is as follows.
With the interface (Latest version as of today), If I load any aircraft other than the 737NGX, all of the module tabs are grey and unclickable.
If I load the NGX, my GF modules are recognised and fully customisable as designed.
I have thoroughly read the manual and checked that all is as it should be. I have attempted to upload the event log. If I need to do it again, please advise the best way to do this.
Cheers Marty.
Thank you for your efforts with this module. My problem is as follows.
With the interface (Latest version as of today), If I load any aircraft other than the 737NGX, all of the module tabs are grey and unclickable.
If I load the NGX, my GF modules are recognised and fully customisable as designed.
I have thoroughly read the manual and checked that all is as it should be. I have attempted to upload the event log. If I need to do it again, please advise the best way to do this.
Cheers Marty.
Comments
Hi Marty,
The tabs only enable when the Interface recieves a sim running event. Normally this occurs during loading a flight or when the VC/2D cockpit is visible.
This was added in the last few releases because not all lvars are available until the sim is in a running state and so configuration was not consistent and error prone.
Best wishes
Steve