8,560
edits
FlightGear Newsletter August 2012: Difference between revisions
Jump to navigation
Jump to search
FlightGear Newsletter August 2012 (view source)
Revision as of 12:14, 2 September 2012
, 2 September 2012Cleanup
m (→Useful links) |
(Cleanup) |
||
| Line 9: | Line 9: | ||
http://www.flightgear.org/news/flightgear-v2-8-0-released/ | http://www.flightgear.org/news/flightgear-v2-8-0-released/ | ||
Major improvements from v2.6.0 include improved AI aircraft, up to date with all the recent JSBSim flight dynamics model improvements, support for region specific textures, better random 3d buildings, better random object placement, 3d airport signage, in-sim toggling between summer and winter texture sets. The core FlightGear code now supports a flexible 2d rendering system which can be used to accurately model glass cockpit displays and other complex instrumentation. There are many new and improved aircraft to explore. A new automated system is now available for scenery submissions that automatically get rolled into the scenery distribution to be enjoyed by everyone. Version 2.8 has improved atmospheric light scatter modeling, better terrain haze, and improved 3d clouds. | Major improvements from v2.6.0 include improved AI aircraft, up to date with all the recent JSBSim flight dynamics model improvements, support for region specific textures, better random 3d buildings, better random object placement, 3d airport signage, in-sim toggling between summer and winter texture sets. The core FlightGear code now supports a flexible 2d rendering system which can be used to accurately model glass cockpit displays and other complex instrumentation. There are many new and improved aircraft to explore. A new automated system is now available for scenery submissions that automatically get rolled into the scenery distribution to be enjoyed by everyone. Version 2.8 has improved atmospheric light scatter modeling, better terrain haze, and improved 3d clouds. | ||
| Line 16: | Line 14: | ||
A very exciting new addition is “Project Rembrandt”. This is still considered “experimental” and not enabled by default. But when you turn it on you will get real-time shadows, support for multiple light sources (landing lights, instrument lights, directional ground spotlights, even the rotating beacons illuminate the surrounding correctly.) In addition, Project Rembrandt offers a variety of other visual effects such as night vision, film grain effects, depth of field effects, lens (i.e. fisheye) distortion — all in real time. | A very exciting new addition is “Project Rembrandt”. This is still considered “experimental” and not enabled by default. But when you turn it on you will get real-time shadows, support for multiple light sources (landing lights, instrument lights, directional ground spotlights, even the rotating beacons illuminate the surrounding correctly.) In addition, Project Rembrandt offers a variety of other visual effects such as night vision, film grain effects, depth of field effects, lens (i.e. fisheye) distortion — all in real time. | ||
For the full change log, please see [ | For the full change log, please see [http://www.flightgear.org/news/flightgear-v2-8-0-released/ the release announcement]. | ||
Enjoy!!! | Enjoy!!! | ||
| Line 43: | Line 41: | ||
| [[File:Fgfs-rembrandt-night-vision-2.png|thumb|400px|Rembrandt night vision simulation]] | | [[File:Fgfs-rembrandt-night-vision-2.png|thumb|400px|Rembrandt night vision simulation]] | ||
|} | |} | ||
This | This did not make it for the 2.8 release but it's likely that an add-on will be available as it is contained in the data. | ||
See also : | See also : | ||
| Line 52: | Line 50: | ||
|} | |} | ||
=== Unified | === Unified weather GUI === | ||
As most readers will be aware, | As most readers will be aware, FlightGear supports two weather models - Basic Weather which represents METAR data directly, and Local Weather which models weather more realistically, with more variation. In 2.8.0 these were configured separately using different UIs. Stuart Buchanan and Thorsten Renk have been working on unifying the user interfaces to provide a more user-friendly and consistent interface. This work is now available in git. | ||
=== Joystick | === Joystick configuration GUI === | ||
[[File:Joystick Configuration Dialog.jpg|thumb|The new Joystick Configuration Dialog, available in git.]] | [[File:Joystick Configuration Dialog.jpg|thumb|The new Joystick Configuration Dialog, available in git.]] | ||
A further usability enhancement has been made by Stuart Buchanan to allow configuration of joysticks through a GUI in-sim. Instead of configuring a joystick using XML, users can now change joystick bindings within the simulator - no XML knowledge required. The updated joystick configuration takes effect immediately. This work is also available in git, and should make it much easier for new users (or those with joysticks unknown to | A further usability enhancement has been made by Stuart Buchanan to allow configuration of joysticks through a GUI in-sim. Instead of configuring a joystick using XML, users can now change joystick bindings within the simulator - no XML knowledge required. The updated joystick configuration takes effect immediately. This work is also available in git, and should make it much easier for new users (or those with joysticks unknown to FlightGear) to get flying. | ||
=== Canvas | === Canvas news === | ||
As of August, the new [[Canvas]] 2D drawing system in FlightGear HEAD has now also support for: | |||
As of | |||
* using raster images (vector images were already supported previously) | * using raster images (vector images were already supported previously) | ||
* nested canvases, where a canvas may contain images created by another canvas texture [[Howto:Using raster images and nested canvases]] | * nested canvases, where a canvas may contain images created by another canvas texture [[Howto:Using raster images and nested canvases]] | ||
| Line 94: | Line 90: | ||
Hooray and TheTom have now started collecting ideas on how this could be changed, by making subsystem initialization more explicit using listeners, so that SGSubsystems can be dynamically allocated and freed based on setting signal properties, so that recursive run levels can be implemented. For more information, please see [[FlightGear Run Levels]]. Feedback welcome! | Hooray and TheTom have now started collecting ideas on how this could be changed, by making subsystem initialization more explicit using listeners, so that SGSubsystems can be dynamically allocated and freed based on setting signal properties, so that recursive run levels can be implemented. For more information, please see [[FlightGear Run Levels]]. Feedback welcome! | ||
=== | === FlightGear On Android === | ||
[[File:Flightgear Android Launcher.png|thumb|FOA]] | |||
[[File:FOA.jpg|thumb|FOA ingame]] | |||
A new developer has achieved a way to run [[FlightGear on Android]] (FOA) phones. He has done a lot of Android and C++ coding. His phone is a Samsung Galaxy Nexus and is running Android 4.04 (custom ROM but stock ROM should be OK). If your ready to test with us, please read the technical info then send a email to lacbrc@gmail.com! | |||
His phone is a Samsung Galaxy Nexus and is running Android 4.04 (custom ROM but stock ROM should be OK). If your ready to test with us, please read the technical info then send a email to lacbrc@gmail.com! | |||
TECHNICAL INFO: | '''TECHNICAL INFO:''' | ||
It should have at least a 1GHz processor and decent graphics chip. Android 2.3 is a | It should have at least a 1GHz processor and decent graphics chip. Android 2.3 is a must but a rooted device is not needed but can improve performance. Not much in this, as we haven't finished it to a release yet. He tested it on a bluetooth keyboard and a wired one through usb host mode. Hope you are interested in it! | ||
must but a rooted device is not needed but can improve performance. | |||
Not much in this, as we haven't finished it to a release yet. | |||
He tested it on a bluetooth keyboard and a wired one through usb host mode. Hope you are interested in it! | |||
The first ALPHA release is fresh out of its release, and you can read more | The first ALPHA release is fresh out of its release, and you can read more [http://www.flightgear.org/forums/viewtopic.php?f=18&t=16719&p=163745#p163745 at the forum]. | ||
http://www.flightgear.org/forums/viewtopic.php?f=18&t=16719&p=163745#p163745 | |||
The FlightGear for Android Team | The FlightGear for Android Team | ||
* [http://horizonflightgearhangar.yolasite.com/fg-on-android.php Website] | |||
* [http://www.flightgear.org/forums/viewtopic.php?f=18&t=16719 Forum topic] | |||
http://horizonflightgearhangar.yolasite.com/fg-on-android.php | |||
http:// | |||
=== Getting involved as a programmer === | === Getting involved as a programmer === | ||
| Line 148: | Line 125: | ||
Unfortunately, we didn't find and interview candidate in August 2012. | Unfortunately, we didn't find and interview candidate in August 2012. | ||
== In the hangar == | == In the hangar == | ||
| Line 159: | Line 131: | ||
=== New aircraft === | === New aircraft === | ||
==== Yakovlev Yak 18T ==== | |||
[[File:Yak18t-splash.png|thumb|Yakovlev Yak 18T]] | |||
At the request by a new user of FG, Helijah has created and made available the Yakovlev Yak 18T in his hangar and GIT. | At the request by a new user of FG, Helijah has created and made available the Yakovlev Yak 18T in his hangar and GIT. | ||
==== [[ATC-FS]] | ==== ATC-FS ==== | ||
The Air Traffic Control tool ATC-FS got an update. The old radar screen was replaced by a radar screen, which can display fixes, navaids and ILS localizers. This new radar is resizable, so you can use your big screen more efficient. | [[Image:ATC-FS.jpg|thumb|ATC-FS radar screen.]] | ||
The Air Traffic Control tool [[ATC-FS]] got an update. The old radar screen was replaced by a radar screen, which can display fixes, navaids and ILS localizers. This new radar is resizable, so you can use your big screen more efficient. | |||
The next version is already being worked on, it will reimplement ATC-FS using the new [[Canvas]] system (scheduled for FG 3.0) so that a fully custom drawn radar screen can be created in scripting space, including custom GUI widgets (e.g. for flight strips) - without depending on any hard coded instruments or dialogs any longer. | The next version is already being worked on, it will reimplement ATC-FS using the new [[Canvas]] system (scheduled for FG 3.0) so that a fully custom drawn radar screen can be created in scripting space, including custom GUI widgets (e.g. for flight strips) - without depending on any hard coded instruments or dialogs any longer. | ||
| Line 170: | Line 143: | ||
This new design will eventually even make it possible to reuse ATC-FS for other purposes, or even include it in an AWACS aircraft that is multiplayer-enabled. | This new design will eventually even make it possible to reuse ATC-FS for other purposes, or even include it in an AWACS aircraft that is multiplayer-enabled. | ||
==== Mil Mi-6 ==== | |||
The big old russian helicopter [[Mil Mi-6]] from the Mil design bureau has received a new update. More than a year after the last update a new structure of the Models-subfolder allows new instruments to be added much easier. Also the electrical system has been revisited and new instruments have beed added to the engineer panels. Please keep in mind that this still is a very early development version and therefore a lot of work still needs to be done. It is available from its [https://gitorious.org/mil-mi-6 gitorious-page]. | |||
==== | |||
The big old russian helicopter Mi-6 from the Mil design bureau has received a new update. More than a year after the last update a new structure of the Models-subfolder allows new instruments to be added much easier. Also the electrical system has been revisited and new instruments have beed added to the engineer panels. Please keep in mind that this still is a very early development version and therefore a lot of work still needs to be done. It is available from its [https://gitorious.org/mil-mi-6 gitorious-page. | |||
== Scenery corner == | == Scenery corner == | ||
| Line 205: | Line 176: | ||
At this time of year, it's important to take into account the temperature and altitude of the airstrips, as they combine to sap the power and lift from GA aircraft. AVWeb recently [http://www.avweb.com/avwebflash/news/stinson_crash_cockpit_video_ntsb_faa_207184-1.html highlighted] the (non-fatal) crash of a [http://en.wikipedia.org/wiki/Stinson_108 Stinson 108], which included a video taken by one of the passengers. Though the NTSB has only produced a preliminary report, it was notable that the aircraft was taking off from a grass airstrip at high altitude on a hot day and appears from the video to struggle to get airborne. The Stinson is broadly similar in performance to the c172p in our base package, and the airstrip (Bruce Meadows Airport, Idaho - U63) exists in our scenery. Those interested can try taking off using the c172p with 4 people on board (2400lbs max gross weight) and high temperatures. McCall Municipal Airport (KMYL) is 44nm away, and a good destination. | At this time of year, it's important to take into account the temperature and altitude of the airstrips, as they combine to sap the power and lift from GA aircraft. AVWeb recently [http://www.avweb.com/avwebflash/news/stinson_crash_cockpit_video_ntsb_faa_207184-1.html highlighted] the (non-fatal) crash of a [http://en.wikipedia.org/wiki/Stinson_108 Stinson 108], which included a video taken by one of the passengers. Though the NTSB has only produced a preliminary report, it was notable that the aircraft was taking off from a grass airstrip at high altitude on a hot day and appears from the video to struggle to get airborne. The Stinson is broadly similar in performance to the c172p in our base package, and the airstrip (Bruce Meadows Airport, Idaho - U63) exists in our scenery. Those interested can try taking off using the c172p with 4 people on board (2400lbs max gross weight) and high temperatures. McCall Municipal Airport (KMYL) is 44nm away, and a good destination. | ||
== Community news == | == Community news == | ||
| Line 247: | Line 199: | ||
* The [[OpenRadar]] project is looking for a new maintainer. | * The [[OpenRadar]] project is looking for a new maintainer. | ||
* 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|2012 08]] | [[Category:FlightGear Newsletter|2012 08]] | ||