FlightGear Newsletter November 2013

From FlightGear wiki
Jump to navigation Jump to search
Welcome to the FlightGear Newsletter!
Please help us write the next edition!
Enjoy reading the latest edition!

We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.

Available in: English, Spanish (contributed by Wallkon)

Please help us translate in other languages!

Development news

Atmospheric Light Scattering

The Atmospheric Light Scattering rendering framework adopts a technique that has recently been introduced for the default and the Rembrandt rendering framework which allows to utilize a global map of Ocean water depth. This allows to render the shallow waters around islands in a compelling way. Combined with the ability of ALS to change the basic water color based on location and weather conditions/sky appearance, many combination of shallows, mud content and weather conditions can now be addressed by the highest detail water shader effect.

Water depth mapping in ALS

Initial OsgEarth integration

Thanks to recent work by forum user poweroftwo we now have initial osgEarth integration featuring a runtime selectable option for the terrain scene in FlightGear. Once enabled, osgEarth renders the terrain scene by building the textured geometry at runtime from raw source imagery and elevation data. Load times for an unvisited location are surprisingly fast given a respectable Internet download rate. For locations previously visited, an optimized file cache data is saved for rapid loading.

Input data can come from a variety of sources including web mapping services or local source data (e.g. geotiff) stored on disk. Once rendering is enabled, the entire FlightGear terrain scene graph is replaced along as well as the scene elevation queries. However, the native terrain implementation remains fully intact and can be restored by disabling osgEarth from its configuration dialog.

The benefits gained from this initial osgEarth integration include geo-specific imagery rendered in real-time from a variety of sources that are available worldwide; tiled terrain on demand; and high altitude views from anywhere above the earth. However, this implementation with FlightGear includes some notable limitations listed in the compromises section.

Learn more at the forum topic This is a link to the FlightGear forum.

Introducing two new frameworks: NavDisplay & MapStructure

MapStructure demo
A NavDisplay-driven Canvas/GUI dialog
Independent NavDisplay instances on Hyde's 777-200ER

In a joint effort, Gijs' original Boeing 747-400 NavDisplay/Canvas code (fully scripted using Nasal; see the October newsletter) has meanwhile been sufficiently generalized to be also usable in other aircraft without having to copy/paste lots of code (typically, ~30 lines will do now).

The Boeing 777-200ER in Hyde's fgdata branch being the very first adopter for the time being, with the added bonus that the 777-200ER now also supports independent ND instances, i.e. independent displays and switches for each pilot. Hyde is also planning on implementing missing 777-specific features.

In the meantime, Philosopher and Hooray have started working on a new Nasal framework, called MapStructure, to easily create charting displays like the NavDisplay with very little specialized Nasal code being required. Once the MapStructure framework is completed, we will work towards porting our old *.layer/*.draw/*.model files to make use of the new MapStructure framework and adapt the NavDisplay framework accordingly.

MapStructure is going to be common backend for all charting needs in FlightGear, not just in instruments (i.e. MFDs like the ND), but also in GUI dialogs (Map, instructor console, ATC etc).

Currently, there are still some minor performance issues (especially on less powerful computers), which we hope to resolve by moving some parts into C++ space, hopefully in time for the 3.0 release (Our Canvas/C++ guys, TheTom and Zakalawe are looking into it).

Please get in touch if you have any questions or if you'd like to get involved in some way.

Getting started with CppBind

FlightGear's built-in Nasal scripting language comes with a set of standard libraries, and can be extended using FlightGear specific APIs.

Until FlightGear 2.8, the Nasal scripting engine only provided a C API to expose such hooks/bindings to scripting space or to expose scripting space data structures back to C/C++.

Exposing simulator internals to scripting space is a fairly common and useful thing, because it enables base package developers to access these internals without having to build FlightGear from source, so the barrier to entry is significantly lower and we've seen an increasing number of novel features purely implemented in scripting space, due to powerful APIs being available to aircraft developers and other base package developers.

Unlike the core Nasal engine itself (which is C), FlightGear however is mostly written and being developed in C++. For quite a while, that meant that the Nasal APIs were a bit low-level, and sometimes also awkward to use when making functions, data structures or objects accessible between C++ and Nasal.

Thanks to Tom's Canvas system, there's now a new bindings framework to be found in simgear/nasal/cppbind. This is fully object oriented and supports modern C++ features.

You will find that most of the "old" code in $FG_SRC/Scripting still uses those old C-APIs for interacting with the Nasal engine. Only the new code, #include'ing <simgear/nasal/cppbind>, uses boost templates to hide low level details.

Most of the code in the Nasal subsystem itself (FGNasalSys) also still uses the legacy C APIs - this is just to explain the two approaches, to avoid unnecessary confusion. You will find the old, low-level APIs explained at Howto:Extend Nasal.

The cppbind framework is much more generic and high level than the bare C APIs, cppbind includes unit testing support and makes use of modern C++ features like templates and STL support, including SimGear specific types like SGPath/SGGeod etc, its overhead is fairly small (not just performance, but also LoC to create new bindings). The cppbind framework is already extensively used by the Canvas system and the NasalPositioned_cppbind bindings, both of which are a good place to look for code examples.

Continue reading at Nasal/CppBind...

JSBSim Flight Dynamics Model Validation Effort

JSBSim (one of the flight dynamics models featured in FlightGear) is currently being validated against a set of simulations used at various NASA centers. A set of check cases is under development and is expected to be published next year. The check cases are numerous and rigorous and encompass both atmospheric and orbital scenarios. Early comparisons between JSBSim and the other simulations show very good matching for the atmospheric cases compared so far.

New Control System Component in JSBSim

A new control system component has been added recently to JSBSim. It is called the distributor component. This article is a quick introduction to the distributor component, and it includes a description on one way that it has been used. You may know that the switch component features a default value that the switch takes if none of the test conditions evaluate to true. The first test condition that evaluates to true also dictates the value that the switch takes. With the distributor component, the component does not take on a value of its own (in fact, the value of the component – which still must be named – is always zero).

The exact syntax of the distributor component is as follows:

<distributor name="name/is/irrelevant" type="exclusive|inclusive">

    [<test logic="{AND|OR}" value="{property|value}">
      {property} {conditional} {property|value}
      <test logic="{AND|OR}">
        {property} {conditional} {property|value}
    <property value="number|property"> property_name </property>

  ... <!-- Additional optional cases -->


There’s more to this, though, as this is one of the more capable, but complex, components in the set of JSBSim control system components. The distributor component features one or more <case> elements. Each <case> element may contain a <test> element (which may contain either conditional test statements, or one or more nested tests). Each <case> element will also contain one or more property statements with a value to be set. A <case> element with no tests will always be executed (have its property values set as stated). A distributor component can have a type of either exclusive or inclusive. An exclusive distributor will only execute the first <case> element that is encountered that has a test that evaluates to true. An inclusive distributor will execute all <case> elements for which the supplied test evaluates to true. In both cases, any and all <case> elements that have no tests will always be executed in the order that they are encountered. Each <case> element will have one or more property values to be set, and each <case> element does not need to feature the same set of properties to be set.

This component is very useful in cases where (for example) guidance, navigation, and control laws are defined, where - for certain modes of operation - various control system approaches and target values must be set simultaneously. The distributor component can also serve as a sort of relay, featuring a <case> element with no test, and several <property> elements. Here’s an example where one might have a set of sequential “modes” that a launch vehicle might cycle through in order during ascent:

<?xml version="1.0"?>
<!DOCTYPE system [
  <!ENTITY Off "0">
  <!ENTITY On  "1">
  <!ENTITY InitialRise  "1">
  <!ENTITY GravityTurn  "1">
  <!ENTITY EngineCutoff "2">
  <!ENTITY RateHold     "0">
<system name="Demo Rocket Guidance Executive"

  <property value="0"> executive/mode </property>
  <property value="0"> executive/clock/advance-burn-clock </property>
  <property value="1"> executive/clock/advance-met-clock </property>
  <property value="0"> guidance/pitch/rate-target-rad_sec </property>
  <property value="0"> guidance/yaw/rate-target-rad_sec </property>
  <property value="0"> guidance/roll/rate-target-rad_sec </property>

  <channel name="Executive Mode Sequencer">

    <integrator name="executive/clock/mission-elapsed-time">
      <input> executive/clock/advance-met-clock </input>
      <c1> 1 </c1>

    <integrator name="executive/clock/elapsed-burn-time">
      <input> executive/clock/advance-burn-clock </input>
      <c1> 1 </c1>
    <distributor name="executive/sequencer" type="exclusive">

          executive/clock/mission-elapsed-time gt 0.1
          executive/mode eq &Off;
        <property value="&InitialRise;"> executive/mode </property>
        <property value="&On;"> propulsion/engine[0]/throttle-cmd </property>
        <property value="&On;"> propulsion/engine[1]/throttle-cmd </property>
        <property value="&RateHold;"> control/pitch/mode </property>
        <property value="&RateHold;"> control/roll/mode </property>
        <property value="&RateHold;"> control/yaw/mode </property>
        <property value="&On"> executive/clock/advance-burn-clock </property>

          executive/clock/mission-elapsed-time ge 10
          executive/mode eq &InitialRise;
        <property value="&GravityTurn;"> executive/mode </property>
        <property value="-0.05"> guidance/pitch/rate-target-rad_sec </property>

          executive/clock/mission-elapsed-time gt 122
          executive/mode eq &GravityTurn;
        <property value="&EngineCutoff;"> executive/mode </property>
        <property value="&Off;"> propulsion/engine[0]/throttle-cmd </property>
        <property value="&Off;"> propulsion/engine[1]/throttle-cmd </property>
        <property value="&Off;"> executive/clock/advance-burn-clock </property>



As you can see, each mode occurs sequentially and causes a number of properties to be set for each case. Note also the definitions used in the various elements and attributes – these can be used to make the code more readable and comprehensible. Definitions (similar to #defines in C/C++) are declared at the top of the file using the !ENTITY construct.

FGRun repository changes

The FGRun Git repository now uses the same branch concept as FlightGear and SimGear. Current development takes place in the next branch, while release/X.X branches are created for each release. In addition to that the FGRun version number is now in sync with FlightGear/SimGear, to make it easier to see whether your FGRun and FlightGear builds match.

The Walker

The Walker is currently made portable to be easily incorporated in arbitrary aircraft. Additionally, an animatable pilot model for cockpit placement is in development. Walker and crew will be supporting different hand poses, such as pointing, a fist, thumbsup or a victory sign.

The male Walker The female Walker

A pilot model, co-pilot and crew are to come. Hand Poses that will be selectable within the animation dialog

Getting involved as a programmer

Unfortunately, most of the active FG developers are currently very overstretched in terms of the areas that they have ownership of, which is affecting how much can actually be done. Fundamentally we need more core devs.

If you are interested in contributing as a core developer, please see Howto:Start core development.

Nasal Internals for hackers: Intern'ing symbols

Contributed by Philosopher

As some of you experienced Nasal/C-code hackers should recall, or even those familiar with scripting languages internals, namespaces are just hashes, with keys representing symbols - right? Well yes, mostly, but each of those symbols are unique in a way from all of the other strings out there: they're interned. (Interning is a process that takes strings and a dictionary and returns a matching string, adding one if needed. That means equal strings are substituted so they have the same pointer, i.e. one string represents all instances of "io", stored in a pool/hash of all used symbols.) Though these interned strings appear at runtime in the keys in namespaces, they get created during code generation (codegen), where the symbols (TOK_SYMBOL) get converted to Nasal strings, are interned to get the correct string (using the globals->symbols hash), and are stored in the naCode's constants' block. From there, the symbol-strings are used to set and get various lvalues (both local/global symbols and objects' members) in an optimized way (that's the whole point of the exercise). Looking at hash.c, there are some specialized functions that make use of the potential optimizations:

  • naiHash_sym (looks up an interned symbol)
  • naiHash_newsym (adds a symbol in the first empty slot for the hashcode)

(There's another that looks similar, naiHash_tryset, but it does not deal with interned symbols: it uses the findkey() method, which in turn uses the equals() method that checks for more general key equality instead of simple pointer equality.)

The first, naiHash_sym, is pretty neat and the prime example of the optimization: it runs through a hashcode's potential slots, checking only pointer equality (note that interned symbols' hashcodes are computed during interning, so that's another step that doesn't have to be done are runtime). naiHash_newsym is another nice optimization but a little problematic, due to its assumption that the key doesn't exist already. It's basically used for adding another argument as a local key, but it doesn't care about if it exists already, it just sees an occupied slot and keeps going. Consider the following example that illustrates calling with an argument into a hash that already has the argument's key in it:

var f_creates_arg = func(arg...) {
    foreach (var k; keys(caller(0)[0]))
call(f_creates_arg, nil, nil, {arg:nil}); # call into namespace: arg=nil; with arguments of: arg=[]

This should print:


This shows that the key is being set twice (which violates a normal precondition of hashes): once as an argument and once to create an existing key in the namespace. The one set first is the one being picked up (e.g. the arg in {arg:nil} versus the arg... that equals []). And this behavior persists even through resizing: hashset() (which is used to reinitialize a hash after reallocation) only keeps appending keys in empty slots, so the number of keys doesn't change (even if there are multiple of the same keys).

For this reason, I would suggest amending naiHash_newsym to check keys' pointer equality before continuing; that way symbols aren't "trodden" over like this. (Please note that if "arg" exists in the hash as non-interned, then it will be trodden over anyways; having to look for non-interned symbols would mainly violate the point of the optimization at this step, and doesn't actually matter in the long run.) I would argue that finding an existing key (a few simple pointer comparisons!) would be more efficient generally, because the hash would never need to be resized if an existing one is found, whereas the old version would append regardless. (I think I once counted well over a hundred "arg" symbols in the __js0 namespace from the continual firing of bindings, which obviously isn't good.)

Continue reading at [1] This is a link to the FlightGear forum..

FlightGear addons and mods

New textures and lightmaps for random buildings

Lightmap terrain at noon
Lightmap terrain at night

The urban lightmap works using a modified urban shader + modified urban effect, the modified files need to be improve to make work the original urban shader when the random building function is off and enable new shader when the random building function is on.


  1. Download from here
  2. Unzip the file
  3. Copy, paste and replace
    • urban.eff at $FG_ROOT/Effects/
    • urban.frag , urban-gbuffer.frag and urban-lightfield.frag at $FG ROOT/Shaders/
    • buildings.png and buildings-lightmap at $FG ROOT/Textures/
  4. I suggest to change the random building density to the middle of your computer default settings, you can make this by edit at autosave.xml or autosave_2_12.xml (depend your version), at the line "<building-density type="double">1</building-density>"

If you want to go back to the default effects, please download this package and follow the installation instructions again.

In the hangar

Tupolev Tu-134

The "whistle" taking speed for take-off.
You can choose one of the 3 noses.

The Tupolev Tu-134 development team proudly announce a new soviet airliner for FlightGear! Some have already read a topic about it at the forum. The release of version 1.0 is available for download from here. This YAsim aircraft has a very good FDM, great exterior and a basic cockpit. To contribute (improve the cockpit for example) contact us at the forum This is a link to the FlightGear forum.

Many thanks to Helijah, Buckaroo, Cossack90.

New aircraft

Not an aircraft but a cruise ship, Oasis of the Seas has been released to the public and getting updates, it's sister ships and ferries are coming in from the ACJZA Hangar as well! If you have any skill with coding, it'll be thankful if you could help me. More information and download at the forum topic This is a link to the FlightGear forum.

Updated aircraft

Eurocopter EC130-B4 Ecostar

The EMS variant of EC130-B4, used by MedFlight, Ohio, USA
New Livery of Grand Canyon Helicopters
Closeup of EC130 Mainrotor, fully animated in all details
EC130 Helicopter using the SX-16 Nightsun searchlight
Even the pilot window can be opened now

The Eurocopter EC130 B4 helicopter is on short final for a new major upgrade. The existing model, which already had been of very high quality, has been refined in various aspects with lots of effort by mhab. The outside model has been enriched to a degree which should justify a 5* rating and the overall status of the aircraft improves to "production".

The Rotorhead has been brought to a new level of detail, a full detailed Fenestron was added and animations were introduced to all moving parts.

Cockpit was enriched for Pilot/Copilot controls, seats are textured now and a variable cabin configuration allows to set up an Emergency Medical Services (EMS) variant, which comes preconfigured with a new Livery of N130NE MedFlight (Ohio).

Fans of Grand Canyon Helicopters now find a livery of the N155GC and the colorful painting in red/gold.

A lot of equipment (most of which was there already but hidden) can now be used, including a full blown SX16-Nightsun searchlight.

All of this has been brought together in a fully integrated configuration dialog which allows to set-up livery, fuel, extra views, weights, cabin setup and equipment.

Extra gimmics include a fully animated pilot, glass reflection on windows and front shield and variable rotor wakes depending on the strength of the downwash.

If you can't wait for the next release check it out from the Git-Hangar

Some of the most interesting changes:

  • Mainrotor fully animated and adapted to original
  • Fenestron fully designed and animated, incl. control rod
  • Cockpit Controls added: Stick, Collective, Pedals, Co-Pilot Controls (optional)
  • Doors movable
  • Searchlight
  • Snowshoes
  • Hoist/Hook
  • Checklists implemented with conditional display
  • Pilot: fully animated
  • Autostart/Autoshutdown enabled after 15 flights
  • Rotor-Wakes off-low-medium-high cyclable
  • Sound improved (doors moving, low/high rotor rpm, overspeed warning, and noise inside depends on open doors/window)

Configuration Dialogs and Help Screens:

Things on stack for FG 3.0:

  • Rembrandt support
  • BUG fixing

Wiki updates

Translators required

En.gif The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multi-language then start at Help:Translate.
De.gif Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki Mehrsprachig zu machen, dann fang doch mit Help:Übersetzen an.
Nl.gif De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij Help:Vertalen.
Es.gif La FlightGear wiki todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en Help:Traducir.

And finally ...


One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: Volunteer.

To learn more about how the project works, please see this short essay This is a link to the FlightGear forum. written by Thorsten, for a more detailed article see How the FlightGear project works.

Call for volunteers

  • The Target4Today team is looking for volunteers to help improving FlightGear's combat support