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.
TQ6 issues - GIP: Pipe Connect Failed
Win7/64, X-Plane 11.05
X-Plane 11 - Laminar Beechcraft Baron 58
Multi installation issues
Hi Steve, I have an issue with the correct operation of my TQ6 unit whereby each lever calibrates perfectly within the X-Plane Joystick settings, yet fails to function correctly when X-Plane 11 is running - each lever ‘jumps’ about erratically when moved and the power lever response is limited to a slight throttle change - so I have a conflict.
I have substituted the TQ6 quadrant with a HOTAS warthog to test the unit and the results remain the same.
During my attempts to rectify my previous LGTII rudder trim issues, I believe I may have over-written the default Beechcraft Baron 58 file and am left with my modified file (Baron 58) .. that may be part of the issue.
My startup log indicates - GIP: Pipe Connect Failed! (five occasions) early in the startup phase - this issue is addressed in the GIT X-Plane version of FAQ’s.
GIP: Pipe Connect Failed
GIT FAQ: If you have multiple installations of X-Plane, the installer can install the GIT Plugin into the wrong directory.
I have two installations of X-Plane - The first is the MASTER with a second slaved as the EXTERNAL view only.
The MASTER PC is connected by USB 2.0 to all of my GF devices and has the GIT plugin installed in the Resources/Plugins folder. The slaved installation does NOT have the GIT plugin installed .. and being the slave unit, joystick controllers are inaccessible from the settings menu.
GIT FAQ: Simply locate the GIT plugin in one of your installations under Resources/Plugins and copy and paste the GIT plugin folder to the correct X-Plane installation.
My questions are:
1) Do I need to copy and paste the GIT plugin folder to my second PC (external view) installation ?
2) Can you please provide me with a list of the correct files (a screenshot of the X-Plane folder tree would be preferred) that should be included in the GIT plugin folder (in case I am missing a file).
3) Do I leave the Goflight.config GUI default settings as is, or do I manually disable each lever ? (similar to the MCP selection requirement).
4) Can you attach a fresh copy of the default Beechcraft Baron 58 so I can import this file to the GIT to get back to square one.
All the best for the Xmas season.
Regards
Brett
X-Plane 11 - Laminar Beechcraft Baron 58
Multi installation issues
Hi Steve, I have an issue with the correct operation of my TQ6 unit whereby each lever calibrates perfectly within the X-Plane Joystick settings, yet fails to function correctly when X-Plane 11 is running - each lever ‘jumps’ about erratically when moved and the power lever response is limited to a slight throttle change - so I have a conflict.
I have substituted the TQ6 quadrant with a HOTAS warthog to test the unit and the results remain the same.
During my attempts to rectify my previous LGTII rudder trim issues, I believe I may have over-written the default Beechcraft Baron 58 file and am left with my modified file (Baron 58) .. that may be part of the issue.
My startup log indicates - GIP: Pipe Connect Failed! (five occasions) early in the startup phase - this issue is addressed in the GIT X-Plane version of FAQ’s.
GIP: Pipe Connect Failed
GIT FAQ: If you have multiple installations of X-Plane, the installer can install the GIT Plugin into the wrong directory.
I have two installations of X-Plane - The first is the MASTER with a second slaved as the EXTERNAL view only.
The MASTER PC is connected by USB 2.0 to all of my GF devices and has the GIT plugin installed in the Resources/Plugins folder. The slaved installation does NOT have the GIT plugin installed .. and being the slave unit, joystick controllers are inaccessible from the settings menu.
GIT FAQ: Simply locate the GIT plugin in one of your installations under Resources/Plugins and copy and paste the GIT plugin folder to the correct X-Plane installation.
My questions are:
1) Do I need to copy and paste the GIT plugin folder to my second PC (external view) installation ?
2) Can you please provide me with a list of the correct files (a screenshot of the X-Plane folder tree would be preferred) that should be included in the GIT plugin folder (in case I am missing a file).
3) Do I leave the Goflight.config GUI default settings as is, or do I manually disable each lever ? (similar to the MCP selection requirement).
4) Can you attach a fresh copy of the default Beechcraft Baron 58 so I can import this file to the GIT to get back to square one.
All the best for the Xmas season.
Regards
Brett
Comments
GIT for X-Plane has no axes support so will not be interfering with X-Plane in any way.
So long as the "GIP: Pipe Connect Failed" messages stop once X-Plane is running then the plugin is installed correctly.
Best wishes
Steve
2) Can you please provide me with a list of the correct files (a screenshot of the X-Plane folder tree would be preferred) that should be included in the GIT plugin folder (in case I am missing a file).
4) Can you attach a fresh copy of the default Beechcraft Baron 58 so I can import this file to the GIT to get back to square one.
I don't have a copy of the Beech Baron config. Does it not work with FS Default button pressed on the MCP PRO?
Best wishes
Steve
WRT the TQ6 - I deleted the output/preferences folder, forced an update of X-Plane 11 and the TQ6 throttle axis returned to fully operational - the bug was with an Alabeo aircraft and nothing to do with GIT.
Thx Brett