FlightGear Newsletter February 2010: Difference between revisions

Jump to navigation Jump to search
m
livery database + Dutch airports
m (livery database + Dutch airports)
Line 3: Line 3:
Welcome to the February 2010 edition of the [[FlightGear]] Newsletter.  
Welcome to the February 2010 edition of the [[FlightGear]] Newsletter.  


The big news this month is that FlightGear v2.0 was released on 27th February, and is available for download from [http://www.flightgear.org www.flightgear.org] and mirrors.  
The big news this month is that FlightGear v2.0 was released on the 25th of February, and is available for download from [http://www.flightgear.org www.flightgear.org] and mirrors.  


This is obviously very exciting, and represents a huge amount of work by the developers over the last year. As you can see from the release [http://www.flightgear.org/version.html version summary], there have been a whole host of changes since v1.9.1
This is obviously very exciting, and represents a huge amount of work by the developers over the last year. As you can see from the release [http://www.flightgear.org/version.html version summary], there have been a whole host of changes since v1.9.1
==FlightGear 2.0.0==
On February 25, 2010, FlightGear v2.0.0, successor of 1.9.1, was released with binary downloads for Windows being made available.
Since the last release, FlightGear has improved dramatically with such things as ultra-realistic [[3D clouds]] and dynamic water. A summary of new features can be seen at [http://www.flightgear.org/version.html our website].


==What's new in CVS==
==What's new in CVS==


== Finally: Bug Tracking ==
== Finally: Bug Tracking ==
As of February 2010, fellow FlightGear developers and users are encouraged <sup>[http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg26333.html][http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg26380.html]</sup> to file ''bug'' reports using http://code.google.com/p/flightgear-bugs/issues/list


As of February 2010, fellow FlightGear developers and users are encouraged [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg26333.html] [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg26380.html] to file ''bug'' reports using
Please note that this tracker is at the moment purely meant to be used for ''bug tracking'' purposes <sup>[http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg26354.html]</sup>, i.e. bugs directly related to FlightGear and not for feature requests (there are plans being discussed to eventually set up a separate tracker for these <sup>[http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg26357.html]</sup>).
http://code.google.com/p/flightgear-bugs/issues/list
 
Please note that this tracker is at the moment purely meant to be used for ''bug tracking'' purposes [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg26354.html], i.e. bugs directly related to FlightGear and not for feature requests (there are plans being discussed to eventually set up a separate tracker for these [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg26357.html]).


At the moment, this tracker is being used for both, FlightGear core, as well as the base package (aircraft, scenery etc) - this may however change at a later time once the tracker is being used more widely to help developers differentiate between core coding related issues and those that are related to base package contributions such as individual aircraft [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg26342.html].
At the moment, this tracker is being used for both, FlightGear core, as well as the base package (aircraft, scenery etc) - this may however change at a later time once the tracker is being used more widely to help developers differentiate between core coding related issues and those that are related to base package contributions such as individual aircraft <sup>[http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg26342.html]</sup>.


==In the hangar==
==In the hangar==
===Livery database is growing===
In the January newsletter we announced the new, more or less official, [http://liveries.flightgear.org livery database]. In the past two weeks, over 250 people (unique visitors) from over 35 countries have visited the database.


==FlightGear 2.0==
A lot of liveries were added over the past month, resulting in a pretty complete database of available liveries, with almost 170 unique liveries. However, it is possible that there are still liveries missing that were available with the old list. Such liveries can be uploaded through the [http://liveries.flightgear.org/contribute.php contribute page]. Newly made liveries are welcome as well!
 
On February 25, 2010, FlightGear v2.0.0 was released with binary downloads for Windows being made available.
 
Since the last release, FlightGear has improved dramatically with such things as 3D clouds. Please see documentation for more details.
 
Onwards, towards 3.0.


==Scenery Corner==
==Scenery Corner==
===All Dutch airports available===
With the upcoming [[scenery]] release, all Dutch [[:Category:Airports|airports]] and [[FlightGear User Created Helipad List|heliports]] will be available. A couple of airports have been updated, as well as some missing airports were added.


== New Wiki Articles ==
== New Wiki Articles ==


=== Creating Textures for 3D Clouds ===
=== Creating Textures for 3D Clouds ===
As of February 2010, the FlightGear wiki now provides a fairly comprehensive introduction about creating custom and new 3D cloud textures for use in FlightGear, this will enable community members to start modifying and improving existing FlightGear cloud textures, or even create textures for completely new cloud types so that the visual FlightGear experience may become more appealing soon. Please see [[Howto: Modelling Clouds]] for details.
As of February 2010, the FlightGear wiki now provides a fairly comprehensive introduction about creating custom and new 3D cloud textures for use in FlightGear, this will enable community members to start modifying and improving existing FlightGear cloud textures, or even create textures for completely new cloud types so that the visual FlightGear experience may become more appealing soon. Please see [[Howto: Modelling Clouds]] for details.


==Community News==
==Community News==


===TransGear Airways holds its largest gathering yet===
===TransGear Airways held its largest gathering yet===
'''TransGear Airways''' is a cross between a [[Virtual airlines|virtual airline]] and a monthly [[:Howto: Multiplayer|multiplayer]] event organized by Rob Shearman (aka "MD-Terp"). It was founded last summer as a means to bring together pilots who are interested in flying passenger transports in a simulated environment containing a moderately busy controlled airspace. It began by utilizing typed multiplayer chat messages to issue [[Air Traffic Control]] directives, but thanks to further development of [[FGCOM|FGCom]], the event has moved exclusively to voice-to-voice communication.
'''TransGear Airways''' is a cross between a [[Virtual airlines|virtual airline]] and a monthly [[:Howto: Multiplayer|multiplayer]] event organized by Rob Shearman (aka "MD-Terp"). It was founded last summer as a means to bring together pilots who are interested in flying passenger transports in a simulated environment containing a moderately busy controlled airspace. It began by utilizing typed multiplayer chat messages to issue [[Air Traffic Control]] directives, but thanks to further development of [[FGCOM|FGCom]], the event has moved exclusively to voice-to-voice communication.


Line 57: Line 57:




[[Category:FlightGear Newsletter|2009 12]]
[[Category:FlightGear Newsletter|2010 2]]

Navigation menu