FlightGear Newsletter March 2015: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
No edit summary
(Switched from the master {{repo link}} template to the {{fgaddon aircraft source}} and {{github source}} subtemplates (to fix broken links).)
 
(43 intermediate revisions by 12 users not shown)
Line 1: Line 1:
{{draft|Newsletter|Please feel free to add content you think will be of interest to the community.}}
{{Newsletter-header|March 2015}}
{{Newsletter-header|March 2015}}
<div style="border-bottom:3px double #BBB;">
<div style="border-bottom:3px double #BBB;">
{| width="100%" |
{| width="100%" |
  | valign="top" width="33%" |
  | valign="top" width="33%" |
[[#Project restructuring|Project restructuring]]<br/><br/>
{{Newsletter-cover-header|Development news}}<br/>
{{Newsletter-cover-header|Development news}}<br/>
[[#FGData split|FGData split]]<br/>
[[#Upcoming built-in GUI|Upcoming built-in GUI]]<br/>
[[#New ATC-pie release and OpenRadar interoperability|New ATC-pie release and OpenRadar interoperability]]<br/>
[[#Environment-responsive glass|Environment-responsive glass]]<br/>
[[#Variant-of tag added|Variant-of tag added]]<br/>
[[#Cockpit interior light and shadow|Cockpit interior light and shadow]]<br/>
[[#FlightGear goes to space, part III|FlightGear goes to space, part III]]<br/>
[[#New ATC-pie release|New ATC-pie release]]<br/>
[[#Variant-of tag added|Variant-of tag added]]
  | 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/><br/>
{{Newsletter-cover-header|Scenery Corner}}<br/>
{{Newsletter-cover-header|Scenery Corner}}<br/>
[[#Verona Villafranca 2D layout released|Verona Villafranca 2D layout released]]<br/>
[[#Project Venezuela|Project Venezuela on the way!]]
| valign="top" width="33%" |
{{Newsletter-cover-header|Community News}}<br/>
{{Newsletter-cover-header|Community News}}<br/>
[[#FlightGear Space Program|FlightGear Space Program]]<br/>
[[#FlightGear on YouTube|FlightGear on YouTube]]<br/>
| valign="top" width="33%" |
[[#FlightGear Space Program|FlightGear Space Program]]<br/><br/>
{{Newsletter-cover-header|Contributing}}<br/>
{{Newsletter-cover-header|Contributing}}<br/>
[[#Translators required|Translators required]]<br/>
[[#Translators required|Translators required]]<br/>
[[#FlightGear logos|FlightGear logos]]<br/>
[[#FlightGear logos|FlightGear logos]]<br/>
[[#Screenshots|Screenshots]]<br/>
[[#Screenshots|Screenshots]]
|}</div>
|}</div>


== Relocating ==
== Project restructuring ==
{{FGCquote
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 ([https://about.gitlab.com/2015/03/03/gitlab-acquires-gitorious/ read more]) and the second is that Google Code will shut down in 2016 ([http://google-opensource.blogspot.co.uk/2015/03/farewell-to-google-code.html 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 [[#fgdata split|below]] for details).
  |Hi everybody,<br/>
 
<br/>
All repositories of the FlightGear project have been synchronized to [http://sourceforge.net/p/flightgear/_list/git SourceForge.net]<ref>{{cite web
due to the fact that gitorious is about to close soon, we need to find a<br/>
|url    = http://sourceforge.net/p/flightgear/mailman/message/33588398/
new home for our source code repositories. I'd suggest that we collect all<br/>
|title  = <nowiki>[Flightgear-devel] [MasterCaution] (ding!) FlightGear is now at SourceForge</nowiki>
of our FlightGear belongings and relocate them to sourceforge.<br/>
|author = Torsten Dreyer
SF might not have the coolest user interface but offers some nice features<br/>
|authorlink-wiki = User:T3r
that makes administration of infrastructure easy. Having everything in one<br/>
|date  = 2015-03-12
place keeps administration overhead simple.<br/>
}}</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.
<br/>
 
I have already mirrored the repositories from gitorious to sourceforge. I<br/>
Example for SimGear with read-only access:
suggest to make the official move next weekend March 14/15 so everybody has<br/>
<syntaxhighlight lang="bash">
some time to prepare whatever is needed.
git remote set-url origin <protocol>git.code.sf.net/p/flightgear/<sub-project>
  |{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33569715/
</syntaxhighlight>
    |title=<nowiki>[Flightgear-devel] Completely moving to sourceforge</nowiki>
 
    |author=<nowiki>Torsten Dreyer</nowiki>
<code><nowiki><protocol></nowiki></code> can be either of <code><nowiki>git://</nowiki></code> (read-only access) or <code><nowiki>http://</nowiki></code> (read/write access). See http://sourceforge.net/p/flightgear/_list/git for a list of what <code><nowiki><sub-project></nowiki></code> should (they should also be lowercase).
    |date=<nowiki>2015-03-09</nowiki>
 
  }}
Example for [[SimGear]] with read/write access:
}}
<syntaxhighlight lang="bash">
git remote set-url origin http://git.code.sf.net/p/flightgear/simgear
</syntaxhighlight>
 
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.
 
The bug tracker has moved to http://sourceforge.net/p/flightgear/codetickets/<ref>{{cite web
|url   = http://sourceforge.net/p/flightgear/mailman/message/33600886
|title = <nowiki>[Flightgear-devel] Bugtracker moving to sourceforge</nowiki>
|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]).
 
TerraSync is yet to be moved as of April 2.


{{FGCquote
  |evelopers with write access should start regsitering with sourceforge and<br/>
upload their public key now. Please send me or Clément your SF username and<br/>
we will happily grant you the same level of access rights.<br/>
<br/>
To avoid duplicate work, I'll revoke all write access from the gitorious<br/>
repositories on Friday afternoon (it's the 13th - always a good date for<br/>
changing things). Thereafter, I push the latest changes to sourceforge and<br/>
re-add the write-access rights to those users that have send me their IDs.<br/>
<br/>
James and Clément will take care of Jenkins.
  |{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33569715/
    |title=<nowiki>[Flightgear-devel] Completely moving to sourceforge</nowiki>
    |author=<nowiki>Torsten Dreyer</nowiki>
    |date=<nowiki>2015-03-09</nowiki>
  }}
}}
== Development news ==
=== 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 71: Line 81:
|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/
|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.
 
As of 08/03/2015, most contributors have read-only permission (except for admins), and this will remain the case for a day or two<ref name="multiple">{{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/
|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 (optionally with a chocolate bar) to Curt, Clément, James, or Torsten D.
 
[[FlightGear Git: data developers]] has been updated to reflect the new repository.


{{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 112: Line 106:
{{note|See [[FGAddon]] for obtaining aircraft other than the C172p and UFO.}}
{{note|See [[FGAddon]] for obtaining aircraft other than the C172p and UFO.}}


''Enjoy and keep flying!''
== Development news ==
=== Upcoming built-in GUI ===
[[File:Qt launcher for FlightGear 3.5 on Windows 7.jpg|thumb|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 [http://www.qt.io/qt-quick/ Qt Quick], at the suggestion and encouragement of Curt, Torsten D & others<ref>{{cite web
|url    = http://sourceforge.net/p/flightgear/mailman/message/33245028
|title  = <nowiki>[Flightgear-devel] Gui technologies</nowiki>
|author = James Turner
|authorlink-wiki = User:Zakalawe
|date  = 2015-01-20
}}</ref>.  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.
 
{{inote|The parallel development of HTML and Qt-based UIs is happening by intention and is not the result of discoordination<ref>{{cite web
|url    = http://forum.flightgear.org/viewtopic.php?p=229445#p229445
|title  = Re: New Canvas GUI
|author = Torsten Dreyer
|authorlink-wiki = User:T3r
|date  = Jan 10, 2015
}}</ref>.  It is likely both will use a common service layer to provide necessary data<ref>{{cite web
|url    = http://forum.flightgear.org/viewtopic.php?p=229303#p229303
|title  = Re: New Canvas GUI
|author = Torsten Dreyer
|date  = Jan 08, 2015
}}</ref>.}}
 
To learn more, see [[Integrated Qt5 Launcher]].
 
=== 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.
 
[[File:Glass01.jpg|400px|Frost effect]]
[[File:Glass07.jpg|400px|Raindrop splashes]]
 
Both frost and the correct splash dynamics of the raindrops need to be modelled by the aircraft developer, as the shader cannot have get the required information. See [[ALS technical notes#ALS glass effect|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.
 
[[File:Interior01.jpg|400px|Colored glass]]
[[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|internal cockpit reflection]] and [[ALS technical notes#Interior shading|interior shading]] for more details.
 
=== FlightGear goes to space, part III ===
Independent of the [[FlightGear space program]], efforts are underway to provide the [[Space Shuttle]] with a flight dynamics model which has the characteristics of a real spacecraft and performance close to the real Shuttle.


<references/>
[[File:Shuttle FG01.jpg|600px|The Space Shuttle]]


=== New ATC-pie release and OpenRadar interoperability ===
Currently, a plausible behaviour of the {{Wikipedia|Space Shuttle Solid Rocket Booster|{{Abbr|SRBs|Solid Rocket Boosters}}}} has been implemented.  Only the main engines respond to throttle, but SRBs burn until exhausted when ignited. The ascent path is controlled by thrust vectoring on both main engines and SRBs. Callouts for important ascent milestones are implemented, such as thrust bucket<ref>Throttling down to prevent the exceeding of {{Wikipedia|maximum dynamic pressure}}.</ref>, SRB separation, orbital insertion, {{Abbr|MECO|Main Engines Cut-Off}}, etc. Balancing the top-heavy external tank to a good orbit is moderately challenging.
[[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.
[[File:Shuttle FG02.jpg|300px|Launch]]
[[File:Shuttle FG03.jpg|300px|At 4,000 ft.]]


Beginning to populate the network with a new program without dividing the MP network (esp. controllers) was 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 preference.
The best visuals can be obtained by switching to the Earthview orbital rendering engine at high altitude:


[[File:Shuttle FG04.jpg|300px|Crossing 30,000 ft.]]
[[File:Shuttle FG5.jpg|300px|Racing to orbital speed at 650,000 ft.]]
Stay tuned for more! Modelers interested in realism are very welcome to come aboard and help.
=== New ATC-pie release ===
[[File:ATC-pie-logo.png|200px|left|ATC-pie logo.]]
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 existence. 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 [http://forum.flightgear.org/viewtopic.php?f=83&t=25573#p234276 the forum announcement] …''


=== Variant-of tag added ===
=== Variant-of tag added ===
Aircraft developers can make use of a new tag in the [[Aircraft-set.xml]] file.  Added to the <code><nowiki><sim></nowiki></code>, the <code><nowiki><variant-of></nowiki></code> tag states to the launcher the aircraft type that your aircraft is a variant of.  For example, the [[British Aerospace Sea Harrier|BAe Sea Harrier FA2]] is a variant of the BAe Sea Harrier, and the ''Cessna 172P - Canvas Demo'' is a variant of the [[Cessna C172P|C172P]].
Aircraft developers can make use of a new tag in the [[Aircraft-set.xml]] file.  Added to the <code><nowiki><sim></nowiki></code>, the <code><nowiki><variant-of></nowiki></code> tag states to the launcher the aircraft type that your aircraft is a variant of.  For example, the [[British Aerospace Sea Harrier|BAe Sea Harrier FA2]] is a variant of the BAe Sea Harrier, and the ''Cessna 172P - Canvas Demo'' is a variant of the [[Cessna C172P|C172P]].
{{note|At the moment, only the Mac Qt launcher (which comes with FlightGear for Mac v3.4+) will read this tag.}}


Syntax:
Syntax:
Line 138: Line 190:
</syntaxhighlight>
</syntaxhighlight>


Example from {{repo link|site=gito|path=Aircraft/777/777-200ER-set.xml|pre=$FG_ROOT}} (see [https://gitorious.org/fg/fgdata/commit/1017a32b1b078f46959b3b6e7510a7376458b02b commit]):
Example from the {{fgaddon aircraft source|777|777-200ER-set.xml|line=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>
=== Upcoming features of FGCamera ===
[[FGCamera]] v1.3 will have few notable features:
* "Click-camera" mode. Camera is activated by left-clicking on scenery while pressing modifier (customizable key/button). Previous view is restored by pressing modifier again (without LMB);
* AI-object camera mode. Each AI object can have pre-defined camera views;
* Replay timestamps. Camera views can be "tied" to specific replay timestamp. Timestamps are defined using *.xml files;
* "Chainable" cameras (automatic switching of cameras in the same category);
* [[FGCamera API|API]]. Cameras can be created and manipulated procedurally.
{|
|{{#ev:youtube|_KEq5hSKurE|300||Click-camera in action}}
|{{#ev:youtube|xsnWJe_xUgw|300||Demonstration of AI object cameras}}
|{{#ev:youtube|u7B4ZmcHimM|300||Replay timestamps}}
|}


== In the hangar ==
== 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:
[[File:Screenshots of the project c172p-detailed.jpg|800px|Some 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 ===
{{usr|Elgaton}} has released the complete 2D layout for the [[Verona Villafranca Airport]] (LIPX) and submitted it to the Airport Scenery Gateway. See the [http://forum.flightgear.org/viewtopic.php?f=5&t=21576 forum thread] for download links. 3D buildings will be added in the coming months.
<gallery mode="packed">
LIPX-RC2-panorama.png|Airport and the surrounding area
LIPX-RC2-top.png|Top view
LIPX-RC2-apron.png|The apron now features up-to-date stands
LIPX-B-CRJ700.png|Holding short in the [[Bombardier CRJ700 series|CRJ700]] at night
</gallery>
===Project Venezuela===
[[Project Venezuela]] is on the way, with a team of users, headed by [[User:legoboyvdlp|legoboyvdlp]] working on several airports, namely SVMI and SVVP. Their progress can be downloaded at [http://www.github.org/legoboyvdlp/ProjectFlightGearScenery their GitHub repository.] Note: legoboyvdlp currently on vacation, so P.Ven. is on a hiatus until June.


== Community News ==
== Community News ==
=== FlightGear on YouTube ===
<big>''From the [https://www.youtube.com/user/3ZzOoOZz1/featured SMAAF GAMEZ] channel.''</big>
{{#ev:youtube|uvZF-Yv0yiM|600||Video of several FlightGear aircraft using [[Changelog 3.4|FlightGear v3.4]].|frame}}
=== FlightGear Space Program ===
=== FlightGear Space Program ===
[[File:Fgspbadge.png|thumb|FGSP Cosmonaut Badge "The Owl"]]
[[File:Fgspbadge.png|thumb|FGSP Cosmonaut Badge "The Owl"]]
[[File:spacetripready.png]]
[[File:spacetripready.png|link=FlightGear space program]]


Now is your time to become official cosmonaut of The FlightGear Space Program. Just downloading the famous '''[[Space Shuttle]]'''  that has been largely reworked, and select any of the available [[FlightGear_space_program_missions|missions]]. Report your succesfull orbit flight tracker screenie and you'll receive a custom badge of The FlightGear Space Program.
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 [[FlightGear space program missions|missions]]. Report your successful orbit flight tracker screenie and you'll receive a custom badge of the FlightGear Space Program.


The Space Shuttle can be downloaded from {{repo link|site=gith|proj=herbyw/antonov-aircrafts|view=tree|text=the GitHub repository}} in either a ZIP file or by cloning.
The Space Shuttle can be downloaded from {{github source|HerbyW|Antonov-Aircrafts|text=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 {{Wikipedia|An-12}}, [[Antonov_An-22|An-22]], and [[An-225]] (mission transport variants).
As an add-on also you can fly our Special Cargo Transport Missions with the heavily updated [[Antonov An-12|An-12]], [[Antonov An-22|An-22]], and [[An-225]].


''Find out more about space flight in FlightGear at [[FlightGear space program]] …''
''Find out more about space flight in FlightGear at [[FlightGear space program]] …''


== Contributing ==
== Contributing ==
Line 178: Line 264:


=== FlightGear logos ===
=== FlightGear logos ===
If you want some graphic elements for your FlightGear-related site (for example 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.
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 ===
=== Screenshots ===
The FlightGear project always needs screenshots for the website, which show features that were added since the last release.  These shots 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]].
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]].


{{Appendix}}
{{Appendix}}

Latest revision as of 10:52, 24 May 2016

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
FlightGear goes to space, part III
New ATC-pie release
Variant-of tag added

In the hanger
c172p-detailed project

Scenery Corner
Verona Villafranca 2D layout released
Project Venezuela on the way!

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 April 2.

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[7]. 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[8]. It is likely both will use a common service layer to provide necessary data[9].

To learn more, see Integrated Qt5 Launcher.

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 modelled 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.

FlightGear goes to space, part III

Independent of the FlightGear space program, efforts are underway to provide the Space Shuttle with a flight dynamics model which has the characteristics of a real spacecraft and performance close to the real Shuttle.

The Space Shuttle

Currently, a plausible behaviour of the SRBs This is a link to a Wikipedia article has been implemented. Only the main engines respond to throttle, but SRBs burn until exhausted when ignited. The ascent path is controlled by thrust vectoring on both main engines and SRBs. Callouts for important ascent milestones are implemented, such as thrust bucket[10], SRB separation, orbital insertion, MECO, etc. Balancing the top-heavy external tank to a good orbit is moderately challenging.

Launch At 4,000 ft.

The best visuals can be obtained by switching to the Earthview orbital rendering engine at high altitude:

Crossing 30,000 ft. Racing to orbital speed at 650,000 ft.

Stay tuned for more! Modelers interested in realism are very welcome to come aboard and help.

New ATC-pie release

ATC-pie logo.

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 existence. 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>

Upcoming features of FGCamera

FGCamera v1.3 will have few notable features:

  • "Click-camera" mode. Camera is activated by left-clicking on scenery while pressing modifier (customizable key/button). Previous view is restored by pressing modifier again (without LMB);
  • AI-object camera mode. Each AI object can have pre-defined camera views;
  • Replay timestamps. Camera views can be "tied" to specific replay timestamp. Timestamps are defined using *.xml files;
  • "Chainable" cameras (automatic switching of cameras in the same category);
  • API. Cameras can be created and manipulated procedurally.
Click-camera in action
Demonstration of AI object cameras
Replay timestamps

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) and submitted it to the Airport Scenery Gateway. See the forum thread for download links. 3D buildings will be added in the coming months.

Project Venezuela

Project Venezuela is on the way, with a team of users, headed by legoboyvdlp working on several airports, namely SVMI and SVVP. Their progress can be downloaded at their GitHub repository. Note: legoboyvdlp currently on vacation, so P.Ven. is on a hiatus until June.

Community News

FlightGear on YouTube

From the SMAAF GAMEZ channel.

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 successful 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.

References