FlightGear Newsletter June 2013: Difference between revisions

Jump to navigation Jump to search
Prepare for publishing
(Prepare for publishing)
Line 1: Line 1:
{{newsletter}}
{{newsletter}}
{{TOC_right|limit=2}}
{{TOC_right|limit=2}}
Line 6: Line 5:


== Development news ==
== Development news ==
Note to all contributors: Please also copy your newsletter additions to the changelog for the upcoming release: [[Next Changelog]].
=== Release preparations ===
=== Release preparations ===
In line with the [[release plan]], the FlightGear repositories are frozen as of June 17. In this "frozen" state, no new features or major changes shall be pushed onto the development streams (neither source nor data). This period is for preparing the code for the release and make sure there are no major issues. It lasts for four weeks until creation of the release branches on July 17.
In line with the [[release plan]], the FlightGear repositories are frozen as of June 17. In this "frozen" state, no new features or major changes shall be pushed onto the development streams (neither source nor data). This period is for preparing the code for the release and make sure there are no major issues. It lasts for four weeks until creation of the release branches on July 17.
Line 14: Line 11:


=== TerraSync changes (libsvn replacement) ===
=== TerraSync changes (libsvn replacement) ===
SimGear 2.11+ now has experimental support for a webDAV based libsvn replacement, people building from source are encouraged to help with testing and debugging this new feature:
SimGear 2.11+ now has experimental support for a webDAV based libsvn replacement, people building from source are encouraged to help with testing and debugging this new feature:


{{cquote|<nowiki>First, I need some help; for people to rebuild simgear with -DSG_SVN_CLIENT=1, and mv / erase their TerraSync dir. Then simply run FGFS as normal, as if you were starting on a new machine / account with no previous use of TerraSync.</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40191.html|title=TerraSync libSVN replacement testing|author=James Turner|date=Tue, 11 Jun 2013 08:58:20 -0700}}</ref>|James Turner}}
{{cquote|<nowiki>First, I need some help; for people to rebuild simgear with -DSG_SVN_CLIENT=1, and mv / erase their TerraSync dir. Then simply run FGFS as normal, as if you were starting on a new machine / account with no previous use of TerraSync.</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40191.html|title=TerraSync libSVN replacement testing|author=James Turner|date=Tue, 11 Jun 2013 08:58:20 -0700}}</ref>|James Turner}}
 
Please provide feedback via the [http://flightgear-bugs.googlecode.com issue tracker].
Please provide feedback via the issue tracker.
 
<references/>
 
=== Random Buildings ===
<!-- These are currently just a bunch of placeholders for the latest projects (as of 08/2012)  -->


=== Project Rembrandt ===
=== Project Rembrandt ===
A number of Mac users have been reporting issues related to running [[Project Rembrandt]] (deferred rendering/shadows) on Mac OSX with ATI/AMD GPUS, we are now looking for Mac users to provide feedback on running Rembrandt on Mac OSX, required information includes errors and warnings shown during startup/runtime, but also screen shots showing any issues. Please see: [[Project Rembrandt#Mac Issues]].
A number of Mac users have been reporting issues related to running [[Project Rembrandt]] (deferred rendering/shadows) on Mac OSX with ATI/AMD GPUS, we are now looking for Mac users to provide feedback on running Rembrandt on Mac OSX, required information includes errors and warnings shown during startup/runtime, but also screen shots showing any issues. Please see: [[Project Rembrandt#Mac Issues]].
=== Canvas System ===
<!--additions should also be added to:http://wiki.flightgear.org/Changelog_3.0.0#Some_of_the_major_changes_include: -->


=== High Level Architecture ===
=== High Level Architecture ===
Line 40: Line 27:


Continue reading at [[FlightGear Benchmark]].
Continue reading at [[FlightGear Benchmark]].
=== FlightGear an Android ===
=== Usability Improvements ===
=== Mailing list digest ===
(by far the easiest option to populate the newsletter with contents is copying/pasting stuff from the forum and the mailing list or the git logs)
=== Forum digest ===
=== Git digest ===


=== Getting involved as a programmer ===
=== Getting involved as a programmer ===
Line 57: Line 32:


If you are interested in contributing as a core developer, please see [[Howto:Start core development]].
If you are interested in contributing as a core developer, please see [[Howto:Start core development]].
== Release ChangeLog ==
This section lists changes committed this month that will be available in the next release, these will be copied to the release changelog shortly before a release (for each month), so that we hopefully get a comprehensive list of new features.
== Interview with a contributor (NAME) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''
* How long have you been involved in FlightGear?
* What are your major interests in FlightGear?
* What project are you working on right now?
* What do you plan on doing in the future?
* Are you happy with the way the FlightGear project is going?
* What do you enjoy most about developing for FlightGear?
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?
More questions are being collected here: [[Interview questions]].
Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX
== Snapshot releases ==
Every now and then, easy-to-install development snapshots are created (usually, twice montlhy). These snapshos depict a recent state of the development version of FlightGear. By using them users can test out features that will be included in the upcoming release. Testers are encouraged to file bugs at [http://code.google.com/p/flightgear-bugs/ the issue tracker].
The snapshot can be download via the links at the bottom of this page: http://www.flightgear.org/download/. Updates and feedback can be found [http://flightgear.org/forums/viewtopic.php?f=28&t=10488&p=144233&hilit=snapshot#p144233 at the forum].


== International FlightGear websites ==
== International FlightGear websites ==
Line 112: Line 63:
Forum users dbelcham, Philosopher and Hooray had an interesting discussion about introducing unit testing into FlightGear's Nasal scripting system, resulting in an effort to come up with a standalone Nasal interpreter for unit testing purposes. For additional info, please see [[Nasal Unit Testing Framework]].
Forum users dbelcham, Philosopher and Hooray had an interesting discussion about introducing unit testing into FlightGear's Nasal scripting system, resulting in an effort to come up with a standalone Nasal interpreter for unit testing purposes. For additional info, please see [[Nasal Unit Testing Framework]].


== New software tools and projects ==
=== OpenRadar ===
 
[[File:OpenRadar.g128.png|thumb|OpenRadar]]
[[File:OpenRadar.g128.png|thumb|OpenRadar]]
 
The [[OpenRadar]] project provides an [[ATC]] radar interface for FlightGear. Over the past few months it is steadily becoming one of the most used ATC applications. Under development by Ralf Gerlich and Wolfram Wagner among others "all-stars" code contributors, this java application will make you became an ATC-Controller all around the FG's MP network.
=== OpenRadar is beating hard ===
The project [[OpenRadar]], [[ATC]] for FlightGear is beating hard and become one of the most used applications in FlightGear since last months.
Under development by Ralf Gerlich and Wolfram Wagner among others "all-stars" code contributors, this java application will make you became an ATC-Controller all around the FG's MP network.


Be sure you have [[FGCOM]] installed in order to use it like real ATC does.
Be sure you have [[FGCOM]] installed in order to use it like real ATC does.


In general terms we can say that OpenRadar is solid - fast - multiplatform - open source - well programmed application, but first of all is fun.
In general terms we can say that OpenRadar is solid - fast - multiplatform - open source - well programmed application, but best of all it is fun. Without doubts you must try it.
 
Without doubts you must try it.
 
From here we'll like to say thanks for the big effort done behind OpenRadar.


From here we would like to say thanks for the big effort done behind OpenRadar.


=== OS-RC and FlightGear ===
=== OS-RC and FlightGear ===
Line 136: Line 80:
Linux inside, this new system has changed the way we fly, bringing us even a broader new FGecosystem for FlightGear.
Linux inside, this new system has changed the way we fly, bringing us even a broader new FGecosystem for FlightGear.


[http://www.os-rc.com  OS-RC Project].
[http://www.os-rc.com  OS-RC Project]
 
== FlightGear addons and mods ==


== In the hangar ==
== In the hangar ==
All the way back in May 2011, we addopted a new status-rating system for aircraft. So far, only a few have actually been rated, as can be seen in the list 'hockenberry' set up at [https://docs.google.com/spreadsheet/ccc?key=0ApzphjA4w05ndF94Y2F0bzJTbHQ5QTJXZXJRcUVRbWc&hl=en_US Google Docs]. If you're an aircraft developer and your aircraft is/are not on the list, please consider rating their status. All you'll need to know/do is described at [[Formalizing Aircraft Status]]. If you'd just like to get started contributing to FlightGear, this would also seem like an excellent way to get started.
=== New aircraft ===
=== New aircraft ===
jormapaappa1235 has been working on a new 757-200 with fully modeled interior. The plane has now almost finished cabin and pretty detailed cockpit. It is sad that the systems are not as finished as the model, so everybody who is interested in any kinds of systems and wants to help, please contact jormapaappa1235 in the forums or in the 757-200 (V2) thread: http://www.flightgear.org/forums/viewtopic.php?f=4&t=19644 .
==== Boeing 757-200 ====
 
[[File:Thenew757cockpit.png|thumb|270px|Boeing 757-200 cockpit]]
[[File:Thenew757cockpit.png|thumb|Cockpit]]
Jormapaappa1235 has been working on a new Boeing 757-200 with fully modeled interior. The plane has now almost finished cabin and pretty detailed cockpit. Sadly the systems are not as finished as the model, so everybody who is interested in any kinds of systems and wants to help, please contact jormapaappa1235 in the [http://www.flightgear.org/forums/viewtopic.php?f=4&t=19644 forum topic].
 
The new 757 can be downloaded through git but there is no official support yet.
 
Warning: The plane is much heavier than a regular plane, mainly because of fully-modeled cabin.
So it is not recommended at download this if you have a really poor computer.
 
=== Updated aircraft ===


=== Liveries ===
The new 757 can be obtained through git but there is no official support yet.


== Scenery corner ==
Warning: The plane is much heavier than the average FlightGear plane, mainly because of a fully-modeled cabin. It is therefore not recommended for low-end computers.
=== Airports ===
 
== Aircraft of the month ==
== Airport of the month ==
== Screenshot of the month ==


== Suggested flights ==
== Suggested flights ==
===Training Manchester VOR DME Approach===
===Training Manchester VOR DME Approach===
For this training flight you have to take a 737 performing a VOR DME Approach Procedure for the RWY 23R at Manchester airport. Repeat practice if you need and enjoy.
For this training flight you'll have to take a Boeing 737 and perform a VOR DME Approach Procedure for the RWY 23R at Manchester airport. Repeat practice if you need and enjoy. Some info:
 
*Manchester EGCC Elevation 257ft
Info
*RWY Heading 23R 231.
#Manchester EGCC Elevation 257ft
*Manchester VOR MCT 113.55
#RWY Heading 23R 231.
*ILS/DME INN 109.5
#Manchester VOR MCT 113.55
#ILS/DME INN 109.5
 


See the following video of a Manchester 23R VOR/DME APP in a full motion simulator. It's not much different in FlightGear.
{{#ev:youtube | 9RzCB6ZcTLA}}
{{#ev:youtube | 9RzCB6ZcTLA}}
Youtube video: Manchester 23R VOR/DME APP in a full simulator, in FG not much different.


More amazing flights can be found at [[Suggested Flights]].
More amazing flights can be found at [[Suggested Flights]].
== Aircraft reviews ==
== Wiki updates ==
===New articles===
<DynamicArticleList>
  type=new
  count=10
</DynamicArticleList>
===New aircraft articles===
<DynamicArticleList>
  type=new
  count=10
  categoryRoot=Aircraft
</DynamicArticleList>
===Most popular newsletters===
<DynamicArticleList>
  type=hot
  count=5
  categoryRoot=FlightGear Newsletter
</DynamicArticleList>


== Community news ==
== Community news ==
=== FlightGear Community Pages closing down ===
=== FlightGear Community Pages closing down ===
The [http://fgfs.i-net.hu FlightGear Community Pages] will be pulled offline in August. Its maintainer does not have enough spare time to take care of the website and co no longer provide hosting for it. Please save all your important data (think of screenshots, statistics...), before it is gone.
The [http://fgfs.i-net.hu FlightGear Community Pages] will be pulled offline in August. Its maintainer does not have enough spare time to take care of the website and co no longer provide hosting for it. Please save all your important data (think of screenshots, statistics...), before it is gone.
=== FlightGear on YouTube ===


=== New tutorials and screencasts ===
=== 727-230 Tribute ===
=== Forum news ===
FlightGear's 727-230 Tribute is a fun way to fly, as well as an opportunity to help improve this old aircraft. It's very simple. The pilot takes the [[Boeing 727-230]], flies wherever he wants, reports some basic PIREPs and informs where he/she has landed, so the next pilot can take the aircraft and fly it to another place and so on.
=== Multiplayer ===
FG's 727-230 Tribute is a funny way to fly, also an anarchy way to cooperate improving this old aircraft.


Just simple, the pilot takes the 727-230, flying whatever he wants, reporting some basic PIREPs and informing where he/she has landed, so next pilot can take the aircraft fly to another place and report.
The 727-230 received some minor enhancements by IH-COL. The aircraft is behaving well, so we expect long life for this old lady. She's just waiting for your help. Either by flying and providing feedback or by contributing some code.


For the moment 727-230 has received some minor enhancements by IH-COL user and the aircraft is having great performance, so we expect long life for this old 722 lady that is waiting for your help, just by flying or just contributing with some code.
If you want to fly her or simply check the state of development, see [http://flightgear.org/forums/viewtopic.php?f=10&t=19943 this forum topic].


If you want to fly her or simply checking the state of development, see forum [http://flightgear.org/forums/viewtopic.php?f=10&t=19943]
=== Virtual airlines ===
=== FlightGear events ===
== Useful links ==
== And finally ... ==
== And finally ... ==
=== Contributing ===
=== Contributing ===
Line 237: Line 129:
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.


=== Did you know ===
{{Appendix}}
 
[[Category:FlightGear Newsletter]]
<!-- this needs to be changed after each release, so that newsletters show up in the proper category -->


[[Category:FlightGear Newsletter|2013 06]]
[[Category:Changes after 2.10]]
[[Category:Changes after 2.10]]

Navigation menu