FlightGear wiki

FlightGear Newsletter July 2014: Difference between revisions

Page Discussion

FlightGear Newsletter July 2014 (view source)

Revision as of 14:43, 2 August 2014

7,605 bytes removed ,  2 August 2014
Prepare for publishing
(Prepare for publishing)
Line 1: Line 1:
{{Newsletter being written}}
{{Newsletter-header|July 2014}}
 
<div style="border-bottom:3px double #BBB;">
{| width="100%" |
| valign="top" width="33%" |
{{Newsletter-cover-item|5 years of newsletters}}<br/><br/>
{{Newsletter-cover-header|Development news}}<br/>
{{Newsletter-cover-item|A Canvas based GNS 530 GPS}}<br/>
{{Newsletter-cover-item|Nasal: Making safer base-class calls}}<br/>
{{Newsletter-cover-item|FGCamera}}
| valign="top" width="33%" |
{{Newsletter-cover-header|Scenery corner}}<br/>
{{Newsletter-cover-item|Paro Int. Airport - VQPR}}<br/><br/>
{{Newsletter-cover-header|Other}}<br/>
{{Newsletter-cover-item|Support for Nasal in Notepad++}}<br/>
{{Newsletter-cover-item|Primary Flight Displays for Android Devices}}<br/>
{{Newsletter-cover-item|Parachute for YASim (Thrusters & Nasal)}}<br/><br/>
| valign="top" width="33%" |
{{Newsletter-cover-header|In the hangar}}<br/>
{{Newsletter-cover-item|Mainair Flash 2 Alpha}}<br/>
{{Newsletter-cover-item|Aero L-159 ALCA}}<br/><br/>
{{Newsletter-cover-header|Multiplayer events}}<br/>
{{Newsletter-cover-item|FGUK Mach Loop Challenge}}
|}
</div>
== 5 years of newsletters ==
== 5 years of newsletters ==
[[File:Fgmagfiveyears.png]]
[[File:Fgmagfiveyears.png]]


The newsletter started in July 2009. (more to write here, just so we don't forget about it)
The first edition of the FlightGear newsletter in its current form was published in July 2009. Over the years we've seen a large number of volunteers writing articles, collecting news and providing images.
 
{{FGCquote
  |Would it be an idea to provide some sort of weekly or monthly newsletter? I often find out that there are new things I didn't new about or other users that don't follow all topics won't know if there's an awsome plane released. That's why I think we need a newsletter.<br/>
<br/>
'''Possible things to write about could be:'''<br/>
- New planes that are released.<br/>
- New scenery projects (like a new/redrawed airport, things like the corse scenery etc.).<br/>
- New FG releases (this is not very often, but it should be in the letter if so).<br/>
- New forum features/subforums and other news from the forum.<br/>
- News from the wiki (only detailed and large tutorials, or new portals etc. so not every new article ofcourse)<br/>
- Events that will be held within a short periode or (links to) screenshots of the latest event(s).<br/>
- The first 3 or 5 pictures of a screenshot contest.<br/>
<br/>
If you got other idea's, post in this topic so we could extend the list.<br/>
I don't really know what's best way to provide the letter. But we have some options:<br/>
- a topic that's closed, only open for people that are making the letter (at the moment this sounds best to me).<br/>
- emails send to all forum-users (I don't really like this myself).<br/>
- a .pdf file with a link on the main page of [http://www.flightgear.org http://www.flightgear.org]<br/>
- or even something else<br/>
<br/>
I would like to write the letter, but if there are other people to we might split stuff (someone for scenery news, someone else for aircrafts etc.). Please respond and vote in the poll. Tips/ideas are very much appreciated.
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=11211#p11211
    |title=<nowiki>Newsletter</nowiki>
    |author=<nowiki>Gijs</nowiki>
    |date=<nowiki>Mon May 26</nowiki>
  }}
}}
 
{{FGCquote
  |The devel-list is great, I'm subscribed to, but not simple to read. It's more like the forum. Usually I don't want to or have time to read through all emails. So I delete most of it without reading anything more than the subject. We don't want to read a lot of topics if we only want to know what function is new and what it does. The the users (so not the developers) want something more ease to read/check. With some screenies of what they will get with a new function etc. So my idea was to make it especially for users.<br/>
<br/>
Events aren't listed on the pages you gave nor some other stuff we could place in the newsletter. In the letter all important news to know will be listed together. If we get this of the ground it could be a great way to reach users to (for events etc.). So I think the newsletter still will be a addition to the lists.
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=11216#p11216
    |title=<nowiki>Re: Newsletter</nowiki>
    |author=<nowiki>Gijs</nowiki>
    |date=<nowiki>Mon May 26</nowiki>
  }}
}}
 
{{FGCquote
  |At one time a few years ago we attempted to launch a newsletter.  We had two volunteers, but we never got even the first issue out.  It's a lot of work so we need a pretty dedicated volunteer.  I've heard of other folks using scribus, but even open-office writer would probably be just fine.  Let's not get too caught up in the details of a print/publishing quality layout if we have to sacrifice time for content and just getting the newsletter out on a regular time frame.  There are a bazillion ideas for articles.  I could dust off my unpublished "yasim howto" for instance.  That ended up being about 10 pages (so not newsletter material really) but I could trim it down to a teaser article and we could post the full version on the wiki or something?<br/>
<br/>
But if you are willing to get a newsletter rolling, that would be awsome.
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=11277#p11277
    |title=<nowiki>Re: Newsletter</nowiki>
    |author=<nowiki>curt</nowiki>
    |date=<nowiki>Tue May 27</nowiki>
  }}
}}
 
{{FGCquote
  |Gijs is right when it comes to being a Developer or a User of FG is Vastly different. I know when i first started here i had no clue about lots of developmental things, now i talk of writing .xml files, modelling nasal scripting. That is due to people describing things is basic easy to understand" Laymans" terms and not the kind of language that the DEvs use (understandably of course)<br/>
 
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=11368#p11368
    |title=<nowiki>Re: Newsletter</nowiki>
    |author=<nowiki>MaverickAlex</nowiki>
    |date=<nowiki>Thu May 29</nowiki>
  }}
}}
 
{{FGCquote
  |Since 16 to 3 voted for Yes I will release the first Newsletter as soon as possible.
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=15619#p15619
    |title=<nowiki>Re: Newsletter</nowiki>
    |author=<nowiki>Gijs</nowiki>
    |date=<nowiki>Thu Aug 21</nowiki>
  }}
}}
 
{{FGCquote
  |Why not simply start a new page on the wiki where anybody can provide contents, so that whenever it's time to send out a newsletter, the draft from the wiki could be taken?<br/>
That way, it wouldn't be too much work for a single person - more like a "community-driven" newsletter, while this may appear to sort of defeat the purpose, not all newsletter recipients are necessarily also wiki users.
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=18015#p18015
    |title=<nowiki>Re: Newsletter</nowiki>
    |author=<nowiki>Hooray</nowiki>
    |date=<nowiki>Fri Oct 03</nowiki>
  }}
}}
 
== Adding backdrop styling to Canvas (by Gijs) ==
Gijs was looking for an outline that follows the shape of the text, which is what backdrop provides.


For his solution, see the two diffs below. He didn't add the full range of backdrop options, just outline for now [http://forum.flightgear.org/viewtopic.php?f=71&t=23500&p=214278#p214275].
Thanks to all readers and contributors.
{{FGCquote
  |And this is how it looks in FlightGear now :-) Notice how the overlapping waypoints are easier to read (this image is a little exaggerated with all those fixes).<br/>
<br/>
(see the [http://i.imgur.com/dqMzBS4.png linked image])
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=214268#p214268
    |title=<nowiki>Re: osgText backdrop</nowiki>
    |author=<nowiki>Gijs</nowiki>
    |date=<nowiki>Mon Jul 07</nowiki>
  }}
}}


<syntaxhighlight lang="diff">
PS: Please take a look at [[FlightGear Newsletter]] if you're interested in helping!
commit 5cc0adc778bda1773189b0119d24fbaf5ecd4500
Author: Gijs de Rooy
Date:  Mon Jul 7 18:26:16 2014 +0200


    Canvas: add backdrop option to text
== Development news ==
 
=== FGCanvas Updates ===
diff --git a/simgear/canvas/elements/CanvasText.cxx b/simgear/canvas/elements/CanvasText.cxx
index d99760a..3a986e1 100644
--- a/simgear/canvas/elements/CanvasText.cxx
+++ b/simgear/canvas/elements/CanvasText.cxx
@@ -39,6 +39,7 @@ namespace canvas
      void setLineHeight(float factor);
      void setFill(const std::string& fill);
      void setBackgroundColor(const std::string& fill);
+      void setOutlineColor(const std::string& backdrop);
      SGVec2i sizeForWidth(int w) const;
      osg::Vec2 handleHit(const osg::Vec2f& pos);
@@ -97,6 +98,15 @@ namespace canvas
  }
  //----------------------------------------------------------------------------
+  void Text::TextOSG::setOutlineColor(const std::string& backdrop)
+  {
+    osg::Vec4 color;
+    setBackdropType(osgText::Text::OUTLINE);
+    if( parseColor(backdrop, color) )
+      setBackdropColor( color );
+  }
+
+  //----------------------------------------------------------------------------
  // simplified version of osgText::Text::computeGlyphRepresentation() to
  // just calculate the size for a given weight. Glpyh calculations/creating
  // is not necessary for this...
@@ -546,6 +556,7 @@ namespace canvas
    addStyle("fill", "color", &TextOSG::setFill, text);
    addStyle("background", "color", &TextOSG::setBackgroundColor, text);
+    addStyle("backdrop", "color", &TextOSG::setOutlineColor, text);
    addStyle("character-size",
              "numeric",
              static_cast<
</syntaxhighlight>
 
 
<syntaxhighlight lang="diff">commit 838cabd2a551834cbcac2b3edd21500409ff2e98
Author: Gijs de Rooy
Date:  Mon Jul 7 18:27:50 2014 +0200
 
    Canvas: add backdrop option to text
 
diff --git a/Nasal/canvas/api.nas b/Nasal/canvas/api.nas
index 8bc12d8..3047dbf 100644
--- a/Nasal/canvas/api.nas
+++ b/Nasal/canvas/api.nas
@@ -634,6 +634,8 @@ var Text = {
  setColorFill: func me.set('background', _getColor(arg)),
  getColorFill: func me.get('background'),
+ 
+  setBackdropColor: func me.set('backdrop', _getColor(arg)),
};
# Path
</syntaxhighlight>
 
== FGCanvas Updates ==
[[File:Dedicated-aircraft-subsystem-group-for-fgcanvas.png|600px|thumb|checking how difficult it would be to put all aircraft related subsystems (fdm, replay, history, controls etc) into a single SGSubsystemGroup named "main-aircraft" to easily make the whole shebang optional using a single --prop for "FGCanvas" use, but also to check if it's feasible to prepare things for later reuse by the AI traffic system (for AI traffic that uses actual FDMs, APs and RMs - but also so that things are affected by the environment) , and it's actually working - even though reset/re-init is obviously hard-coded currently, which I am breaking by shuffling around subsystems, but as long as  each SGSubsystemGroup implements the full SGSubsystem interface (postinit, reinit, shutdown etc), this could help clean up fg_init.cxx quite considerably [http://forum.flightgear.org/viewtopic.php?f=71&t=23499]]]
[[File:Dedicated-aircraft-subsystem-group-for-fgcanvas.png|600px|thumb|checking how difficult it would be to put all aircraft related subsystems (fdm, replay, history, controls etc) into a single SGSubsystemGroup named "main-aircraft" to easily make the whole shebang optional using a single --prop for "FGCanvas" use, but also to check if it's feasible to prepare things for later reuse by the AI traffic system (for AI traffic that uses actual FDMs, APs and RMs - but also so that things are affected by the environment) , and it's actually working - even though reset/re-init is obviously hard-coded currently, which I am breaking by shuffling around subsystems, but as long as  each SGSubsystemGroup implements the full SGSubsystem interface (postinit, reinit, shutdown etc), this could help clean up fg_init.cxx quite considerably [http://forum.flightgear.org/viewtopic.php?f=71&t=23499]]]
{{FGCquote
{{FGCquote
Line 247: Line 114:


=== A Canvas based GNS 530 GPS ===
=== A Canvas based GNS 530 GPS ===
{{FGCquote
After a long hiatus (3 years!) forum user cbendele felt like doing some FlightGear aircraft modeling again. Three years ago, when he started the panel for his Bo, he could not find a nice, modern, panel mount IFR GPS. The King GPS we have is ancient, and the Garmin 196, while nicely modelled, Is a VFR handheld. So he decided to start with this:
  |After a long hiatus (3 years!) I felt like doing some flightgear aircraft modeling again. 3 Years ago when I started the panel for my Bo, I couldn't find a nice, modern, panel mount IFR GPS. The King GPS we have is ancient, and the Garmin 196, while nicely modelled, Is a VFR handheld. So I decided to start with this:<br/>
 
<br/>
[[File:Gns530-prototype-07-2014.png|300px]]
[[File:Gns530-prototype-07-2014.png|300px]]
<br/>
 
I know the GNS530 is already kind of outdated as well, but together with its smaller sibling, the GNS430 it's still much more widespread than its successor (GTN650/750). Also the GTN650/750 use touch screen interfaces, which I'm not really a fan of.<br/>
The GNS530 is already kind of outdated as well, but together with its smaller sibling the GNS430, it is still much more widespread than its successor (GTN650/750). Also the GTN650/750 use touch screen interfaces.
<br/>
 
Right now this is very much work in progress. It's also the first time I wrote more than 5 lines of nasal, so I was basically learning the language while I wrote this. Still, I think it's far enough to present it here and let people try it and send critique and suggestions. Learn more at [[Garmin GNS530]]...
Right now this is very much work in progress. It is also the first time cbendele wrote more than five lines of nasal, so he was basically learning the language while he wrote this. Still, it's far enough to present it here and let people try it and send critique and suggestions. Learn more at [[Garmin GNS530]] or the [http://forum.flightgear.org/viewtopic.php?p=215254#p215254 forum topic]
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=215254#p215254
    |title=<nowiki>Garmin gns530</nowiki>
    |author=<nowiki>cbendele</nowiki>
    |date=<nowiki>Wed Jul 23</nowiki>
  }}
}}


=== Nasal: Making safer base-class calls ===
=== Nasal: Making safer base-class calls ===
There's a lot of Nasal code floating around doing the equivalent of this when using multiple inheritance to make base class calls:
There is a lot of Nasal code floating around doing the equivalent of this when using multiple inheritance to make base class calls:


<syntaxhighlight lang="nasal">
<syntaxhighlight lang="nasal">
Line 323: Line 183:


== FGCamera ==
== FGCamera ==
Development of FGCamera continues. The script is being redesigned to be compatible with default view system.
Development of FGCamera continues. The script is being redesigned to be compatible with default view system. The upcoming version (FGCamera v1) will have new camera mode: "world-view".
Upcoming version (FGCamera v1) will have new camera mode: "world-view".


{{#ev:youtube|hebx8WdXHa0}}
{{#ev:youtube|hebx8WdXHa0}}
Line 331: Line 190:
=== Paro Int. Airport - VQPR ===
=== Paro Int. Airport - VQPR ===
[[File:VQPR PARO AIRPORT.jpg|320px|right]]
[[File:VQPR PARO AIRPORT.jpg|320px|right]]
{{#ev:youtube|itNY9YUmY3M||right|domestic flight from Bumthang to Paro}}
Works have been added to [[Paro Airport|Paro International Airport]] (VQPR) with terminal, tower, hangars and other buildings. Now users you can enjoy the apron lights, the reference points like Mr. Smiths House or other POIs like the Sangchen Choekhor Monastery. [[TerraSync]] has it all! It is not necessary to download any custom scenery. More information can be found on the wiki page: [[Paro Airport]]. This is the first airport of the Bhutanese Series. Three new domestic airports like Gelephu Airport (VQGP) are currently being developed. Work also continues on navaids for the Kingdom of Bhutan - of course only in the FlightGear-World. Everybody is invited to follow the stage of development at the designers wiki user page ([[User:Fgjosh|Fgjosh]]).
Works have been added to [[Paro Airport|Paro International Airport]] (VQPR) with terminal, tower, hangars and other buildings. Now users you can enjoy the apron lights, the reference points like Mr. Smiths House or other POIs like the Sangchen Choekhor Monastery. [[TerraSync]] has it all! It is not necessary to download any custom scenery. More information can be found on the wiki page: [[Paro Airport]]. This is the first airport of the Bhutanese Series. Three new domestic airports like Gelephu Airport (VQGP) are currently being developed. Work also continues on navaids for the Kingdom of Bhutan - of course only in the FlightGear-World. Everybody is invited to follow the stage of development at the designers wiki user page ([[User:Fgjosh|Fgjosh]]).
{{-}}
 
{{#ev:youtube|itNY9YUmY3M}}
 
== Support for Nasal in Notepad++ ==
== Support for Nasal in Notepad++ ==
[[File:Highlight parse.png|400px|thumb|Screenshot of [http://gitorious.org/nasal-support/nasal-npp Nasal support for Notepad++]]]
[[File:Highlight parse.png|400px|thumb|Screenshot of [http://gitorious.org/nasal-support/nasal-npp Nasal support for Notepad++]]]
Programming in Nasal on Windows can now be a lot friendlier with [http://gitorious.org/nasal-support/nasal-npp Nasal support for Notepad++].<br />
Programming in Nasal on Windows can now be a lot friendlier with [http://gitorious.org/nasal-support/nasal-npp Nasal support for Notepad++]. It provides comprehensive syntax highlighting and class/function listing in a hierarchical fashion.  
Provides comprehensive syntax highlighting and class/function listing in a hierarchical fashion.<br/>
 
Syntax highlighting is available for other editors as well, for more information see [[Howto:Syntax highlighting for Nasal]]
Syntax highlighting is available for other editors as well, for more information see [[Howto:Syntax highlighting for Nasal]]
{{-}}


== Primary Flight Displays for Android Devices ==
== Primary Flight Displays for Android Devices ==
Android devices are light, thin, and offer a very decent computing power and graphics processing. They are battery operated and can connect to other devices through WiFi (there is no need of cables). They are, in fact, perfect for integration in home-made cockpits. This new project offers the opportunity of extending their usage in the form of Primary Flight Displays and Navigation displays for airliners in Fligthgear. There are currently 4 Primary Flight Display (PFD) Apps in "early production" state: Basic, Boeing 777, Boeing 787-8, and Airbus 330. The Basic App is at this moment available in the Android Play Store. The other Apps will be uploaded during the next days provided that no serious problems are found in the Basic App. You are more than welcome to test it and give feedback! Visit the project website for more information: https://sites.google.com/site/flightgearandroid/
Android devices are light, thin, and offer a very decent computing power and graphics processing. They are battery operated and can connect to other devices through WiFi (there is no need of cables). They are, in fact, perfect for integration in home-made cockpits. This new project offers the opportunity of extending their usage in the form of Primary Flight Displays and Navigation displays for airliners in FlightGear. There are currently four Primary Flight Display (PFD) Apps in "early production" state: Basic, Boeing 777, Boeing 787-8, and Airbus 330. The Basic App is at this moment available in the Android Play Store. The other Apps will be uploaded during the next days provided that no serious problems are found in the Basic App. You are more than welcome to test it and give feedback! Visit the project website for more information: https://sites.google.com/site/flightgearandroid/


{{#ev:youtube|jd61x-_QNpM}}
{{#ev:youtube|jd61x-_QNpM}}
{{#ev:youtube|Y6M9SyMZSCk}}
{{#ev:youtube|Y6M9SyMZSCk}}
{{#ev:youtube|N1D--DZjvtE}}
{{#ev:youtube|N1D--DZjvtE}}
{{-}}


== Parachute for YASim (Thrusters & Nasal) ==
== Parachute for YASim (Thrusters & Nasal) ==
[[File:V-1 Parachute.png|350px|thumb|V-1falling slowly with a parachute]]
[[File:V-1 Parachute.png|350px|thumb|V-1falling slowly with a parachute]]
Tomaskom developed a realistically behaving parachute for YASim aircraft. It is capable of a slow and stable fall and can recover the aircraft even from very severe rotations. <br/>
Tomaskom developed a realistically behaving parachute for YASim aircraft. It is capable of a slow and stable fall and can recover the aircraft even from very severe rotations. It all began as a question about a parachute which ended by brainstorming of the best approach. See [http://fguk.eu/index.php/forum/development-hangar/4546-external-reactions-forces-in-yasim this forum topic] for the discussion.
It all began as a question about a parachute which ended by brainstorming of the best approach, you can read the related thread here: <br/>
 
http://fguk.eu/index.php/forum/development-hangar/4546-external-reactions-forces-in-yasim <br/>
Re-implementing the code elsewhere is very easy. Most of it can be blindly copied with just some adjustments (trigger binding, chute area, ...). See [http://forum.flightgear.org/viewtopic.php?f=49&p=215650 this forum topic] for instructions.
<br/>
 
Re-implementing the code elsewhere is very easy, most of it can be blindly copied with just some adjustments (trigger binding, chute area, ...). There is a thread on the main forum with HOWTO for implementation, see [http://forum.flightgear.org/viewtopic.php?f=49&p=215650&sid=97b2010406d31b6fc2fabc7cf8b1c8f8 Parachute for YASim (Thrusters & Nasal)]. <br/>
Currently there is a reference implementation in a special version of the V-1 flying bomb, available at [http://fguk.eu/index.php/hangar/viewdownload/11-other-objects-and-vehicles/400-v-1-flying-bomb FGUK]. You can also get an idea of it's stabilization properties from [https://www.dropbox.com/s/81ns5ib5tf3y74t/V-1_Parachute.avi this video]
Currently there is a reference implementation in a special version of the V-1 flying bomb: <br/>
 
http://fguk.eu/index.php/hangar/viewdownload/11-other-objects-and-vehicles/400-v-1-flying-bomb <br/>
The drone (Firebee) for which the parachute was requested is not yet publicly available.
The drone (Firebee) for which the parachute was requested is not yet publicly available. <br/>
You can also get an idea of it's stabilization properties from this video: <br/>
https://www.dropbox.com/s/81ns5ib5tf3y74t/V-1_Parachute.avi
{{-}}


== In the hangar ==
== In the hangar ==
=== Mainair Flash 2 Alpha ===
=== Mainair Flash 2 Alpha ===
[[File:Flash2a_in_Air2.png|350px|thumb]]
The microlight [[Mainair Flash 2 Alpha]] is now weightshift controlled and has a new wing model.
The microlight [[Mainair Flash 2 Alpha]] is now weightshift controlled and has a new wing model.
* redesigned FDM with weightshift-control
* redesigned FDM with weightshift-control
Line 375: Line 230:
* multiplayer ready
* multiplayer ready
* aerotow hitch
* aerotow hitch
[[File:Flash2a_in_Air2.png|400px]]


=== Aero L-159 ALCA ===
=== Aero L-159 ALCA ===
{{#ev:youtube|uLojBI7ezdM||right|L-159 Disintegration}}
{{#ev:youtube|uLojBI7ezdM|350|right|L-159 Disintegration}}
A first public version of the L-159 ALCA (Advanced Light Combat Aircraft) has been released. The aircraft is still in alpha stage and fairly incomplete (there are some changes to the model planned, so no texturing yet, no cockpit instruments), but it already has many advanced and sometimes unique features, most notably the disintegration animations.<br/>
A first public version of the L-159 ALCA (Advanced Light Combat Aircraft) has been released. The aircraft is still in alpha stage and fairly incomplete (there are some changes to the model planned, so no texturing yet, no cockpit instruments), but it already has many advanced and sometimes unique features, most notably the disintegration animations.<br/>
Some of the most important features include:  
Some of the most important features include:  
Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/74601"