FlightGear Newsletter August 2015: Difference between revisions

Jump to navigation Jump to search
Cleanup
(Cleanup)
Line 1: Line 1:
{{draft|newsletter|Please feel free to add content you think will be of interest to the FlightGear community. You can read the latest newsletter at [[FlightGear Newsletter July 2015]].}}
{{Newsletter-header|August 2015}}
{{Newsletter-header|August 2015}}
<div style="border-bottom:3px double #BBB;">
<div style="border-bottom:3px double #BBB;">
Line 10: Line 8:
[[#Thunderstorms|Thunderstorms]]<br>
[[#Thunderstorms|Thunderstorms]]<br>
[[#Irradiance maps|Irradiance maps]]<br/>
[[#Irradiance maps|Irradiance maps]]<br/>
[[#Tracking FlightGear RAM/VRAM Utilization|Tracking FlightGear RAM/VRAM Utilization]]</br>
[[#Tracking FlightGear RAM/VRAM Utilization|Tracking FlightGear RAM/VRAM Utilization]]
{{Newsletter-cover-header|In the hangar}}
  | valign="top" width="33%" |
  | valign="top" width="33%" |
{{Newsletter-cover-header|Scenery Corner}}<br>
{{Newsletter-cover-header|Scenery Corner}}<br>
Line 17: Line 14:
[[#Belgium|Belgium]]<br>
[[#Belgium|Belgium]]<br>
[[#Venezuela|Venezuela]]<br>
[[#Venezuela|Venezuela]]<br>
[[#Saudi Arabia|Saudi Arabia]]<br>
[[#Saudi Arabia|Saudi Arabia]]
| valign="top" width="33%" |
{{Newsletter-cover-header|Community News}}<br>
{{Newsletter-cover-header|Community News}}<br>
[[#Wiki updated to MediaWiki 1.25|Wiki updated to MediaWiki 1.25]]<br/>
[[#Wiki updated to MediaWiki 1.25|Wiki updated to MediaWiki 1.25]]<br/><br/>
| valign="top" width="33%" |
{{Newsletter-cover-header|Contributing}}<br>
{{Newsletter-cover-header|Contributing}}<br>
[[#Translators required|Translators required]]<br>
[[#Translators required|Translators required]]<br>
[[#FlightGear logos|FlightGear logos]]<br>
[[#FlightGear logos|FlightGear logos]]<br>
[[#Screenshots|Screenshots]]<br/>
[[#Screenshots|Screenshots]]
<small>[[#Screenshot of the month|Screenshot of the month]]<br/></small>
|}</div>
|}</div>


Line 32: Line 28:
=== FlighGear v3.6 release ===
=== FlighGear v3.6 release ===
{{FGCquote|1= As many people have noticed, the v3.6 release has been slightly delayed. The main reason is that too many key developers have been out of town for work or holiday this month. We are currently hoping for a mid-September release. We will post further updates once our release manager returns and we can regroup from all the end of the summer (northern hemisphere) :-) activities. Thank you, Curt.|2= {{cite web  | url    = http://sourceforge.net/p/flightgear/mailman/message/34407279/  | title  = <nowiki>[Flightgear-devel] Release v3.6 update</nowiki>  | author = <nowiki>Curtis Olson</nowiki>  | date  = Aug 26th, 2015  }}}}
{{FGCquote|1= As many people have noticed, the v3.6 release has been slightly delayed. The main reason is that too many key developers have been out of town for work or holiday this month. We are currently hoping for a mid-September release. We will post further updates once our release manager returns and we can regroup from all the end of the summer (northern hemisphere) :-) activities. Thank you, Curt.|2= {{cite web  | url    = http://sourceforge.net/p/flightgear/mailman/message/34407279/  | title  = <nowiki>[Flightgear-devel] Release v3.6 update</nowiki>  | author = <nowiki>Curtis Olson</nowiki>  | date  = Aug 26th, 2015  }}}}
=== ATC-pie tower viewing ===
=== ATC-pie tower viewing ===
[[File:ATC-pie-logo.png|90px|left|ATC-pie logo.]]
[[File:ATC-pie-logo.png|90px|left|ATC-pie logo.]]
For when most of the Northern (resp. Southern) hemisphere comes back to FlightGear from their summer (resp. winter) holiday time off, new [[ATC-pie]] r6 has come out this month, featuring a '''tower viewing system''' working for '''both solo and multi-player''' games. It uses FlightGear to render the airport scene, and allows to overlook ground traffic and follow airborne aircraft in the surroundings. An integrated packet forwarding system also allows to connect to multiple views for all sorts of camera shots.
For when most of the Northern (resp. Southern) hemisphere comes back to FlightGear from their summer (resp. winter) holiday time off, new [[ATC-pie]] r6 has come out this month, featuring a '''tower viewing system''' working for '''both solo and multi-player''' games. It uses FlightGear to render the airport scene, and allows to overlook ground traffic and follow airborne aircraft in the surroundings. An integrated packet forwarding system also allows to connect to multiple views for all sorts of camera shots.


[[File:ATC-pie-screenshot-towerViewing.png|550px|Following a departing aircraft at good old San Francisco int'l, with the basic FG scenery]]
[[File:ATC-pie-screenshot-towerViewing.png|600px|Following a departing aircraft at good old San Francisco int'l, with the basic FG scenery]]


Also added in this new version:
Also added in this new version:
Line 76: Line 73:


=== Tracking FlightGear RAM/VRAM Utilization ===
=== Tracking FlightGear RAM/VRAM Utilization ===
[[File:Sigar-support.png|thumb|Screen shot showing the property browser running on Netbook in a patched version of FlightGear with [[Resource Tracking for FlightGear|resource tracking support]] using the cross platform SIGAR library.]]
[[File:Sigar-memory.png|thumb|Screen shot showing the property browser running on Netbook in a patched version of FlightGear with [[Resource Tracking for FlightGear|resource tracking support]] using the cross platform SIGAR library.]]
[[File:Sigar-cpu-info.png|thumb|CPU information exposed to the property tree using the SIGAR library]]
{{FGCquote|1= We've been resurrecting and extending an old patch to track FlightGear resource utiliation (primarily RAM and VRAM for the time being), and are hoping to extend the patch over time - currently, this is specific to Linux and has only been tested with NVIDIA GPUs. So we're now looking for people who are able to build from source (e.g. using the Superbuild and/or the fgbuild script), who are willing to help integrate/test and develop this for platforms to which we don't have access ourselves.
{{FGCquote|1= We've been resurrecting and extending an old patch to track FlightGear resource utiliation (primarily RAM and VRAM for the time being), and are hoping to extend the patch over time - currently, this is specific to Linux and has only been tested with NVIDIA GPUs. So we're now looking for people who are able to build from source (e.g. using the Superbuild and/or the fgbuild script), who are willing to help integrate/test and develop this for platforms to which we don't have access ourselves.


Line 90: Line 81:
[[File:KSFO memory usage.png|250px]]
[[File:KSFO memory usage.png|250px]]
For some background info, please refer to: [[Resource Tracking for FlightGear]]|2= {{cite web  | url    = http://forum.flightgear.org/viewtopic.php?p=254967#p254967  | title  = <nowiki>Looking for people with ATI/AMD GPUs building from source</nowiki>  | author = <nowiki>Hooray</nowiki>  | date  = Aug 25th, 2015  }}}}
For some background info, please refer to: [[Resource Tracking for FlightGear]]|2= {{cite web  | url    = http://forum.flightgear.org/viewtopic.php?p=254967#p254967  | title  = <nowiki>Looking for people with ATI/AMD GPUs building from source</nowiki>  | author = <nowiki>Hooray</nowiki>  | date  = Aug 25th, 2015  }}}}
<gallery mode=packed widths=230px heights=230px>
Sigar-support.png|Screen shot showing the property browser running on Netbook in a patched version of FlightGear with [[Resource Tracking for FlightGear|resource tracking support]] using the cross platform SIGAR library.
Sigar-memory.png|Screen shot showing the property browser running on Netbook in a patched version of FlightGear with [[Resource Tracking for FlightGear|resource tracking support]] using the cross platform SIGAR library.
Sigar-cpu-info.png|CPU information exposed to the property tree using the SIGAR library
</gallery>


== In the hangar ==
== In the hangar ==

Navigation menu