In order to effectively configure the XGoFlight plugin, a basic knowledge of datarefs and commands is required.  The default datarefs and commands generated by X-Plane can be found in a text file located within the plugins directory (e.g. Commands.txt, Datarefs.txt).  In addition, simmers can use the XGoFlight Configuration Generator to get started; however, dataref and command-driven events will still need to be configured using a basic text editor.

Aircraft-Specific Configuration

XGoFlight supports aircraft-specific configuration files.  Whenever an aircraft is loaded, XGoFlight searches the aircraft folder for a file called xgoflight.json.  If found, the aircraft-specific file will override the default configuration file in its entirety.  For example, the path to the aircraft-specific configuration file for the native Cessna 172SP would look like this:

X-Plane 10/Aircraft/General Aviation/Cessna 172SP/xgoflight.json


GoFlight 46

The 46 module is be configured using a series of “functions.” Each function defines the operation of the LCD screens and rotary knob. The white pushbutton is used to cycle through the various functions.

Function Rotary Rotary (pushed)
adf1 +/- 1 digit Digit selector
adf2 +/- 1 digit Digit selector
com1 Least significant digits Most significant digits
com2 Least significant digits Most significant digits
nav1 Least significant digits Most significant digits
nav2 Least significant digits Most significant digits
obs1 +/- 1 degree +/- 6 degrees
obs2 +/- 1 degree +/- 6 degrees
xpdr +/- 1 digit Digit selector
ap_alt +/- 100 ft. +/- 1,000 ft.
ap_hdg +/- 1 degree +/- 6 degrees
ap_ias +/- 1 knot or 0.01 Mach +/- 6 knots or 0.06 Mach
ap_vs +/- 100 ft. +/- 1,000 ft.
barometer +/- via command +/- via command

The following example might be useful for general aviation aircraft.

GoFlight EFIS

As of XGoFlight 3.0, the EFIS module can be fully customized by the user.  While the EFIS module will still work out-of-the-box for aircraft using standard datarefs and commands, the equivalent configuration file would look something like this:

In releases prior to XGoFlight 3.0, the EFIS module used profiles instead of explicit datarefs and commands.  Currently, two profiles are available.

Aircraft Profile
Default default
Boeing 777 Worldliner (VMAX) vmax_777

To configure the EFIS module, insert the “EFIS” line into your configuration file.  If no profile is indicated, the default profile will be loaded.

If certain functions of the EFIS module are not working properly, you may need to add the version parameter to your configuration file. The version parameter defaults to “1”, and in most cases, is not be required.

GoFlight LGTII

The configuration for the GoFlight LGTII is quite easy.  The trim, gear, and flaps are require no additional configuration.  The three-way switch can be customized using commands.  The following LGTII configuration can be used with the Cessna 172SP included with X-Plane 10.


Instead of using commands and datarefs, the MCPPRO configuration uses profiles.  A profile is configured at the code level meaning no additional work is required on the part of the user.  Currently, seven profiles are available.

Aircraft Profile
Default default
Bombardier Challenger 300 (ddenn) cl30
Bombardier CRJ-200 (JRollon) crj2
General Aviation ga
Airbus A320neo (JARDesign) jar_a320
Boeing 777 Worldliner (VMAX) vmax_777
Boeing 737 (EADT) x737

To configure the MCPPRO, insert the “MCPPRO” line into your configuration file.  If no profile is indicated, the default profile will be loaded.

GoFlight P8/RP48

The GoFlight P8 and RP48 are configured in roughly the same manner.  The main difference between the P8 and RP48 is that the RP48 has four rotaries.  Like the T8, the P8 and RP48 can be configured in three ways—actions, commands, or datarefs.  See the Examples section for more details.

GoFlight T8

There are three ways to configure the T8 module—with preset actions, commands, or datarefs.  To configure the fifth switch with an action, add the following entry to the appropriate T8 module.

To configure the same switch using commands:

Lastly, if you want to configure that switch with datarefs, insert the following:

To see the various use cases in context, see the Examples section.

GoFlight WP6

The GoFlight WP6 shares its actions with the GoFlight P8 and RP48; however, in most cases, the user will need to use dataref-based configuration.  The dataref configuration matches that of the P8/RP48 with the exception of two attributes—blink and color.  When blink is set to “1”, the LED will blink when the specified dataref is greater than zero.  The available colors are as follows:

  • black
  • white
  • red
  • green
  • blue
  • magenta
  • yellow
  • cyan

Below is an example configuration for the WP6, where the first block is a red master warning, the second is a yellow master caution, the third is a red stall warning, the fourth is not set, and the fifth and sixth blocks are red fire indicators.


Share and Enjoy

  • Facebook
  • Twitter
  • Delicious
  • LinkedIn
  • StumbleUpon
  • Add to favorites
  • Email
  • RSS
  • Pingback: XGoFlight 2.3 release adds GF-46 support, fixes EFIS switch reversal | Caffeinated Aviator()

  • 9SL9

    Any chance of adding Barometer to the GF-46?

    • rescuetruth

      Yeah – I’ll add that next release. =)

  • Pingback: How to configure the EFIS module in XGoFlight 3.0 | Caffeinated Aviator()

  • Demian

    The example given for a GF46 doesn’t work to me, I copied exactly the same in my .json and the panel remains black. What am I doing wrong? Thanks

  • Giovanni

    Hi any configuration for B757 ramsess?

  • Trevg

    Has work on this plugin stopped now ??

    • rescuetruth

      Hi Trevg, Plugin development is ongoing, but I’ve had much less time to do consistent releases. I don’t have a timeline at this time. If you have suggestions on what you’d like to see, please feel free to post them!

  • Trevg

    Hi Chris,
    Nice to hear you are still about.
    I have upgraded my computer systems running Nvidia 980 and CPU i7 4790k.
    Still on Win7. I think my system maybe too fast for your programme now, when loading.
    Been working well for over a year but now CTD when XP starts.
    xpl error on start and in the log, it shows crashes due to your programme.

    Seems to initalise and start to recognise, then crashes out.

    Have reloaded from original zips and tried with the old 2.3.2 version with same results.

    Possible due to not having enough time on start up ??