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-LGT2 X-Plane 11: Rudder and aileron trim
Win7/64, X-Plane 11.05, GIT (X-Plane version 2.04)
* GF-Pro Yoke - functions okay,
* GF-TQ6 - functions okay,
* GF-LGT2 with all functions operating, except for rudder & aileron trim (elevator trim ok).
1) Standard X-Plane 11 Laminar Beechcraft Baron B58,
2) Internal rudder & aileron trim wheels appear to initiate a slight movement in first rotated direction when each of the two LGT2 trim wheels operated, however they have no effect on any of the external control surfaces.
3) GIT X-Plane LGT tab selected with:
Device 0, ENABLED, 8.
ROTARY_RUDDERTRIM Input Event set to: CLOCKWISE, rudder_trim_right: Input Action: ROTATE
ROTARY_RUDDERTRIM Input Event set to: ANTICLOCKWISE, rudder_trim_left: Input Action: ROTATE
4) Reboot, with no change to trim controls.
5) Attempted an Input reset to: Default FS - no change to LGT2 issues (rudder/aileron trim plus Saitek pedals are now unserviceable).
6) Saitek rudder pedals now fail to function, although they do identify and calibrate under standard X-Plane Joystick settings (and still remain fully functional under P3D).
7) GIT uninstalled, Goflight files in Documents deleted and XP_11 plugin deleted.
8) XPGF_config plugin deleted.
CURRENT CONFIG (under XP_11 - no GF plugins)
* GF-LGT2 no longer identified,
* GF-TQ6 identifies and calibrates, but fails to function,
* GF_Pro Yoke identifies, calibrates and remains functional,
* Saitek rudder pedals identified, calibrated but no longer function (under any XP_11 aircraft).
* Saitek rudder functions rechecked to be normal ops under P3D.
I wouldn't expect the LGT2 to function under XP_11 as it is unidentified without the plugin, however the TQ6 should function.
I can't work out how to re-establish the Saitek rudder pedals under XP_11 without a full re-install.
Rob Ainscough's Youtube tutorials for GIT P3D appear helpful, but not so much for GIT X-Plane version.
There may be a full GIT XP_11 tutorial within the Pollypot site, but so far I'm only able to locate a brief summary with little detail.
Any advice appreciated.
* GF-Pro Yoke - functions okay,
* GF-TQ6 - functions okay,
* GF-LGT2 with all functions operating, except for rudder & aileron trim (elevator trim ok).
1) Standard X-Plane 11 Laminar Beechcraft Baron B58,
2) Internal rudder & aileron trim wheels appear to initiate a slight movement in first rotated direction when each of the two LGT2 trim wheels operated, however they have no effect on any of the external control surfaces.
3) GIT X-Plane LGT tab selected with:
Device 0, ENABLED, 8.
ROTARY_RUDDERTRIM Input Event set to: CLOCKWISE, rudder_trim_right: Input Action: ROTATE
ROTARY_RUDDERTRIM Input Event set to: ANTICLOCKWISE, rudder_trim_left: Input Action: ROTATE
4) Reboot, with no change to trim controls.
5) Attempted an Input reset to: Default FS - no change to LGT2 issues (rudder/aileron trim plus Saitek pedals are now unserviceable).
6) Saitek rudder pedals now fail to function, although they do identify and calibrate under standard X-Plane Joystick settings (and still remain fully functional under P3D).
7) GIT uninstalled, Goflight files in Documents deleted and XP_11 plugin deleted.
8) XPGF_config plugin deleted.
CURRENT CONFIG (under XP_11 - no GF plugins)
* GF-LGT2 no longer identified,
* GF-TQ6 identifies and calibrates, but fails to function,
* GF_Pro Yoke identifies, calibrates and remains functional,
* Saitek rudder pedals identified, calibrated but no longer function (under any XP_11 aircraft).
* Saitek rudder functions rechecked to be normal ops under P3D.
I wouldn't expect the LGT2 to function under XP_11 as it is unidentified without the plugin, however the TQ6 should function.
I can't work out how to re-establish the Saitek rudder pedals under XP_11 without a full re-install.
Rob Ainscough's Youtube tutorials for GIT P3D appear helpful, but not so much for GIT X-Plane version.
There may be a full GIT XP_11 tutorial within the Pollypot site, but so far I'm only able to locate a brief summary with little detail.
Any advice appreciated.
Comments
This is what is so frustrating about X-Plane. You would expect standard Commands to work with their default aircraft and they sometimes don't.
Having used Detective, I can see its wired up to the standard Datarefs only and it ignores the Commands. So you need to create two Bespoke Events for each function; one that increments the relevant Dataref and one the decrements the relevant Dataref.
E.g. For the A/L TRIM, create a Bespoke Event called BE_AL_TRIM_Right. Then add the Task "Set+" against the Dataref sim/cockpit2/controls/aileron_trim with a value of 0.01. Create another Bespoke Event for trimming to the left with the Task "Set-" using the same Dataref and value. Assign these to your LGT2 aileron rotary.
Do the same for the rudder, using the Dataref sim/cockpit2/controls/rudder_trim.
Best wishes
Steve
I have reinstalled XP11 - this returned my rudder to full operation.
GIT INSTALLATION
I re-installed XP11 GIT confirming that it resides in the same folder as GPConfig.exe (as per the P3D installation guide) .. following the User Guide>Goflight Interface Tool X-Plane>Installation there appears to be no specific reference to the prefered XP11 location.
GF_Config.exe (V2.26.1)
I have yet been able to locate a specific X-Plane 11 GF-Config version, the only GF-Config.exe file I can locate is for P3D. The GF-Config GUI also indicates Prepar3D on the GUI LGT2 tab.
In my case: AILERON TRIM Control and RUDDER TRIM Control have both been set to (No Selection) .. (ELEVATOR TRIM Control remains selected to ELEVATOR TRIM)
The XP11 DataRef Editor Plugin does not appear to be installed .. although I haven’t been able to confirm it’s probable location - I expect this may be located in the SDK which is not included in my X-Plane 11.
User key registration occurred only on the first occasion, however after uninstall and re-install of XP11 GIT there was no further requirement to enter the User key - I’m assuming that GIT identifies the specific PC and retains full functionality after a second install.
Both the TQ6 and GF Yoke function under the standard XP11 Joystick interface.
GF-LGT2
GoFlight Interface Tool X-Plane Guide
CONCEPTS
Std DataRefs & Commands - no worries, I get that.
Custom DataRefs & Commands - I am unsure of the correct method to search and for DataRefs under the Detective as the XP11 GUI differs from the one used by Rob A. in his Youtube tutorial. I anticipate his tutorial is based on either a GIT P3D version, or a previous version of GIT (I don’t really know) as a number of the Detective panel buttons appear to have been changed. Immediately apparent, are the buttons on the lower right (pink) Events panel where:
EVENTS - MSE CLKS - DETECTED - HIDDEN - SEARCHED
have been replaced with:
STANDARD - CUSTOM - SEARCHED - (now also without a Hide icon available to the right)
Bespoke Events & Variables - As per your advise above, I added the Bespoke events to both the AILERON_TRIM and the RUDDER_TRIM.
Set+ and Set- buttons
I assume that the (Set-) button does not automatically apply a negative value to the field
(i.e. you still are required to enter a decrement prefixed by a minus value -0.01). These values were applied to the ANTICLOCKWISE Input Events (LEFT) for each of the RUDDER and AILERON trim events with an Input Action ROTATE.
Movement of the AILERON trim wheel now applies LEFT aileron trim only (to the full value), no matter whether the trim wheel is rotated in either a Clockwise or Anticlockwise direction.
Movement of the RUDDER trim wheel now applies RIGHT rudder trim only (to the full value), no matter whether the trim wheel is rotated in either a Clockwise or Anticlockwise direction.
I anticipate you would advise that I had applied a positive value to the Set- field in error .. but I have checked, rechecked and rebuilt these Bespoke events so many times now without a change to the pattern that I have exhausted all the variables that I can think of. One thing I am not entirely clear on with the Bespoke event creation is if the events are automatically 'saved' each time they are edited as there is no specific 'save' function.
Strange results
The XP11 plugin dropdown list does not indicate a Goflight plugin, however under Plugin>enable/disable the GIT plugin is checked and win.xpl file is located in the XP11>Resources>Plugins>GIT Plugin>64 folder.
The GF_LGT2 will not function at all unless the GIT has been loaded prior to XP11 starting - if during the operation of XP11 the GIT is closed, the LGT2 does not function.
Each time the GIT is loaded the LGT 'Device 0' selection has to be imported from the Documents>GIT folder and re-seleced to 'ENABLED' on the LGT tab
I apologise for not fully understanding X-Plane 11, as I've only just recently moved over from P3D .. but I'm on my third full day attempting to correct a simple rudder and aileron trim issue that should have taken 10 minutes to resolve and get on my merry way. I don't think I have enough years left in me to tackle the GF-MCP.
Obviously I've missed something ..
Thanks - Brett
So long as the plugin is listed and enabled, everything is OK.
A device can look disabled when you first click the tab - it is however enabled. Once you select the device number, the fields are populated and the correct device state is shown.
I will check the LGT not functioning issue and come back to you. GIT needs to be running for any of the GoFlight devices to work.
** Update **
I have checked the LGT and it works regardless of the loading order. I think something must be wrong with your config or Bespoke Events. Attach the exported files to this thread and I will take a look.
Best wishes
Steve
Thanks for the tips, when I can get some free time I'll give that a go.
So long as the plugin is listed and enabled, everything is OK.
As I mentioned, under XP11 the plugin drop down does not actually list Goflight so there may be an installation error that requires a fix my end - I'll re download your latest version and give it another try, when I get some free time.
A device can look disabled when you first click the tab
That may be part of my problem.
I may need to spend time to work out the correct steps to follow when using the latest version of Detective, as it differs significantly from the Rob A. Youtube tutorial Part 1, so for the moment it's trial and error until eventually I happen to get it right.
The LGT2 unit is a number of years old now .. and I stumbled over this info just the other day. This may be the cause of my troubles.
Could there be a way to manage this by applying opposite values within GIT ?
Brett
What are the current issues you are experiencing as my last message to you was to attach your Bespoke Events so I could check they were correct.
Thx
Steve
I am mid way thru a hardware rebuild, so I'll follow up when I'm back up and running as time allows.
Brett
I have replaced the GF-LGTII with a new unit and the GIT default trim settings now function correctly.
Thx Brett