8,602
edits
FlightGear Newsletter January 2018: Difference between revisions
FlightGear Newsletter January 2018 (view source)
Revision as of 14:18, 3 February 2018
, 3 February 2018Protected "FlightGear Newsletter January 2018": Publishing newsletter ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))
m (Protected "FlightGear Newsletter January 2018": Publishing newsletter ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))) |
|||
| (15 intermediate revisions by 7 users not shown) | |||
| Line 1: | Line 1: | ||
{{Newsletter-header|January 2018}} | |||
{{TOC_right|limit=2}} | |||
''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter. If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.'' | |||
== Development news == | |||
<!-- News about FlightGear itself. The FlightGear mailing list and/or core developers are a good source. --> | |||
=== Docker-based scenery toolchain === | |||
[[File:Docker-sourceforge.png|thumb|screenshot showing sourceforge header with new docker entry]] | |||
Torsten has recently been working on preparing and running Docker-containers for the scenery toolchain. The jenkins server responsible for maintaining the terrasync data at https://scenery.flightgear.org/jenkins/ already does some tasks within containers. | |||
The jenkins instance itself will move into a container soon. Torsten also created a Docker image for terragear to make its usage a lot easier. The short term goal is to get all the tools required to run the scenemodels database with its web frontend, the terrasync upstream data maintenance into containers, hoping to be able to run this entire chain at any public or private cloud. | |||
A mid term goal might be to have terragear running from Jenkins on automatically-provisioned virtual machines whenever a new scenery set needs to be rebuilt. There is still a lot to do before this becomes reality and a docker swarm or kubernetes cluster generates scenery for us regulary. | |||
As all journeys starts with the first step, Torsten is happy to announce the public docker repository for our images and the git repository for the config files behind: | |||
* Our official docker hub repository is at: https://hub.docker.com/u/flightgear/ | |||
* The backing Dockerfiles live at: https://sourceforge.net/p/flightgear/docker/ | |||
Anybody interested in driving this forward, willing to learn or contribute is more than welcome to do so. <ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/36206523/ | |||
|title = <nowiki> [Flightgear-devel] Making containers fly: FlightGear scenery goes | |||
docker </nowiki> | |||
|author = <nowiki> Torsten Dreyer </nowiki> | |||
|date = Jan 27th, 2018 | |||
|added = Jan 27th, 2018 | |||
|script_version = 0.36 | |||
}}</ref> | |||
The Docker image is now capable of performing almost all tasks required for building scenery: | |||
* Fetch SRTM elevation data | |||
* Run hgtchop | |||
* Run terrafit | |||
* Fetch airports and stay in sync with the x-plane gateway | |||
* Run ogr-decode against local shapefiles or perform direct queries to a postgres database | |||
Torsten has sucessfully created the elevation data from SRTM1/3 for the entire globe and created a few random airports with this image. Currently, he is playing with integrating ogr-decode. The docker image gets automatically built, including building latest simgear & terragear from GIT. This build process runs directly at the docker hub: https://hub.docker.com/r/flightgear/terragear/builds/ (Yes: docker hub compiles simgear and terragear for us, amazing, isn't it?) Torsten hopes to be able to compile the a first chunk of scenery within the next couple of weeks.<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/36209739/ | |||
|title = <nowiki> Re: [Flightgear-devel] Making containers fly: FlightGear scenery | |||
goes docker </nowiki> | |||
|author = <nowiki> Torsten Dreyer </nowiki> | |||
|date = Jan 30th, 2018 | |||
|added = Jan 30th, 2018 | |||
|script_version = 0.36 | |||
}}</ref> | |||
That means, if someone wants to generate scenery in the future they will simply be able to download the latest docker image, start it up on Docker CE and run the commands. No compilation required. Which is quite amazing, and could massively reduce the effort required to work on scenery.<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/36209758/ | |||
|title = <nowiki> Re: [Flightgear-devel] Making containers fly: FlightGear scenery | |||
goes docker </nowiki> | |||
|author = <nowiki> Stuart Buchanan </nowiki> | |||
|date = Jan 30th, 2018 | |||
|added = Jan 30th, 2018 | |||
|script_version = 0.36 | |||
}}</ref> | |||
In other words, Build once, run anywhere - thats what docker is made for. (caveat: anywhere means "any Linux flavor or MacOS on x86-64 architecture and eventually Windows64, too.)<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/36209773/ | |||
|title = <nowiki> Re: [Flightgear-devel] Making containers fly: FlightGear scenery | |||
goes docker </nowiki> | |||
|author = <nowiki> Torsten Dreyer </nowiki> | |||
|date = Jan 30th, 2018 | |||
|added = Jan 30th, 2018 | |||
|script_version = 0.36 | |||
}}</ref> | |||
=== Oscilloscope Addon === | |||
[[File:Rleibner-canvas-vsd-12-2017.png|thumb|left|rleibner is developing a graph class that works using local (customized) coordinates and calls the plot2D helpers (see below).For testing (and as exercise) he came up with a VSD (Vertical Situation Display): <ref>https://forum.flightgear.org/viewtopic.php?f=71&t=33457#p324637</ref>]] | |||
[[File:Oscilloscope.png|thumb|rleibner's new Oscilloscope addon is working.This screenshot shows the usual c172p "magnetos checking" Channel 1 (yellow) is '''rpm''' (100 rpm / div).Channel 2 (mauve) is '''magnetos''' (1 / div).Time sweep is 200 ms / div.The idea is to share it as an addon. Mainly to have some feedback about plot2D/graph.<ref>{{cite web |url = https://forum.flightgear.org/viewtopic.php?p=325929#p325929 |title = <nowiki> Re: Plot2D and graph helpers </nowiki> |author = <nowiki> rleibner </nowiki> |date = Jan 6th, 2018 |added = Jan 6th, 2018 |script_version = 0.36 }}</ref>]] | |||
rleibner is developing a graph class that works using local (customized) coordinates and calls the plot2D helpers (see below). | |||
For testing (and as exercise) he came up with a VSD (Vertical Situation Display): <ref>https://forum.flightgear.org/viewtopic.php?f=71&t=33457#p324637</ref> | |||
This '''oscilloscope''' was created as an example of the use of 3 helpers included in the addon: | |||
* '''skinnable.nas''' to create Canvas GUI dialogs including multiple clickable layers. | |||
* '''graph.nas''' to create various types of Canvas instruments. | |||
* '''plot2D.nas''' the very basic Canvas helpers. | |||
But apart from that, the '''oscilloscope''' itself may be an useful tool for developers and coders. Although I do not know any aircraft that has this instrument in its panel, the on-board engineer will eventually appreciate having it on hand at some point. | |||
-- | See [[Oscilloscope addon]] | ||
{{-}} | |||
=== Aircraft Dialogs === | |||
[[File:Extra500-Failuredialog-deice.png|right|thumb|Extra 500 - failure dialog - de-ice]] | |||
[[File:Propellant dlg02.jpg|thumb|right|An example of the detail dialog which allows to set levels of fuel and oxidizer separately (and the overview dialog shows the usable propellant then, i.e. the minimum of the two) - for aircraft, this would be somewhat simpler.]] | |||
Some of you may already know that the current tool to generate the dialogs ([[PUI]]) is going to disappear in the mid-future. After some (partially controversial) discussion, there seems now to be some support for the idea that canvas is a good tool to generate aircraft-specific dialogs in the future (as it allows to tailor the dialog closely to the plane and also, canvas being canvas, the UI can smoothly mesh with the 3d models, so you can project a canvas checklist onto a 3d model in sim for instance rather than a popup window). | |||
Thorsten would very much like to claim to be pioneering this approach, but in fact he believes the [[Extra EA-500|Extra-500 team]] is - look at the [[Extra_EA-500/failure_dialog|failure dialog of that plane]] where you can click the components you want to fail and you see what he means! | |||
Anyway, Thorsten has started to roll out a few designs of his own and try to keep the tools fairly general so that they can be re-used by others- so here's the revised version of the Shuttle propellant dialog. | |||
== | The general idea is to use semi-transparent 'content gauges' on a background raster image to show where the tank is located and how full it currently is - double-clicking any tank will bring up a detail window which allows to set the content (here propellant and oxidier separately, this is rocket fuel...) and also shows the current tank pressures and temperatures. | ||
The whole thing can readily be applied on top of a different raster image with a different number of tanks - you just instance and position the labels and 'gauges' you need - in fact placement is probably what's going to take longest (at least for me). | |||
< | The whole thing is currently in flux <ref>{{cite web | ||
|url = https://forum.flightgear.org/viewtopic.php?p=326789&sid=c15d338facab18fb091aa0530f5dfa0f#p326789 | |||
|title = <nowiki> Aircraft-specific dialogs </nowiki> | |||
|author = <nowiki> Thorsten </nowiki> | |||
|date = Jan 24th, 2018 | |||
|added = Jan 24th, 2018 | |||
|script_version = 0.36 | |||
}}</ref> | |||
If anyone wants to follow the development or use the code, it's here: | |||
https://sourceforge.net/p/fgspaceshuttledev/code/ci/development/tree/Nasal/canvas/canvas_dialogs.nas | |||
=== FG1000 Updates === | === FG1000 Updates === | ||
| Line 71: | Line 136: | ||
Learn more at [[FG1000]] ... | Learn more at [[FG1000]] ... | ||
=== Airbus GPWS === | |||
FlightGear now provides better [[GPWS]] support for Airbus aircraft - the unit which triggers voice alerts like "''Pull up!''" and altitude callouts ''...50-40-30-20-10''. The original FlightGear GPWS implementation was made to exactly match all details of a specific real-world hardware unit. The specific unit was never intended to be installed on Airbus aircraft, hence, so far lacked the Airbus-specific warnings and callouts. | |||
Starting with FG2018.1, the FlightGear GPWS unit was extended with optional support for Airbus callouts. The short description of how to enable the Airbus mode is: set the "category-4" configuation value in the "mk-viii" section of the aircraft's "...-set.xml" file to "1000". The long and detailed description is: read the [[GPWS#Altitude_Callouts|Wiki page]]. :-) You can also improve the realism of the unit by providing more realistic Airbus-style voice samples (.wav files). | |||
'''So, what's different with an Airbus GPWS then?''' | |||
While some callouts may depend on an airline's company policy, there's usually several voice alerts specific to Airbus, which are not to be heard on a Boeing aircraft. | |||
* '''2500'''!: When landing with an Airbus, you'll hear the first GPWS altitude announcement earlier - starting with an early "''2500''" callout when descending below 2500ft. | |||
* '''Hundred above!''': An additional "''Hundred above!''" callout is issued at 100ft above the ''selected decision height''. The decision height is the altitude where the crew needs to make their final decision whether to continue with the approach or whether they need to abort due to bad visibility. The "''Hundred above!''" callout gives an Airbus crew some extra time to make up their minds. Seconds later, the actual decision height is then announced by the "Minimums!" callout - which is also common with Boeing and many other aircraft. | |||
* '''Retard! Retard! Retard!''': Retard? Well, yes. This is the infamous Airbus-specific callout which has caused thousands of teenagers to leave more or less funny comments and questions on YouTube Airbus cockpit videos. The "''Retard!''" callout is triggered, when an Airbus decends below 20-30ft above the runway and the thrust-levers are not yet set to idle. The callouts reminds the crew to "''Retard the thrust-levers '''now'''!''". So, why did Airbus decide to use the word "retard"? Well, since the engineers certainly didn't care about teenage YouTube comments. Instead, they needed to find a word which is short and also uniquely connected to a thrust-lever. Something like "''Pull the thrust-levers all the way back to idle now!''" would have been far to long - and also "''pull''" is already associated with the yoke/stick (remember the "''Pull up! Pull up!''" alert). "Retard" is nice and short - and certainly not connected with any other control input. So, on an Airbus, you simply "''retard the thrust-levers to idle''" just before landing the aircraft... | |||
== New software tools and projects == | == New software tools and projects == | ||
Sidi has updated the iOS version of FGYoke and make it available on AppStore recently. | Sidi has updated the iOS version of FGYoke and make it available on AppStore recently. | ||
For details, check [[ | For details, check [[Yoke for FlightGear]] | ||
[[File:Screenshot of FGYoke in AppStore.png|thumbnail| | [[File:Screenshot of FGYoke in AppStore.png|thumbnail|center|Screenshot of FGYoke in AppStore]] | ||
<!-- Those not being part of FlightGear itself, like for example OpenRadar, TerreMaster or flightgear-atc.alwaysdata.net. --> | <!-- Those not being part of FlightGear itself, like for example OpenRadar, TerreMaster or flightgear-atc.alwaysdata.net. --> | ||
| Line 85: | Line 162: | ||
<!-- === New aircraft === --> | <!-- === New aircraft === --> | ||
=== Aérospatiale SA 315B Lama === | |||
[[File:Lama Sunset.png|thumb|Screenshot of Lama 315B at sunset]] | |||
[[File:Lama Overhead.png|thumb|Overhead panel for SA 315B Lama]] | |||
The FGUK Development team are very pleased to announce the '''Aérospatiale SA 315B Lama''' for FlightGear. An incredibly accurate model with a selection of liveries, equipment loadouts and a totally custom FDM for flying by the book | |||
More photos on the [https://www.facebook.com/FlightGearUK/ FGUK Facebook Page] | |||
[http://www.http://fguk.eu/index.php/hangar/download/13-rotary-wing/558-aerospatiale-sa-315b-lama Download here] | |||
<!-- === Updated aircraft === --> | <!-- === Updated aircraft === --> | ||
| Line 92: | Line 178: | ||
<!-- === Aircraft reviews === --> | <!-- === Aircraft reviews === --> | ||
== AI == | <!-- == AI == --> | ||
== Scenery corner == | <!-- == Scenery corner == --> | ||
<!-- Scenery development news --> | <!-- Scenery development news --> | ||
| Line 166: | Line 252: | ||
==== Screenshot of the Month ==== | ==== Screenshot of the Month ==== | ||
FlightGear's Screenshot of the Month January 2017 is '''Flying high with the Lama''' by StuartC | |||
[[File:SOTM-Jan18.jpg|900px|center|Flying high with the Lama - StuartC]] | |||
If you want to participate in the screenshot contest of | If you want to participate in the screenshot contest of February 2018, you can submit your candidate to [https://forum.flightgear.org/viewtopic.php?f=19&t=33703 this] forum topic. Be sure to see the [https://forum.flightgear.org/viewtopic.php?f=19&t=33703#p327123 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 in the Newsletter edition of February 2018. | ||
''Thanks for reading {{PAGENAME}}!'' | |||
{{Appendix}} | |||
[[Category:FlightGear Newsletter|2018 01]] | [[Category:FlightGear Newsletter|2018 01]] | ||
[[Category:Changes after 2017.3]] | [[Category:Changes after 2017.3]] | ||
[[de:FlightGear Newsletter Januar 2018]] | [[de:FlightGear Newsletter Januar 2018]] | ||