FlightGear Newsletter December 2011: Difference between revisions

Jump to navigation Jump to search
m
add bunch of mailing list news, some of them dating back as far as November - which were not yet mentioned in the previous edition, easiest way to populate the newsletter like this! :-)
m (→‎Logo & banner contest: add demo banner)
m (add bunch of mailing list news, some of them dating back as far as November - which were not yet mentioned in the previous edition, easiest way to populate the newsletter like this! :-))
Line 10: Line 10:
=== Aircraft maintenance ===
=== Aircraft maintenance ===
Some bug fixes and improvements require aircraft to be adapted/fixed to remain airworthy, to be working correctly, or to be taking full advantage of latest FlightGear version. This is why some developers now went ahead and created a check list including guide lines on maintaining aircraft, please see [[Aircraft maintenance]] for more info.
Some bug fixes and improvements require aircraft to be adapted/fixed to remain airworthy, to be working correctly, or to be taking full advantage of latest FlightGear version. This is why some developers now went ahead and created a check list including guide lines on maintaining aircraft, please see [[Aircraft maintenance]] for more info.
=== Improving random trees & buildings ===
Some core developers have been thinking about ways to improve our random scenery, in particular buildings and vegetation. For more details see [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35035.html].
=== Marketting of 2.6.0 via FS Break podcast ===
The idea was raised to market FlightGear using the FS Break podcast, for more details please check: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35023.html]
=== Trying to get more performance out of the 3D clouds! ===
There has been quite a lengthy discussion on optimizing FlightGear's 3D clouds even more, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35092.html] and [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35100.html].
=== Improvements to the radio code in FlightGear ===
The FlightGear radio code has been recently overhauled, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35010.html].
=== Southwest Colorado Scenery - beta 4 ===
New custom built scenery has been made available for the region of Southwest Colorado Scenery, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34986.html]
=== Shader dialog revamp completed ===
Gijs has been working hard to revamp the shader dialog, for more details please see [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34919.html].
=== Sound support for AI traffic ===
Erik has been working on implementing an FGFX class for AIModels and is pretty much done, a first stab at the sound code has been committed now. For more info see [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34985.html].
=== New performance dialog ===
FlightGear core developer ThorstenB has added a new subsystem and a dialog to monitor FG performance. It's  replacing/improving the original code which was only capable of writing statistics data to the console (presumably, few people ever used or were even aware of the old option). The new GUI dialog is available in the menu: "Debug" => "Monitor system performance". More info is available here: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34886.html]. A screen shot can be found here: http://imageshack.us/photo/my-images/521/fgfsscreen031.png/


=== Shaders ===
=== Shaders ===

Navigation menu