Author Archives: cstrosser

Report XGoFlight bugs

It’s been a long time since XGoFlight has been updated, and I need an accounting of all bugs or incompatibilities with the most recent version of X-Plane. So, now is your chance! While I’m happy to look at feature requests, my main focus is ensuring the plugin still works for everyone while I have some free time. Thanks!

Share and Enjoy

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

XGoFlight 3.0 Alpha 2 now available for Windows/Mac

The second development release of XGoFlight 3.0 is now available for Windows and Mac users. Notable changes in this release include:

  • MCPPRO: Boeing 757 Professional profile added (vmax_757)
  • Major revamp of configuration file format
  • Added ability to disable modules within the configuration file
  • Several bug fixes and performance improvements

The configuration file changes should be backwards-compatible with all but the EFIS module.  If you are using the old format, it will be notated in the log file.  It is also important to note that modules cannot be disabled via configuration file without using the new format. The new format replaces the “function” key inside each configuration item with a unique key.

Here’s an example of the new EFIS configuration format:

The keys are equally unique for the SECM and MESM modules.

For the T8 module, the keys (e.g. “wpt”, “arpt”) are “switch_1,” “switch_2,” all the way up to “switch_8″.  For the RP48 module, the keys are “rotary_1″ to “rotary_4″ and “button_1″ to “button_8.”  For the P8 module, the keys are “button_1″ to “button_8.”

Lastly, to disable a module, simply add a key called “disabled” and set it to true.  For example, to disable the LGT-II module, use the following configuration.

Share and Enjoy

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

X-Plane 10.30 Beta 1

There are a few key changes in X-Plane 10.30 Beta 1 that have the potential to affect the operation of the XGoFlight plugin, most notably changes to trim interpretation.  As I work on the third development release of XGoFlight, I will take this into account.  If you are using the beta release, please feel free to send any bug reports my way.  The same applies to XHatSwitch and XRemoteFMC.  Thanks!

Share and Enjoy

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

XGoFlight 3.0 Alpha 1 for Windows now available

I have posted XGoFlight 3.0 Alpha 1, which adds support for the MESM and the SECM modules.  This release also shifts from a profile-based EFIS configuration to a command and dataref based configuration, and contains several performance improvements and bug fixes.  I still have some more work to do on documentation, but below are several links that will help get you setup.

NOTE:  This is a development release.  It is not stable and requires further testing, which is why I want to get it out there.  The development release is strictly Windows-based, but rest assured, the final release will include the Mac and Linux versions.

Share and Enjoy

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

April scenery updates and hosting transition

If you haven’t noticed, I started to transition all of my scenery from X-Plane.org to Caffeinated Aviator including four new Utah backcountry airports.  The reason for this change is twofold.  First and foremost, it is much easier to maintain all of my scenery and plugins in one place.  Up until now, I have been posting updates to X-Plane.org, as well as this web site.  I will, however, still update the scenery version on the Org to keep users abreast of changes.  Second, some of the recent administrative changes, like the odd new scenery naming conventions, take autonomy away from scenery developers.  Hosting my scenery on Caffeinated Aviator will allow me to maintain that autonomy.

Fellow scenery developers are probably aware of the recent release of WorldEditor 1.2 Beta 2.  This release fixes crashes experienced when exporting airports with polygons that use bezier curves.  This release was supposed to help scenery developers get rid of the backlog of unreleased scenery, but another showstopping bug was introduced.  Any draped polygons with “Use Texture Map” checked will not show up in the airport.  For the non-scenery developers out there, draped polygons are used to paint the ground with orthophotos, taxi signs, and other airport features.  Once this bug is fixed, I will be able to finish some of the airports I have been working on (e.g. Reading Regional Airport).

Share and Enjoy

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

XGoFlight 2.3 release adds GF-46 support, fixes EFIS switch reversal

Just moments ago, I made XGoFlight 2.3 available for download.  The primary focus for this release was adding support for the GF-46 module.  I also fixed the EFIS switch reversal that several people kindly reported.  Another change, which has the potential to affect users, involved the renaming of the XGoFlight plugin directory.  The plugin directory has been renamed from Xgoflight to XGoFlight.  Lastly, I made a few internal improvements from logging to abstraction, which should make troubleshooting a little easier and save users a tiny bit of memory.

To learn how to configure the GF-46, please visit the Usage section of the plugin documentation.  Also, if you happen to come across any new bugs, please feel free to report them on the Troubleshooting page.

Share and Enjoy

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

XGoFlight 2.3.2 maintenance release available

As of this evening, another maintenance release of XGoFlight has been made available.  If you are one of the individuals having issues with the EFIS map mode knob, the XGoFlight 2.3.2 update is for you.  Based on the feedback I’ve received, I’m hoping this will fix the map mode issue once and for all.  If you don’t own the EFIS module or are not having issues, you can safely skip this release.

Share and Enjoy

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

Laminar gives Cessna 172SP some noticeable improvements

Up until X-Plane 10.21 Release Candidate 1, the native Cessna 172SP has featured a bland 3D cockpit.  While there is still significant room for improvement, Laminar Research has made some noticeable improvements to the 3D and flight models.

Before X-Plane 10.21 RC1, this was the 3D cockpit for the Cessna 172SP.

Cessna 172SP (Pre-10.21 RC1)

Cessna 172SP (Pre-10.21 RC1)

While the overall feel of the 3D pit is the same in X-Plane 10.21 RC1, there are several improvements to note.  Both the radio and instrument panels are no longer flat; now they are in 3D.  In addition, the lighting for the landing lights, taxi lights, and annunciator panel appears to have been improved.  The switches just below the yoke also got a makeover.

Lastly, there seems to be a backpack in the backseat.  It’s not mine!  I can’t remember whether this was there before 10.21 RC1.

Cessna_172SP_2

Share and Enjoy

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

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

XGoFlight 2.1 brings full customization for RP48 rotaries, array dataref support, and GA MCPPRO profile

Although it has been a mere two and a half weeks since the release of XGoFlight 2.0, I am pleased to announce the release of XGoFlight 2.1, which adds full customization for the RP48 rotaries, array dataref support, and a general aviation MCPPRO profile.

Customizing RP48 rotaries

When I started the XGoFlight project, my goal was to create the most flexible and customizable GoFlight plugin on the market.  In all versions prior to XGF 2.1, the rotaries could only be used with a limited number of preset actions.  After receiving some user feedback, I decided it was time to extend command and dataref-based customization to the RP48 rotaries.  An example JSON configuration for the rotaries is included below:

Let’s break it down…

  1. Uses preset action: spoiler
  2. Each turn to the right will increment the auto brake by one, whereas each turn to the left will decrement the auto brake by one.  The minimum auto brake level is zero, which usually signifies RTO.  The maximum auto brake level is 5, which usually signifies MAX.
  3. Each turn to the right will execute the command defined by “command_on,” whereas each turn to the left will execute the command defined by “command_off.”  In this case, turning the rotary left will turn the XPDR off, whereas turning the rotary right will turn the XPDR on.
  4. Uses preset action: engine_apu_switch

Using array datarefs

While most X-Plane datarefs contain only one integer or float value, some datarefs contain multiple integers or float values.  The datarefs that contain multiple values are called arrays.  In plugins/DataRefs.txt, those datarefs are indicated with brackets, as pictured below:

We will use the two “generator_on” datarefs for this example.  The first dataref (sim/cockpit2/electrical/generator_on) is an array of eight integers.  The following example can be used with the RP48, P8, or WP6 for any aircraft with two generators.

The number located within the brackets is called the offset.  Every array starts with a zero offset.  In this example, generator_on[0] is the first generator, and generator_on[1] is the second generator.  This pattern is relatively consistent across all X-Plane datarefs.

MCPPRO: General aviation profile

The default MCPPRO profile is geared toward jet aircraft with complex autopilot systems.  The default profile supports VNAV, autothrottle, and other functionality not seen in a common Cessna 172.  The general aviation profile provides a non-specific solution for users looking to more closely match that class of aircraft.  Below is a comparison between default and GA profiles (only differences are highlighted):

Default GA
A/T ARM NORMAL
SPEED NORMAL
LVL CHG NORMAL
VNAV NORMAL
ALT HLD ARM SYNC/HOLD
V/S NORMAL PITCH SYNC
V/S WHEEL NORMAL NOSE UP/DOWN
DISENGAGE NORMAL

To use the general aviation MCPPRO profile, add the following to your xgoflight.json configuration file.

 

Share and Enjoy

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