FlightGear Newsletter October 2013: Difference between revisions

Jump to navigation Jump to search
Prepare for publishing
(→‎Boeing 747-400 instrument displays: work on the ND now also started)
(Prepare for publishing)
Line 5: Line 5:


== Development news ==
== Development news ==
Note to all contributors: please also copy your newsletter additions to the changelog for the upcoming release: [[Next Changelog]].
=== Atmospheric Light Scattering ===
=== Atmospheric Light Scattering ===
The highest quality shader effect of the Atmospheric Light Scattering rendering framework has received an upgrade in the way the ground fog layer is rendered. Up to now ground haze has been rendered up to a fixed altitude. Close to the upper layer edge, this inevitably leads to an artificially-looking sharp intersection line of fog and terrain. The new effect adds a noise distribution to the line and blurs it selectively, thus leading to a more natural appearance of partially fogged terrain from all altitudes.
The highest quality shader effect of the Atmospheric Light Scattering rendering framework has received an upgrade in the way the ground fog layer is rendered. Up to now ground haze has been rendered up to a fixed altitude. Close to the upper layer edge, this inevitably leads to an artificially-looking sharp intersection line of fog and terrain. The new effect adds a noise distribution to the line and blurs it selectively, thus leading to a more natural appearance of partially fogged terrain from all altitudes.


Line 15: Line 12:


=== FGCom ===
=== FGCom ===
FlightGear has FGCom built-in since two months now and all reported bugs has been solved.
FlightGear has the voice client [[FGCom]] built-in since two months now and all reported bugs has been solved.


The new server is now providing a simple interface showing who is connected ( http://fgcom.flightgear.org ) You can also find FGCom-sa (standalone) in the download page ( http://fgcom.flightgear.org/download )
The new server is now providing a simple interface showing who is connected at http://fgcom.flightgear.org. You can also find FGCom-sa (standalone) on [http://fgcom.flightgear.org/download the download page], or use one of these direct links:
* [http://fgcom.flightgear.org/download/fgcom-2.99.0_win.zip FGCom-sa for Windows]
* [http://fgcom.flightgear.org/download/fgcom-2.99.0_win.zip FGCom-sa for Windows]
* [http://fgcom.flightgear.org/download/fgcom-2.99.0_linux32.zip FGCom-sa for Linux 32]
* [http://fgcom.flightgear.org/download/fgcom-2.99.0_linux32.zip FGCom-sa for Linux 32]
Line 36: Line 33:
* Several rendering options that are no longer in use have been removed.
* Several rendering options that are no longer in use have been removed.
* FlightGear's built-in [[anti-aliasing]] can now be set through Advanced > Rendering.
* FlightGear's built-in [[anti-aliasing]] can now be set through Advanced > Rendering.
=== Random Buildings ===
=== Project Rembrandt ===
A number of Mac users have been reporting issues related to running [[Project Rembrandt]] (deferred rendering/shadows) on Mac OSX with ATI/AMD GPUS, we are now looking for Mac users to provide feedback on running Rembrandt on Mac OSX, required information includes errors and warnings shown during startup/runtime, but also screen shots showing any issues. Please see: [[Project Rembrandt#Mac Issues]].
=== Canvas System ===
=== High Level Architecture ===
=== Usability Improvements ===


==== opentrack ====
==== opentrack ====
Line 63: Line 49:
=== Soaring Instrumentation Toolkit ===
=== Soaring Instrumentation Toolkit ===


A new project has started for bringing improved support for soaring instrumentation to FlightGear. The soaring instrumentation toolkit is a small library written in [[Nasal]] code that allows the creation of glider specific gauges (variometers and glide computers) by connecting elementary blocks together (implemented in OOP). Although still in early stages of development, the library already supports TE (Total Energy) compensated, Netto, Relative (aka Super Netto) and Speed Command variometers. There are plans for supporting final glide computers as well. To learn more about the project, see the forum thread at [http://forum.flightgear.org/viewtopic.php?f=14&t=21020] or directly follow the progress in galvedro's fgdata/soaring-sdk branch [https://gitorious.org/fg/galvedros-fgdata].
A new project has started for bringing improved support for soaring instrumentation to FlightGear. The soaring instrumentation toolkit is a small library written in [[Nasal]] code that allows the creation of glider specific gauges (variometers and glide computers) by connecting elementary blocks together (implemented in OOP). Although still in early stages of development, the library already supports TE (Total Energy) compensated, Netto, Relative (aka Super Netto) and Speed Command variometers. There are plans for supporting final glide computers as well. To learn more about the project, see [http://forum.flightgear.org/viewtopic.php?f=14&t=21020 the forum thread] or directly follow the progress in [[https://gitorious.org/fg/galvedros-fgdata galvedro's fgdata/soaring-sdk branch].


=== A fun Adventure for Halloween ===
=== A fun Adventure for Halloween ===
This is an Experiment to explore FlightGears Capabilities beyond simulating Flight. You control a human "Walker" and explore a cursed Graveyard. Find hidden treasures and avoid being caught by evil Forces.
This is an experiment to explore FlightGear's capabilities beyond simulating flight. You control a human "walker" and explore a cursed graveyard. Find hidden treasures and avoid being caught by evil forces.


Download and instructions here:
Download and instructions at [http://cms.flightgear-de.net/index.php/scenery/91-hwspecialen the German website]
http://cms.flightgear-de.net/index.php/scenery/91-hwspecialen


[[File:Halloween2013-1.png|320px|Halloween 2013-1]]
[[File:Halloween2013-1.png|320px|Halloween 2013-1]]
Line 76: Line 61:


=== Getting involved as a programmer ===
=== 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.
Unfortunately, most of the active FlightGear 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]].
If you are interested in contributing as a core developer, please see [[Howto:Start core development]].
== Release ChangeLog ==
This section lists changes committed this month that will be available in the next release, these will be copied to the release changelog shortly before a release (for each month), so that we hopefully get a comprehensive list of new features.
== Interview with a contributor (NAME) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''
* How long have you been involved in FlightGear?
* What are your major interests in FlightGear?
* What project are you working on right now?
* What do you plan on doing in the future?
* Are you happy with the way the FlightGear project is going?
* What do you enjoy most about developing for FlightGear?
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?
More questions are being collected here: [[Interview questions]].
Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX
== Nasal for newbies ==
== New software tools and projects ==
== FlightGear addons and mods ==


== In the hangar ==
== In the hangar ==
Line 109: Line 69:
=== New aircraft ===
=== New aircraft ===
==== Piaggio Pegna Pc 7 ====
==== Piaggio Pegna Pc 7 ====
[[File:Pc-7-splash.png|thumb|Piaggio Pegna Pc 7]]
Helijah introduces a new old airplane, the Piaggio Pegan Pc 7.Designed to win the "Schneider Cup," the development of the aircraft was too complex and the time available was too short. He never flew :(
Helijah introduces a new old airplane, the Piaggio Pegan Pc 7.Designed to win the "Schneider Cup," the development of the aircraft was too complex and the time available was too short. He never flew :(


Available in [http://helijah.free.fr/ this hangar] and on Git. Obviously, improvements are welcome as always.
Available in [http://helijah.free.fr/ this hangar] and on Git. Obviously, improvements are welcome as always.


[[File:Piaggio-Pegna-Pc7-7.png|400px|Detail of the cockpit]] [[File:Pc-7.png|400px|Exterior details]]
[[File:Piaggio-Pegna-Pc7-7.png|320px|Detail of the cockpit]] [[File:Pc-7.png|320px|Exterior details]] [[File:Pc-7-splash.png|x240px|Piaggio Pegna Pc 7]]


<br style="clear:both"/>
<br style="clear:both"/>
==== Gotha G. V ====
==== Gotha G. V ====
[[File:GV-splash.png|thumb|Gotha G. V for FlightGear]]
Helijah introduces a new old airplane, the Gotha G. V. During the First World War, the Gotha G series devices were among the most effective long range airplanes. They carried the war to England from German airfields located in Belgium.
Helijah introduces a new old airplane, the Gotha G. V. During the First World War, the Gotha G series devices were among the most effective long range airplanes. They carried the war to England from German airfields located in Belgium.


Available in [http://helijah.free.fr/ this hangar] and on Git. Obviously, improvements are welcome as always.
Available in [http://helijah.free.fr/ this hangar] and on Git. Obviously, improvements are welcome as always.


[[File:G-V1.png|400px|G.V : Detail of the cockpit]] [[File:G-V2.png|400px|G.V : exterior details]]
[[File:G-V1.png|320px|G.V : Detail of the cockpit]] [[File:G-V2.png|320px|G.V : exterior details]] [[File:GV-splash.png|x240px|Gotha G. V for FlightGear]]


<br style="clear:both"/>
<br style="clear:both"/>
==== Robin DR400 Dauphin ====
==== Robin DR400 Dauphin ====
[[File:Robin DR400 Dauphin.jpg|thumb|350px|Robin DR400 Dauphin]]
A new [[Robin DR400 Dauphin]] is now available. This aircraft is a common general aviation airplane used all over the world.
A new [[Robin DR400 Dauphin]] is now available. This aircraft is a common general aviation airplane used all over the world.


Line 135: Line 91:
The aircraft is available in Git repository and at [http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf PAF team hangar]
The aircraft is available in Git repository and at [http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf PAF team hangar]


[[File:DR400_Dauphin_Rembrandt_02.jpg|400px|Cockpit of Robin DR400 Dauphin]] [[File:DR400_Dauphin_Rembrandt_10.jpg|368px|Rembrandt lights of Robin DR400 Dauphin]]
[[File:DR400_Dauphin_Rembrandt_02.jpg|320px|Cockpit of Robin DR400 Dauphin]] [[File:DR400_Dauphin_Rembrandt_10.jpg|x210px|Rembrandt lights of Robin DR400 Dauphin]] [[File:Robin DR400 Dauphin.jpg|x210px|Robin DR400 Dauphin]]


=== Updated aircraft ===
=== Updated aircraft ===
Line 151: Line 107:


The new displays are already available through Git and will be available for all with the next release in February. A note for aircraft developers: please do not copy them to your aircraft yet. The code that drives the displays will be generalized further, so it can be easily re-used on other aircraft.
The new displays are already available through Git and will be available for all with the next release in February. A note for aircraft developers: please do not copy them to your aircraft yet. The code that drives the displays will be generalized further, so it can be easily re-used on other aircraft.
=== Liveries ===


== Scenery corner ==
== Scenery corner ==
The FlightGear world scenery version 2.0 was officially released during FSWeekend. This new scenery reflects a major improvement over the existing default world scenery and has taken over five years to complete. A much higher level of detail and internal consistency characterizes this new release, in addition to the fact that it will serve as a stepping-stone for further incremental refinements. Although there are currently still a number of known issues with the scenery, the overall flying experience is significantly improved, and the team aims to provide patches for these issues in the near future. The completed build is currently transferred to the terrasync servers and will appear there early November. Once the complete build is uploaded it will also be available for download via http://www.flightgear.org .
=== World Scenery 2.0 released ===
The FlightGear world scenery version 2.0 was officially released during [[FSWeekend]]. This new scenery reflects a major improvement over the existing default world scenery and has taken over five years to complete. A much higher level of detail and internal consistency characterizes this new release, in addition to the fact that it will serve as a stepping-stone for further incremental refinements. Although there are currently still a number of known issues with the scenery, the overall flying experience is significantly improved, and the team aims to provide patches for these issues in the near future. The completed build is currently transferred to the terrasync servers and will appear there early November. Once the complete build is uploaded it will also be available for download via http://www.flightgear.org .


This FlightGear World Scenery was compiled from:
This FlightGear World Scenery was compiled from:
Line 172: Line 127:
[[File:scandinavia01.jpg|400px|Scandinavia regional textures]]
[[File:scandinavia01.jpg|400px|Scandinavia regional textures]]
[[File:scandinavia02.jpg|400px|Scandinavia regional textures (detail)]]
[[File:scandinavia02.jpg|400px|Scandinavia regional textures (detail)]]
=== Airports ===
== Aircraft of the month ==
== Airport of the month ==
== Screenshot of the month ==
== Suggested flights ==
== Aircraft reviews ==


== Wiki updates ==
== Wiki updates ==
Line 230: Line 176:
%$@&^|\`
%$@&^|\`
</syntaxhighlight>
</syntaxhighlight>


=== Translators required ===
=== Translators required ===
Line 247: Line 192:
|}
|}


== Community news ==
== Buckaroo's YASim guide updated ==
=== FlightGear on YouTube ===
 
=== New tutorials and screencasts ===
 
==== Buckaroo's YASim guide updated ====
Gary "Buckaroo" Neely have released a new version of his [http://www.buckarooshangar.com/flightgear/yasimtut.html Guide To YASim].  [[YASim]] is one of the two flight dynamic models (FDMs) that comes included with FlightGear, the other one being [[JSBSim]].  Depending on the available data either of the models can be used.  In general it is said that if aerodynamic test or simulation data is available JSBSim is the better choice and if not YASim is a better choice.
Gary "Buckaroo" Neely have released a new version of his [http://www.buckarooshangar.com/flightgear/yasimtut.html Guide To YASim].  [[YASim]] is one of the two flight dynamic models (FDMs) that comes included with FlightGear, the other one being [[JSBSim]].  Depending on the available data either of the models can be used.  In general it is said that if aerodynamic test or simulation data is available JSBSim is the better choice and if not YASim is a better choice.


Line 261: Line 201:
=== Forum news ===
=== Forum news ===
[[Image:FlightGear forum 25 October 2013.png|thumb|270px|The new board index]]
[[Image:FlightGear forum 25 October 2013.png|thumb|270px|The new board index]]
On the 25th of October, the FlightGear forum was moved to a new server. At the same time the forum software was updated to the latest version and a new style was installed. The new style is responsive, which means that scales with your screen size. More and more people view the forum on tablets or smarthphones, which should be a little easier now. For desktop users, the restyling provides a cleaner, more modern look with more room for actual content. By removing lots of ballast, the forum has also gotten a significant speed up.
On the 25th of October, the FlightGear forum was moved to a new server. At the same time the forum software was updated to the latest version and a new style was installed. The new style is responsive, which means that scales with your screen size. More and more people view the forum on tablets or smart phones, which should be a little easier now. For desktop users, the restyling provides a cleaner, more modern look with more room for actual content. By removing lots of ballast, the forum has also gotten a significant speed up.


From now on, the FlightGear forum lives on http://forum.flightgear.org Please update your favourites to point to the new url. The old links will forward you to the new forum for the time being.
From now on, the FlightGear forum lives on http://forum.flightgear.org Please update your favourites to point to the new url. The old links will forward you to the new forum for the time being.


As with all software, some issues will only show up once end-users start using it. Please post to the [http://forum.flightgear.org/viewtopic.php?f=8&t=21163 special forum topic] if you've found something that doesn't work, looks broken or is missing.
As with all software, some issues will only show up once end-users start using it. Please post to the [http://forum.flightgear.org/viewtopic.php?f=8&t=21163 special forum topic] if you've found something that doesn't work, looks broken or is missing.
=== Multiplayer ===
=== Virtual airlines ===
=== FlightGear events ===


== Useful links ==
== Useful links ==
== And finally ... ==
=== Contributing ===
=== Contributing ===
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.  
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.  
Line 282: Line 217:
=== Call for volunteers ===
=== Call for volunteers ===
* The [[Target4Today]] team is looking for volunteers to help improving FlightGear's combat support
* The [[Target4Today]] team is looking for volunteers to help improving FlightGear's combat support
=== Did you know ===


[[Category:FlightGear Newsletter|2013 10]]
[[Category:FlightGear Newsletter|2013 10]]
[[Category:Changes after 2.12]]
[[Category:Changes after 2.12]]

Navigation menu