FlightGear Newsletter June 2014: Difference between revisions

Jump to navigation Jump to search
m
restore editable newsletter sections as per discussion on Gijs' talk page ... feel free to revert if this breaks anything (also check out the last two changes at newsletter-article-start)
m (Protected "FlightGear Newsletter June 2014": Newsletter ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)))
m (restore editable newsletter sections as per discussion on Gijs' talk page ... feel free to revert if this breaks anything (also check out the last two changes at newsletter-article-start))
Line 33: Line 33:
</div>
</div>


{{Newsletter-article-start|FlightGear 3.2 - Feature Freeze|By [[User:t3r|TorstenD]]|Development news}}
== {{Newsletter-article-start|FlightGear 3.2 - Feature Freeze|By [[User:t3r|TorstenD]]|Development news}} ==
On June 17, we entered our scheduled feature freeze state for the next release. Please use the remaining weeks to improve the existing features, harden and cleanup the code, edit the [[Next Changelog|ChangeLog]], improve the Manual, document the undocumented etc. etc. The release branches will be created on July 17th to have the release ready by Aug. 17th. See our [[release plan]] for detals about the release process.
On June 17, we entered our scheduled feature freeze state for the next release. Please use the remaining weeks to improve the existing features, harden and cleanup the code, edit the [[Next Changelog|ChangeLog]], improve the Manual, document the undocumented etc. etc. The release branches will be created on July 17th to have the release ready by Aug. 17th. See our [[release plan]] for detals about the release process.


{{Newsletter-article-start|Canvas GUI: Layouting, Widgets and MessageBoxes|By [[User:TheTom|TheTom]]}}
== {{Newsletter-article-start|Canvas GUI: Layouting, Widgets and MessageBoxes|By [[User:TheTom|TheTom]]}} ==


=== Widgets and Layouting ===
=== Widgets and Layouting ===
Line 61: Line 61:
</gallery>
</gallery>


{{Newsletter-article-start|Preview: Aircraft Center - get it on the fly|By [[User:TheTom|TheTom]] and [[User:Zakalawe|Zakalawe]]}}
== {{Newsletter-article-start|Preview: Aircraft Center - get it on the fly|By [[User:TheTom|TheTom]] and [[User:Zakalawe|Zakalawe]]}} ==


[[File:Aircraft-center-prototype.png|270px|thumb|Canvas dialog showing the prototype for an [[Aircraft Center]] for directly installing/managing aircraft from within FlightGear, an upcoming feature scheduled for FlightGear 3.2, currently being developed by TheTom and Zakalawe]]
[[File:Aircraft-center-prototype.png|270px|thumb|Canvas dialog showing the prototype for an [[Aircraft Center]] for directly installing/managing aircraft from within FlightGear, an upcoming feature scheduled for FlightGear 3.2, currently being developed by TheTom and Zakalawe]]
Line 74: Line 74:
Thus, adopting Canvas is going to address a number of long-standing issues, but it's obviously a process that only just got started, and it will not happen overnight - 2-3 release cycles are not far-fetched, that's how long the whole migration could very well take, unless there are more people interested in helping.
Thus, adopting Canvas is going to address a number of long-standing issues, but it's obviously a process that only just got started, and it will not happen overnight - 2-3 release cycles are not far-fetched, that's how long the whole migration could very well take, unless there are more people interested in helping.


{{Newsletter-article-start|Canvas/MapStructure Updates|By [[User:Hooray|Hooray]] and [[User:Philosopher|Philosopher]]}}
== {{Newsletter-article-start|Canvas/MapStructure Updates|By [[User:Hooray|Hooray]] and [[User:Philosopher|Philosopher]]}}==


The upcoming FlightGear version (3.2) will contain a canvas-based map dialog, including a modular "plugin" system for creating custom map layers and charts with roughly ~50 lines of code, most of it boilerplate. This is entirely XML/Nasal based (scripted) - symbols can be pretty much anything, raster or vector images (png or svg), but even animated. Styling can be customized, too.
The upcoming FlightGear version (3.2) will contain a canvas-based map dialog, including a modular "plugin" system for creating custom map layers and charts with roughly ~50 lines of code, most of it boilerplate. This is entirely XML/Nasal based (scripted) - symbols can be pretty much anything, raster or vector images (png or svg), but even animated. Styling can be customized, too.
Line 107: Line 107:
</gallery>
</gallery>


{{Newsletter-article-start|Boeing 777 EFB prototype|By [[User:I-NEMO|I-NEMO]]}}
== {{Newsletter-article-start|Boeing 777 EFB prototype|By [[User:I-NEMO|I-NEMO]]}} ==
[[File:777-EFB-MAIN.png|thumb|777-200ER EFB [http://forum.flightgear.org/viewtopic.php?f=71&t=23196]]]
[[File:777-EFB-MAIN.png|thumb|777-200ER EFB [http://forum.flightgear.org/viewtopic.php?f=71&t=23196]]]
[[File:777-EFB-AIRPORT-SEARCH.png|thumb|777-200 EFB AIRPORT SEARCH, see [http://forum.flightgear.org/viewtopic.php?f=71&t=23196&p=211410#p211410]]]
[[File:777-EFB-AIRPORT-SEARCH.png|thumb|777-200 EFB AIRPORT SEARCH, see [http://forum.flightgear.org/viewtopic.php?f=71&t=23196&p=211410#p211410]]]
Line 134: Line 134:
Learn more at [[Canvas EFB Framework]] or follow the [http://forum.flightgear.org/viewtopic.php?f=71&t=23204 forum discussion]...
Learn more at [[Canvas EFB Framework]] or follow the [http://forum.flightgear.org/viewtopic.php?f=71&t=23204 forum discussion]...


{{Newsletter-article-start|Towards an Aircraft-agnostic MFD Framework|By [[User:Hooray|Hooray]]}}
== {{Newsletter-article-start|Towards an Aircraft-agnostic MFD Framework|By [[User:Hooray|Hooray]]}} ==
Given the recent trend of having several MFD-related efforts without any kind of collaboration/code reuse going on here among our contributors (PFD, ND, Avidyne Entegra R9, EFB), I have started prototyping a generic MFD framework that is purely XML-based, inspired by discussions we've had over the last couple of weeks, and lessons learnt from the missions subsystem.
Given the recent trend of having several MFD-related efforts without any kind of collaboration/code reuse going on here among our contributors (PFD, ND, Avidyne Entegra R9, EFB), I have started prototyping a generic MFD framework that is purely XML-based, inspired by discussions we've had over the last couple of weeks, and lessons learnt from the missions subsystem.


Line 156: Line 156:
</gallery>
</gallery>


{{Newsletter-article-start|Mapping polar and date line crossing routes|By [[User:Gijs|Gijs]]}}
== {{Newsletter-article-start|Mapping polar and date line crossing routes|By [[User:Gijs|Gijs]]}} ==
The [[Map|map dialog]] used to fail plotting routes near the poles, as well as routes crossing the International Date Line. The Sanson–Flamsteed projection that we used simply could not cope with such extreme latitudes and longitudes. By changing the map to an Azimuthal equidistant projection all points on the map are at proportionately correct distances from the center point at the correct azimuth (direction) from the center point.<ref>{{Cite web |url=http://en.wikipedia.org/wiki/Azimuthal_equidistant_projection |title=Azimuthal equidistant projection |publisher=Wikipedia}}</ref> Ideal for navigating to your next way point!
The [[Map|map dialog]] used to fail plotting routes near the poles, as well as routes crossing the International Date Line. The Sanson–Flamsteed projection that we used simply could not cope with such extreme latitudes and longitudes. By changing the map to an Azimuthal equidistant projection all points on the map are at proportionately correct distances from the center point at the correct azimuth (direction) from the center point.<ref>{{Cite web |url=http://en.wikipedia.org/wiki/Azimuthal_equidistant_projection |title=Azimuthal equidistant projection |publisher=Wikipedia}}</ref> Ideal for navigating to your next way point!


Line 164: Line 164:
</gallery>
</gallery>


{{Newsletter-article-start|Logo proposal|By [[User:Aepcam|Aepcam]]}}
== {{Newsletter-article-start|Logo proposal|By [[User:Aepcam|Aepcam]]}} ==
This is a new logo badge concept proposal for FlightGear designed by Michat.
This is a new logo badge concept proposal for FlightGear designed by Michat.


Line 171: Line 171:
[[File:Fglogoforum.png]]
[[File:Fglogoforum.png]]


{{Newsletter-article-start|Damage and disintegration|By [[User:Algernon|Algernon]]|FlightGear addons and mods}}
== {{Newsletter-article-start|Damage and disintegration|By [[User:Algernon|Algernon]]|FlightGear addons and mods}} ==
{{#ev:youtube|OpwNaoO3xMQ|200|right|Tomaskom's V-1 used in anger over London}}
{{#ev:youtube|OpwNaoO3xMQ|200|right|Tomaskom's V-1 used in anger over London}}
{{#ev:youtube|H4XDuLo35ks|200|right|Victor V2.0 damage script causing a catastrophic failure and fire}}
{{#ev:youtube|H4XDuLo35ks|200|right|Victor V2.0 damage script causing a catastrophic failure and fire}}
Line 181: Line 181:
Finally, and most spectacularly, Tomaskom has demonstrated the disintegration capabilities of his L-159, which is under development. Hopefully, he will explain all here before publication date.
Finally, and most spectacularly, Tomaskom has demonstrated the disintegration capabilities of his L-159, which is under development. Hopefully, he will explain all here before publication date.


{{Newsletter-article-start|Scenesetter|By [[User:Algernon|Algernon]]}}
== {{Newsletter-article-start|Scenesetter|By [[User:Algernon|Algernon]]}} ==
Scenesetter is a piece of code by Algernon, very early in development but already quite effective, which can effect changes to the time and weather from an AI scenario synchronously with other MP players. A crude proof of concept was used in the recent FGUK #FlightNight "British Weather", where pilots visited different airfields with various unpleasant flying conditions. Scenesetter pushes METAR strings to the FlightGear weather system based on the location of an associated Navaid, establishing a circular zone of a specified radius around it in which METAR will be changed. Start time can be specified too, either by providing a local start time or a local time offset (useful for multiplayer use where players will not all start the AI scenario at precisely the same time).
Scenesetter is a piece of code by Algernon, very early in development but already quite effective, which can effect changes to the time and weather from an AI scenario synchronously with other MP players. A crude proof of concept was used in the recent FGUK #FlightNight "British Weather", where pilots visited different airfields with various unpleasant flying conditions. Scenesetter pushes METAR strings to the FlightGear weather system based on the location of an associated Navaid, establishing a circular zone of a specified radius around it in which METAR will be changed. Start time can be specified too, either by providing a local start time or a local time offset (useful for multiplayer use where players will not all start the AI scenario at precisely the same time).


{{Newsletter-article-start|Beechcraft Bonanza|By [[User:Flyingfisch|Flyingfisch]]|In the hangar}}
== {{Newsletter-article-start|Beechcraft Bonanza|By [[User:Flyingfisch|Flyingfisch]]|In the hangar}} ==
Flyingfisch is building the Beechcraft A35 Bonanza for Flightgear. Some pictures:
Flyingfisch is building the Beechcraft A35 Bonanza for Flightgear. Some pictures:
<gallery mode=packed>
<gallery mode=packed>
Line 193: Line 193:
</gallery>
</gallery>


{{Newsletter-article-start|Saab JA-37 Viggen|By [[User:Necolatis|Necolatis]]}}
== {{Newsletter-article-start|Saab JA-37 Viggen|By [[User:Necolatis|Necolatis]]}} ==
The Swedish fighter jet [[Saab JA-37 Viggen]] has been updated, since it was included in FlightGear 3.0. More instruments, additional liveries, aerodynamic response to payload and tooltips on instruments. Option for automatic reverse thrust at touchdown, selection of HUD brightness, disabling of structural damage. HUD can now switch to imperial units and show MP and AI aircraft and closest airport. The aircraft now also has multiplayer sounds and better cockpit view helps seeing the landing strip. Support for FG 2.8 by deleting a small section in an xml file. Also worth mentioning is countless bug-fixes and improvements, e.g. better handling at high altitudes and a bug fix in the lift force formula.
The Swedish fighter jet [[Saab JA-37 Viggen]] has been updated, since it was included in FlightGear 3.0. More instruments, additional liveries, aerodynamic response to payload and tooltips on instruments. Option for automatic reverse thrust at touchdown, selection of HUD brightness, disabling of structural damage. HUD can now switch to imperial units and show MP and AI aircraft and closest airport. The aircraft now also has multiplayer sounds and better cockpit view helps seeing the landing strip. Support for FG 2.8 by deleting a small section in an xml file. Also worth mentioning is countless bug-fixes and improvements, e.g. better handling at high altitudes and a bug fix in the lift force formula.


[[File:Saab JA-37 Viggen Blue Peter Livery.png|Blå Petter Livery for JA-37]]
[[File:Saab JA-37 Viggen Blue Peter Livery.png|Blå Petter Livery for JA-37]]


{{Newsletter-article-start|Updated P-51D now in git|By [[User:hvengel|hvengel]]}}
== {{Newsletter-article-start|Updated P-51D now in git|By [[User:hvengel|hvengel]]}} ==
The new 3D exterior model for the [[North American P-51 Mustang|North American P-51D Mustang]] is now in git and under active development. It is currently in gray primer waiting for the UV map to be finalized. It is now fully integrated into the existing FDM.  Extensive new animation work has been done including animated trim tabs and a fully functional canopy. Here are some screen shots taken in sim for your enjoyment.
The new 3D exterior model for the [[North American P-51 Mustang|North American P-51D Mustang]] is now in git and under active development. It is currently in gray primer waiting for the UV map to be finalized. It is now fully integrated into the existing FDM.  Extensive new animation work has been done including animated trim tabs and a fully functional canopy. Here are some screen shots taken in sim for your enjoyment.


Line 206: Line 206:
</gallery>
</gallery>


{{Newsletter-article-start|Balancing the Boeing 747-400|By [[User:Gijs|Gijs]]}}
== {{Newsletter-article-start|Balancing the Boeing 747-400|By [[User:Gijs|Gijs]]}} ==
After he started developing the [[Boeing 747-400]] as a hobby project six years ago, Gijs finally managed to get the weight and balancing right. The center of gravity is now within 0.05% MAC (40 cm) of the published values.
After he started developing the [[Boeing 747-400]] as a hobby project six years ago, Gijs finally managed to get the weight and balancing right. The center of gravity is now within 0.05% MAC (40 cm) of the published values.


Line 213: Line 213:
The updated 747-400 is already available through Git and will be on the download page when FlightGear 3.2 is released.
The updated 747-400 is already available through Git and will be on the download page when FlightGear 3.2 is released.


{{Newsletter-article-start|Extra500 is updated to production status|By [[User:Evandenberg|Evandenberg]]}}
== {{Newsletter-article-start|Extra500 is updated to production status|By [[User:Evandenberg|Evandenberg]]}} ==
The [[Extra EA-500]] is updated and has reached "production status"! Just a short list of changes for release 1.1.0:
The [[Extra EA-500]] is updated and has reached "production status"! Just a short list of changes for release 1.1.0:
* Engine+fuel: realistic flame-out, fuel flow to collector compartment, anti ice influence on TOT, improved oil press and temp model<br/>
* Engine+fuel: realistic flame-out, fuel flow to collector compartment, anti ice influence on TOT, improved oil press and temp model<br/>
Line 233: Line 233:
</gallery>
</gallery>


{{Newsletter-article-start|USA state capital buildings|By [[User:Jonbourg|Jonbourg]]|Scenery corner}}
== {{Newsletter-article-start|USA state capital buildings|By [[User:Jonbourg|Jonbourg]]|Scenery corner}} ==
There is a project to add all the USA state capital buildings into FG.  It is discussed in [http://forum.flightgear.org/viewtopic.php?f=5&t=22715&sid=ea847909bde2e1f8ffe5b94bcc673f4f this scenery forum thread]. There is also a wiki page: [[State Capitol Buildings in the United States]].  So far, Idaho, Louisiana & Nebraska have been completed. Hawaii and New York are currently in progress.  Please feel free to join in with any other state that has not been done yet.  Just let us know through the forum and we will add it to the in progress list.
There is a project to add all the USA state capital buildings into FG.  It is discussed in [http://forum.flightgear.org/viewtopic.php?f=5&t=22715&sid=ea847909bde2e1f8ffe5b94bcc673f4f this scenery forum thread]. There is also a wiki page: [[State Capitol Buildings in the United States]].  So far, Idaho, Louisiana & Nebraska have been completed. Hawaii and New York are currently in progress.  Please feel free to join in with any other state that has not been done yet.  Just let us know through the forum and we will add it to the in progress list.


{{Newsletter-article-start|LIPY, a scenery conversion from MSFS|By [[User:bigstones|bigstones]]}}
== {{Newsletter-article-start|LIPY, a scenery conversion from MSFS|By [[User:bigstones|bigstones]]}} ==
This month saw the [http://forum.flightgear.org/viewtopic.php?f=5&t=22623 second "preview" release] of the conversion of a scenery for MS Flight Simulator, [[Falconara Airport]] (ICAO code: LIPY), a small Italian international airport halfway down the Adriatic coast. The original author granted the permission to the conversion and even allowed for it to be included in the FlightGear official [[World Scenery]], at least the GPL compatible parts. This is not a huge limitation though, because most of the material was created from scratch, included pictures taken on purpose at the real airport, with the authorities' collaboration. Copyrighted aerial imagery only include the (unsuable) photoreal ground and some roofs.
This month saw the [http://forum.flightgear.org/viewtopic.php?f=5&t=22623 second "preview" release] of the conversion of a scenery for MS Flight Simulator, [[Falconara Airport]] (ICAO code: LIPY), a small Italian international airport halfway down the Adriatic coast. The original author granted the permission to the conversion and even allowed for it to be included in the FlightGear official [[World Scenery]], at least the GPL compatible parts. This is not a huge limitation though, because most of the material was created from scratch, included pictures taken on purpose at the real airport, with the authorities' collaboration. Copyrighted aerial imagery only include the (unsuable) photoreal ground and some roofs.


Line 248: Line 248:
{{cquote|I really wanted to have this scenery in FG because it's my home base, and seeing it ready and so well done just made me want it. However, even if still easier than making it from scratch (even if reusing the textures), I'd have to think well if I had to do this again.|bigstones, maintainer of the conversion}}
{{cquote|I really wanted to have this scenery in FG because it's my home base, and seeing it ready and so well done just made me want it. However, even if still easier than making it from scratch (even if reusing the textures), I'd have to think well if I had to do this again.|bigstones, maintainer of the conversion}}


{{Newsletter-article-start|Reshaping Leipzig/Halle Airport|By [[User:August|August]]}}
== {{Newsletter-article-start|Reshaping Leipzig/Halle Airport|By [[User:August|August]]}} ==
[[File:2014 new-layout-EDDP 05.jpg|650px|right]]
[[File:2014 new-layout-EDDP 05.jpg|650px|right]]
In FlightGear Germany's second largest cargo airport [[EDDP]] is well known as a detailed model accessible for everybody via [[TerraSync]]. Until 2013 it was famous for its regular ATC-events. It has been updated several times, at least 2012 by users D-STHO and August. When FlightGear 3.0 was published the airport layout changed from the old 810-standard to the new 850-standard. But the update (based on a taxiway layout modelled for X-Plane) turned out to be very imperfect. Many aprons and taxiways did not exist, dimensions did not appear to be correct and many new facilities which had been added at the real-world airport had not been taken into account. So maintainer August decided to redesign the whole airport from the scratch using [[WorldEditor]].  
In FlightGear Germany's second largest cargo airport [[EDDP]] is well known as a detailed model accessible for everybody via [[TerraSync]]. Until 2013 it was famous for its regular ATC-events. It has been updated several times, at least 2012 by users D-STHO and August. When FlightGear 3.0 was published the airport layout changed from the old 810-standard to the new 850-standard. But the update (based on a taxiway layout modelled for X-Plane) turned out to be very imperfect. Many aprons and taxiways did not exist, dimensions did not appear to be correct and many new facilities which had been added at the real-world airport had not been taken into account. So maintainer August decided to redesign the whole airport from the scratch using [[WorldEditor]].  
Line 263: Line 263:
</gallery>
</gallery>


{{Newsletter-article-start|An updated Weather article|By [[User:bigstones|bigstones]]|Wiki updates}}
== {{Newsletter-article-start|An updated Weather article|By [[User:bigstones|bigstones]]|Wiki updates}} ==
The [[Weather]] wiki article went through a wide extension. Although Advanced Weather was released quite a while ago, its usage has never been explained in the wiki, and some thorough instructions were available only in a readme in the "docs" folder of the base package which is not commonly explored by users, while the wiki article [[Advanced weather]] is more about the project than the usage.
The [[Weather]] wiki article went through a wide extension. Although Advanced Weather was released quite a while ago, its usage has never been explained in the wiki, and some thorough instructions were available only in a readme in the "docs" folder of the base package which is not commonly explored by users, while the wiki article [[Advanced weather]] is more about the project than the usage.


AW's advanced configuration is known to be not easy. So, if you always only used the weather selection menu and want to know more, or want to understand what the options actually do and how you can combine them, the [[Weather]] article has now been updated with some hints and basic notions extracted from experience and the original documentation, and quality checked by the author of the AW weather engine.
AW's advanced configuration is known to be not easy. So, if you always only used the weather selection menu and want to know more, or want to understand what the options actually do and how you can combine them, the [[Weather]] article has now been updated with some hints and basic notions extracted from experience and the original documentation, and quality checked by the author of the AW weather engine.


{{Newsletter-article-start|Translators required|}}
== {{Newsletter-article-start|Translators required|}} ==
{|
{|
|[[File:en.gif]]
|[[File:en.gif]]
Line 283: Line 283:
|}
|}


{{Newsletter-article-start|Call for volunteers||And finally...}}
== {{Newsletter-article-start|Call for volunteers||And finally...}} ==
* The [[TerraGear]] maintainers are looking for volunteers to help with development on the next world scenery project.  If you've ever wondered how a full 3D model of earth can be generated from raw data, now is your chance.  See the plan at [[TerraGear roadmap]].
* The [[TerraGear]] maintainers are looking for volunteers to help with development on the next world scenery project.  If you've ever wondered how a full 3D model of earth can be generated from raw data, now is your chance.  See the plan at [[TerraGear roadmap]].


Navigation menu