FlightGear Newsletter January 2016: Difference between revisions
No edit summary |
Red Leader (talk | contribs) (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> | ||
[[# | [[#New ATC-pie release|New ATC-pie release]]<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> | ||
[[#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> | ||
[[#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 | === New version scheme and release preparations === | ||
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]]. | |||
''From {{cite web | |||
|url = http://sourceforge.net/p/flightgear/mailman/message/34741767/ | |||
|title = <nowiki>[Flightgear-devel] Release preparations</nowiki> | |||
|author = Torsten Dreyer | |||
|date = Jan 5th, 2016 | |||
}}'' | |||
} | |||
=== 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> | |||
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, | |||
[[File:Shuttle cockpit panorama01.jpg|800px|Status of the Shuttle 3d cockpit in Jan 2016]] | [[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. | 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]] | ||
Revision as of 11:28, 5 February 2016
| This newsletter is a draft.
Please feel free to add content you think will be of interest to the FlightGear community. You can read the latest newsletter at FlightGear Newsletter December 2015. |
Development news
New ATC-pie release
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 version scheme and release preparations
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 here.
From Torsten Dreyer (Jan 5th, 2016). [Flightgear-devel] Release preparations.
Project3000 and TerraSync
|
I am thinking about making the scenery object from project3000 and osm2city available via terrasync. Just dumping the files in the models database is probably not a good idea as this would be a bit too much for many systems to render. But probably we could load those objects under individual subtrees in the scene graph and make them selectable using a new draw-mask flag? Even the loading of the scenery should be selectable by a property, at least at startup of fgfs. This should not be too complicated and would eventually needs the following tasks to be done: - work out a directory structure within the scenery system, besides /Objects /Models etc. - work out a scene graph structure for the models and a corresponding draw mask - implement the loader in SimGear (mostly copy&paste) - help me writing the automated importer/exporter script for our scenery server Anybody interested in pushing this? I don't have enough time to to this myself but I would happily help getting started. — Torsten Dreyer (Jan 7th, 2016). [Flightgear-devel] Making project3000 and osm2city part of
terrasync?.
(powered by Instant-Cquotes) |
|
Python and FlightGear
|
|
I wrote a really quick/simple property tree implementation in python ... it doesn't do any of the fancy stuff the FlightGear property system does (like listeners, read/write tracing, etc.) But it does implement a basic shared property tree and allows (in python) direct referencing of property tree elements. https://github.com/AuraUAS/aura-core/blob/python/src/python/props.py |
|
|
|
After some long forum discussions [1], followed by some private discussions with Curt about his own Python property system developments, I have written some code that might be of general interest. This started as an experiment to learn more about the design of the complicated Python object data structure, but it has expanded somewhat. The code is currently for experimentation, as only the property tree is accessible. It is written to be compatible only with Python 3k, as py2 support is not needed for an interpreter compiled into the fgfs binary. — Edward d'Auvergne (Jan 22nd, 2016). [Flightgear-devel] A FGPythonSys implementation: The embedded
Python interpreter as a FlightGear subsystem..
(powered by Instant-Cquotes) |
|
Experimental directional moonlight patches
|
|
The changes here are for an initial milestone - exposing the position of the moon in the local aircraft frame and setting the amount of night-time illumination based on the phase of the moon. I have implemented some core infrastructure in Durk's ancient 1997-1998 ephemeris code (simgear), and in the flightgear time manager, ephemeris and solar system body (sun)solver code. I'll delve into full details below but, quickly, the changes are in the branches: https://sourceforge.net/u/edauvergne/flightgear/ci/directional_moonlight_v1/tree/ https://sourceforge.net/u/edauvergne/simgear/ci/directional_moonlight_v1/tree/ https://sourceforge.net/u/edauvergne/fgdata/ci/directional_moonlight_v1/tree/ More details can be found in the corresponding forum thread [1]. Initial results of the current code - specifically the automatic lighting of the ALS scene at night based on the moon's phase - are given in that thread [2], as well as below. Cheers, Edward [1] http://forum.flightgear.org/viewtopic.php?f=47&t=28201 (permanent archive: https://web.archive.org/web/http://forum.flightgear.org/viewtopic.php?f=47&t=28201 ). [2] http://forum.flightgear.org/viewtopic.php?f=47&t=28201&start=75#p271916 (permanent archive: https://web.archive.org/web/http://forum.flightgear.org/viewtopic.php?f=47&t=28201&start=75#p271916 ). — Edward d'Auvergne (Jan 8th, 2016). [Flightgear-devel] Implementing directional moonlight (local
position, phase-based full scene lighting, reflections,
and optical effects)..
(powered by Instant-Cquotes) |
|
In the hangar
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.
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.
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.
With additional work going into Aurora Borealis rendering, there's now also something to see in space during the night!
GTA V Airtug & Vapid Speedo
Two GTA V vehicles have been released by Ausdkunst. The Aitug and Vapid Speedo can be downloaded from their development repositories (1 2 respectively). You can find out his other projects by clicking here.
Scenery corner
Kansai (RJBB) Sneak Peak
Work continues on Kansai Intl Airport by a team headed by Israel Hernandez (IH-COL). A custom 850 dat layout has been made, with all the appropriate markings. The main terminal has been built, including an animated 'sky-train'. Work continues on Terminal 2, the FEDEX building, and the cargo ramp. Most recently, J. Redpath has been adding lamps to the remote stands and cargo ramp, as seen in this screenshot:
Gatwick Redevelopment Efforts
J. Redpath has been redeveloping Gatwick airport with an all-new 850 layout, which includes apron markings, proper taxiways, and more. Here we have a little preview screenshot from WED:
Maiquetia New Layout
J. Redpath has also redone the Maiqeutia layout with another all-new 850 layout, which includes proper taxiways, markings, and apron markings. This is already uploaded, and may be downloaded from [1]. Simply add the path: SVMI-fg-CustomScenery/SVMI/Scenery to $FG_SCENERY and enjoy!
More og Romsdal
More og Romsdal is a province in Norway. For a part of it, there is now a custom scenery available featuring new airport layouts and (partly) z-fighting/flooding fix:
Airport buildings for ENAL, EMNL and ENKB are now available via terrasync.
For more information, visit More og Romsdal
Community news
Happy birthday ATC-pie!
ATC-pie is one year old! On January 15 last year, the initial beta version was released and put to real game testing. On February 1, the first version (r1) was out, initiating the string of improvements that took place until today. This is certainly a time for the developer to thank all users who have tried or adopted it and those who have helped to improve it. Perhaps also an occasion for happy players to wrap up a nice present for it in the form of a kind review? ;-)
Contributing
Translators required
|
The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, start at Help:Translate. |
|
Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire Help:Traduire. |
|
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. |
|
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. |
|
La wiki de FlightGear 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. |
|
La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a Help:Traduir. |
|
A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em Help: Traduzir. |
FlightGear logos
If you want some graphic elements for your FlightGear-related site (such as 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 (anti-aliasing, texture sharpening, etc.). More info at Howto:Make nice screenshots.