FlightGear Newsletter March 2015

From FlightGear wiki
Revision as of 15:07, 22 March 2015 by Red Leader (talk | contribs) (links)
Jump to navigation Jump to search
This newsletter is a draft.

Please feel free to add content you think will be of interest to the FlightGear community.



Magagazine.png
Enjoy reading the latest edition!
Please help us write the coming edition!
March 2015

Project restructuring
Development news
Upcoming built-in GUI
Environment-responsive glass
Cockpit interior light and shadow
New ATC-pie release
Variant-of tag added

In the hanger
c172p-detailed project
Scenery Corner
Verona Villafranca 2D layout released
Community News
FlightGear on YouTube
FlightGear Space Program

Contributing
Translators required
FlightGear logos
Screenshots

Project restructuring

Due to two recent developments, large parts of the FlightGear project are moving. The first is the announcement that Gitorious.org will shut down in May this year (read more) and the second is that Google Code will shut down in 2016 (read more). These developments have affected the source code (SimGear and FlightGear), bug tracker, and TerraSync SVN repository are moving. In addition, just previous to these developments, fgdata was split (see below for details).

All repositories of the FlightGear project have been synchronized to SourceForge.net[1]. No more work should be pushed to Gitorious any more. Except for fgdata, all others are mirrors of the original and a new clone is not necessary. All you have to do is update the URL(s) of your remote(s) and pull as usual.

Example for SimGear with read-only access:

git remote set-url origin <protocol>git.code.sf.net/p/flightgear/<sub-project>

<protocol> can be either of git:// (read-only access) or http:// (read/write access). See http://sourceforge.net/p/flightgear/_list/git for a list of what <sub-project> should (they should also be lowercase).

Example for SimGear with read/write access:

git remote set-url origin http://git.code.sf.net/p/flightgear/simgear

Several (but not all) of the Git related articles on the wiki have been updated, including FlightGear Git: data developers.

To get re-added as a contributor to the FlightGear repositories, you will have to do the following steps[2]:

  1. Register a SourceForge.net
  2. Upload your public key.
  3. Send your SourceForge username to Curt, Clément, James, or Torsten D, stating which repo(s) you want to be re-added to.

The bug tracker has moved to http://sourceforge.net/p/flightgear/codetickets/[3]. All old issues/feature requests have been preserved. The wiki template {{Issue}} has been updated (diff).

TerraSync is yet to be moved as of March 22.

FGData split

After lots of hard work by Torsten D, a new, more compact fgdata repository (base package) has now been created. Located at http://sourceforge.net/p/flightgear/fgdata/, this new fgdata has had all aircraft (except for the C172p and UFO) stripped from it, as well as the histories of the Scenery, AI, and Models directories[2]. This has reduced its size to about 1.3 GB[4]. As almost all commit IDs have changed, you will have to get a fresh clone of this new fgdata[2]. See above for information on getting re-added as a contributor.

Note  For consistency reasons, fgdata development should now happen on the "next" branch and no longer in "master". "next" should be the default branch[5].
Note  IAHM-COL has preserved the history of all aircraft at https://github.com/FGMEMBERS[6].
Note  See FGAddon for obtaining aircraft other than the C172p and UFO.

Development news

Upcoming built-in GUI

The aircraft page of the Qt launcher for FlightGear 3.5 as rendered on Windows 7.

Development of a new GUI frontend for FlightGear has started, with the aim to replace FGRun and eventually the PLIB PUI. James Turner is currently prototyping this new launcher, based on Qt Quick, at the suggestion and encouragement of Curt, Torsten D & others[1]. There will also be the HTML5-based GUI called Phi, which is being developed by Torsten D.

The reason for the announcement is that this would overlap some areas other developers are working on. This will hopefully avoid others unnecessarily expending energy on areas that might be affected.

Note The parallel development of HTML and Qt-based UIs is happening by intention and is not the result of discoordination[2]. It is likely both will use a common service layer to provide necessary data[3].

To learn more, see Integrated Qt5 Launcher.

  1. James Turner (2015-01-20). [Flightgear-devel] Gui technologies.
  2. Torsten Dreyer (Jan 10, 2015). Re: New Canvas GUI.
  3. Torsten Dreyer (Jan 08, 2015). Re: New Canvas GUI.

Atmospheric light scattering

Two new cockpit interior effects have been added to the ALS rendering framework.

Environment-responsive glass

A new glass effect for the cockpit interior brings dynamical rendering of raindrop splashes as well as frost. In future, the effect will also include fogging and windshield wiper support with aircraft-supplied texture masks, all with a realistic interaction with the sunlight, including the enhanced visibility of dirt on glass when looking into the sun due to Mie scattering.

Frost effect Raindrop splashes

Both frost and the correct splash dynamics of the raindrops need to be modeled by the aircraft developer, as the shader cannot have get the required information. See ALS glass effect for details.

Cockpit interior light and shadow

Do you like the way shadow and light move across the panel in flight when using Rembrandt? ALS is now able to do the same and more using the new model-interior effect which utilizes a cubemap representing the cockpit layout – at hardly any framerate cost. The effect is able to draw very sharp shadows without flickering, semi-shadows, dirty or tinted glass, and even render caustics from light refracted on curved glass surfaces.

Colored glass Caustics

All that's needed from aircraft modellers is a pre-computed cube map representing the cockpit. See internal cockpit reflection and interior shading for more details.

New ATC-pie release

Announced as beta in January and released as stable early February, ATC-pie has happily served a few ATC sessions in its first month of existance. In particular, it seems to have found comfortable homes for adoption in EKCH and LFOK already. Meanwhile, progress was made on its development to reach the important milestone of general and continuous ATC coordination on Flightgear with the handover feature, released this month.

Beginning to populate the network with a new program without dividing the MP network (especially controllers) was a challenge as interesting as necessary. Collaborative work made this possible, enabling both OpenRadar and ATC-pie users to exchange strips in a transparent way, regardless of their software choice.

See also the forum announcement

Variant-of tag added

Aircraft developers can make use of a new tag in the Aircraft-set.xml file. Added to the <sim>, the <variant-of> tag states to the launcher the aircraft type that your aircraft is a variant of. For example, the BAe Sea Harrier FA2 is a variant of the BAe Sea Harrier, and the Cessna 172P - Canvas Demo is a variant of the C172P.

Syntax:

<sim>
    ...
    <variant-of>[aircraft]</variant-of>
    ...
</sim>

Example from the Boeing 777-200ER:

<variant-of>777-200</variant-of>

In the hangar

c172p-detailed project

A new, more detailed version of the C172p is currently being worked on by wlbragg, gsagostinho, thevirtualfer, ludomotico, onox and others. It brings amazing new textures, controls, switches, and systems! Below are some of the results of their work:

Some screenshots of the c172p-detailed project

Find out more at Cessna 172P detailed

Scenery Corner

Verona Villafranca 2D layout released

Elgaton has released the complete 2D layout for the Verona Villafranca Airport (LIPX). It is going to be submitted to the Airport Scenery Gateway at the end of March for inclusion into X-Plane and FlightGear. See the forum thread for download links. 3D buildings will be added in the coming months.

Community News

FlightGear on YouTube

From the SMAAF GAMEZ channel.

(en) Video of several FlightGear aircraft using FlightGear v3.4.

FlightGear Space Program

FGSP Cosmonaut Badge "The Owl"

Spacetripready.png

Now is your time to become official cosmonaut of The FlightGear Space Program. Just download the famous Space Shuttle and select any of the available missions. Report your succesfull orbit flight tracker screenie and you'll receive a custom badge of the FlightGear Space Program.

The Space Shuttle can be downloaded from the GitHub repository either in a ZIP file or by cloning.

As an add-on also you can fly our Special Cargo Transport Missions with the heavily updated An-12, An-22, and An-225.

Find out more about space flight in FlightGear at FlightGear space program

Contributing

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.

FlightGear logos

If you want some graphic elements for your FlightGear-related site (for example a hangar or YouTube channel), please feel free to visit FlightGear logos for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.

Screenshots

The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings (antialiasing, texture sharpening, etc.). More info at Howto:Make nice screenshots.