FlightGear Newsletter October 2016: Difference between revisions

Some updates
(Some updates)
Line 1: Line 1:
{{draft|newsletter|Please feel free to add content that you think will be of interest to the FlightGear community.<br>You can read the latest newsletter at [[FlightGear Newsletter September 2016]].}}


{{draft|newsletter|Please feel free to add content that you think will be of interest to the FlightGear community.<br>You can read the latest newsletter at [[FlightGear Newsletter September 2016]].}} <!-- change month and year as required-->
{{Newsletter-header|October 2016}}
 
{{Newsletter-header|October 2016}} <!-- change month and year as required-->
<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%" |
{{Newsletter-cover-header|Development news}}<br>
{{Newsletter-cover-header|Development news}}<br>
[[#Git multimail script updated|Git multimail script updated]]<br>
{{Newsletter-cover-header|In the hangar}}<br>
{{Newsletter-cover-header|In the hangar}}<br>
  | valign="top" width="33%" |
  | valign="top" width="33%" |
Line 21: Line 21:


== Development news ==
== Development news ==
{{Next default airport|airport=LSZH (Zürich)}}
[[LSZH]] (Zürich) has been chosen as the FlightGear v2016.4 default airport.


===Local apt.dat versions support ===
=== Git multimail script updated ===
For all git repositories on SourceForge, Edward d'Auvergne has updated the git-multimail repository hook script to 1.5-dev (the current master branch) from 1.2-dev, with a few customisations/simplifications for our commitlogs ML [1,2]. If you see any error messages when committing, please report these. A failure of the git-multimail Python script will only result in a failure of the sending of an email to the ML, as this is a post-receive hook - the commit will have been successfully pushed/etc.<ref>{{cite web
  |url    =  https://sourceforge.net/p/flightgear/mailman/message/35435904/
  |title  =  <nowiki> Re: [Flightgear-devel] Git-multimail repository hook script
merge-request bug (was Re: apt.dat - add local version ?) </nowiki>
  |author =  <nowiki> Edward d'Auvergne </nowiki>
  |date  =  Oct 18th, 2016
  |added  =  Oct 18th, 2016
  |script_version = 0.40
  }}</ref>
 
 
=== Local apt.dat versions support ===
apt.dat now supports local versions:
apt.dat now supports local versions:


Line 59: Line 71:
</pre>
</pre>


where “Scenery path” can be any of you scenery paths (e.g., any component of --fg-scenery/$FG_SCENERY; the path given to --terrasync-dir is also one). The files read are all NavData/apt/*.dat[.gz] files inside each scenery path, followed by the default $FG_ROOT/Airports/apt.dat.gz (last in precedence order, thus allowing your custom sceneries to override airports already present in $FG_ROOT/Airports/apt.dat.gz). In the typical case, just put your apt.dat files(*) in the NavData/apt subdirectory of your custom scenery and they will be picked up automatically. In each of these files, you may include as many airport definitions as you want. (*) Actually, any name ending with .dat or .dat.gz---but the syntax inside, of course, must be valid "apt.dat syntax". And if the file name ends in .gz, of course the contents must be gzipped-compressed. <ref>{{cite web
where "Scenery path" can be any of you scenery paths (e.g., any component of --fg-scenery/$FG_SCENERY; the path given to --terrasync-dir is also one). The files read are all NavData/apt/*.dat[.gz] files inside each scenery path, followed by the default $FG_ROOT/Airports/apt.dat.gz (last in precedence order, thus allowing your custom sceneries to override airports already present in $FG_ROOT/Airports/apt.dat.gz). In the typical case, just put your apt.dat files(*) in the NavData/apt subdirectory of your custom scenery and they will be picked up automatically. In each of these files, you may include as many airport definitions as you want. (*) Actually, any name ending with .dat or .dat.gz---but the syntax inside, of course, must be valid "apt.dat syntax". And if the file name ends in .gz, of course the contents must be gzipped-compressed. <ref>{{cite web
   |url    =  https://sourceforge.net/p/flightgear/mailman/message/35432391/  
   |url    =  https://sourceforge.net/p/flightgear/mailman/message/35432391/  
   |title  =  <nowiki> Re: [Flightgear-devel] apt.dat - add local version ? </nowiki>  
   |title  =  <nowiki> Re: [Flightgear-devel] apt.dat - add local version ? </nowiki>  
Line 74: Line 86:


When you have some spare time left, interested in heliopters and always wished to improve things, you might want to apply to this job. More informations on: [[MBB Bk 117|MBB Bk 117 wiki-page]]
When you have some spare time left, interested in heliopters and always wished to improve things, you might want to apply to this job. More informations on: [[MBB Bk 117|MBB Bk 117 wiki-page]]
=== 2016 Camaro SS and more ===
=== 2016 Camaro SS and more ===
Auskunst is currently seeking help to improve the handling of his 2016 Camaro SS and another future automobile project.  If you have experience of tweaking YASIM FDM, you can apply the job by clicking [https://bulldogrs.wordpress.com/2016/10/16/help-request-1-0-yasim-fdm-expert/ here]
Auskunst is currently seeking help to improve the handling of his 2016 Camaro SS and another future automobile project.  If you have experience of tweaking YASIM FDM, you can apply the job by clicking [https://bulldogrs.wordpress.com/2016/10/16/help-request-1-0-yasim-fdm-expert/ here]


== Scenery corner ==
== Scenery corner ==
=== Scenery/LOD experiments ===
=== Scenery/LOD experiments ===
psadro_gm has the normal calculations, now.  Everything is being generated on the fly.  psadro_gm sees very little CPU usage.
psadro_gm has the normal calculations, now.  Everything is being generated on the fly.  psadro_gm sees very little CPU usage.
Line 142: Line 154:


[[Category:FlightGear Newsletter|2016 10]]
[[Category:FlightGear Newsletter|2016 10]]
[[Category:Changes after 2016.3]] <!--change version as necessary -->
[[Category:Changes after 2016.3]]


[[de:FlightGear Newsletter Oktober 2016]] <!--change year and name for the month IN GERMAN (a list of German months can be found in [[De/FlightGear Newsletter]])-->
[[de:FlightGear Newsletter Oktober 2016]]
----