8,814
edits
FlightGear Newsletter January 2013: Difference between revisions
Jump to navigation
Jump to search
FlightGear Newsletter January 2013 (view source)
Revision as of 16:43, 3 February 2013
, 3 February 2013Prepare for publishing
No edit summary |
(Prepare for publishing) |
||
| Line 1: | Line 1: | ||
{{newsletter}} | {{newsletter}} | ||
{{TOC_right|limit=2}} | {{TOC_right|limit=2}} | ||
| Line 7: | Line 5: | ||
== Development news == | == Development news == | ||
With just two more weeks to go till the release of FlightGear 2.10, you are encouraged to test the release candidates | With just two more weeks to go till the release of FlightGear 2.10, you are encouraged to test the release candidates! These are basically complete releases, meant for testing by a large group of people. Bugs found (and reported!) during these tests have a fair chance getting fixed. Do note that the earlier bugs are reported, the more time we'll have to fix them. | ||
You can download the latest release | You can download the latest release candidates [http://www.flightgear.org/download/ from our website]. Please install it in a special directory, away from your current FlightGear. | ||
Bugs should be reported [http://code.google.com/p/flightgear-bugs/issues/entry?template=Release%20candidate at our bug tracker], while questions or comments about the release candidate are welcome at [http://www.flightgear.org/forums/viewforum.php?f=68 our special subforum | Bugs should be reported [http://code.google.com/p/flightgear-bugs/issues/entry?template=Release%20candidate at our bug tracker], while questions or comments about the release candidate are welcome at [http://www.flightgear.org/forums/viewforum.php?f=68 our special subforum]. | ||
=== State Machines === | === State Machines === | ||
James added initial support for state-machines to the XML autopilot code. This expands on the existing stateful flip-flop components, to allow arbitrarily complex collections of states and transitions between them. Each transition is controlled by a usual XML condition, and state and transitions can run arbitrary commands when activated. This system allows high-level control of complex auto-flight modes, without requiring a mixture of Nasal and XML. For example the armed / engaged / disarm states of many auto-flight subsystems (e.g., auto-brakes and auto-spoilers) can be expressed in a way that models the functional description. | James added initial support for state-machines to the XML autopilot code. This expands on the existing stateful flip-flop components, to allow arbitrarily complex collections of states and transitions between them. Each transition is controlled by a usual XML condition, and state and transitions can run arbitrary commands when activated. This system allows high-level control of complex auto-flight modes, without requiring a mixture of Nasal and XML. For example the armed / engaged / disarm states of many auto-flight subsystems (e.g., auto-brakes and auto-spoilers) can be expressed in a way that models the functional description. | ||
Of course the state-machine concept has uses beyond auto-flight systems, for example it could be used to drive GUI dialog logic, but that's left as an exercise for the reader! | Of course the state-machine concept has uses beyond auto-flight systems, for example it could be used to drive GUI dialog logic, but that's left as an exercise for the reader! | ||
=== Canvas-based CDU development === | === Canvas-based CDU development === | ||
| Line 43: | Line 31: | ||
=== Procedural Terrain Texturing === | === Procedural Terrain Texturing === | ||
For users with powerful graphics cards, a much improved version of [[Procedural Texturing]] of the | For users with powerful graphics cards, a much improved version of [[Procedural Texturing]] of the FlightGear terrain (which is as of now implemented under the [[Atmospheric light scattering]] framework) is currently being developed. This generates highly detailed visuals of the terrain seen from close-up (the smallest structures generated are of 1 cm scale), including a gentle bump-mapping, grain overlay and optional sparse-dot noise generated rocks or grass patches. | ||
[[File:hires_terrain01.jpg|300px|Hires terrain - Lanai shrub cover]] | [[File:hires_terrain01.jpg|300px|Hires terrain - Lanai shrub cover]] | ||
| Line 57: | Line 45: | ||
Note that this feature will not be available for the 2.10 release, as it requires still some testing. | Note that this feature will not be available for the 2.10 release, as it requires still some testing. | ||
=== | === TerraGear === | ||
The master branch of | The master branch of TerraGear has recently seen more enhancements and cleanup. Most of the functionality has been put into a single TerraGear library for reuse in all tools. Furthermore, all essential parts of the toolchain now support multithreading. The multiprocess support for genapts has been removed in favour of threading as well. | ||
Most of the functionality has been put into a single | |||
Furthermore, all essential parts of the toolchain now support multithreading. The multiprocess support for genapts has been removed in favour of threading as well. | |||
Work continues on the elevation tools. GDALchop has been re-activated and should become the prior tool to chop up elevation source files into buckets. As it relies on the well-established codebase of GDAL, it takes away the task of opening and reading the different kinds of elevation files from the terragear developers. Supported formats can be seen at http://www.gdal.org/formats_list.html | |||
== Translators required == | == Translators required == | ||
| Line 117: | Line 64: | ||
|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 [[:es:Help:Traducir|Help:Traducir]]. | |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 [[:es:Help:Traducir|Help:Traducir]]. | ||
|} | |} | ||
== Scenery corner == | == Scenery corner == | ||
=== Regional texturing === | === Regional texturing === | ||
More regional texturing definitions are arriving on GIT! Hawaii has just received an update to make full use of procedural texturing techniques - see [http://www.flightgear.org/tours/fly-hawaii Fly Hawaii!] for some additional info. Indonesia has arrived on GIT, and the Middle East region is currently being worked on - look forward to some nice variety in scenery in the future. | More regional texturing definitions are arriving on GIT! Hawaii has just received an update to make full use of procedural texturing techniques - see [http://www.flightgear.org/tours/fly-hawaii Fly Hawaii!] for some additional info. Indonesia has arrived on GIT, and the Middle East region is currently being worked on - look forward to some nice variety in scenery in the future. | ||
| Line 148: | Line 74: | ||
(Other regions having received regional texturing definitions so far include Europe, South American rain forest belt, Iceland and the Caribbean.) | (Other regions having received regional texturing definitions so far include Europe, South American rain forest belt, Iceland and the Caribbean.) | ||
== Community news == | == Community news == | ||
=== | === Forum news === | ||
[[File:FlightGear_forum_index_mobile_theme.png|thumb|Mobile theme of the FlightGear forum.]] | |||
To ease the use of [http://flightgear.org/forums|the FlightGear forum] on mobile (small screen) devices, a special mobile theme has been created. You should see the mobile theme automatically when you visit the forum on a device with a screen size of 640 pixels or smaller. | |||
The basic layout works, but there are still parts left waiting for optimisation. Therefore, certain features may not be available or might not function properly. You can turn back to the normal layout at any time by clicking a link at the bottom of each page. | |||
=== Virtual airlines === | === Virtual airlines === | ||
FlightGear has a brand new airline, [[Galaxy Virtual Airlines]] has now commenced operations created by George9 & Sbyx. They are currently desprate for pilots & help so go and visit their website. | |||
== And finally ... == | == And finally ... == | ||
=== Contributing === | === Contributing === | ||
| Line 201: | Line 97: | ||
* The [[Target4Today]] team is looking for volunteers to help improving FlightGear's combat support | * The [[Target4Today]] team is looking for volunteers to help improving FlightGear's combat support | ||
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer. | * The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer. | ||
[[Category:FlightGear Newsletter|2013 01]] | [[Category:FlightGear Newsletter|2013 01]] | ||