8,564
edits
(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 == | ||
=== 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. | |||
=== 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]]. | ||
=== High Level Architecture === | === High Level Architecture === | ||
Line 40: | Line 27: | ||
Continue reading at [[FlightGear Benchmark]]. | Continue reading at [[FlightGear Benchmark]]. | ||
=== 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]]. | ||
== 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]]. | ||
== | === 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. | |||
The | |||
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 | 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 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] | ||
== In the hangar == | == In the hangar == | ||
=== New aircraft === | === New aircraft === | ||
==== Boeing 757-200 ==== | |||
[[File:Thenew757cockpit.png|thumb|270px|Boeing 757-200 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 obtained through git but there is no official support yet. | |||
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. | |||
== Suggested flights == | == Suggested flights == | ||
===Training Manchester VOR DME Approach=== | ===Training Manchester VOR DME Approach=== | ||
For this training flight you have to take a 737 | 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 | |||
*RWY Heading 23R 231. | |||
*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}} | ||
More amazing flights can be found at [[Suggested Flights]]. | More amazing flights can be found at [[Suggested Flights]]. | ||
== 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. | ||
=== | === 727-230 Tribute === | ||
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. | |||
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. | |||
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]. | |||
== 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. | ||
{{Appendix}} | |||
[[Category:FlightGear Newsletter|2013 06]] | |||
[[Category:Changes after 2.10]] | [[Category:Changes after 2.10]] |