FlightGear Newsletter January 2016: Difference between revisions

Jump to navigation Jump to search
Being cleanup for publishing
No edit summary
(Being cleanup for publishing)
Line 6: Line 6:
  | valign="top" width="33%" |
  | valign="top" width="33%" |
{{Newsletter-cover-header|Development news}}<br>
{{Newsletter-cover-header|Development news}}<br>
[[#Reset & Re-init Improvements|Reset & Re-init Improvements]]<br>
[[#New ATC-pie release|New ATC-pie release]]<br>
[[#Route Manager GUI|Route Manager GUI]]<br>
[[#New version scheme and release preparations|New version scheme and release preparations]]<br>
[[#Project3000 and TerraSync|Project3000 and TerraSync]]<br>
[[#Python and FlightGear|Python and FlightGear]]<br>
[[#Python and FlightGear|Python and FlightGear]]<br>
[[#Experimental directional moonlight patches|Experimental directional moonlight patches]]<br>
| valign="top" width="33%" |
{{Newsletter-cover-header|In the hangar}}<br>
{{Newsletter-cover-header|In the hangar}}<br>
| valign="top" width="33%" |
[[#Space Shuttle|Space Shuttle]]<br>
[[#GTA V Airtug & Vapid Speedo|GTA V Airtug & Vapid Speedo]]<br>
{{Newsletter-cover-header|Scenery Corner}}<br>
{{Newsletter-cover-header|Scenery Corner}}<br>
[[#Kansai (RJBB) Sneak Peak|Kansai (RJBB) Sneak Peak]]<br>
[[#Kansai (RJBB) Sneak Peak|Kansai (RJBB) Sneak Peak]]<br>
[[#Gatwick Redevelopment Efforts|Gatwick Redevelopment Efforts]]<br>
[[#Maiquetia New Layout|Maiquetia New Layout]]<br>
[[#More og Romsdal|More og Romsdal]]<br>
[[#More og Romsdal|More og Romsdal]]<br>
| valign="top" width="33%" |
{{Newsletter-cover-header|Community News}}<br>
{{Newsletter-cover-header|Community News}}<br>
| valign="top" width="33%" |
[[#Happy birthday ATC-pie!|Happy birthday ATC-pie!]]<br>
{{Newsletter-cover-header|Contributing}}<br>
{{Newsletter-cover-header|Contributing}}<br>
[[#Translators required|Translators required]]<br>
[[#Translators required|Translators required]]<br>
Line 27: Line 34:
[[File:ATC-pie-logo.png|90px|left|ATC-pie logo]]
[[File:ATC-pie-logo.png|90px|left|ATC-pie logo]]


ATC-pie has been incremented to r8, a new release featuring an '''en-route control mode'''. It allows to play without a base airport, and to centre the radar anywhere on Earth, i.e. to detach it from any available airport position. The good news is that it supports solo games as well, which brings a new type of fun into the program. In solo CTR mode, aircraft transit your airspace following assigned routes. Your job is to reassign levels, routing points, etc. to have aircraft fly across safely until handover to the neighbouring CTR.
[[ATC-pie]] has been incremented to r8, a new release featuring an '''en-route control mode'''. It allows to play without a base airport, and to centre the radar anywhere on Earth, i.e., to detach it from any available airport position. The good news is that it supports solo games as well, which brings a new type of fun into the program. In solo CTR mode, aircraft transit your airspace following assigned routes. Your job is to reassign levels, routing points, etc. to have aircraft fly across safely until handover to the neighbouring CTR.


=== New Versioning Scheme ===
=== New version scheme and release preparations ===
{{FGCquote
Early in January, in preparation for fully automated releases, the version numbers of FGData, SimGear, FlightGear source, and FGRun were set to 2016.1.0. This marks the beginning of the new version scheme, of which you can find out more [[Release plan#2016.1 and after|here]].
|1= Hi all to prepare for our next releases, I have just set the version number for - fgdata - simgear - flightgear - fgrun to 2016.1.0 This marks the beginning of the new version number scheme as discussed before and hopefully the beginning of fully automated releases in a few weeks. Now that our scenery infrastructure is in a working condition again, I will focus on preparing the scripts for Jenkins. Usual disclaimer: In the unlikely event of receiving a version number mismatch error message for fgdata, please tripple check that you have compiled simgear AND flightgear AND have the latest fgdata. Regards, Torsten
|2= {{cite web
  | url    = http://sourceforge.net/p/flightgear/mailman/message/34741767/
  | title  = <nowiki>[Flightgear-devel] Release preparations</nowiki>
  | author = <nowiki>Torsten Dreyer</nowiki>
  | date  = Jan 5th, 2016
  | added  = Jan 5th, 2016
  | script_version = 0.23
  }}
}}


=== Release changes ===
''From {{cite web
{{FGCquote
|url = http://sourceforge.net/p/flightgear/mailman/message/34741767/
|1= Hi all to prepare for our next releases, I have just set the version number for - fgdata - simgear - flightgear - fgrun to 2016.1.0 This marks the beginning of the new version number scheme as discussed before and hopefully the beginning of fully automated releases in a few weeks. Now that our scenery infrastructure is in a working condition again, I will focus on preparing the scripts for Jenkins. Usual disclaimer: In the unlikely event of receiving a version number mismatch error message for fgdata, please tripple check that you have compiled simgear AND flightgear AND have the latest fgdata.
|title = <nowiki>[Flightgear-devel] Release preparations</nowiki>
|2= {{cite web
|author = Torsten Dreyer
  | url   = http://sourceforge.net/p/flightgear/mailman/message/34741767/
|date = Jan 5th, 2016
  | title = <nowiki>[Flightgear-devel] Release preparations</nowiki>
}}''
  | author = <nowiki>Torsten Dreyer</nowiki>
  | date   = Jan 5th, 2016
  | added  = Jan 5th, 2016
  | script_version = 0.23
  }}
}}
 
=== Reset & Re-init Improvements ===
{{WIP}}
* Pull Ephemeris out of FGGlobals {{flightgear commit|ba56c4}}
* Make PerformanceDB a real subsystem{{flightgear commit|83ea6d}}
* Stop OSG threading earlier on shutdown. Avoid intermittent race conditions on shutdown when the OSG pager/Db thread is running. Ensure the OSG threads are stopped before we start tearing down any scene graph nodes. {{flightgear commit|b7c88e}}
* AI subsystem now does an orderly shutdown - remove special case logic which is no longer required {{flightgear commit|c69e6f}}
* Pull Sound-manager out of FGGlobals{{flightgear commit|52fd69}}
* Remove FontCache from globals. - access via a singleton instead. {{flightgear commit|fc9c43}}
* Chatter-queue moved out of globals - now lives as part of the sound-manager, {{flightgear commit|c40040}}
 
=== Route Manager GUI ===
waypointlist commits


=== Project3000 and TerraSync ===
=== Project3000 and TerraSync ===
Line 81: Line 59:
   }}
   }}
}}
}}
=== Python and FlightGear ===
=== Python and FlightGear ===
{{FGCquote
{{FGCquote
Line 123: Line 102:


== In the hangar ==
== In the hangar ==
=== Space Shuttle ===
=== Space Shuttle ===
The '''[[Space Shuttle]]''' development team is proud to announce that Milestone 5 of the Space Shuttle has arrived in the repository. Breaking new grounds in FG glass cockpits, we have the ability to drive as many as nine distinct Multifunction Display Units (MDUs) on the forward panel, each capable of showing a different part of the Shuttle's Guidance and Navigation or Systems Management avionics package.<p>


The Shuttle development team is proud to announce that Milestone 5 of the Space Shuttle has arrived on the repository. Breaking new grounds in FG glass cockpits, we have the ability to drive as many as nine distinct Multifunction Display Units (MDUs) on the forward panel, each capable of showing a different part of the Shuttle's Guidance and Navigation or Systems Management avionics package.<p>
Two keyboards are used to communicate with the flight computer, and many functions (payload bay door, automatic pointing and tracking in orbit, propellant dump, DAP configuration, etc.) can be called via the control software.
 
Two keyboards are used to communicate with the flight computer, and many functions (payload bay door, automatic pointing and tracking in orbit, propellant dump, DAP configuration,...) can be called via the control software.<p>


[[File:Shuttle cockpit panorama01.jpg|800px|Status of the Shuttle 3d cockpit in Jan 2016]]<p>
[[File:Shuttle cockpit panorama01.jpg|800px|thumb|none|Status of the Shuttle 3d cockpit in Jan 2016]]


For the night half of the orbit, the cockpit panels are backlit to allow reading the labels, and the rest of the surfaces are illuminated by the residual ambience.<p>
For the night half of the orbit, the cockpit panels are backlit to allow reading the labels, and the rest of the surfaces are illuminated by the residual ambience.


[[File:Shuttle cockpit panorama02.jpg|800px|Status of the Shuttle 3d cockpit in Jan 2016]]
[[File:Shuttle cockpit panorama02.jpg|800px|thumb|none|Status of the Shuttle 3d cockpit in Jan 2016]]


With additional work going into Aurora Borealis rendering, there's now also something to see in space during the night!
With additional work going into Aurora Borealis rendering, there's now also something to see in space during the night!
Line 140: Line 117:
=== GTA V Airtug & Vapid Speedo ===  
=== GTA V Airtug & Vapid Speedo ===  
[[File:GTA V Vapid Speedo.png|thumb|GTA V Vapid Speedo]]
[[File:GTA V Vapid Speedo.png|thumb|GTA V Vapid Speedo]]
Two GTA V vehicles have been released by Ausdkunst. The Aitug and Vapid Speedo can be downloaded from their development repositories ([https://github.com/ausdkunst/gtav-airtug 1] [https://github.com/ausdkunst/gtav-vapid-speedo 2] respectively). You can find out his other projects by clicking [http://ausdkunst.wix.com/kerdigarage here].
Two GTA V vehicles have been released by Ausdkunst. The '''Aitug''' and '''Vapid Speedo''' can be downloaded from their development repositories ([https://github.com/ausdkunst/gtav-airtug 1] [https://github.com/ausdkunst/gtav-vapid-speedo 2] respectively). You can find out his other projects by clicking [http://ausdkunst.wix.com/kerdigarage here].


== Scenery corner ==
== Scenery corner ==
Line 202: Line 179:
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 ([[anti-aliasing]], 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 ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].


<!--
==== Screenshot of the Month ====
==== Screenshot of the Month ====
Entries for this month's best screenshot can be submitted to [http://forum.flightgear.org/viewtopic.php?f=19&t=28453 this] forum topic. Be sure to see the [http://forum.flightgear.org/viewtopic.php?f=19&t=28453#p271662 first post] for participation rules. For purposes of convenience and organization, after all the entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there. Once the voting has finished, the best screenshot will be presented on this page.
Entries for this month's best screenshot can be submitted to [http://forum.flightgear.org/viewtopic.php?f=19&t=28453 this] forum topic. Be sure to see the [http://forum.flightgear.org/viewtopic.php?f=19&t=28453#p271662 first post] for participation rules. For purposes of convenience and organization, after all the entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there. Once the voting has finished, the best screenshot will be presented on this page.
-->


[[Category:FlightGear Newsletter|2016 01]]
[[Category:FlightGear Newsletter|2016 01]]
[[Category:Changes after 3.6]]
[[Category:Changes after 3.6]]

Navigation menu