FlightGear Newsletter March 2015: Difference between revisions

Jump to navigation Jump to search
More cleanup
No edit summary
(More cleanup)
Line 11: Line 11:
[[#Environment-responsive glass|Environment-responsive glass]]<br/>
[[#Environment-responsive glass|Environment-responsive glass]]<br/>
[[#Cockpit interior light and shadow|Cockpit interior light and shadow]]<br/>
[[#Cockpit interior light and shadow|Cockpit interior light and shadow]]<br/>
[[#New ATC-pie release and OpenRadar interoperability|New ATC-pie release and OpenRadar interoperability]]<br/>
[[#New ATC-pie release|New ATC-pie release]]<br/>
[[#Variant-of tag added|Variant-of tag added]]<br/>
[[#Variant-of tag added|Variant-of tag added]]<br/>
  | valign="top" width="33%" |
  | valign="top" width="33%" |
{{Newsletter-cover-header|In the hanger}}<br/>
{{Newsletter-cover-header|In the hanger}}<br/>
[[#C172P-detailed project|C172P-detailed project]]<br/>
[[#c172p-detailed project|c172p-detailed project]]<br/>
{{Newsletter-cover-header|Scenery Corner}}<br/>
{{Newsletter-cover-header|Scenery Corner}}<br/>
[[#Verona Villafranca 2D layout released|Verona Villafranca 2D layout released]]<br/>
{{Newsletter-cover-header|Community News}}<br/>
{{Newsletter-cover-header|Community News}}<br/>
[[#FlightGear Space Program|FlightGear Space Program]]<br/>
[[#FlightGear Space Program|FlightGear Space Program]]<br/>
Line 29: Line 30:
Due to two recent developments, large parts of the FlightGear project are going to be moving.  The first is the announcement that Gitorious.org will shut down in May this year ([https://about.gitlab.com/2015/03/03/gitlab-acquires-gitorious/ read more]) and that Google Code will shut down in 2016 ([http://google-opensource.blogspot.co.uk/2015/03/farewell-to-google-code.html read more]).  This means that all the source code (SimGear and FlightGear), the bug tracker, and [[TerraSync]]{{clarify}} are moving.  In addition, just previous to these developments, [[fgdata]] was split, see [[#fgdata split|below]] for details.
Due to two recent developments, large parts of the FlightGear project are going to be moving.  The first is the announcement that Gitorious.org will shut down in May this year ([https://about.gitlab.com/2015/03/03/gitlab-acquires-gitorious/ read more]) and that Google Code will shut down in 2016 ([http://google-opensource.blogspot.co.uk/2015/03/farewell-to-google-code.html read more]).  This means that all the source code (SimGear and FlightGear), the bug tracker, and [[TerraSync]]{{clarify}} are moving.  In addition, just previous to these developments, [[fgdata]] was split, see [[#fgdata split|below]] for details.


All repositories of the FlightGear project have been synchronized to [http://sourceforge.net/p/flightgear/_list/git SourceForge.net]<ref>{{cite web|url=http://sourceforge.net/p/flightgear/mailman/message/33588398/|title=<nowiki>[Flightgear-devel] [MasterCaution] (ding!) FlightGear is now at SourceForge</nowiki>|author=Torsten Dreyer|date=2015-03-12}}</ref>.  '''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.
All repositories of the FlightGear project have been synchronized to [http://sourceforge.net/p/flightgear/_list/git SourceForge.net]<ref>{{cite web
|url   = http://sourceforge.net/p/flightgear/mailman/message/33588398/
|title = <nowiki>[Flightgear-devel] [MasterCaution] (ding!) FlightGear is now at SourceForge</nowiki>
|author = Torsten Dreyer
|authorlink-wiki = User:T3r
|date   = 2015-03-12
}}</ref>.  '''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:
Example for SimGear with read-only access:
Line 49: Line 56:
|title  = <nowiki>[Flightgear-devel] Bugtracker moving to sourceforge</nowiki>
|title  = <nowiki>[Flightgear-devel] Bugtracker moving to sourceforge</nowiki>
|author = Torsten Dreyer
|author = Torsten Dreyer
|date  = 2015-03-16}}</ref>. All old issues/feature requests have been preserved.  The wiki template {{tl|Issue}} has been updated ([http://wiki.flightgear.org/index.php?title=Template:Issue&diff=82555&oldid=72743 diff]).
|date  = 2015-03-16
}}</ref>. All old issues/feature requests have been preserved.  The wiki template {{tl|Issue}} has been updated ([http://wiki.flightgear.org/index.php?title=Template:Issue&diff=82555&oldid=72743 diff]).


TerraSync is yet to be moved as of March 18.
TerraSync is yet to be moved as of March 18.
Several (but not all) of the [[:Category:Git|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<ref name="a">{{cite web
|url    = http://sourceforge.net/p/flightgear/mailman/message/33562106/
|title  = <nowiki>[Flightgear-devel] FGData - The Next Generation is ready.</nowiki>
|author = Torsten Dreyer
|date  = 2015-03-07
}}</ref>:
# [https://sourceforge.net/user/registration Register] a SourceForge.net
# Upload your public key.
# Send your SourceForge username to Curt, Clément, James, or Torsten D, stating which repo(s) you want to be re-added to.


=== FGData split ===
=== 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<ref name="multiple">{{cite web
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<ref name="a">{{cite web
|url    = http://sourceforge.net/p/flightgear/mailman/message/33562106/
|url    = http://sourceforge.net/p/flightgear/mailman/message/33562106/
|title  = <nowiki>[Flightgear-devel] FGData - The Next Generation is ready.</nowiki>
|title  = <nowiki>[Flightgear-devel] FGData - The Next Generation is ready.</nowiki>
Line 63: Line 83:
|title  = <nowiki>Re: [Flightgear-devel] FGData - The Next Generation is ready.</nowiki>
|title  = <nowiki>Re: [Flightgear-devel] FGData - The Next Generation is ready.</nowiki>
|author = Anders Gidenstam
|author = Anders Gidenstam
|authorlink-wiki = User:AndersG
|date  = 2015-03-07
|date  = 2015-03-07
}}</ref>.  As almost all commit IDs have changed, you will have to get a fresh clone of this new fgdata<ref name="multiple">{{cite web
}}</ref>.  As almost all commit IDs have changed, you will have to get a fresh clone of this new fgdata<ref name="a">{{cite web
|url    = http://sourceforge.net/p/flightgear/mailman/message/33562106/
|title  = <nowiki>[Flightgear-devel] FGData - The Next Generation is ready.</nowiki>
|author = Torsten Dreyer
|date  = 2015-03-07
}}</ref>.
 
To get re-added you will have to do the following steps<ref name="multiple">{{cite web
|url    = http://sourceforge.net/p/flightgear/mailman/message/33562106/
|url    = http://sourceforge.net/p/flightgear/mailman/message/33562106/
|title  = <nowiki>[Flightgear-devel] FGData - The Next Generation is ready.</nowiki>
|title  = <nowiki>[Flightgear-devel] FGData - The Next Generation is ready.</nowiki>
|author = Torsten Dreyer
|author = Torsten Dreyer
|date  = 2015-03-07
|date  = 2015-03-07
}}</ref>:
}}</ref>. See above for information on getting re-added as a contributor.
# [https://sourceforge.net/user/registration Register] a SourceForge.net
# Upload your public key.
# Send your SourceForge username (optionally with a chocolate bar) to Curt, Clément, James, or Torsten D.
 
Several (but not all) of the [[:Category:Git|Git related articles]] have been updated, including [[FlightGear Git: data developers]].


{{note|For consistency reasons, fgdata development should now happen on the "next" branch and no longer in "master".  "next" should be the default branch<ref>{{cite web
{{note|For consistency reasons, fgdata development should now happen on the "next" branch and no longer in "master".  "next" should be the default branch<ref>{{cite web
Line 117: Line 126:
|url    = http://forum.flightgear.org/viewtopic.php?p=229445#p229445
|url    = http://forum.flightgear.org/viewtopic.php?p=229445#p229445
|title  = Re: New Canvas GUI
|title  = Re: New Canvas GUI
|author = Torsten
|author = Torsten Dreyer
|authorlink-wiki = User:T3r
|authorlink-wiki = User:T3r
|date  = Jan 10, 2015
|date  = Jan 10, 2015
Line 123: Line 132:
|url    = http://forum.flightgear.org/viewtopic.php?p=229303#p229303
|url    = http://forum.flightgear.org/viewtopic.php?p=229303#p229303
|title  = Re: New Canvas GUI
|title  = Re: New Canvas GUI
|author = Torsten
|author = Torsten Dreyer
|authorlink-wiki = User:T3r
|date  = Jan 08, 2015
|date  = Jan 08, 2015
}}</ref>.}}
}}</ref>.}}
Line 136: Line 144:


==== Environment-responsive glass ====
==== 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.
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.


[[File:Glass01.jpg|400px|Frost effect]]
[[File:Glass01.jpg|400px|Frost effect]]
[[File:Glass07.jpg|400px|Raindrop splashes]]
[[File:Glass07.jpg|400px|Raindrop splashes]]


Both frost and the correct splash dynamics of the raindrops need to be modeled airplane side, as the shader can not have the required information. See [[ALS technical notes#ALS glass effect]] for details.
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 technical notes#ALS glass effect]] for details.


==== Cockpit interior light and shadow ====
==== 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 and dirty glass, tinted glass and even render caustics from light refracted on curved glass surfaces:
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.


[[File:Interior01.jpg|400px|Colored glass]]
[[File:Interior01.jpg|400px|Colored glass]]
[[File:Opacity04.jpg|400px|Caustics]]
[[File:Opacity04.jpg|400px|Caustics]]


All that's needed from aircraft modellers is a pre-computed cube map representing the cockpit.  See [[ALS technical notes#Internal cockpit reflection]] for more details
All that's needed from aircraft modellers is a pre-computed cube map representing the cockpit.  See [[ALS technical notes#Internal cockpit reflection]] for more details.


=== New ATC-pie release and OpenRadar interoperability ===
=== New ATC-pie release ===
[[File:ATC-pie-logo.png|96x96px|left]] ''"[http://forum.flightgear.org/viewtopic.php?f=83&t=25573#p234276 the fully multiplayer environment a controller deserves]"''
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.


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.


Beginning to populate the network with a new program without dividing the MP network (esp. 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 [http://forum.flightgear.org/viewtopic.php?f=83&t=25573#p234276 the forum announcement] …''


=== Variant-of tag added ===
=== Variant-of tag added ===
Line 170: Line 178:
</syntaxhighlight>
</syntaxhighlight>


Example from {{repo link|site=sf|path=Aircraft/777/777-200ER-set.xml|pre=$FG_ROOT}} (see [https://gitorious.org/fg/fgdata/commit/1017a32b1b078f46959b3b6e7510a7376458b02b commit]):
Example from the {{repo link|site=sf|path=Aircraft/777/777-200ER-set.xml|lines=11|text=Boeing 777-200ER}}:


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


== In the hangar ==
== In the hangar ==
=== C172P-detailed project ===
=== c172p-detailed project ===
A new, more detailed version of the C172 is currently being worked on by wlbragg, gsagostinho, thevirtualfer, ludomotico, onox and others. It brings amazing new textures, controls, switches, and systems! Check out this forum topic: [http://forum.flightgear.org/viewtopic.php?f=4&t=25157 Cessna 172P detailed]
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:
 
[[File:Screenshots of the project c172p-detailed.jpg|800px|Some screenshots of the c172p-detailed project]]


[[File:Screenshots of the project c172p-detailed.jpg|800px|Screenshots of the c172p-detailed project]]
''Find out more at [http://forum.flightgear.org/viewtopic.php?f=4&t=25157 Cessna 172P detailed] …''


== Scenery Corner ==
== Scenery Corner ==
=== Verona Villafranca 2D layout released ===
=== Verona Villafranca 2D layout released ===
[[User:Elgaton|elgaton]] has released the complete 2D layout for [[LIPX]]; the work is going to be submitted to the Airport Scenery Gateway at the end of March for inclusion in X-Plane and FlightGear. A scenery build can be downloaded from the [http://forum.flightgear.org/viewtopic.php?f=5&t=21576 official development thread on the forum]. 3D buildings will be added in the coming months.
[[User:Elgaton|elgaton]] has released the complete 2D layout for [[LIPX]]; the work is going to be submitted to the Airport Scenery Gateway at the end of March for inclusion in X-Plane and FlightGear. A scenery build can be downloaded from the [http://forum.flightgear.org/viewtopic.php?f=5&t=21576 official development thread on the forum]. 3D buildings will be added in the coming months.
<gallery>
<gallery mode="packed">
File:LIPX-RC2-panorama.png|The airport and the surrounding area.
File:LIPX-RC2-panorama.png|The airport and the surrounding area.
File:LIPX-RC2-top.png|Top view.
File:LIPX-RC2-top.png|Top view.

Navigation menu