Tag Archives: configuration

Added nine example XGoFlight configuration files

The next version of XGoFlight will not include example configuration files in the ZIP file itself.  Instead, all example configuration files will be posted and maintained on this web site.  This simplifies the release process and reduces clutter in the plugin directory.  So far, nine example configuration files have been posted.

  • Airbus A320neo (JARDesign)
  • Baron B58 (Laminar Research)
  • Boeing 727 (FlyJSim)
  • Boeing 737-800 (EADT x737)
  • Boeing 747-400 (Laminar Research)
  • Bombardier Challenger 300 (ddenn)
  • Bombardier CRJ-200 (JRollon)
  • Bombardier Dash 8 Q400 (FlyJSim)
  • Cessna C172SP (Laminar Research)

[View Examples]

Share and Enjoy

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

How to configure starters for the MESM in XGoFlight 3.0

The upcoming release of XGoFlight adds support for GoFlight’s Multi-Engine Start Module.  The configuration for the MESM is very similar to that of the EFIS module.  MESM functionality can be assigned using datarefs or commands, offering the flexibility needed to accommodate custom aircraft.  Below is a command-based configuration file for the default Cessna 172:

As stated, the MESM also supports datarefs.  The configuration file below is based on the Challenger 300 by ddenn:

Since the igniter switch is still a work-in-progress, I have opted to exclude it from this tutorial.  Stay tuned for much more news on the upcoming and highly anticipated XGoFlight 3.0 release!

Share and Enjoy

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

GoFlight EFIS supported in XGoFlight 2.2

As of XGoFlight 2.2, the GoFlight EFIS module is fully supported.  Like the MCPPRO, the EFIS module uses profiles configured at the code level.  Currently, there are two profiles available—default and vmax_777.  The default profile works for almost all freeware and payware aircraft.  The only outlier found was the Boeing 777 Worldliner by VMAX.  If other outliers are found, please feel free to make a feature request by posting a comment on the XGoFlight page.

This release also adds the “increment” parameter for integer datarefs to P8/RP48/WP6 events.  The behavior of the “min” and “max” parameters was also changed.  If “min” and “max” are equal, the button will no longer act as a toggle.  This allows a very specific use case, as detailed below.

Today, a user asked how to configure the fuel selector for a general aviation aircraft.  In the native Cessna 172SP, there are four settings for the fuel selector—off, left, all, right.  Prior to XGoFlight 2.2, making “min” and “max” equal prevented the button from working at all.  Now, users can configure four distinct buttons for the four fuel selector positions without any unanticipated side effects. Continue reading

Share and Enjoy

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

Auto-generate XGoFlight configuration files with our new tool

xgoflight.jsonBack in January, I announced the start of a project with the single goal of making the XGoFlight configuration process a little easier.  As stated in the announcement, the highly flexible and configurable nature of XGoFlight came at the cost of configuration simplicity.  The new tool acts as a JSON configuration generator for XGoFlight.  Best of all, it’s extremely easy to use…

  1. Add and configure all of your devices
  2. Click Export
  3. Copy and paste into xgoflight.json

I originally planned on releasing the tool at the end of January, but life and its many requirements got in the way.  In the interest of time, I left out the dataref and command configuration modes for the RP48 and T8.  You’ll have to continue adding custom dataref and command functionality manually for the time being.  Rest assured, although I can’t provide a timeline, these features will be added in the next iteration of the tool.

Currently, all supported modules can be configured using the preset actions.  Even if you don’t want to use the preset actions, the tool can generate a blank configuration file that includes all your devices.  This means it will be useful to anyone who uses my plugin, regardless of whether preset actions are used.  As always, please report any challenges so I can address them!

Start generating XGoFlight configuration files »

Share and Enjoy

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

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

How to configure the GF-SECM in XGoFlight 3.0

The upcoming release of XGoFlight will also include support for the Single Engine Control Module (GF-SECM).  The configuration for the SECM should be a little familiar to those who already have a T8 module.

Like the EFIS implementation in XGoFlight 3.0, the SECM will work without any configuration entries.  XGoFlight will automatically setup the default commands and datarefs used by native aircraft.  If you choose the custom configuration route, you must provide a configuration entry for each switch, or that switch will not be active.

Below is an example configuration file using datarefs, commands, and actions: Continue reading

Share and Enjoy

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