Tag Archives: GF-WP6

Auto-generate XGoFlight configuration files & notes on community adoption

Since its inception, XGoFlight has utilized JSON-based configuration files.  The JSON format is extremely popular on the web and can be edited in any text editor, but is rarely used as a configuration file on personal computers.  Compounding the learning curve is the complexity involved in configuring the plugin to work with specific custom aircraft.  While intermediate and expert level X-Plane users will have no problems on either end, novice users may struggle.

To alleviate any learning curve or potential confusion with XGoFlight configuration, I have begun creating an web-based application that will allow users to easily generate a configuration file without having expert knowledge of JSON or X-Plane.  Even if the user is an expert, (s)he will benefit from the interface being built.  I hope to have it released by the end of the month, so please stay tuned!

Notes on XGoFlight community adoption

Currently, there are a number of barriers to more widespread adoption of the XGoFlight plugin.  First, I only support four of the 12 GoFlight modules.  For those with only a few modules that’s probably not a big deal.  For those people who own a home cockpit filled with GoFlight modules, it poses a problem.  Right now there is a tradeoff required between the custom aircraft functionality and flexibility provided by XGoFlight, and the full range of module support provided by Sandy Barbour’s plugin.  It seems as though people primarily want support for the WP-6, GF-166, and GF-46 modules.  As I’ve said in community conversations, I fully plan to support these modules; however, support is wholly dependent upon my ability to obtain said modules.

Another barrier to more widespread adoption is cross-platform compatibility.  While I provide a 32-bit and 64-bit version of XGoFlight for Windows, I do not provide any solution for Mac or Linux users.  Currently all of my computers run on Windows 7/8 x64, so I cannot test the plugin on Linux or Mac.  If someone knows how to compile the plugin for all platforms from Windows, I’m all ears.  The other option is to have another X-Plane-GoFlight-Visual C++-Mac-Linux user compile the Linux and Mac versions for inclusion with every release.  Either option works for me.

Until next time!

Share and Enjoy

  • Facebook
  • Twitter
  • Delicious
  • LinkedIn
  • StumbleUpon
  • Add to favorites
  • Email
  • RSS

XGoFlight 2.0 adds P8, WP6 support and more

Last week, I released XGoFlight 2.0 which added support for GoFlight’s P8 and WP6 modules.  I also added additional customization, four preset actions for the pushbutton modules, continued improving logging, and fixed several bugs as detailed below.  Today, the XGoFlight Configuration Generator was updated to reflect these changes.

For the most part, the LGTII requires no customization.  The three trim wheels, gear, and flaps switch work out of the box for almost every aircraft.  The three-way switch, however, was not used and could not be customized.  With XGoFlight 2.0, the three-way switch can now be customized using commands, as exemplified below.

In previous versions of XGoFlight, when the batteries or avionics were off, the MCPPRO would build up a backlog of events (e.g. button push, rotary turn).  When the batteries or avionics were switched on, the backlog of events was carried out.  For example, if you pressed HDG SEL with batteries off, HDG SEL would be triggered when the batteries were turned on.  XGoFlight 2.0 includes a fix preventing a buildup of events with batteries and avionics off.

Prior to XGoFlight 2.0, the configuration file was loaded when the plugin started, as well as when any aircraft was loaded.  The execution order looked like this before XGoFlight 2.0.

  1. X-Plane started
  2. XGoFlight loaded
  3. XGoFlight loads default configuration file
  4. Aircraft loaded
  5. XGoFlight loads custom (if found), or falls back to default configuration file

While this was transparent and never caused any problems, it was largely unnecessary.  In XGoFlight 2.0, step three has been eliminated, which prevents the double loading of configuration files.

Lastly, XGoFlight 2.0 includes improved logging and various internal improvements.  On that note, I have another iteration of XGoFlight in the works.  So far, it will allow full customization of the RP48 rotaries and add a general aviation MCPPRO profile (similar to default Cessna 172SP).  Stay tuned for more!  As always, suggestions and comments are welcome.

Share and Enjoy

  • Facebook
  • Twitter
  • Delicious
  • LinkedIn
  • StumbleUpon
  • Add to favorites
  • Email
  • RSS