8,556
edits
m (Small cleanups) |
|||
Line 3: | Line 3: | ||
''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.'' | ''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.'' | ||
== Release status == | |||
A changelog is currently being written at [[Changelog 2.4.0]]. | |||
== Development news == | == Development news == | ||
== Snapshot releases == | |||
Some of you might know that James and Gene have spent a lot of time assembling a [[FlightGear Build Server|nightly build server]] for the FlightGear project. This monitors the [[git]] repository for any source code changes and then spawns builds for Windows, Linux, and Mac. | |||
You can find the build server at http://flightgear.simpits.org:8080/ | |||
Unfortunately, to run a nightly build from the build server, you still have to pull the latest data tree from the git repository. That's not all that hard once you work through the details, but it's a bit "fiddly" for some folks. | This is really great work and a huge contribution to the FlightGear project. Unfortunately, to run a nightly build from the build server, you still have to pull the latest data tree from the git repository. That's not all that hard, once you work through the details, but it's a bit "fiddly" for some folks. | ||
So Curt has been playing around with creating a developer's snapshot release which would be similar to our official release. | So Curt has been playing around with creating a developer's snapshot release which would be similar to our official release. It is one big setup.exe that includes all the programs and the data. We are hopeful that this will eventually make the current development version of FlightGear more accessible for "joe average" users which would then in term hopefully give us more feedback and bug reports ahead of our official release. | ||
None of this would be possible without the "Jenkins" (formerly Hudson) build server that Gene and James set up. | |||
None of this would be possible without the " | |||
There are a couple things that are done with this snapshot package: | There are a couple things that are done with this snapshot package: | ||
* An unique app name of the form <tt>FlightGear YYYYMMDD</tt> is assigned so you can have multiple versions installed concurrently and they don't step on each other and don't step on the official release. If people maintain multiple snapshots installed on their systems, that might help narrow down when a bug was introduced. | |||
* | |||
* The openal installer "oalinst.exe" is included and vcredist_x86.exe ... neither of these may be required in the long term if we can just ship the needed dll's, but that probably needs further testing. | * The openal installer "oalinst.exe" is included and vcredist_x86.exe ... neither of these may be required in the long term if we can just ship the needed dll's, but that probably needs further testing. | ||
Does it basically work? Are there any major packaging blunders? Please note, FlightGear bugs and feature request should still be handled through normal channels. But I am interested in packaging issues right now. | Does it basically work? Are there any major packaging blunders? Please note, FlightGear bugs and feature request should still be handled through normal channels. But I am interested in packaging issues right now. | ||
To provide feedback please | To provide feedback please use [http://flightgear.org/forums/viewtopic.php?f=28&t=10488 this forum thread]. | ||
For downloads please see: [http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Win32/Setup%20FlightGear%20v20110629.exe this location] | |||
== Nasal for newbies == | == Nasal for newbies == | ||
Line 41: | Line 36: | ||
[[File:bannerFGanswers.png|top-left|link=http://flightgear.shapado.com]] | [[File:bannerFGanswers.png|top-left|link=http://flightgear.shapado.com]] | ||
Michat has been working | Michat has been working to start a questions and answers (Q&A) service for the FlightGear community based on Shapado AGPL. | ||
FGAnswers is attempt to provide an easy way to find first hand brief information around the massive info-data that FG generates. Michat | FGAnswers is an attempt to provide an easy way to find first hand brief information around the massive info-data that FG generates. Michat designed the basis of the system, giving space to a broad range of languages, in order to reach as many pilots and developers as FG used to enjoy. | ||
FGAnswers, offers all kind of services: Live Chat Support, Flight Center, Training Center, FGSoft Center, ATC Center, VA Center. From easy FAQ's to the deepest Q's. Classic routes, flying techniques, school, fly essentials, dedicated Wiki pages for ATC, VA's, Pilots, or Simply for How to's.. writters-readers, video makers.... and many more. | FGAnswers, offers all kind of services: Live Chat Support, Flight Center, Training Center, FGSoft Center, ATC Center, VA Center. From easy FAQ's to the deepest Q's. Classic routes, flying techniques, school, fly essentials, dedicated Wiki pages for ATC, VA's, Pilots, or Simply for How to's.. writters-readers, video makers.... and many more. | ||
With almost infinite possibilities, for sure that FGAnswers will need your help, but how? Easy just using it for free, with honor and honesty. Make your questions [http://flightgear.shapado.com here]. | |||
With almost infinite possibilities, for sure that FGAnswers will need your help, but how? Easy just using it for free, with honor and honesty. | |||
Make your questions [http://flightgear.shapado.com here] | |||
Happy answers, have a good summer. | Happy answers, have a good summer. | ||
== FlightGear addons and mods == | == FlightGear addons and mods == | ||
Line 83: | Line 70: | ||
== Airport of the month == | == Airport of the month == | ||
== New SketchUp | == New SketchUp exporter plugin == | ||
[[SketchUp]] models which are completed using the existing [[SketchUp to AC3D exporter]] are rendered in FlightGear with double sided faces. Though there is nothing wrong with double sided faces, there is a considerable saving in FlightGear processing if single faces can be used. This affects frames per second and is particularly noticeable when entering an area which is heavily inhabited by buildings/models. | |||
SketchUp | It is possible to export SketchUp models with single faces by using a new version of the exporter (adapted by VicMar and i4dnf). This new version is named <tt>ac3dS_export.rb</tt> and is available for download from http://vicmar.weebly.com/downloads.html | ||
The <tt>ac3dS_export.rb</tt> file should be placed in the same folder/directory as the existing exporter. In the SketchUp ‘Plugins’ menu, it will appear as “Export to AC3D (Single_Faced)” and will appear with the existing exporter. | |||
The new version is recommended for use with SketchUp models which DO NOT have any see-through (alpha) textures. It is also not recommended if your model has apertures like hangar doors, which allow a view inside the building, as the opposite walls will be invisible. | |||
The new version is recommended for use with SketchUp models which DO NOT have any see-through textures. It is also not recommended if your model has apertures like | |||
There is a work around for models which have see-through textures, but it is a chore to do, so it is recommended you use the existing exporter. If you would like details of the work arounds, yes there are two, just ask. | There is a work around for models which have see-through textures, but it is a chore to do, so it is recommended you use the existing exporter. If you would like details of the work arounds, yes there are two, just ask. | ||
Any feedback will be welcomed | Any feedback will be welcomed at [http://www.flightgear.org/forums/viewtopic.php?f=5&t=12778 the forum]. | ||
http://www.flightgear.org/forums/viewtopic.php?f=5&t=12778 | |||
== Screenshot of the month == | == Screenshot of the month == | ||
Line 113: | Line 90: | ||
== Wiki updates == | == Wiki updates == | ||
The FlightGear Wiki used to block open proxy IP adresses. Several people reported that they were unable to register an account because of that. Such issues should be solved by now. So, if you were unable to register before, [http://wiki.flightgear.org/index.php?title=Special:UserLogin&type=signup please try again]. | The FlightGear Wiki used to block open proxy IP adresses. Several people reported that they were unable to register an account because of that. Such issues should be solved by now. So, if you were unable to register before, [http://wiki.flightgear.org/index.php?title=Special:UserLogin&type=signup please try again]. | ||
== Community news == | == Community news == |