https://wiki.flightgear.org/w/api.php?action=feedcontributions&user=Blackiris&feedformat=atomFlightGear wiki - User contributions [en]2024-03-29T08:19:43ZUser contributionsMediaWiki 1.39.6https://wiki.flightgear.org/w/index.php?title=Howto:Texture_a_building&diff=103131Howto:Texture a building2016-08-17T15:05:29Z<p>Blackiris: Fix URL</p>
<hr />
<div>In this [[:Category:Howto|howto]] I'll show how I '''texture a [[FlightGear]] building''' using [[Blender]] and [[Gimp]]. I'll assume you're quite familiar with them both - knowing how to use UV maps in Blender and Layers in Gimp for instance - and can therefore follow my method. <br />
<br />
There are no images in this article. For examples see [[San Francisco International Airport]] (KSFO) terminal 2 (the control tower) or [[London Gatwick Airport]] (EGKK).<br />
<br />
== Approach ==<br />
Variety, randomness and non-uniformity in textures give models a more natural appearance. Use the burn, dodge and blur tools wherever you can and slightly modify textured areas. Lighten edges and darken corners, introduce shadows, subtly change hues and bravely blur details. Darken edges in contact with the ground and add random highlights at corners and horizontal surfaces. Make the observer's eye and brain work a little more and (s)he will often assume that the fuzz contains more than it actually does. Give him(er) sharp lines and pure tones and (s)he will just see unrealistic forms. Of course, if you have your own photographs of building elevations then your work is much easier.<br />
<br />
== Blender ==<br />
=== Modelling ===<br />
I guess you've almost finished constructing your model in Blender saving regularly as you go along ({{key press|F2}}, {{key press|+}}, {{key press|Enter}}). If in doubt at any stage, simplify entities as simple geometric forms and add as much detail as you wish (future PCs will always be able to handle whatever you construct and low power users can always opt for another model). Remember to get the scale of your model correct. An alternative estimate of height is to make each storey (floor) 3m high or try importing an existing building and sit it by the side of yours.<br />
<br />
For this howto I chose an existing, simple FG model - <tt>[[$FG ROOT]]/Models/Industrial/Industrial50x100.ac</tt> which is not yet textured. In Blender I combined the two object meshes ({{key press|Ctrl}}+{{key press|J}}) to make UV mapping easier. Looking at the model in Blender I also saw that I could merge several vertices (select, Mesh, Vertices, Merge, At Center). This reduced vertices from 26 to 14 without changing the model. I increased the roof overhang which was not prominent so it was considered better to exaggerate it a little - every little bit of complexity adds to the realism in FG. Right, that's the modelling done now to bring it to life with texturing.<br />
<br />
=== UV Maps ===<br />
Create a UV map by selecting all vertices ({{key press|A}}) in Edit Mode ({{key press|Tab}}) and using Blender's powerful UV generator (Mesh, UV Unwrap, Unwrap (smart projections). Quite often the UV map layout seen in the UV/Image Editor window is not suitable for full utilisation of available texture space; so the UV maps need manipulation, as described later.<br />
<br />
=== UV Alternative Method ===<br />
# Build up the UV map by first selecting one face and projecting it exactly as it is seen in the Edit view (Mesh, UV Unwrap, Project From View).<br />
# Repeat this for each face and chosen an appropriate view from which to project - thus building up the whole UV mapping of the model. It is convenient to move each UV map away from the grid area to avoid them being sat on top of each other before organizing them back on the grid in an efficient layout. <br />
# Finally, check there are no isolated UV's by selecting all vertices which then displays all the UV maps.<br />
<br />
=== Organize UV Maps ===<br />
In either case the next job is to tidy up the positions of the UV maps so that the available space is utilised most efficiently. This can take some time but is a worthwhile process. The aim is to make most use of the UV grid available, so start with the most important aspect of the building and give it the largest area - in this case the side that would normally be seen from your aircraft. <br />
# Select each UV map ({{key press|Ctrl|L}}), resize it if necessary ({{key press|S}}) and grab it ({{key press|G}}) and move it into position until all maps are located so that the grid area is fully used. Superimpose the long wall on top of each other to make the best use of space. Also do the same the same with the end walls, gable ends and roof. <br />
# Change things a little, if necessary, as you go along but it is worth the effort. A neat trick is to expand the UV maps of the long walls outside the grid area so that a single texture area can be repeated thus giving much more detail to your building (some adjustments can be done in Blender later).<br />
<br />
=== Export UV Map ===<br />
When you’ve created a compact UV map layout on the grid export it ready for painting the textures (UV/Image Editor view, {{key press|A}}, UVs, Scripts, Save UV Face Layout, Size:512, OK, <tt>Industrial50x100_new.tga</tt>). Keep Blender open because you will be doing an iterative process later.<br />
<br />
== Gimp ==<br />
# Open Gimp and open the <tt>Industrial50x100.tga</tt> file and use this as the base for the texturing. <br />
# Create a new layer (Layer, New, colour) and fill the layer with the main colour of the building - say a warm tan-grey. This is eventually going to be lightened, darkened and smeared to give variety. <br />
# Set the opacity of the layer so that the underlying <tt>Industrial50x100.tga</tt> layout can be seen (60%). <br />
# Save the file regularly as <tt>Industrial50x100.xcf</tt>.<br />
<br />
=== Texturing Strategy ===<br />
Details of the building are then painted. This is where you use knowledge and observation of the real world. For example: no areas are completely uniform, there is variety everywhere, there are subtle changes in hue (colour values) in everything and hardly ever are colours seen in pure form. If in doubt, always tone things down, blur details and add a little blue to make things blend into the distance. Weathering is important too, most entities are bleached by the sun, smeared by the rain and generally age. If in doubt, do it (you can't do worse than the gaudy, uniform tones of many models).<br />
<br />
=== Walls ===<br />
# Create a new layer called “walls“ (Layer, New Layer, walls). <br />
# Switch the grid on (View, Show Grid) and adjust to show many lines (Image, Configure Grid). <br />
# Draw several vertical corrugated sides using the Pencil tool, dark tone and keep them straight (click and {{key press|Shift}}) using the grid as guide. <br />
# Select the drawn area, copy and paste it as a new layer. <br />
# Position the new layer alongside thus creating a larger corrugated wall area. <br />
# Repeat pasting and creating new areas a number of times until the corrugated area is complete. During this process, laterally invert a couple of the layers to give variety. Merge Down the layers until one corrugated layer is left. <br />
# Mildly Burn and Dodge this layer randomly to give more variety. Blur a little to add subtlety. <br />
# Copy the layer (Layer, Duplicate Layer, wall_end (.... and ...., gable)) and position over the gable and end wall regions and use the Eraser to create suitable shaped areas. <br />
# Subtly darken, lighten and blur the lines again in random areas to give variety.<br />
# Select the colour layer, using the Rectangle Select tool and select a single wall area in between the vertical lines and, using the shift key, select another wall area nearby. <br />
# Still holding the shift key down, repeat this a dozen or so times so that the colour layer has a number of randomly selected rectangular areas. Change them in hue a little (Colors, Hue saturation) and also Burn and Dodge a little then switch the selection off ({{key press|Shift|Ctrl|A}}).<br />
<br />
=== Roof ===<br />
# Create a layer for the roof lines (Layer, New Layer, roof) and draw them in a different style from the wall lines (again to add variety).<br />
# Treat the roof lines in a similar manner to the wall lines: random darken, lighten, blur.<br />
<br />
=== Rooflights ===<br />
# Create a “rooflights” layer (Layer, New Layer, rooflights).<br />
# Select a small rectangular area and fill it with dark blue. <br />
# Burn this a little over part of the area then Blur it a little. <br />
# Use the Pencil tool to draw a frame around the edges of the rectangle in a lighter and slightly different colour. Always change colours and tones a little to randomize the visual effects. <br />
# Still with rectangular area selected, copy and paste as a new layer. <br />
# Move it a slight distance along the roof in between the joints. <br />
# Switch the selection off. <br />
# Duplicate the rooflights layer a number of times, occasionally laterally inverting the layer, and position along the roof to create a row of roof window lights. <br />
# Merge Down the layers to give just one rooflights layer.<br />
<br />
=== Windows ===<br />
Similarly to above, a "windows" layer is created and windows are painted. <br />
# Once the window frames are drawn over the varied glass tones randomly select (holding down the {{key press|Shift}} key) a number of the rectangular window panes and use the Dodge and Burn tools in a casual manner to give more variety to the panes; add extra highlights to give the impression of the reflected sky, for example. <br />
# Copy the first window, paste, layer and change it slightly to make it subtly different.<br />
<br />
=== Doors ===<br />
# Create a "doors" layer paint a rectangular area slightly different in hue from the wall colouring. <br />
# Create a line layer created over the top of this on which a few horizontal lines can be drawn to represent joints in the roller door. Copy these to give enough lines to cover the door. <br />
# Darken, lighten and blur these lines in a non-uniform manner.<br />
# A personnel door should also be constructed - another hue with more darkening, lightening and blurring.<br />
<br />
=== Shadows ===<br />
Make a "shadows" layer and add overhang shadows with the airbrush set at 15% opacity. Blur the bottom edges.<br />
<br />
=== Weathering ===<br />
# Merge all the layers as "day" ready to check, add final details, weather and create night textures. <br />
# Check that the alpha layer works by Erasing a small area to reveal a chequered background. <br />
# Carry out weathering by using the Burn tool along the ground edges and Smudging a little. <br />
# Lighten the corners and add one or two specks of highlight on roof fittings. <br />
# Do a final pass with the Burn tool over corner areas.<br />
<br />
=== Iteration ===<br />
During all the operations above, save the texture file as <tt>Industrial50x100.png</tt> and reload it in Blender and view it on the model to see how it is progressing (View, Texture Mode).<br />
<br />
=== Night Textures ===<br />
# Resize the "day" layer to 512 width 256 height (Layer, Scale Layer, unlock link).<br />
# Carefully position the layer exactly on the bottom of the working square. <br />
# Duplicate the resized layer and name it "night" and move it exactly on to the top edge of the square. <br />
# Create a new layer called "dark" and colour it almost blue-black. <br />
# Sort the layers so that the "day" layer sits at the top with the "dark" layer next and the "night" layer at the bottom. <br />
# Add another layer at the bottom called “light”. Colour it pale yellow. <br />
# Adjust the opacity of the "dark" layer so that detail on the "night" layer could be seen underneath. <br />
# Select the window areas so that the corresponding areas on the "dark" layer can be Erased leaving the windows showing through. <br />
# Keep the areas slected and move to the “night” layer and Erase the windows leaving the pale yellow “light” layer showing through. <br />
# The windows may then be modified a little by Dodging and Blurring.<br />
#* Paint the window frames in black. (A drawing guide can be made by making a copy of the "night" layer but often, a guess is good enough). <br />
#* Treat the rooflights in the same manner. <br />
#* A similar procedure is carried out to create half opened doors. <br />
#* Lights falling on walls may be created by using the Eraser at 10% opacity and gently revealing details under the "dark" layer. <br />
#* Another technique is to use the Overlay mode whilst Airbrushing very pale yellow around window and door edges to give a slight glare or hazy appearance. <br />
# Increase the "dark" layer opacity back to about 94% before finally saving the file as <tt>Industrial50x100.png</tt> to give the texture for use on the Blender model.<br />
<br />
== Blender again ==<br />
# Make one more visit to the Blender model to change the UV maps to coincide with the textures. Select all the UV maps in the UV/Image Editor and scale by a factor of 0.5 in the Y direction ({{key press|S}}, 0.5, {{key press|Y}}).<br />
# Carefully grab and position exactly on the bottom of the grid square ({{key press|G}}, {{key press|Y}}). The UV maps are then on the bottom of the UV grid square with the "day" textures sat exactly on the top and ready for the switch to "night" textures with .xml file.<br />
# Export the model as <tt>Industrial50x100.ac</tt>.<br />
<br />
== XML ==<br />
A xml file is needed to switch on the night textures at the correct time. Copy an existing xml file and change the appropriate lines for model and texture. Because the textures were made in this model to repeat horizontally, the swipe of the textures has to be in the Y direction.<br />
<br />
== Testing ==<br />
Copy the files <tt>Industrial50x100.ac</tt>, <tt>Industrial50x100.png</tt> and <tt>Industrial50x100.xml</tt> to your <tt>[[$FG ROOT]]/Models/Industrial/</tt> folder ready to try out in the [[Howto: Place 3D objects with the UFO|UFO view]] in FlightGear.<br />
== Database ==<br />
This model has been added to the FlightGear Models database https://scenery.flightgear.org/app.php?c=Models&a=browse&shared=4<br />
<br />
[[Category:Scenery enhancement|Texture a Building]]<br />
[[Category:Howto|Texture a Building]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=FlightGear_Scenery_Database&diff=86087FlightGear Scenery Database2015-07-07T22:42:47Z<p>Blackiris: Update GIT repo URL</p>
<hr />
<div>The '''FlightGear Scenery Database''' collects all 3D objects that are placed in the [[FlightGear]] [[World Scenery]] releases.<br />
<br />
== Contribute ==<br />
* ''Contribution guidelines'' are available at http://scenemodels.flightgear.org/contribute.php<br />
* ''Semi''-automatic insert/delete/update webtools for shared and static objects/models are here : http://scenemodels.flightgear.org/submission<br />
<br />
=== Interactive World Map to update & delete objects === <br />
http://mapserver.flightgear.org/popmap/?zoom=9&lat=51.36835&lon=7.0752&layers=0BTTTTTTT<br />
<br />
Zoom in to the place of you interest. If you zoom enough then the dots change to big red arrows. Click on the arrow to see the thumbnail of the object. click on '''update''' to modify the object (model, position, orientation, elevation offset). If you are sure that this object does not exist in real life then click on '''delete'''. If flightgear shows a skyscraper and in real life there is a communication tower then don't delete but update the object (generic skyscaper -> radio tower)<br />
<br />
== Related content ==<br />
* [[FlightGear related projects]]<br />
<br />
== External links ==<br />
* [http://scenemodels.flightgear.org FlightGear Scenery Database]<br />
* [http://sourceforge.net/p/flightgear/sceneryweb/ Website repository] (Sourceforge)<br />
<br />
[[Category:Scenery]]<br />
[[Category:Scenery enhancement]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=Landmark_Wish_List&diff=85856Landmark Wish List2015-07-02T20:00:12Z<p>Blackiris: One Raffles Place done</p>
<hr />
<div>This page provides a list of landmarks which are not currently in the FlightGear scenery that the community consider important and would like to see modeled.<br />
<br />
If you are a FlightGear modeler and are looking for something to model, please consider something on this list.<br />
<br />
Feel free to add to this list.<br />
<br />
__TOC__<br />
<br />
{{note|<br />
If you are modelling a landmark, please change the "Completed" column from {{tl|no}} to <nowiki>{{</nowiki>[[:Template:n/a|n/a|Claimed]]<nowiki>}}</nowiki>, and when done change to {{tl|yes}}.}}<br />
<br />
== Africa ==<br />
{| class="wikitable sortable"<br />
! Landmark !! City !! Country !! Completed<br />
|-<br />
| {{wikipedia|Basilica of Our Lady of Peace of Yamoussoukro}} || Yamoussoukro || Côte d'Ivoire || {{no}}<br />
|-<br />
| {{wikipedia|Mount Kilimanjaro}} || Kilimanjaro National Park || Tanzania || {{no}}<br />
|-<br />
| Pyramids || Cairo || Egypt || {{yes}}<br />
|-<br />
| {{wikipedia|Table Mountain}} || Cape Town || South Africa || {{no}}<br />
|-<br />
| Victoria Falls || Victoria Falls || Zimbabwe || {{no}}<br />
|}<br />
<br />
== America ==<br />
{| class="wikitable sortable"<br />
! Landmark !! City !! Country !! Completed<br />
|-<br />
| Adler Planetarium || Chicago || USA || {{no}}<br />
|-<br />
| Bank of America Tower || New York || USA || {{yes}}<br />
|-<br />
| Brooklyn Bridge || New York || USA || {{n/a|Claimed}}<br />
|-<br />
| Christ the Redeemer || Rio de Janeiro || Brazil || {{yes}}<br />
|-<br />
| Chrysler Building || New York || USA || {{yes}}<br />
|-<br />
| Empire State Building || New York || USA || {{yes}}<br />
|-<br />
| {{wikipedia|Hoover Dam}} || Boulder|| USA || {{no}}<br />
|-<br />
| {{wikipedia|Machu Picchu}} || Aguas Calientes || Peru || {{no}}<br />
|-<br />
| Marina City || Chicago || USA || {{no}}<br />
|-<br />
| McCormick Place || Chicago || USA || {{no}}<br />
|-<br />
| Millenium Park || Chicago || USA || {{no}}<br />
|-<br />
| Milwaukee Art Museum || Milwaukee || USA || {{no}}<br />
|-<br />
| National Congress || Brasilia || Brazil || {{yes}}<br />
|-<br />
| Navy Pier || Chicago || USA || {{no}}<br />
|-<br />
| {{wikipedia|Nazca Lines}} || Estudiantes || Peru || {{no}}<br />
|-<br />
| Oglivie Transportation Center || Chicago || USA || {{no}}<br />
|-<br />
| {{wikipedia|Panama canal}} and some boats pls|| Panama city - Colòn || Panama || {{yes}}<br />
|-<br />
| Shedd Aquarium || Chicago || USA || {{no}}<br />
|-<br />
| {{wikipedia|Skunk Works|Skunkworks aircraft] hidden in the mountain of KXTA || Area 51 || USA || {{no}}<br />
|-<br />
| Smurfit-Stone Building || Chicago || USA || {{no}}<br />
|-<br />
| Soldier Field || Chicago || USA || {{no}}<br />
|-<br />
| Space Needle || Seattle || USA || {{yes}}<br />
|-<br />
| Union Station || Chicago || USA || {{no}}<br />
|-<br />
| United Center || Chicago || USA || {{no}}<br />
|-<br />
| United Nations Headquarters || New York || USA || {{yes}}<br />
|-<br />
| U.S. Cellular Field || Chicago || USA || {{no}}<br />
|-<br />
| Verizon Center || Washington, D.C. || USA || {{no}}<br />
|-<br />
| {{wikipedia|Windsor Atlantica Hotel}} || Rio de Janeiro || Brazil || {{n/a|Claimed}}<br />
|-<br />
| White House || Washington, D.C. || USA || {{no}}<br />
|-<br />
| Wrigley Field || Chicago || USA || {{no}}<br />
|}<br />
<br />
== Asia ==<br />
{| class="wikitable sortable"<br />
! Landmark !! City !! Country !! Completed<br />
|-<br />
| Akashi Kaikyo bridge || Kobe || Japan || {{yes}}<br />
|-<br />
| Azadi Square || Tehran || Iran || {{no}}<br />
|-<br />
| Bank of China Tower || Hong Kong || China || {{yes}}<br />
|-<br />
| Bitexco Financial Tower || Ho Chi Minh City || Vietnam || {{yes}}<br />
|-<br />
| Burj al Arab || Dubai || UAE || {{yes}}<br />
|-<br />
| Burj Khalifa || Dubai || UAE || {{yes}}<br />
|-<br />
| CCTV Tower || Beijing || China || {{yes}}<br />
|-<br />
| {{wikipedia|Kai Tak Airport|"Checkerboard Hill" (VHHX approach)}} || Hong Kong || China || {{no|No, see [[Talk:Landmark_Wish_List#VHHX request| talk page]]}}<br />
|-<br />
| Great Wall of China || Huairou, Peking / Jiuduhezhen, Huairou, Peking || China || {{no}}<br />
|-<br />
| [[Talk:Landmark_Wish_List#Singapore| Marina Bay Sands]] || Singapore ||Singapore || {{yes}}<br />
|-<br />
| Milad Tower || Tehran || Iran || {{no}}<br />
|-<br />
| Mount Everest || Chukhung || Nepal || {{no}}<br />
|-<br />
| [[Talk:Landmark_Wish_List#Singapore| One George Street]] || Singapore ||Singapore || {{no}}<br />
|-<br />
| [[Talk:Landmark_Wish_List#Singapore| One Raffles Place]] || Singapore ||Singapore || {{yes}}<br />
|-<br />
| [[Talk:Landmark_Wish_List#Singapore| One Shenton Way]] || Singapore ||Singapore || {{no}}<br />
|-<br />
| Petronas Towers || Kuala Lumpur || Malaysia || {{yes}}<br />
|-<br />
| [[Talk:Landmark_Wish_List#Singapore| The Pinnacle@Duxton]] || Singapore ||Singapore || {{no}}<br />
|-<br />
| Ryugyong Hotel || Pyongyang || North Korea || {{yes}}<br />
|-<br />
| Sigiriya || Matale District || Sri Lanka || {{no}}<br />
|-<br />
| Taj Mahal || Agra || India || {{yes}}<br />
|}<br />
<br />
== Europe ==<br />
{| class="wikitable sortable"<br />
! Landmark !! City !! Country !! Completed<br />
|-<br />
| Aeroport Leonardo da Vinci INTL || Rome,Fiumicino || Italy || {{no}}<br />
|-<br />
| Big Ben || London || UK || {{yes}}<br />
|-<br />
| Colosseum || Rome || Italy || {{yes}}<br />
|-<br />
| Lapan || Oldenburg, Niedersachsen || Germany || {{no}}<br />
|-<br />
| North Pole (flag and light) || North Pole || World || {{no}}<br />
|-<br />
| Oeresund Bridge || Copenhagen-Malmo || Scandinavia || {{yes}}<br />
|-<br />
| {{wikipedia|Oslo Plaza}} || Oslo || Norway || {{n/a|Claimed}}<br />
|-<br />
| Porta Westfalica/Hermans-Denkmal || Bückeburg (ETHB), Minden || Germany || {{no}}<br />
|-<br />
| Schloss || Oldenburg || Germany || {{no}}<br />
|-<br />
| Schloss || Neuschwanstein || Germany || {{n/a|Claimed}}<br />
|-<br />
| Stade de France || Saint-Denis || France || {{no}}<br />
|-<br />
| Westminster Abbey || London || UK || {{yes}}<br />
|-<br />
| Zwischenahner Meer || Zwischenahn, Niedersachsen || Germany || {{n/a|CS done}}<br />
|}<br />
<br />
== Australia and Oceania ==<br />
{| class="wikitable sortable"<br />
! Landmark !! City !! Country !! Completed<br />
|-<br />
| Ayers rock || Uluru || Australia || {{no}}<br />
|-<br />
| Sky Tower || Auckland || New Zealand || {{n/a|Claimed}}<br />
|-<br />
| Sydney Opera House || Sydney || Australia || {{yes}}<br />
|}<br />
<br />
== Related content ==<br />
* [[FlightGear Scenery Designer]]<br />
* [[FlightGear Scenery Database]]<br />
* [[UK Scenery Wish List]]<br />
<br />
== External links ==<br />
* [http://forum.flightgear.org/viewtopic.php?f=5&t=2390 The forum topic]<br />
* See [http://scenemodels.flightgear.org/ FGFS Scenery Object Database], for more on models for [[Scenery]]<br />
<br />
[[Category:Scenery]]<br />
[[Category:Community]]<br />
[[Category:Contribution requests]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_November_2014&diff=77882FlightGear Newsletter November 20142014-11-17T21:38:29Z<p>Blackiris: /* Scenery corner */</p>
<hr />
<div>{{draft|newsletter}}<br />
<br />
<br />
{{Newsletter-header|November 2014}}<br />
<div style="border-bottom:3px double #BBB;"><br />
{| width="100%" |<br />
| valign="top" width="33%" |<br />
{{Newsletter-cover-header|Development news}}<br/><br />
{{Newsletter-cover-item|Scripted AI objects|[[User:Red_Leader|Red Leader]]}}<br/><br />
<br />
| valign="top" width="33%" |<br />
{{Newsletter-cover-header|Scenery corner}}<br/><br />
<br />
| valign="top" width="33%" |<br />
{{Newsletter-cover-header|Events}}<br/><br />
{{Newsletter-cover-item|FSweekend 2014}}<br/><br />
|}<br />
</div><br />
<br />
== Development news ==<br />
=== Scripted AI objects ===<br />
For a long time, one of the [[:Category:Popular_Community_Requests|popular requests]] has been to have more combat-related features in [[FlightGear]]. Although FlightGear is not a combat simulator, this has, at least partly, been made possible by the [[Bombable]] add-on. However, work has begun on a new framework that will enable easy creation of scripted {{Abbr|AI|Artificial Intelligence}} objects using [[Nasal]]. This work, although available for scripts such as tanker.nas, will also be used for a more generic AI missile framework, but is not specific to just combat applications-the same modules can be used to create scripted drone/UAV scenarios. Continue reading at [[Scripted_AI_Objects|Scipted AI Objects]]...<br />
<br />
<gallery mode="packed"><br />
File:Missile instances.png|Screenshot showing the ability of [[User:Red_Leader|Red Leader's]] AI missiles script to instantiate an arbitrary number of AI models that can be independently updated/controlled (using the tanker 3D model here, which is rotated each frame using [https://gitorious.org/fg/hoorays-fgdata/source/2857d8fc9fcfe2bb162a9eb9d3dcca4d41b3a876:Nasal/ai/aim9/aim9.fdm#L9 a simple/pseudo FDM], for illustration purposes).<br />
File:Missiles on a map.png|[[User:Red_Leader|Red Leader's]] AI missiles script used for instancing and controlling independent missiles, shown on the hard-coded [[Map]] dialog.<br />
File:MapStructure-TFC-with-scripted-AI-missiles.png|Scripted AI missiles used to populate the sky with independently-controlled AI objects, shown using the [[MapStructure]] TFC [[Canvas MapStructure Layers|(traffic) layer]] (TCAS symbology).<br />
File:Aim9-via-scripted-AI-missiled.png|The [[Scripted AI Missiles]] framework actually being used to instantiate and animate a number of independent Aim9 missiles.<br />
</gallery><br />
<br />
== In the hangar ==<br />
<br />
== Scenery corner ==<br />
=== List of updated airports ===<br />
These airports have seen new and/or updated models:<br />
*La Coruña Airport (LECO)<br />
*Nowe Miasto Airport (EPNM)<br />
*Heraklion International Airport (LGIR)<br />
*Flamingo International Airport (TNCB)<br />
*Porto Velho International Airport (SBPV)<br />
<br />
<br />
=== Updated cities ===<br />
*Barcelona (La Monumental, and some skyscrapers)<br />
*Washington DC (US Capitol, and some memorials)<br />
*La Coruna (some landmarks)<br />
*Ho Chi Minh City (some skyscrapers)<br />
<br />
== Events ==<br />
=== FSweekend 2014 ===<br />
On the 1<sup>st</sup> and 2<sup>nd</sup> of November, the FSWeekend 2014 was celebrated at EHLE Leylstad Airport, and as always FlightGear was present! <br />
On the same dates, FG users held a festival on the Iberian peninsula with minigames and ATC'ing. Everyone had fun flying!<br />
=== USA Tour 15<sup>th</sup> November ===<br />
IHAM-COL has something special for us this month – a balloon/airship flight between KEWR and KJFK, a distance of only 20nm! He has also opened it for any towable/glider aircraft. Basically anything lighter than air, or that glides.<br />
Sign up here: http://forum.flightgear.org/viewtopic.php?f=10&t=24296<br />
<br />
<br />
[[Category:FlightGear Newsletter|2014 11]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=Troubleshooting_crashes&diff=77749Troubleshooting crashes2014-11-11T14:42:45Z<p>Blackiris: /* Debugging Segfaults & Obtaining Backtraces */</p>
<hr />
<div>{{Troubleshooting}}<br />
{{note|'''This article is valid for FlightGear versions: 2.6, 2.8, 2.10, 2.12, 3.0+'''. Help us in keeping this article up to date! If you're facing some crash not listed here and manage to solve it, '''please add it to a proper section''', so that other can benefit from your experience!}}<br />
<br />
Crashes are never easy to troubleshoot. It's very likely that you'll need to experiment a bit to find out the cause, or at least to provide useful feedback. In fact issues depend a lot on things like hardware components, driver support and so on. Developers can't work on your machine, so you'll need to provide them with some specific information. This article will guide you in that.<br />
<br />
If not only FlightGear, but the whole system crashes, or freezes, please refer to [[System Crashes]].<br />
<br />
If in the end you like bug hunting, please consider helping in [[Volunteer#Pre-Release Testers|testing future releases]].<br />
<br />
== Known problems ==<br />
Before diving into the real troubleshooting, first try to see if one of the following is your case. This could be a huge time saver!<br />
<br />
'''If you problem is not listed here, please consider adding it after you have solved it! Others like you will be grateful!'''<br />
<br />
=== Optimus/Hybrid graphics technologies for laptops ===<br />
If FlightGear crashes with <br />
Unknown exception in the main loop. Aborting... <br />
Possible cause: Not enough space<br />
and you happen to have a laptop with Optimus Technology (NVidia) or Hybrid Graphics technology (ATI) onboard, you'll find some help at [[Troubleshooting performance issues#Operating system and driver setup]]. (Note that the problem is treated there because it's mostly cause of low performance.)<br />
<br />
=== World Scenery 2.0 and 32-bit machines ===<br />
[[World Scenery]] 2.0 (the one with [[CORINE]] and [[OpenStreetMap]] data) highly raised memory requirements with respect to the previous version. Basically, with 4GB of RAM once you could safely use a visibility of a hundred kilometers; with Scenery 2.0, 4GB is barely enough for 10 km. A 32-bit machine can't use more than that memory, and simply kills FlightGear when it asks for more. To verify this, reduce your visibility (in-sim with ''View > Level of Detail adjustment'' and set ''Bare'' to 5000 m) and see if it stops crashing. You can also check memory consumption with the tools provided by your OS.<br />
<br />
Sadly, the solution is keeping a low visibility, or moving to a 64-bit machine with at least 8GB of RAM, which can provide even 45km of visibility. If you're feeling "hackish", you can try the solution reported at [[Unexpected Crashes with Scenery ver.2]].<br />
<br />
=== Old graphics cards and FlightGear 2.10 ===<br />
If you're using FlightGear 2.10, you're seeing crashes during simulator startup (without seeing the actual aircraft/scenery), and you're using an old enough graphics card, it is possible that your crash is due to a bug in that FG version and to your card lacking [[Shader|GLSL]] support. This bug would prevent using FG even with shaders off! Ironically, this bug comes from a feature introduced to help troubleshooting bugs.<br />
<br />
So, if you're on 2.10 and think your card could be old enough, try the minimal startup configuration below: if it keeps crashing, that's definitely it. The bug was solved immediately later (ver. 2.11)<br />
<br />
== Troubleshooting your crash ==<br />
FlightGear crashes are due to a number of reasons, not necessarily to bugs in its code. After all, it works "out of the box" for most users, so if something's broken it's often a system-specific issue, and yet again, it could be a system configuration that the developers couldn't test - [[Volunteer#Pre-Release Testers|you can help with that]]!)<br />
<br />
It's just as well possible that the FlightGear default settings are not supported with your hardware/drivers. Since version 2.6, FlightGear will assume support for certain features that hardware older than 4-5 years might not give (especially graphics cards), so the default settings need to be customized to disable all unsupported features. See [[Troubleshooting performance issues]], [[Problematic Video Cards]] and [[FlightGear Hardware Recommendations]] for more details.<br />
<br />
=== Preliminary check ===<br />
Make sure you've got the newest driver for your video card installed and running without errors. A suggestion for a thorough updating procedure can be found at [[Graphics drivers configuration]]. '''Before proceeding any further, please make sure that you are actually able to run other OpenGL-based software/simulators/games, unrelated to FlightGear!'''<br />
<br />
=== The standard procedure ===<br />
Given the above, it is important to start up FlightGear with a '''minimal startup profile''', with ''all'' eye candy and features disabled (so that FG won't crash due to lack of support for them) and start re-enabling them step by step to see what's supported by your hardware. You may want to [[Flightgear debug log|raise the FlightGear log level]], so that you get to see where the program stops starting/working, and what it was doing before it got terminated. This procedure will also help in [[troubleshooting performance issues]].<br />
<br />
These settings use the simple UFO and a suitable scenery location to rule out aircraft or scenery as a cause for crashes. Don't even touch the aircraft and location settings (airport, azimuth, offset) until you have really fixed everything else already. Working step by step is the only real way, so don't bite off more than you can chew.<br />
<br />
If you find it looks like the Windows "compatibility mode" that you boot into after a crash, then you understand perfectly what we're doing here. However it's not as straightforward to do, so if in trouble [http://forum.flightgear.org/viewforum.php?f=17 ask for support at the forum]!<br />
<br />
=== Minimal startup profile ===<br />
{{Note|If you find any other settings causing a massive improvement of performance/compatibility, please feel free to add those below, so that others can benefit from your findings.}}<br />
<br />
<gallery mode="packed"><br />
Tweaking-nvidia-settings1.png|Tweaking nvidia settings to obtain higher frame rates by disabling vsync to blank<br />
Tweaking-nvidia-settings2.png|Tweaking Nvidia Powermizer to obtain higher frame rates<br />
</gallery><br />
<br />
<br />
Depending on the hardware specs of the target platform, adjusting the threading mode of FG/OSG may also help: [[Howto:Activate multi core and multi GPU support]]. (If you don't know what we're talking about, you can safely leave it as it is.)<br />
<br />
You can directly use a custom [[Fgfsrc]] file for the following sections or parse the following lines to the console (separated by one empty character, e.g. a space) after "FGFS" or set the respective options in [[Fgrun]] or in [[FlightGear configuration via XML|one of FlightGear's XML configuration files]]. <br />
<br />
Please make sure to rename/delete your autosave and fgfsrc files prior to trying these settings, or your local settings would possibly override these settings.<br />
<br />
<pre><br />
# --ignore-autosave # uncomment this for FlightGear versions >= 2.99<br />
--airport=ksfo<br />
--offset-distance=4000<br />
--offset-azimuth=90<br />
--altitude=500<br />
--heading=0<br />
--model-hz=60<br />
--disable-random-objects<br />
--prop:/sim/rendering/texture-compression=off<br />
--prop:/sim/rendering/quality-level=0<br />
--prop:/sim/rendering/shaders/quality-level=0<br />
--disable-ai-traffic<br />
--prop:/sim/ai/enabled=0<br />
--aircraft=ufo<br />
--disable-sound<br />
--prop:/sim/rendering/random-vegetation=0<br />
--prop:/sim/rendering/random-buildings=0<br />
--disable-specular-highlight<br />
--disable-ai-models<br />
--disable-clouds<br />
--disable-clouds3d<br />
# --disable-textures<br />
--fog-fastest<br />
--visibility=5000<br />
--disable-distance-attenuation<br />
--disable-enhanced-lighting<br />
--disable-real-weather-fetch<br />
--prop:/sim/rendering/particles=0<br />
--prop:/sim/rendering/multi-sample-buffers=1<br />
--prop:/sim/rendering/multi-samples=2<br />
</pre><br />
<br />
{{Tip|Beginning with FlightGear 3.1+, you can also toggle individual scenegraph traversal masks on/off (these can be changed at runtime using the [[Property browser]]:<br />
* <nowiki>--prop:/sim/sceneryloaded-override=1</nowiki><br />
* <nowiki>--prop:/sim/rendering/draw-mask/terrain=0</nowiki><br />
* <nowiki>--prop:/sim/rendering/draw-mask/aircraft=0</nowiki><br />
* <nowiki>--prop:/sim/rendering/draw-mask/models=0</nowiki><br />
* <nowiki>--prop:/sim/rendering/draw-mask/clouds=0</nowiki><br />
}}<br />
<br />
If you're running on Windows, you can use the following batch file to start the simulator using the minimal profile. Open Notepad, copy and paste the following lines and save the file on the Desktop (name it ''fgminimal.bat''); change ''C:\Program Files\FlightGear'' to the directory you installed FlightGear in and change ''Win64'' to ''Win32'' if you are using the 32-bit version.<br />
<pre><br />
@echo off<br />
"C:\Program Files\FlightGear\bin\Win64\fgfs.exe" --fg-root="C:\Program Files\FlightGear\data" --ignore-autosave --airport=ksfo --offset-distance=4000 --offset-azimuth=90 --altitude=500 --heading=0 --model-hz=60 --disable-random-objects --prop:/sim/rendering/texture-compression=off --prop:/sim/rendering/quality-level=0 --prop:/sim/rendering/shaders/quality-level=0 --disable-ai-traffic --prop:/sim/ai/enabled=0 --aircraft=ufo --disable-sound --prop:/sim/rendering/random-vegetation=0 --prop:/sim/rendering/random-buildings=0 --disable-specular-highlight --disable-ai-models --disable-clouds --disable-clouds3d --fog-fastest --visibility=5000 --disable-distance-attenuation --disable-enhanced-lighting --disable-real-weather-fetch --prop:/sim/rendering/particles=0 --prop:/sim/rendering/multi-sample-buffers=1 --prop:/sim/rendering/multi-samples=2<br />
</pre><br />
Double-click the batch file to start FlightGear.<br />
<br />
Using these settings, frame rates between 400-500 fps and a steady frame spacing (latency) of 3-11 ms, can be achieved on a notebook from 2007 (1024x768). Disabling wireframe mode lowers the framerate by about 50-80 fps. The window should be up and running (fully initialized) within 3-5 seconds, even on moderately old hardware (absent a navcache rebuild).<br />
<br />
[[File:Fgfs28-bare-bones.png|thumb |FlightGear 2.10 bare bones on 2006-era hardware (NVIDIA 7600GO)]]<br />
[[File:Screen shot minimal startup profile without textures 2.12.png|thumb |FG 2.12 zero eyecandy mode on 2009-era hardware (NVIDIA 260M)]]<br />
[[File:Screen shot minimal startup profile with textures in 2.12.png|thumb |FG 2.12 minimal eye candy mode on 2009-era hardware (NVIDIA 260M)]]<br />
<br />
As can be seen, additional resources can be freed by flying in areas without scenery (ocean tiles), by using simple aircraft like the ufo, and by using a HUD instead of a 2D/3D cockpit panel.<br />
<br />
<!--<br />
=== Minimal Rembrandt Startup Profile ===<br />
<syntaxhighlight lang="text"><br />
--enable-rembrandt<br />
--prop:/sim/rendering/rembrandt/ambient-occlusion-buffers=false<br />
--prop:/sim/rendering/shadows/map-size=1024<br />
--prop:/sim/rendering/shadows/num-cascades=1<br />
--airport=ksfo<br />
--offset-distance=4000<br />
--offset-azimuth=90<br />
--altitude=500<br />
--heading=0<br />
--model-hz=60<br />
--disable-random-objects<br />
--prop:/sim/rendering/texture-compression=off<br />
--prop:/sim/rendering/quality-level=1<br />
--prop:/sim/rendering/shaders/quality-level=1<br />
--disable-ai-traffic<br />
--prop:/sim/ai/enabled=0<br />
--aircraft=ufo<br />
--disable-sound<br />
--prop:/sim/rendering/random-vegetation=0<br />
--prop:/sim/rendering/random-buildings=0<br />
--disable-specular-highlight<br />
--disable-ai-models <br />
--disable-clouds<br />
--disable-clouds3d<br />
--disable-textures<br />
--fog-fastest<br />
--visibility=5000<br />
--disable-distance-attenuation<br />
--disable-enhanced-lighting<br />
--disable-real-weather-fetch <br />
--prop:/sim/rendering/particles=0<br />
</syntaxhighlight><br />
(Again, the point not being to look good, but just to start up without crashing or extreme lag)<br />
--><br />
<br />
=== Reporting incompatible default settings ===<br />
Once you have located and identified settings that seem to cause reproducible issues with your hardware, it would be a good idea to report these settings using the issue tracker, so that these can hopefully be made optional in the upcoming release: http://flightgear-bugs.googlecode.com/<br />
<br />
=== Tracking RAM utilization ===<br />
[[File:Fg-3.2-minimal-settings.png|400px|Screen shot showing FlightGear 3.2 using the minimal startup profile with frame spacing and frame counter displayed.]]<br />
<br />
{{WIP}}<br />
<br />
{{FGCquote<br />
|My measurements (below) suggest that terrain mesh (as loaded at "bare" <br/><br />
LOD) is the dominant memory user, with only small contributions from the <br/><br />
aircraft, terrain textures, and random objects/trees/buildings.<br />
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32445574/<br />
|title=<nowiki>Re: [Flightgear-devel] Memory consumption reduction</nowiki><br />
|author=<nowiki>Rebecca N. Palmer</nowiki><br />
|date=<nowiki>2014-06-11</nowiki><br />
}}<br />
}}<br />
<br />
{{FGCquote<br />
|In Ubuntu 64-bit, measured using System Monitor after it stabilizes (~1min)<br/><br />
Except as stated, c172p stationary on KSFO 28R, night, Terrasync <br/><br />
scenery, default settings (regional textures, LOD range 1500/9000/30000)<br/><br />
baseline: 2.3-2.4GB<br/><br />
Changing shader effects level or enabling/disabling random <br/><br />
objects/trees/buildings: no significant change<br/><br />
Global texture set: 2.2GB<br/><br />
DDS texture set: 2.2GB<br/><br />
Global texture set, no Textures.high: 2.1GB (and some missing effects <br/><br />
textures, as they don't have the "try Textures.high first, then <br/><br />
Textures" fallback mechanism)<br/><br />
LOD range 1500/9000/10000: 1.4GB<br/><br />
LOD range 1500/2000/30000: 2.3GB<br/><br />
LOD range 500/9000/30000: 2.3GB<br/><br />
1.0 scenery (from flightgear-data 3.0 due to above issue): 1.1GB<br/><br />
Ocean location: 0.75GB<br/><br />
F-14: 2.1GB<br/><br />
777-200: 2.6GB<br/><br />
<br />
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32445574/<br />
|title=<nowiki>Re: [Flightgear-devel] Memory consumption reduction</nowiki><br />
|author=<nowiki>Rebecca N. Palmer</nowiki><br />
|date=<nowiki>2014-06-11</nowiki><br />
}}<br />
}}<br />
<br />
[[File:Fg-3.2-RAM-utilization-in-minimal-mode.png|right|500px|htop showing FlightGear 3.2 RAM utilization when in minimal startup mode]]<br />
<br />
== Further assistance ==<br />
If you need help with the whole process, please get in touch via the FG forums.<br />
<br />
When doing that, please fully document the whole process, i.e. including:<br />
<br />
* startup settings (and fgfsrc if used)<br />
* error messages and warnings (console output)<br />
* screen shots<br />
* screen shots showing frame rate, frame spacing, performance monitor, osg on-screen stats (see [[Howto:Use the system monitor]] )<br />
* use the about dialog to provide other important information<br />
<br />
== Troubleshooting Performance Issues ==<br />
<br />
If you're able to build from source and don't mind using development looks like the built-in profiler, it would be interesting to see comparison of both builds - ideally using a simple test case with everything else disabled - you could use a pre-recorded flight and/or a flight recorder type to come up with a "test flight". From our standpoint, it would help tremendously if all features that don't seem to have an effect could be completely disabled, including complex aircraft and scenery/locations. In other words, if you can reproduce the problem using "bare" minimum settings, the resulting log file will be much easier to process.<br />
<br />
There's a built-in profiler which you can use to create these profiles: http://wiki.flightgear.org/Built-in_Profiler<br />
You would then want to use two different build directories, where SG/FG build settings would be identical, but using an older version of OSG: http://wiki.flightgear.org/Building_using_CMake#Multiple_build_directories<br />
<br />
For the sake of simplicity there's a so called "minimal startup profile" that you can use: http://wiki.flightgear.org/Howto:Debugging_FlightGear_Crashes#Minimal_startup_profile<br />
While unlikely, it would be great if the issue could be reproduced that way - but more likely than not, you'll have to re-add a few features and change a few settings, e.g. by using a different location.<br />
<br />
Like I said, you could then use the replay system to create an test flight than can be easily reproduced - to get going more quickly, you can also use the built-in route manager to create a simple flight plan and fly the whole thing on autopilot: http://wiki.flightgear.org/Instant_Replay<br />
<br />
You can use time warp mode to speed up simulation time and finish more quickly.<br />
<br />
Admittedly, all this may seem a bit intimidating and tedious, but once you have such a setup working, you can reuse it over and over again for different startup profiles and provide profiling logs for each.<br />
We do have a number of people interested in adding features to support benchmarking/profiling workflows natively:<br />
<br />
http://wiki.flightgear.org/FlightGear_Benchmark<br />
http://wiki.flightgear.org/Testing<br />
<br />
If that's something you'd like to pursue, feel free to get in touch - it is definitely a worthwhile thing, even regardless of any OSG specific issues, as it will also help with unrelated performance issues.<br />
Obviously, there's a bit of a steep learning curve involved, which is why it's normally only core developers that build multiple versions against different OSG versions and run the profiler.<br />
But once you are able to build from source, you have already completed the most difficult step - everything else is fairly straightforward in comparison - as as you can probably tell, creating test flights using the route manager and/or flight recorder also isn't exactly rocket science.<br />
<br />
However, before you do anything, I'd suggest to check first if you've possibly changed your driver, or if you can install a newer version<br />
<br />
== Debugging Segfaults & Obtaining Backtraces ==<br />
{{Note|This section is currently Linux/gdb specific. Any help in updating it to become less platform/OS/debugger-specific would be greatly appreciated!}}<br />
<br />
A '''segfault''' is another word for "crash", it's a so called "segmentation fault", where the program is doing things that it wasn't designed to do, such as accessing invalid memory for example, so that the operating system will terminate the process because its behavior is no longer valid/correct. These '''segfaults''' will typically happen due to coding errors, either in FlightGear or one of its dependencies (libraries like SimGear, plib, OpenSceneGraph or OpenAL). <br />
<br />
A typical segfault may look like this:<br />
<syntaxhighlight lang="text"><br />
Initializing splash screen<br />
Splash screen progress init<br />
Tungsten Graphics, Inc.<br />
Mesa DRI R200 (RV250 4C66) x86/MMX/SSE2 TCL DRI2<br />
1.3 Mesa 9.1.1<br />
<br />
Program received signal SIGSEGV, Segmentation fault.<br />
0xb71467e6 in __strlen_sse2_bsf () from /usr/lib/libc.so.6<br />
</syntaxhighlight><br />
<br />
The last two lines are basically showing the actual crash, anything shown earlier is normally just an indicator how far the code could proceed shortly before the crash actually occurred. <br />
<br />
In order to see what was going on when the crash occurred, you'll need to build a binary with '''debugging symbols''' enabled/included, usually this includes FlightGear and SimGear - and possibly even OSG (OpenSceneGraph, normally only if your crash happens inside rendering related code).<br />
<br />
A so called '''backtrace''' is basically pretty much like a flight data recorder tape/log that is used to conduct a post-crash analysis.<br />
<br />
A binary with debugging symbols included will contain additional information that helps developers track down what was causing a certain crash, such as for example the file name, function, line number, variable that was accessed before the crash happened. This is analogous to how a FDR/CVR on an airplane records certain parameters like position, orientation, altitude, velocities, configuration, cockpit conversations etc. This can also be used by developers to see who is responsible for a certain segfault/bug, i.e. which commit introduced the bug.<br />
<br />
Debugging FlightGear crashes is significantly simplified by having access to such runtime data, because we can basically go back in time and see what the FlightGear program was doing shortly before the crash.<br />
<br />
Unfortunately, logging all this data by default has a certain run-time overhead and requires additional tools and knowledge, so it is usually too costly and not done, FlightGear will by default be heavily optimized by your compiler and not include code logging important debugging/post-crash parameters, for the sake of better performance. <br />
.<br />
However, as developers, we do appreciate all efforts to provide meaningful bug reports, and a reproducible bug including a good crash analysis, i.e. a so called '''backtrace''' is as good as it gets, and the likelihood of a certain bug being examined and fixed is significantly higher when the bug report includes both, a '''backtrace''', and a set of steps to reproduce the error reliably. <br />
<br />
A good way to to provide a reproducible test case is using the [[Replay]]/flight recorder system to create a flight recorder tape that triggers the crash, alternatively, consider providing a "flight plan" that triggers the crash - ideally, without it being aircraft specific, i.e. reproducible using aircraft like the ufo<br />
<br />
Thus, you'll want to reconfigure your SimGear/FlightGear ($SG_SRC & $FG_SRC) source trees using the '''-CMAKE_BUILD_TYPE=Debug''' switch, for details please refer to: [[Building using CMake#Debug_Builds]]. It is a good idea not to touch your existing build trees for this, but instead create an additional directory hierarchy for your debugging binary, please see [[Building using CMake#Multiple build directories]] for details. <br />
<br />
Once you have rebuilt and relinked SimGear and FlightGear, you'll want to use a debugger like '''gdb''' to run your new binary. It does help to have a good way to reproduce a crash, such as using certain startup/runtime settings. For the sake of simplicity it is usually a good idea to disable all unrelated features and subsystems/settings, this includes complex aircraft and complex scenery locations (airports) if possible. For details, refer to the minimal startup profile detailed in this article.<br />
<br />
# For gdb to be available, you'll normally have to use your package manager (apt, yum, yast etc) and install the "gdb" package first.<br />
# next, you'd navigate to your build directory where your '''fgfs''' debug binary is located<br />
# you'd then, run gdb<br />
# via the gdb shell, you can specify the file to be used via '''file src/Main/fgfs'''<br />
# this will preload the binary and its dependencies<br />
# to actually run the file, you would use the '''run''' command<br />
# you'll normally want to pass arguments right behind '''run''', especially the mandatory ones (i.e. to specify $FG_ROOT)<br />
# creating a simple .[[Fgfsrc]] file helps for the sake of simplicity<br />
# once the segfault/crash occurs, you'll want to run '''backtrace''' (with '''bt''' being the shorter equivalent)<br />
# only if that isn't conclusive, use '''thread apply all bt full''' instead to get a full backtrace for all threads (background tasks)<br />
# please use the issue tracker to post your backtrace<br />
<br />
This is what a typical backtrace may look like:<br />
<br />
<syntaxhighlight lang="gdb">(gdb) thread apply all bt<br />
<br />
Thread 1 (Thread 0xb66c4740 (LWP 10908)):<br />
#0 0xb71467e6 in __strlen_sse2_bsf () from /usr/lib/libc.so.6<br />
#1 0x0886c080 in copy_string (s=s@entry=0x0)<br />
at /home/cesar/compilation/pkg/simgear/2.10.0/src/simgear-2.10.0/simgear/props/props.cxx:161<br />
#2 0x08870550 in set_string (val=0x0, this=0x8dd55b8)<br />
at /home/cesar/compilation/pkg/simgear/2.10.0/src/simgear-2.10.0/simgear/props/props.cxx:524<br />
#3 SGPropertyNode::setStringValue (this=0x8dd55b8, value=0x0)<br />
at /home/cesar/compilation/pkg/simgear/2.10.0/src/simgear-2.10.0/simgear/props/props.cxx:1587<br />
#4 0x08326ae1 in (anonymous namespace)::GeneralInitOperation::run (this=0x8bdea48, gc=0x8be4310)<br />
at /home/cesar/compilation/pkg/flightgear/2.10.0/src/flightgear-2.10.0/src/GUI/gui.cxx:123<br />
#5 0x085c2b7b in flightgear::GraphicsContextOperation::operator() (this=0x8bdea48, gc=0x8be4310)<br />
at /home/cesar/compilation/pkg/flightgear/2.10.0/src/flightgear-2.10.0/src/Viewer/WindowSystemAdapter.cxx:41<br />
#6 0xb78ca246 in osg::GraphicsOperation::operator()(osg::Object*) () from /usr/lib/libosg.so.80<br />
#7 0xb78c7784 in osg::GraphicsContext::runOperations() () from /usr/lib/libosg.so.80<br />
#8 0xb7b29fe2 in osgViewer::ViewerBase::renderingTraversals() () from /usr/lib/libosgViewer.so.80<br />
#9 0xb7b2707c in osgViewer::ViewerBase::frame(double) () from /usr/lib/libosgViewer.so.80<br />
#10 0x085c4841 in fgOSMainLoop ()<br />
at /home/cesar/compilation/pkg/flightgear/2.10.0/src/flightgear-2.10.0/src/Viewer/fg_os_osgviewer.cxx:286<br />
#11 0x082221fa in fgMainInit (argc=32, argv=0xbffff494)<br />
at /home/cesar/compilation/pkg/flightgear/2.10.0/src/flightgear-2.10.0/src/Main/main.cxx:339<br />
#12 0x081e71ee in main (argc=32, argv=0xbffff494)<br />
at /home/cesar/compilation/pkg/flightgear/2.10.0/src/flightgear-2.10.0/src/Main/bootstrap.cxx:251<br />
</syntaxhighlight><br />
<br />
As can be seen, the first few lines basically show exactly what happened, and where it happened, while all the subsequent lines are basically showing the callgraph, i.e. how the piece of code got triggered. For example, FlightGear started in bootstrap.cxx line 251, then called into main.cxx (line 339), at which point the osgviewer setup took place. Next, there are a few lines that do not contain a lot of interesting info, because those are all library calls into OSG - things are starting to be interesting again around line #5, where FlightGear specific code is getting called again. As can be seen in this particular example, the actual segfault was triggered in a SimGear operation here, which was due to a NULL pointer.<br />
<br />
At first, this may look a bit confusing and even intimidating, but it does make sense to people familiar with C++ and FlightGear/SimGear - so even if you cannot understand a single thing, just post such output on the issue tracker, so that others can have a look. We'll ask for additional information if necessary.<br />
<br />
However, at times it may be nearly impossible to see what actually goes in in FG these days simply because there's too many disparate parts involved here. For example, in the rare instance that our [[Nasal]] scripting interpreter could lead to a segfault, we could potentially see where the C code was using a debugger like gdb – but that wouldn't tell us where we were in the Nasal code. <br />
<br />
And that similarly applies to many things, especially things that "jump" boundaries here. Another prime example is property tree listeners - Nasal listeners don't have a backtrace beyond the C code, even if it is triggered directly from a Nasal setprop()/.setValue(), because it passes through C and C++ stack frames and then back into Nasal.<br />
<br />
Thus, valgrind/gdb/cachegrind/perftools may be too low-level to be meaningful in most cases, i.e. just look at what's going on in the scenery/aircraft department, here just identifying "hot spots" in terms of code/functions would be a red herring, because the real culprit is typically not at all in the run-time code, but the underlying scenegraph data, such as highly complex textures, 3D models or terrain/scenery. <br />
<br />
This can now be easily verified by using Zakalawe's new draw-masks to switch off aircraft/scenery/clouds or AI model rendering.<br />
<br />
Having acess to gdb/valgrind etc is one thing, being able to actually run and interpret the results is a completely different thing. <br />
<br />
Thus, it is more promising -in the long term- to optionally expose certain info at run-time, so that users can access it to see how their aircraft/scenery/feature/configuration behaves in comparison to some other aircraft/scenery/feature/configuration.<br />
<br />
Also, when it comes to using tools like gdb -and especially valgrind- the main challenge is that FlightGear is primarily a GUI application, and it doesn't lend itself it being debugged/profiled or leak-tested in an isolated fashion at all. <br />
<br />
For example, for valgrind runs to be useful and straightforward, we would need to be able to minimize what's done inside fg_init.cxx so that we can disable things not needed, but also even run FlightGear in a [[FlightGear Headless|"headless" mode]] without a visible GUI window, so that such tests could be run directly on the build server as part of a regression testing suite. Otherwise, even just running fgfs in valgrind for 10 minutes sim time may turn out to take hours due to the nature of valgrind, i.e. it being an emulator.<br />
<br />
valgrind et all are great if you know how to use them, but for end users, these tools are too fine-grained, we would ideally support some per-subsystem or per-feature granularity for end users.<br />
<br />
== Using AddressSanitizer ==<br />
{{FGCquote<br />
|AddressSanitizer does a similar job to Valgrind with less overhead <br/><br />
(~2.5x memory use, and nearly full speed), but requires recompiling; I <br/><br />
haven't seen the crash under it yet (or at all today), if anyone does <br/><br />
please post your log.<br />
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32749837/<br />
|title=<nowiki>Re: [Flightgear-devel] crash in SGPropertyNode::fireValueChanged</nowiki><br />
|author=<nowiki>Rebecca Palmer</nowiki><br />
|date=<nowiki>2014-08-22</nowiki><br />
}}<br />
}}<br />
<br />
<syntaxhighlight lang="bash"><br />
#this is for Linux with llvm-3.4, libsqlite3-dev, flite1-dev, libhtsengine-dev; it will probably work on Mac (with possibly different ASAN_SYMBOLIZER_PATH) but not Windows<br />
<br />
#simgear<br />
cmake ../../git/simgear -DCMAKE_BUILD_TYPE=RelWithDebInfo <br />
-DCMAKE_C_FLAGS="-fsanitize=address -fno-omit-frame-pointer -O2 -g" <br />
-DCMAKE_CXX_FLAGS="-fsanitize=address -fno-omit-frame-pointer -O2 -g" <br />
-DCMAKE_SHARED_LINKER_FLAGS="-fsanitize=address -fno-omit-frame-pointer <br />
-O2 -g" -DCMAKE_VERBOSE_MAKEFILE=1 -DSIMGEAR_SHARED=ON<br />
make<br />
sudo make install<br />
<br />
#flightgear<br />
cmake ../../git/flightgear -DCMAKE_BUILD_TYPE=RelWithDebInfo<br />
-DCMAKE_C_FLAGS="-fsanitize=address -fno-omit-frame-pointer -O2 -g" <br />
-DCMAKE_CXX_FLAGS="-fsanitize=address -fno-omit-frame-pointer -O2 -g" <br />
-DCMAKE_VERBOSE_MAKEFILE=1 -DSIMGEAR_SHARED=ON -DENABLE_IAX=OFF <br />
-DENABLE_FGCOM=OFF -DSYSTEM_SQLITE=ON<br />
make<br />
sudo make install<br />
<br />
#run<br />
ASAN_SYMBOLIZER_PATH=/usr/lib/llvm-3.4/bin/llvm-symbolizer <br />
ASAN_OPTIONS="symbolize=1 alloc_dealloc_mismatch=0" fgfs [options] 2> <br />
asan_log.txt<br />
<br />
#post asan_log.txt to developers mailing list and/or the issue tracker<br />
</syntaxhighlight><br />
<br />
== The original idea and future developments ==<br />
Our hope is that we can come up with a fairly safe subset of FlightGear settings that should work for 99% of our users, even on moderately old hardware. This would enable us to change the FlightGear defaults accordingly, and use these settings as a safe fallback alternative - so that FlightGear should no longer just crash for people without certain hardware/features. <br />
<br />
There's a trend to expose more and more information via the property tree, to make the simulator increasingly runtime-configurable, and to allow subsystems to be re-initialized at runtime, so being able to start up FlightGear in some form of "safe" mode is generally a good thing and useful for anybody helping with troubleshooting on the forums, because it helps us exclude many potential problems. In the long run, such a profile could also be used as the foundation for a [[FlightGear Benchmark]] or some scripted regression suite to run FlightGear in a [[FlightGear Headless|headless]] mode to help with release preparations, and [[FGCanvas]].<br />
<br />
<br />
== Related ==<br />
* http://flightgear.org/forums/viewtopic.php?f=37&t=17199&p=165503#p163684<br />
* [[System Crashes]]<br />
* [[Hardware Recommendations]]<br />
* [[Troubleshooting performance issues]]<br />
* [[Problematic Video Cards]]<br />
<br />
[[Category:Howto|Debugging FlightGear Crashes]]<br />
[[Category:Troubleshooting]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=Landmark_Wish_List&diff=77318Landmark Wish List2014-10-26T14:17:25Z<p>Blackiris: Update Chrysler Building status</p>
<hr />
<div>This page provides a list of important landmarks which are not currently in FlightGear Scenery that the community would like to see modeled. If you are a FlightGear modeler and are looking for something to model, please consider something on this list.<br />
<br />
Feel free to add to this list.<br />
<br />
If you are modelling a landmark, please change the "Completed" column from {{tl|no}} to <nowiki>{{</nowiki>[[:Template:n/a|n/a|Claimed]]<nowiki>}}</nowiki>, and when done change again to {{tl|yes}}.<br />
<br />
=== Africa ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
| Pyramids || Cairo || Egypt || {{no}}<br />
|-<br />
| Victoria Falls || Victoria Falls || Zimbabwe || {{no}}<br />
|-<br />
| [http://en.wikipedia.org/wiki/Table_Mountain Table Mountain] || Cape Town || South Africa || {{no}}<br />
|-<br />
| [http://en.wikipedia.org/wiki/Mount_Kilimanjaro Mount Kilimanjaro] || Kilimanjaro National Park || Tanzania || {{no}}<br />
|-<br />
| [http://en.wikipedia.org/wiki/Basilica_of_Our_Lady_of_Peace_of_Yamoussoukro Basilica of Our Lady of Peace of Yamoussoukro] || Yamoussoukro || Côte d'Ivoire || {{no}}<br />
|-<br />
|}<br />
<br />
=== America ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|National Congress || Brasilia || Brazil || {{yes}}<br />
|-<br />
|Christ the Redeemer || Rio de Janeiro || Brazil || {{yes}}<br />
|-<br />
|[http://en.wikipedia.org/wiki/Windsor_Atlantica_Hotel Windsor Atlantica Hotel] || Rio de Janeiro || Brazil || {{n/a|Claimed}}<br />
|-<br />
|Navy Pier || Chicago || USA || {{no}}<br />
|-<br />
|Adler Planetarium || Chicago || USA || {{no}}<br />
|-<br />
|Soldier Field || Chicago || USA || {{no}}<br />
|-<br />
|McCormick Place || Chicago || USA || {{no}}<br />
|-<br />
|U.S. Cellular Field || Chicago || USA || {{no}}<br />
|-<br />
|Wrigley Field || Chicago || USA || {{no}}<br />
|-<br />
|Shedd Aquarium || Chicago || USA || {{no}}<br />
|-<br />
|Union Station || Chicago || USA || {{no}}<br />
|-<br />
|Oglivie Transportation Center || Chicago || USA || {{no}}<br />
|-<br />
|Smurfit-Stone Building || Chicago || USA || {{no}}<br />
|-<br />
|Marina City || Chicago || USA || {{no}}<br />
|-<br />
|Millenium Park || Chicago || USA || {{no}}<br />
|-<br />
|United Center || Chicago || USA || {{no}}<br />
|-<br />
|Brooklyn Bridge || New York || USA || {{n/a|Claimed}}<br />
|-<br />
|Empire State Building || New York || USA || {{yes}}<br />
|-<br />
|Chrysler Building || New York || USA || {{yes}}<br />
|-<br />
|United Nations Headquarters || New York || USA || {{yes}}<br />
|-<br />
|Bank of America Tower || New York || USA || {{yes}}<br />
|-<br />
|Verizon Center || Washington, D.C. || USA || {{no}}<br />
|-<br />
|White House || Washington, D.C. || USA || {{no}}<br />
|-<br />
|Space Needle || Seattle || USA || {{yes}}<br />
|-<br />
|Milwaukee Art Museum || Milwaukee || USA || {{no}}<br />
|-<br />
|[http://en.wikipedia.org/wiki/Machu_Picchu Machu Picchu] || Aguas Calientes || Peru || {{no}}<br />
|-<br />
|[http://en.wikipedia.org/wiki/Nazca_Lines Nazca Lines] || Estudiantes || Peru || {{no}}<br />
|-<br />
|[http://en.wikipedia.org/wiki/Panama_canal Panama canal] and some boats pls|| Panama city - Colòn || Panama || {{no}}<br />
|-<br />
|[http://en.wikipedia.org/wiki/Hoover_Dam Hoover Dam]|| Boulder|| USA || {{no}}<br />
|-<br />
|[http://en.wikipedia.org/wiki/Skunk_Works Skunkworks aircraft] hidden in the mountain of KXTA || Area 51 || USA || {{no}}<br />
|}<br />
<br />
=== Asia ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Bank of China Tower || Hong Kong || China || {{yes}}<br />
|-<br />
|[http://en.wikipedia.org/wiki/Kai_Tak_Airport "Checkerboard Hill" (VHHX approach)] || Hong Kong || China || {{no|No, see [[Talk:Landmark_Wish_List#VHHX request| talk page]]}}<br />
|-<br />
|CCTV Tower || Beijing || China || {{yes}}<br />
|-<br />
|Taj Mahal || Agra || India || {{yes}}<br />
|-<br />
|Akashi Kaikyo bridge || Kobe || Japan || {{yes}}<br />
|-<br />
|Petronas Towers || Kuala Lumpur || Malaysia || {{yes}}<br />
|-<br />
|Ryugyong Hotel || Pyongyang || North Korea || {{yes}}<br />
|-<br />
|Burj Khalifa || Dubai || UAE || {{yes}}<br />
|-<br />
|Burj al Arab || Dubai || UAE || {{yes}}<br />
|-<br />
|Bitexco Financial Tower || Ho Chi Minh City || Vietnam || {{yes}}<br />
|-<br />
|Sigiriya || Matale District || Sri Lanka || {{no}}<br />
|-<br />
|Great Wall of China || Huairou, Peking / Jiuduhezhen, Huairou, Peking || China || {{no}}<br />
|-<br />
|Mount Everest || Chukhung || Nepal || {{no}}<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| Something]] || Singapore ||Singapore || {{no}}<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| Marina Bay Sands]] || Singapore ||Singapore || {{yes}}<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| One George Street]] || Singapore ||Singapore || {{no}}<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| One Raffles Place]] || Singapore ||Singapore || {{no}}<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| The Pinnacle@Duxton]] || Singapore ||Singapore || {{no}}<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| One Shenton Way]] || Singapore ||Singapore || {{no}}<br />
|}<br />
<br />
=== Europe ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Aeroport Leonardo da Vinci INTL || Rome,Fiumicino || Italy || {{no}}<br />
|-<br />
|Stade de France || Saint-Denis || France || {{no}}<br />
|-<br />
|Zwischenahner Meer || Zwischenahn, Niedersachsen || Germany || {{n/a|CS done}}<br />
|-<br />
|Porta Westfalica/Hermans-Denkmal || Bückeburg (ETHB), Minden || Germany || {{no}}<br />
|-<br />
|Lapan || Oldenburg, Niedersachsen || Germany || {{no}}<br />
|-<br />
|Schloss || Oldenburg || Germany || {{no}}<br />
|-<br />
|Schloss || Neuschwanstein || Germany || {{n/a|Claimed}}<br />
|-<br />
|Colosseum || Rome || Italy || {{no}}<br />
|-<br />
|Oeresund Bridge || Copenhagen-Malmo || Scandinavia || {{yes}}<br />
|-<br />
|[http://en.wikipedia.org/wiki/Oslo_Plaza Oslo Plaza] || Oslo || Norway || {{n/a|Claimed}}<br />
|-<br />
|Big Ben || London || UK || {{yes}}<br />
|-<br />
|Westminster Abbey || London || UK || {{yes}}<br />
|-<br />
|North Pole (flag and light) || North Pole || World || {{no}}<br />
|}<br />
<br />
=== Australia and Oceania ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Sydney Opera House || Sydney || Australia || {{yes}}<br />
|-<br />
|Sky Tower || Auckland || New Zealand || {{n/a|Claimed}}<br />
|-<br />
|Ayers rock || Uluru || Australia || {{no}}<br />
|}<br />
<br />
== Related ==<br />
<br />
=== Internal links ===<br />
* [[FlightGear Scenery Designer]]<br />
* [[FlightGear Scenery Database]]<br />
* [[UK Scenery Wish List]]<br />
* [[Scenery_Tracker]]<br />
<br />
=== External links ===<br />
* [http://forum.flightgear.org/viewtopic.php?f=5&t=2390 The forum topic]<br />
* See [http://scenemodels.flightgear.org/ FGFS Scenery Object Database], for more on models for [[Scenery]]<br />
<br />
[[Category:Scenery]]<br />
[[Category:Community]]<br />
[[Category:Contribution requests]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_February_2014&diff=68150FlightGear Newsletter February 20142014-02-22T23:49:59Z<p>Blackiris: Add some updated airports</p>
<hr />
<div><br />
{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
{{Note|This newsletter is currently being written by our contributors, people like YOU:<br />
<br />
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 news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter. Core developers are encouraged to add news about their latest work to the newsletter's development section and [[Next Changelog|the changelog of the upcoming release]]. At the end of each month, it's generally a good idea to get in touch with other contributors to ask them to add news about their contributions to the newsletter.}}<br />
<br />
== Development news ==<br />
Note to all contributors: Please also copy your newsletter additions to the changelog for the upcoming release: [[Next Changelog]].<br />
<br />
<br />
=== Advanced Weather ===<br />
<br />
The Advanced Weather system has received a major upgrade, giving it the capability to draw clouds to whatever range is needed to the visible horizon (largest distance tested was 750 km from low Earth orbit).<br />
<br />
The technique used for this utilizes so-called impostors, simple pre-generated texture sheets showing the contents of a 40x40 km weather tile from above in low resolution. Based on the current weather situation, impostors fill the range from the edge of the region where 3d clouds are simulated to the currently selected visibility range / cloud drawing range (whatever is lower). Since the impostors themselves are very simple models, the framerate impact is minimal and independent of the number of apparently visible clouds. A dedicated shader for Atmospheric Light Scattering takes care of matched lighting in low sun conditions.<br />
<br />
On systems which can draw 3d clouds up to 80 km and support visibilities larger than that, this improves visuals at high altitude quite a bit.<br />
<br />
[[File:Farclouds02.jpg|300px|[ Impostors for overcast clouds]]<br />
[[File:Farclouds07.jpg|300px|[ Impostors for scattered clouds]]<br />
[[File:Farclouds10.jpg|300px|[ Impostors for Cumulus clouds]]<br />
<br />
The functionality is currently in an advanced proof of concept stage - METAR mode is not yet fully supported, and the placement algorithms may still be refined.<br />
<br />
=== Revised Nasal APIs: getprop()/setprop() ===<br />
<br />
As of FlightGear 3.1, getprop()/setprop() arguments (those that form a path) can now be numeric to specify a index, so:<br />
<syntaxhighlight lang="nasal"><br />
getprop("canvas/by-index", "texture", 1, "name");<br />
</syntaxhighlight><br />
: is now the same as:<br />
<syntaxhighlight lang="nasal"><br />
getprop("canvas/by-index/texture[1]/name");<br />
</syntaxhighlight><br />
: (see [https://gitorious.org/fg/flightgear/commit/5eee5e42ae4f5cf56283b3bf5a3be46efc2b51c4 merge request 54] and [https://gitorious.org/fg/flightgear/commit/34ed79e5f88ffdfc5e651a1fe3e639cb8f4d3353 actual commit])<br />
<br />
=== Philosopher's fully interactive Nasal Console REPL ===<br />
Philosopher has created a very cool [[Canvas]]-based, fully-interactive, Nasal Console with a real [http://en.wikipedia.org/wiki/Read%E2%80%93eval%E2%80%93print_loop REPL interpreter (Read-eval-print loop)]. <br />
<br />
<br />
[[File:Interactive-Nasal-Console-REPL.png|600px|Philosopher's interactive Nasal console REPL]]<br />
<br />
=== Copy & Paste Programming: A Compass Widget using Nasal/Canvas ===<br />
<br />
<br />
Inspired by a a recent forum discussion, we thought that creating a compass widget would be a neat little project for someone interested in learning a bit more about Nasal and Canvas coding, and it should be possible to accomplish with less than 50-80 lines of code actually - there's a ton of stuff that you could reuse (SVG compass rose or an existing 2D panel texture), we have quite a few tutorials on Nasal, Canvas and Image processing (check the wiki). Furthermore, we have the long-term plan to eventually phase out the old 2D panel code and used a modernized [[Canvas]]-based version to help with [[Unifying the 2D rendering backend via canvas]]. Continue reading at [[Howto:Parsing 2D Instruments using the Canvas]]...<br />
<br />
[[File:Canvas-Compass-Widget.png|thumb|A Nasal/Canvas based compass widget]]<br />
<br />
Paste this into your [[Nasal Console]] and click Execute:<br />
<syntaxhighlight lang="nasal"><br />
var CanvasApplication = {<br />
##<br />
# constructor<br />
new: func(x=300,y=200) {<br />
var m = { parents: [CanvasApplication] };<br />
m.dlg = canvas.Window.new([x,y],"dialog");<br />
m.canvas = m.dlg.createCanvas().setColorBackground(1,1,1,0.5);<br />
m.root = m.canvas.createGroup();<br />
m.timer = maketimer(0.1, func m.update() );<br />
m.init();<br />
return m;<br />
},<br />
<br />
del: func me.timer.stop(),<br />
<br />
update: func() {<br />
var hdg=getprop("/orientation/heading-deg");<br />
me.compass.setRotation(-hdg*D2R);<br />
},<br />
<br />
init: func() {<br />
var filename = "/Aircraft/Instruments/gyro.xml";<br />
var temp= io.read_properties(getprop("/sim/fg-root") ~ filename); <br />
var layers = temp.getValues().layers.layer;<br />
<br />
var z=100;<br />
foreach(var layer; layers ) {<br />
print("new layer:", layer.name);<br />
<br />
# if it's not a texture, skip<br />
if (!contains(layer, "texture")) continue;<br />
<br />
# get a handle to the texture of the layer<br />
var texture = layer.texture;<br />
<br />
# create an image child for the texture<br />
var child=me.root.createChild("image")<br />
.setFile( texture.path )<br />
.setSourceRect( texture.x1, texture.x2, texture.y1, texture.y2 )<br />
.setSize(layer.w,layer.h)<br />
.setTranslation(20,20)<br />
.set("z-index", z +=1 )<br />
.setScale(2.5);<br />
<br />
if (layer.w != nil and layer.h != nil)<br />
child.setCenter(layer.w/2, layer.h/2);<br />
<br />
if (layer.name=="compass rose") {<br />
print("Found compass layer");<br />
# child.setCenter(55,55);<br />
me.compass = child;<br />
}<br />
} # foreach<br />
<br />
me.timer.start();<br />
},<br />
}; # end of CanvasApplication<br />
<br />
<br />
var InstrumentWidget = {<br />
new: func(x,y) {<br />
var m = CanvasApplication.new(x:x,y:y);<br />
},<br />
};<br />
<br />
var compass = InstrumentWidget.new(x:300, y:300);<br />
<br />
print("Compass Loaded...!");<br />
</syntaxhighlight><br />
<br />
=== Canvas & Shaders: A match made in Heaven ? ===<br />
<br />
For quite a while, we've been thinking that at some point, the [[Canvass]] system could probably benefit from being also able to also use FlightGear's Effects/Shader framework, so that canvas textures can also be processed via effects and shaders optionally, before they get drawn. That should make all sorts of fancy effects possible, such as night vision cameras or thermal view, rendered to canvas textures/groups.<br />
<br />
That would then disable the default rendering pipeline for those canvas textures and use shaders.<br />
<br />
Basically, anything that's not directly possible via the core canvas system or via its Nasal wrappers, would then be handled via effects/shaders. So we would gain lots of flexibility, and performance benefits.<br />
<br />
So if people really want to create really fancy textures or camera views, they could use effects/shaders then, which would keep the design truly generic, and it would ensure that there's no bloat introduced into the main canvas system.<br />
<br />
We did have some discussions about supporting per-canvas (actually per canvas::Element) effects and shaders via properties recently, TheTom even mentioned a while ago that he is interested in supporting this at some point, especially given the number of projects that could be realized like that (FLIR, night vision, thermal imaging etc).<br />
<br />
At the time of writing this (02/2014) the Canvas does not yet include any support for applying custom effects or [[Shaders]] to canvas elements or the whole canvas itself - however, supporting this is something that's been repeatedly discussed over time, so we're probably going to look into supporting this eventually[http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg37210.html].<br />
<br />
Some very basic prototyping has already taken place and looks pretty encouraging: <br />
<br />
<gallery mode=packed widths=150px heights=150px><br />
Canvas-glsl-support.png|airport selection dialog with a greyscale fragment shader applied to the canvas<br />
Canvas-Fragment-Shader-red.png|a trivial fragment shader applied to a canvas (the original colors used in the Nasal code were not changed!)<br />
Canvas-Fragment-Shader-circles.png|unmodified airport selection canvas with fragment shader applied<br />
Canvas-Fragment-Shader-experiments.png|more canvas fragment shading experiments<br />
<br />
</gallery><br />
<br />
Continue reading at [[Canvas_Development#Effects_.2F_Shaders|Canvas & Shaders]]<br />
<br />
=== JSBSim Ground Effects ===<br />
This is a heads up for JSBSim aircraft maintainers that user their own <br />
ground detection and handling code.<br />
As of today JSBSim, just like YASim, supports ground effects like <br />
bumpiness, solid-ground detection and adjusting of friction actors.<br />
<br />
Actually JSBSim supports an extra feature, BOGEY contact points sink in <br />
a non-solid ground surface but STRUCTURE contact point do not, making it <br />
easy to define floats using STRUCTURE contact points.<br />
<br />
In order not to pollute /fdm/jsbim too much I've added the following <br />
properties:<br />
<br />
/sim/fdm/surface/override-level<br />
A user defined property which if defined and set to a something higher <br />
than 0 will disable the JSBSim ground reactions code completely and the <br />
following properties are set to false:<br />
/sim/fdm/surface/active<br />
/sim/fdm/surface/valid<br />
<br />
Otherwise the following applies:<br />
/sim/fdm/surface/active<br />
* is set to true<br />
<br />
/sim/fdm/surface/valid<br />
* is set to true if there is a valid material available or set to false <br />
otherwise (the material defaults are set).<br />
<br />
The following properties are set to their respective values:<br />
<br />
/fdm/jsbsim/ground/solid<br />
* flag which defines if the surface is solid not<br />
<br />
/fdm/jsbsim/ground/bumpiness<br />
* defines the bumpiness factor<br />
<br />
/fdm/jsbsim/ground/maximum-force-lbs<br />
* maximum allowed force for this surface<br />
<br />
/fdm/jsbsim/ground/rolling_friction-factor<br />
* rolling friction factor - applies to rolling friction<br />
<br />
/fdm/jsbsim/ground/static-friction-factor<br />
* static friction factor - applies to static friction and dynamic friction<br />
<br />
These properties are also set for the appropriate gear and contact units.<br />
<br />
If you want to keep your old behaviour just set <br />
sim/fdm/surface/override-level to 1 somewhere in the configuration <br />
files, for Nasal this becomes:<br />
setprop("sim/fdm/surface/override-level", 1);<br />
<br />
I've updated the Nasal code for the following aircraft in the base package:<br />
Aircraft/Alouette-III/Systems/terrain.nas<br />
Aircraft/Cap10C/Nasal/cap10c.nas<br />
Aircraft/DR400-dauphin/Nasal/dr400.nas<br />
Aircraft/DR400/Nasal/dr400.nas<br />
Aircraft/F-8E-Crusader/Systems/terrain.nas<br />
Aircraft/JA37/Nasal/crash.nas<br />
Aircraft/MiG-15/Nasal/MiG-15bis.nas<br />
Aircraft/Noratlas/Systems/terrain.nas<br />
Aircraft/P-38-Lightning/Systems/terrain.nas<br />
Aircraft/PBY-Catalina/Systems/terrain.nas<br />
Aircraft/PC-6/Nasal/pc6-b2h4.nas<br />
Aircraft/SR71-BlackBird/Systems/terrain.nas<br />
Aircraft/VMX22-Osprey/Nasal/terrain_under.nas<br />
Aircraft/Short_Empire/Systems/mooring.nas<br />
<br />
Not that some of these might actually be YASim aircraft but YASim will <br />
just ignore the property.<br />
<br />
=== Random Buildings ===<br />
<br />
=== Project Rembrandt ===<br />
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]].<br />
<br />
=== A MapStructure Debugger ===<br />
<br />
[[File:MapStructure-ND-Profiling.png|thumb|MapStructure Debugger running a [[NavDisplay]] and profiling a few layers.]]<br />
<br />
[[MapStructure]] is a [[Nasal]]-space framework (designed and maintained by Philosopher) for managing layers of symbols in Nasal/[[Canvas]]-based mapping displays, which can be used in both aircraft MFDs/instruments like the [[NavDisplay]] (ND) and GUI dialogs, like the airport selection or [[Map]] dialogs. MapStructure is all about separating the visualization of the map from the visualized data itself, and the way it is shown to, and controlled by, the user. MapStructure is designed as a Model/View/Controller (MVC) framework.<br />
<br />
<br />
The MapStructure debugger is a simple GUI dialog intended to be used for debugging and benchmarking MapStructure-based charting layers. In its current form, it simply shows a NavDisplay inside the dialog with several layers enabled, including a 2D graph to benchmark each individual layer (such as APT, DME, FIX, TFC).<br />
Currently, the dialog is fairly simple and pretty crude, the plotting code is entirely based on [[FGPlot]] and needs to be further generalized eventually (see Canvas Plotting Framework). However, so far it's actually working nicely and can help determine where time is spent, i.e. which layers are "expensive" compared to others.<br />
In addition, the MapStructure debugger dialog can be used to easily test MapStructure-based maps/charts like Gijs' NavDisplay, without having to start up a complex aircraft like the 747-400 or 777-200ER. In other words, the ND can be easily tested by using the ufo or ogeL - which are usually up and running within ~10 seconds.<br />
<br />
Continue reading at [[MapStructure Debugger]]...<br />
<br />
=== Canvas System ===<br />
<br />
The F-16CJ is being renovated to include the most realistic fighter HUDs yet. See the progress here:[[F-16CJ HUD Project Newsletter]]. It is also online the FG Forum here: [http://forum.flightgear.org/viewtopic.php?f=71&t=22014 FG Forum Topic]<br />
<br />
=== High Level Architecture ===<br />
<br />
=== Usability Improvements ===<br />
<br />
=== Getting involved as a programmer ===<br />
Unfortunately, most of the active FG developers are currently very overstretched in terms of the areas that they have ownership of, which is affecting how much can actually be done. Fundamentally we need more core devs.<br />
<br />
If you are interested in contributing as a core developer, please see [[Howto:Start core development]].<br />
<br />
== Release ChangeLog ==<br />
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.<br />
<br />
== Interview with a contributor (NAME) ==<br />
''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.''<br />
<br />
* How long have you been involved in FlightGear?<br />
* What are your major interests in FlightGear?<br />
* What project are you working on right now?<br />
* What do you plan on doing in the future?<br />
* Are you happy with the way the FlightGear project is going?<br />
* What do you enjoy most about developing for FlightGear?<br />
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?<br />
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?<br />
<br />
More questions are being collected here: [[Interview questions]].<br />
<br />
Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX <br />
<br />
== Nasal for newbies ==<br />
<br />
== New software tools and projects ==<br />
<br />
== FlightGear addons and mods ==<br />
<br />
== In the hangar ==<br />
<br />
=== New aircraft ===<br />
==== '''Junkers Ju 390''' ====<br />
'''Emmanuel BARANGER, (helijah)'''<br />
<br />
[[File:Ju390-17.png|thumb|The tail gets up during the opening of the bay]]<br />
[[File:Ju390-18.png|thumb|above the sea]]<br />
[[File:Ju390-19.png|thumb|flying]]<br />
[[File:Ju390-20.png|thumb|flying 2]]<br />
<br />
The Junkers Ju 390 was a German aircraft intended to be used as a heavy transport, maritime patrol aircraft, and long-range bomber, a long-range derivative of the Ju 290. It was one of the aircraft designs submitted for the abortive Amerika Bomber project, along with the Messerschmitt Me 264, the Focke-Wulf Ta 400, the Heinkel He 277 (source Wikipedia)<br />
<br />
You can now find it in my hangar and on GIT hoping that you like as much as I enjoyed doing it.<br />
<br />
=== Updated aircraft ===<br />
<br />
<br />
==== '''Sikorsky SH-60 Bravo Seahawk''' ====<br />
'''James Cusick, (X7cusick8X)'''<br />
<br />
[[File:SH-60 Bravo.png|thumb|SH-60B Taking off from the USS Carl Vinson]]<br />
[[File:SH-60 Landing.png|thumb|SH-60 Landing]]<br />
[[File:SH-60 Rotor Wash.png|thumb|Rotor Wash]]<br />
<br />
The FG Seahawk is an incredibly easy to fly helicopter designed for naval conditions, with its integrated FCS and FDM landing on carrier decks is a blast. <br />
<br />
Recently i have take a break form FG but I am proud to announce the updated SH-60B Seahawk! <br />
The updates include:<br />
<br />
Integrated Pushback<br />
<br />
Selectable payloads<br />
<br />
95% complete folding animation for carrier deck transit <br />
<br />
New Liveries <br />
<br />
FDM Fixes <br />
<br />
and more<br />
<br />
=== Liveries ===<br />
<br />
== Scenery corner ==<br />
A great work has been done this month for Spain, such as the city of Barcelona, with the addition of landmarks such as Sagrada Familia, Agbar tower and its airport. These updates are available using Terrasync.<br />
<br />
=== Airports ===<br />
List of updated airports (mostly in Spain, Brazil, and France):<br />
* LEAB Albecete<br />
* LEAT Alfes<br />
* LEBG Burgos<br />
* LEBL Barcelona - El Prat<br />
* LECD La Cerdenya<br />
* LECI Santa Cilia-Los Pirineos<br />
* LECN Pinar de Castellon<br />
* LEDA Lleida<br />
* LEGE Girona<br />
* LEHC Huescas/Pirineos<br />
* LELL Sabadell<br />
* LELN Leon<br />
* LEPP Pamplona<br />
* LERE Requena<br />
* LESB Son Bonet<br />
* LESL San Luis<br />
* LESO San Sebastian<br />
* LESU Seo de Urgel<br />
* LETL Teruel Plata<br />
* LEVD Valladollid<br />
* LFLG Le Versoud<br />
* LFRB Brest Bretagne<br />
* LFRN Rennes St Jacques<br />
* PHNL Honolulu Intl<br />
* SBNF Ministro Victor Konder<br />
* SBPK Pelotas<br />
* SBRJ Santos Dumont Airport<br />
* SBUR Uberaba<br />
* SPAF Camana<br />
<br />
=== Regional texturing ===<br />
<br />
New regional texture definitions are now available on GIT for Ireland in the CORINE-landcover based WorldScenery 2.0. Enjoy the boglands of Connemara, or the hills and lakes of Kerry. With hires scenery and special textures, the Green Isle is now quite a nice place to explore.<br />
<br />
The Ireland texture definitions have full support for procedural texturing and for the autumn coloring effect of ALS.<br />
<br />
<br />
[[File:Eire02.jpg|300px| Connemara bog]]<br />
[[File:Eire04.jpg|300px| Dingle peninsula]]<br />
[[File:Eire05.jpg|300px| Kenmare bay]]<br />
<br />
=== Models optimizations ===<br />
Since a few months, works have been done on the scenery to clean existing models to make them lighter but keeping or even improving the overall quality. Among the tasks are deleting unseen faces, making face singled-sided, reducing texture size or removing unused alpha from texture.<br />
<br />
== Aircraft of the month ==<br />
== Airport of the month ==<br />
== Screenshot of the month ==<br />
<br />
== Suggested flights ==<br />
== Aircraft reviews ==<br />
<br />
== Wiki updates ==<br />
=== Translators required ===<br />
{|<br />
|[[File:en.gif]]<br />
|The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multi-language then start at [[Help:Translate]].<br />
|-<br />
|[[File:de.gif]]<br />
|Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki Mehrsprachig zu machen, dann fang doch mit [[:de:Help:Übersetzen|Help:Übersetzen]] an.<br />
|-<br />
|[[File:nl.gif]]<br />
|De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].<br />
|-<br />
|[[File:es.gif]]<br />
|La FlightGear wiki todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].<br />
|}<br />
<br />
== Community news ==<br />
=== FlightGear on YouTube ===<br />
You can stay updated with FlightGear news, updates and tutorials by visiting and subscribing to [http://www.youtube.com/user/osjcag osjcag's] channel on YouTube.<br />
<br />
=== New tutorials and screencasts ===<br />
<br />
=== FlightGear &diams; Cross-Country Tutorial II &diams; a VFR guide ===<br />
[[File:Coverwiki2.jpg|250px|thumb|left]]<br />
<br /> <br /> <br /> <br />It's almost been a year since the first release of Cross-Country Tutorial II.<br /><br />
Now with '''version three point zero''' the document is better than ever in many aspects.<br /> <br /><br />
Go to the respective FG Forum thread: http://forum.flightgear.org/viewtopic.php?f=72&t=19600 where you can: <br /> <br />
*download this tutorial <br />
**find out more about it <br />
***'''post your comments and suggestions'''<br />
<br /> <br />coming up soon is the X-Country 2's own wiki page!<br />
<br /> <br /> <br /> <br /> <br /> <br /><br />
=== Forum news ===<br />
=== Multiplayer ===<br />
=== Virtual airlines ===<br />
=== FlightGear events ===<br />
<br />
== Useful links ==<br />
== And finally ... ==<br />
=== Contributing ===<br />
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
To learn more about how the project works, please see [http://flightgear.org/forums/viewtopic.php?f=42&t=15267#p149971 this short essay] written by Thorsten, for a more detailed article see [[How the FlightGear project works]].<br />
<br />
=== YASim looking for a new maintainer ===<br />
<br />
<br />
{{cquote|There are some pending merge requests to add some Yasim features, but we have an issue that since none of the current C++ developers own, or are experts in Yasim, we're reluctant to be the person who merges such changes, and potentially introduces subtle regressions.<br />
<br />
Obviously this is chicken-and-egg, since no one can become expert enough in the code to become a maintainer :)<br />
<br />
So, I'm more than happy to apply patches *providing* I can be convinced they are sane+reasonable from a pure code perspective (happy to help with that, too, <br />
if people are new to C++), and providing we have some assurance that a representative sample of yasim aircraft are unchanged or improved by the patch. <br />
Suggestions for that means in practice, are most welcome!<br />
<br />
Otherwise I worry, given the nature of the solver, we'll keep optimising the solver for some aircraft, and making other existing aircraft worse - until someone tests them, and announced that they're no longer working.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23986.html <br />
|title=YASim and documentation<br />
|author=James Turner |date= Fri, 05 Oct 2012 03:54:43 -0700}}</ref>|James Turner}}<br />
<br />
{{cquote|I am still broadly happy to answer questions if posed (as long as I remember enough to come up with a meaningful answer). Just cc: me if you do, because my<br />
latencies here are measured in weeks. <br />
Bugs can always be fixed. What YASim needs is a maintainer, not really expertise per se. The latter comes from the former.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23986.html <br />
|title=YASim and documentation<br />
|author=Andy Ross |date= Fri, 05 Oct 2012 03:54:43 -0700}}</ref>|Andy Ross}}<br />
<br />
<references/><br />
<br />
<br />
=== Call for volunteers ===<br />
* The [[Target4Today]] team is looking for volunteers to help improving FlightGear's combat support<br />
<br />
=== Did you know ===<br />
<br />
[[Category:FlightGear Newsletter]]<br />
<!-- this needs to be changed after each release, so that newsletters show up in the proper category --><br />
<br />
[[Category:Changes after 2.12]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_February_2014&diff=67723FlightGear Newsletter February 20142014-02-16T16:14:25Z<p>Blackiris: /* Scenery corner */</p>
<hr />
<div><br />
{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
{{Note|This newsletter is currently being written by our contributors, people like YOU:<br />
<br />
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 news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter. Core developers are encouraged to add news about their latest work to the newsletter's development section and [[Next Changelog|the changelog of the upcoming release]]. At the end of each month, it's generally a good idea to get in touch with other contributors to ask them to add news about their contributions to the newsletter.}}<br />
<br />
== Development news ==<br />
Note to all contributors: Please also copy your newsletter additions to the changelog for the upcoming release: [[Next Changelog]].<br />
<br />
=== JSBSim Ground Effects ===<br />
This is a heads up for JSBSim aircraft maintainers that user their own <br />
ground detection and handling code.<br />
As of today JSBSim, just like YASim, supports ground effects like <br />
bumpiness, solid-ground detection and adjusting of friction actors.<br />
<br />
Actually JSBSim supports an extra feature, BOGEY contact points sink in <br />
a non-solid ground surface but STRUCTURE contact point do not, making it <br />
easy to define floats using STRUCTURE contact points.<br />
<br />
In order not to pollute /fdm/jsbim too much I've added the following <br />
properties:<br />
<br />
/sim/fdm/surface/override-level<br />
A user defined property which if defined and set to a something higher <br />
than 0 will disable the JSBSim ground reactions code completely and the <br />
following properties are set to false:<br />
/sim/fdm/surface/active<br />
/sim/fdm/surface/valid<br />
<br />
Otherwise the following applies:<br />
/sim/fdm/surface/active<br />
* is set to true<br />
<br />
/sim/fdm/surface/valid<br />
* is set to true if there is a valid material available or set to false <br />
otherwise (the material defaults are set).<br />
<br />
The following properties are set to their respective values:<br />
<br />
/fdm/jsbsim/ground/solid<br />
* flag which defines if the surface is solid not<br />
<br />
/fdm/jsbsim/ground/bumpiness<br />
* defines the bumpiness factor<br />
<br />
/fdm/jsbsim/ground/maximum-force-lbs<br />
* maximum allowed force for this surface<br />
<br />
/fdm/jsbsim/ground/rolling_friction-factor<br />
* rolling friction factor - applies to rolling friction<br />
<br />
/fdm/jsbsim/ground/static-friction-factor<br />
* static friction factor - applies to static friction and dynamic friction<br />
<br />
These properties are also set for the appropriate gear and contact units.<br />
<br />
If you want to keep your old behaviour just set <br />
sim/fdm/surface/override-level to 1 somewhere in the configuration <br />
files, for Nasal this becomes:<br />
setprop("sim/fdm/surface/override-level", 1);<br />
<br />
I've updated the Nasal code for the following aircraft in the base package:<br />
Aircraft/Alouette-III/Systems/terrain.nas<br />
Aircraft/Cap10C/Nasal/cap10c.nas<br />
Aircraft/DR400-dauphin/Nasal/dr400.nas<br />
Aircraft/DR400/Nasal/dr400.nas<br />
Aircraft/F-8E-Crusader/Systems/terrain.nas<br />
Aircraft/JA37/Nasal/crash.nas<br />
Aircraft/MiG-15/Nasal/MiG-15bis.nas<br />
Aircraft/Noratlas/Systems/terrain.nas<br />
Aircraft/P-38-Lightning/Systems/terrain.nas<br />
Aircraft/PBY-Catalina/Systems/terrain.nas<br />
Aircraft/PC-6/Nasal/pc6-b2h4.nas<br />
Aircraft/SR71-BlackBird/Systems/terrain.nas<br />
Aircraft/VMX22-Osprey/Nasal/terrain_under.nas<br />
Aircraft/Short_Empire/Systems/mooring.nas<br />
<br />
Not that some of these might actually be YASim aircraft but YASim will <br />
just ignore the property.<br />
<br />
=== Random Buildings ===<br />
<br />
=== Project Rembrandt ===<br />
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]].<br />
<br />
=== Canvas System ===<br />
<br />
The F-16CJ is being renovated to include the most realistic fighter HUDs yet. See the progress here:[[F-16CJ HUD Project Newsletter]]. It is also online the FG Forum here: [http://forum.flightgear.org/viewtopic.php?f=71&t=22014 FG Forum Topic]<br />
<br />
=== High Level Architecture ===<br />
<br />
=== Usability Improvements ===<br />
<br />
=== Getting involved as a programmer ===<br />
Unfortunately, most of the active FG developers are currently very overstretched in terms of the areas that they have ownership of, which is affecting how much can actually be done. Fundamentally we need more core devs.<br />
<br />
If you are interested in contributing as a core developer, please see [[Howto:Start core development]].<br />
<br />
== Release ChangeLog ==<br />
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.<br />
<br />
== Interview with a contributor (NAME) ==<br />
''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.''<br />
<br />
* How long have you been involved in FlightGear?<br />
* What are your major interests in FlightGear?<br />
* What project are you working on right now?<br />
* What do you plan on doing in the future?<br />
* Are you happy with the way the FlightGear project is going?<br />
* What do you enjoy most about developing for FlightGear?<br />
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?<br />
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?<br />
<br />
More questions are being collected here: [[Interview questions]].<br />
<br />
Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX <br />
<br />
== Nasal for newbies ==<br />
<br />
== New software tools and projects ==<br />
<br />
== FlightGear addons and mods ==<br />
<br />
== In the hangar ==<br />
<br />
=== New aircraft ===<br />
<br />
=== Updated aircraft ===<br />
<br />
<br />
==== '''Sikorsky SH-60 Bravo Seahawk''' ====<br />
'''James Cusick, (X7cusick8X)'''<br />
<br />
[[File:SH-60 Bravo.png|thumb|SH-60B Taking off from the USS Carl Vinson]]<br />
[[File:SH-60 Landing.png|thumb|SH-60 Landing]]<br />
[[File:SH-60 Rotor Wash.png|thumb|Rotor Wash]]<br />
<br />
The FG Seahawk is an incredibly easy to fly helicopter designed for naval conditions, with its integrated FCS and FDM landing on carrier decks is a blast. <br />
<br />
Recently i have take a break form FG but I am proud to announce the updated SH-60B Seahawk! <br />
The updates include:<br />
<br />
Integrated Pushback<br />
<br />
Selectable payloads<br />
<br />
95% complete folding animation for carrier deck transit <br />
<br />
New Liveries <br />
<br />
FDM Fixes <br />
<br />
and more<br />
<br />
=== Liveries ===<br />
<br />
== Scenery corner ==<br />
A great work has been done this month for Spain, such as the city of Barcelona, with the addition of landmarks such as Sagrada Familia, Agbar tower and its airport. These updates are available using Terrasync.<br />
<br />
=== Airports ===<br />
List of updated airports (mostly in Spain, Brazil, and France):<br />
* LEAB Albecete<br />
* LEAT Alfes<br />
* LEBG Burgos<br />
* LEBL Barcelona - El Prat<br />
* LECD La Cerdenya<br />
* LECI Santa Cilia-Los Pirineos<br />
* LECN Pinar de Castellon<br />
* LEDA Lleida<br />
* LEGE Girona<br />
* LELL Sabadell<br />
* LEPP Pamplona<br />
* LERE Requena<br />
* LESB Son Bonet<br />
* LESL San Luis<br />
* LESU Seo de Urgel<br />
* LETL Teruel Plata<br />
* LFLG Le Versoud<br />
* LFRB Brest Bretagne<br />
* LFRN Rennes St Jacques<br />
* PHNL Honolulu Intl<br />
* SBNF Ministro Victor Konder<br />
* SBPK Pelotas<br />
* SBRJ Santos Dumont Airport<br />
* SBUR Uberaba<br />
* SPAF Camana<br />
<br />
<br />
=== Models optimizations ===<br />
Since a few months, works have been done on the scenery to clean existing models to make them lighter but keeping or even improving the overall quality. Among the tasks are deleting unseen faces, making face singled-sided, reducing texture size or removing unused alpha from texture.<br />
<br />
== Aircraft of the month ==<br />
== Airport of the month ==<br />
== Screenshot of the month ==<br />
<br />
== Suggested flights ==<br />
== Aircraft reviews ==<br />
<br />
== Wiki updates ==<br />
=== Translators required ===<br />
{|<br />
|[[File:en.gif]]<br />
|The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multi-language then start at [[Help:Translate]].<br />
|-<br />
|[[File:de.gif]]<br />
|Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki Mehrsprachig zu machen, dann fang doch mit [[:de:Help:Übersetzen|Help:Übersetzen]] an.<br />
|-<br />
|[[File:nl.gif]]<br />
|De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].<br />
|-<br />
|[[File:es.gif]]<br />
|La FlightGear wiki todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].<br />
|}<br />
<br />
== Community news ==<br />
=== FlightGear on YouTube ===<br />
You can stay updated with FlightGear news, updates and tutorials by visiting and subscribing to [http://www.youtube.com/user/osjcag osjcag's] channel on YouTube.<br />
<br />
=== New tutorials and screencasts ===<br />
<br />
=== FlightGear &diams; Cross-Country Tutorial II &diams; a VFR guide ===<br />
[[File:Coverwiki2.jpg|250px|thumb|left]]<br />
<br /> <br /> <br /> <br />It's almost been a year since the first release of Cross-Country Tutorial II.<br /><br />
Now with '''version three point zero''' the document is better than ever in many aspects.<br /> <br /><br />
Go to the respective FG Forum thread: http://forum.flightgear.org/viewtopic.php?f=72&t=19600 where you can: <br /> <br />
*download this tutorial <br />
**find out more about it <br />
***'''post your comments and suggestions'''<br />
<br /> <br />coming up soon is the X-Country 2's own wiki page!<br />
<br /> <br /> <br /> <br /> <br /> <br /><br />
=== Forum news ===<br />
=== Multiplayer ===<br />
=== Virtual airlines ===<br />
=== FlightGear events ===<br />
<br />
== Useful links ==<br />
== And finally ... ==<br />
=== Contributing ===<br />
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
To learn more about how the project works, please see [http://flightgear.org/forums/viewtopic.php?f=42&t=15267#p149971 this short essay] written by Thorsten, for a more detailed article see [[How the FlightGear project works]].<br />
<br />
=== YASim looking for a new maintainer ===<br />
<br />
<br />
{{cquote|There are some pending merge requests to add some Yasim features, but we have an issue that since none of the current C++ developers own, or are experts in Yasim, we're reluctant to be the person who merges such changes, and potentially introduces subtle regressions.<br />
<br />
Obviously this is chicken-and-egg, since no one can become expert enough in the code to become a maintainer :)<br />
<br />
So, I'm more than happy to apply patches *providing* I can be convinced they are sane+reasonable from a pure code perspective (happy to help with that, too, <br />
if people are new to C++), and providing we have some assurance that a representative sample of yasim aircraft are unchanged or improved by the patch. <br />
Suggestions for that means in practice, are most welcome!<br />
<br />
Otherwise I worry, given the nature of the solver, we'll keep optimising the solver for some aircraft, and making other existing aircraft worse - until someone tests them, and announced that they're no longer working.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23986.html <br />
|title=YASim and documentation<br />
|author=James Turner |date= Fri, 05 Oct 2012 03:54:43 -0700}}</ref>|James Turner}}<br />
<br />
{{cquote|I am still broadly happy to answer questions if posed (as long as I remember enough to come up with a meaningful answer). Just cc: me if you do, because my<br />
latencies here are measured in weeks. <br />
Bugs can always be fixed. What YASim needs is a maintainer, not really expertise per se. The latter comes from the former.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23986.html <br />
|title=YASim and documentation<br />
|author=Andy Ross |date= Fri, 05 Oct 2012 03:54:43 -0700}}</ref>|Andy Ross}}<br />
<br />
<references/><br />
<br />
<br />
=== Call for volunteers ===<br />
* The [[Target4Today]] team is looking for volunteers to help improving FlightGear's combat support<br />
<br />
=== Did you know ===<br />
<br />
[[Category:FlightGear Newsletter]]<br />
<!-- this needs to be changed after each release, so that newsletters show up in the proper category --><br />
<br />
[[Category:Changes after 2.12]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_February_2014&diff=67685FlightGear Newsletter February 20142014-02-15T18:43:51Z<p>Blackiris: /* Scenery corner */</p>
<hr />
<div><br />
{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
{{Note|This newsletter is currently being written by our contributors, people like YOU:<br />
<br />
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 news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter. Core developers are encouraged to add news about their latest work to the newsletter's development section and [[Next Changelog|the changelog of the upcoming release]]. At the end of each month, it's generally a good idea to get in touch with other contributors to ask them to add news about their contributions to the newsletter.}}<br />
<br />
== Development news ==<br />
Note to all contributors: Please also copy your newsletter additions to the changelog for the upcoming release: [[Next Changelog]].<br />
<br />
=== JSBSim Ground Effects ===<br />
This is a heads up for JSBSim aircraft maintainers that user their own <br />
ground detection and handling code.<br />
As of today JSBSim, just like YASim, supports ground effects like <br />
bumpiness, solid-ground detection and adjusting of friction actors.<br />
<br />
Actually JSBSim supports an extra feature, BOGEY contact points sink in <br />
a non-solid ground surface but STRUCTURE contact point do not, making it <br />
easy to define floats using STRUCTURE contact points.<br />
<br />
In order not to pollute /fdm/jsbim too much I've added the following <br />
properties:<br />
<br />
/sim/fdm/surface/override-level<br />
A user defined property which if defined and set to a something higher <br />
than 0 will disable the JSBSim ground reactions code completely and the <br />
following properties are set to false:<br />
/sim/fdm/surface/active<br />
/sim/fdm/surface/valid<br />
<br />
Otherwise the following applies:<br />
/sim/fdm/surface/active<br />
* is set to true<br />
<br />
/sim/fdm/surface/valid<br />
* is set to true if there is a valid material available or set to false <br />
otherwise (the material defaults are set).<br />
<br />
The following properties are set to their respective values:<br />
<br />
/fdm/jsbsim/ground/solid<br />
* flag which defines if the surface is solid not<br />
<br />
/fdm/jsbsim/ground/bumpiness<br />
* defines the bumpiness factor<br />
<br />
/fdm/jsbsim/ground/maximum-force-lbs<br />
* maximum allowed force for this surface<br />
<br />
/fdm/jsbsim/ground/rolling_friction-factor<br />
* rolling friction factor - applies to rolling friction<br />
<br />
/fdm/jsbsim/ground/static-friction-factor<br />
* static friction factor - applies to static friction and dynamic friction<br />
<br />
These properties are also set for the appropriate gear and contact units.<br />
<br />
If you want to keep your old behaviour just set <br />
sim/fdm/surface/override-level to 1 somewhere in the configuration <br />
files, for Nasal this becomes:<br />
setprop("sim/fdm/surface/override-level", 1);<br />
<br />
I've updated the Nasal code for the following aircraft in the base package:<br />
Aircraft/Alouette-III/Systems/terrain.nas<br />
Aircraft/Cap10C/Nasal/cap10c.nas<br />
Aircraft/DR400-dauphin/Nasal/dr400.nas<br />
Aircraft/DR400/Nasal/dr400.nas<br />
Aircraft/F-8E-Crusader/Systems/terrain.nas<br />
Aircraft/JA37/Nasal/crash.nas<br />
Aircraft/MiG-15/Nasal/MiG-15bis.nas<br />
Aircraft/Noratlas/Systems/terrain.nas<br />
Aircraft/P-38-Lightning/Systems/terrain.nas<br />
Aircraft/PBY-Catalina/Systems/terrain.nas<br />
Aircraft/PC-6/Nasal/pc6-b2h4.nas<br />
Aircraft/SR71-BlackBird/Systems/terrain.nas<br />
Aircraft/VMX22-Osprey/Nasal/terrain_under.nas<br />
Aircraft/Short_Empire/Systems/mooring.nas<br />
<br />
Not that some of these might actually be YASim aircraft but YASim will <br />
just ignore the property.<br />
<br />
=== Random Buildings ===<br />
<br />
=== Project Rembrandt ===<br />
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]].<br />
<br />
=== Canvas System ===<br />
<br />
The F-16CJ is being renovated to include the most realistic fighter HUDs yet. See the progress here:[[F-16CJ HUD Project Newsletter]]. It is also online the FG Forum here: [http://forum.flightgear.org/viewtopic.php?f=71&t=22014 FG Forum Topic]<br />
<br />
=== High Level Architecture ===<br />
<br />
=== Usability Improvements ===<br />
<br />
=== Getting involved as a programmer ===<br />
Unfortunately, most of the active FG developers are currently very overstretched in terms of the areas that they have ownership of, which is affecting how much can actually be done. Fundamentally we need more core devs.<br />
<br />
If you are interested in contributing as a core developer, please see [[Howto:Start core development]].<br />
<br />
== Release ChangeLog ==<br />
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.<br />
<br />
== Interview with a contributor (NAME) ==<br />
''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.''<br />
<br />
* How long have you been involved in FlightGear?<br />
* What are your major interests in FlightGear?<br />
* What project are you working on right now?<br />
* What do you plan on doing in the future?<br />
* Are you happy with the way the FlightGear project is going?<br />
* What do you enjoy most about developing for FlightGear?<br />
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?<br />
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?<br />
<br />
More questions are being collected here: [[Interview questions]].<br />
<br />
Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX <br />
<br />
== Nasal for newbies ==<br />
<br />
== New software tools and projects ==<br />
<br />
== FlightGear addons and mods ==<br />
<br />
== In the hangar ==<br />
<br />
=== New aircraft ===<br />
<br />
=== Updated aircraft ===<br />
<br />
<br />
==== '''Sikorsky SH-60 Bravo Seahawk''' ====<br />
'''James Cusick, (X7cusick8X)'''<br />
<br />
[[File:SH-60 Bravo.png|thumb|SH-60B Taking off from the USS Carl Vinson]]<br />
[[File:SH-60 Landing.png|thumb|SH-60 Landing]]<br />
[[File:SH-60 Rotor Wash.png|thumb|Rotor Wash]]<br />
<br />
The FG Seahawk is an incredibly easy to fly helicopter designed for naval conditions, with its integrated FCS and FDM landing on carrier decks is a blast. <br />
<br />
Recently i have take a break form FG but I am proud to announce the updated SH-60B Seahawk! <br />
The updates include:<br />
<br />
Integrated Pushback<br />
<br />
Selectable payloads<br />
<br />
95% complete folding animation for carrier deck transit <br />
<br />
New Liveries <br />
<br />
FDM Fixes <br />
<br />
and more<br />
<br />
=== Liveries ===<br />
<br />
== Scenery corner ==<br />
A great work has been done this month for Spain, such as the city of Barcelona, with the addition of landmarks such as Sagrada Familia, Agbar tower and its airport. These updates are available using Terrasync.<br />
<br />
=== Airports ===<br />
List of updated airports (mostly in Spain, Brazil, and France):<br />
* LEAB Albecete<br />
* LEAT Alfes<br />
* LEBG Burgos<br />
* LEBL Barcelona - El Prat<br />
* LECD La Cerdenya<br />
* LECI Santa Cilia-Los Pirineos<br />
* LECN Pinar de Castellon<br />
* LEDA Lleida<br />
* LEGE Girona<br />
* LELL Sabadell<br />
* LEPP Pamplona<br />
* LERE Requena<br />
* LESB Son Bonet<br />
* LESL San Luis<br />
* LESU Seo de Urgel<br />
* LETL Teruel Plata<br />
* LFLG Le Versoud<br />
* LFRB Brest Bretagne<br />
* LFRN Rennes St Jacques<br />
* PHNL Honolulu Intl<br />
* SBNF Ministro Victor Konder<br />
* SBPK Pelotas<br />
* SBUR Uberaba<br />
* SPAF Camana<br />
<br />
<br />
=== Models optimizations ===<br />
Since a few months, works have been done on the scenery to clean existing models to make them lighter but keeping or even improving the overall quality. Among the tasks are deleting unseen faces and making face singled-sided, reducing texture size or removing unused alpha from texture.<br />
<br />
== Aircraft of the month ==<br />
== Airport of the month ==<br />
== Screenshot of the month ==<br />
<br />
== Suggested flights ==<br />
== Aircraft reviews ==<br />
<br />
== Wiki updates ==<br />
=== Translators required ===<br />
{|<br />
|[[File:en.gif]]<br />
|The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multi-language then start at [[Help:Translate]].<br />
|-<br />
|[[File:de.gif]]<br />
|Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki Mehrsprachig zu machen, dann fang doch mit [[:de:Help:Übersetzen|Help:Übersetzen]] an.<br />
|-<br />
|[[File:nl.gif]]<br />
|De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].<br />
|-<br />
|[[File:es.gif]]<br />
|La FlightGear wiki todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].<br />
|}<br />
<br />
== Community news ==<br />
=== FlightGear on YouTube ===<br />
You can stay updated with FlightGear news, updates and tutorials by visiting and subscribing to [http://www.youtube.com/user/osjcag osjcag's] channel on YouTube.<br />
<br />
=== New tutorials and screencasts ===<br />
<br />
=== FlightGear &diams; Cross-Country Tutorial II &diams; a VFR guide ===<br />
[[File:Coverwiki2.jpg|250px|thumb|left]]<br />
<br /> <br /> <br /> <br />It's almost been a year since the first release of Cross-Country Tutorial II.<br /><br />
Now with '''version three point zero''' the document is better than ever in many aspects.<br /> <br /><br />
Go to the respective FG Forum thread: http://forum.flightgear.org/viewtopic.php?f=72&t=19600 where you can: <br /> <br />
*download this tutorial <br />
**find out more about it <br />
***'''post your comments and suggestions'''<br />
<br /> <br />coming up soon is the X-Country 2's own wiki page!<br />
<br /> <br /> <br /> <br /> <br /> <br /><br />
=== Forum news ===<br />
=== Multiplayer ===<br />
=== Virtual airlines ===<br />
=== FlightGear events ===<br />
<br />
== Useful links ==<br />
== And finally ... ==<br />
=== Contributing ===<br />
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
To learn more about how the project works, please see [http://flightgear.org/forums/viewtopic.php?f=42&t=15267#p149971 this short essay] written by Thorsten, for a more detailed article see [[How the FlightGear project works]].<br />
<br />
=== YASim looking for a new maintainer ===<br />
<br />
<br />
{{cquote|There are some pending merge requests to add some Yasim features, but we have an issue that since none of the current C++ developers own, or are experts in Yasim, we're reluctant to be the person who merges such changes, and potentially introduces subtle regressions.<br />
<br />
Obviously this is chicken-and-egg, since no one can become expert enough in the code to become a maintainer :)<br />
<br />
So, I'm more than happy to apply patches *providing* I can be convinced they are sane+reasonable from a pure code perspective (happy to help with that, too, <br />
if people are new to C++), and providing we have some assurance that a representative sample of yasim aircraft are unchanged or improved by the patch. <br />
Suggestions for that means in practice, are most welcome!<br />
<br />
Otherwise I worry, given the nature of the solver, we'll keep optimising the solver for some aircraft, and making other existing aircraft worse - until someone tests them, and announced that they're no longer working.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23986.html <br />
|title=YASim and documentation<br />
|author=James Turner |date= Fri, 05 Oct 2012 03:54:43 -0700}}</ref>|James Turner}}<br />
<br />
{{cquote|I am still broadly happy to answer questions if posed (as long as I remember enough to come up with a meaningful answer). Just cc: me if you do, because my<br />
latencies here are measured in weeks. <br />
Bugs can always be fixed. What YASim needs is a maintainer, not really expertise per se. The latter comes from the former.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23986.html <br />
|title=YASim and documentation<br />
|author=Andy Ross |date= Fri, 05 Oct 2012 03:54:43 -0700}}</ref>|Andy Ross}}<br />
<br />
<references/><br />
<br />
<br />
=== Call for volunteers ===<br />
* The [[Target4Today]] team is looking for volunteers to help improving FlightGear's combat support<br />
<br />
=== Did you know ===<br />
<br />
[[Category:FlightGear Newsletter]]<br />
<!-- this needs to be changed after each release, so that newsletters show up in the proper category --><br />
<br />
[[Category:Changes after 2.12]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_February_2014&diff=67656FlightGear Newsletter February 20142014-02-15T09:33:04Z<p>Blackiris: /* Scenery corner */</p>
<hr />
<div><br />
{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
{{Note|This newsletter is currently being written by our contributors, people like YOU:<br />
<br />
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 news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter. Core developers are encouraged to add news about their latest work to the newsletter's development section and [[Next Changelog|the changelog of the upcoming release]]. At the end of each month, it's generally a good idea to get in touch with other contributors to ask them to add news about their contributions to the newsletter.}}<br />
<br />
== Development news ==<br />
Note to all contributors: Please also copy your newsletter additions to the changelog for the upcoming release: [[Next Changelog]].<br />
<br />
=== JSBSim Ground Effects ===<br />
This is a heads up for JSBSim aircraft maintainers that user their own <br />
ground detection and handling code.<br />
As of today JSBSim, just like YASim, supports ground effects like <br />
bumpiness, solid-ground detection and adjusting of friction actors.<br />
<br />
Actually JSBSim supports an extra feature, BOGEY contact points sink in <br />
a non-solid ground surface but STRUCTURE contact point do not, making it <br />
easy to define floats using STRUCTURE contact points.<br />
<br />
In order not to pollute /fdm/jsbim too much I've added the following <br />
properties:<br />
<br />
/sim/fdm/surface/override-level<br />
A user defined property which if defined and set to a something higher <br />
than 0 will disable the JSBSim ground reactions code completely and the <br />
following properties are set to false:<br />
/sim/fdm/surface/active<br />
/sim/fdm/surface/valid<br />
<br />
Otherwise the following applies:<br />
/sim/fdm/surface/active<br />
* is set to true<br />
<br />
/sim/fdm/surface/valid<br />
* is set to true if there is a valid material available or set to false <br />
otherwise (the material defaults are set).<br />
<br />
The following properties are set to their respective values:<br />
<br />
/fdm/jsbsim/ground/solid<br />
* flag which defines if the surface is solid not<br />
<br />
/fdm/jsbsim/ground/bumpiness<br />
* defines the bumpiness factor<br />
<br />
/fdm/jsbsim/ground/maximum-force-lbs<br />
* maximum allowed force for this surface<br />
<br />
/fdm/jsbsim/ground/rolling_friction-factor<br />
* rolling friction factor - applies to rolling friction<br />
<br />
/fdm/jsbsim/ground/static-friction-factor<br />
* static friction factor - applies to static friction and dynamic friction<br />
<br />
These properties are also set for the appropriate gear and contact units.<br />
<br />
If you want to keep your old behaviour just set <br />
sim/fdm/surface/override-level to 1 somewhere in the configuration <br />
files, for Nasal this becomes:<br />
setprop("sim/fdm/surface/override-level", 1);<br />
<br />
I've updated the Nasal code for the following aircraft in the base package:<br />
Aircraft/Alouette-III/Systems/terrain.nas<br />
Aircraft/Cap10C/Nasal/cap10c.nas<br />
Aircraft/DR400-dauphin/Nasal/dr400.nas<br />
Aircraft/DR400/Nasal/dr400.nas<br />
Aircraft/F-8E-Crusader/Systems/terrain.nas<br />
Aircraft/JA37/Nasal/crash.nas<br />
Aircraft/MiG-15/Nasal/MiG-15bis.nas<br />
Aircraft/Noratlas/Systems/terrain.nas<br />
Aircraft/P-38-Lightning/Systems/terrain.nas<br />
Aircraft/PBY-Catalina/Systems/terrain.nas<br />
Aircraft/PC-6/Nasal/pc6-b2h4.nas<br />
Aircraft/SR71-BlackBird/Systems/terrain.nas<br />
Aircraft/VMX22-Osprey/Nasal/terrain_under.nas<br />
Aircraft/Short_Empire/Systems/mooring.nas<br />
<br />
Not that some of these might actually be YASim aircraft but YASim will <br />
just ignore the property.<br />
<br />
=== Random Buildings ===<br />
<br />
=== Project Rembrandt ===<br />
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]].<br />
<br />
=== Canvas System ===<br />
<br />
The F-16CJ is being renovated to include the most realistic fighter HUDs yet. See the progress here:[[F-16CJ HUD Project Newsletter]]. It is also online the FG Forum here: [http://forum.flightgear.org/viewtopic.php?f=71&t=22014 FG Forum Topic]<br />
<br />
=== High Level Architecture ===<br />
<br />
=== Usability Improvements ===<br />
<br />
=== Getting involved as a programmer ===<br />
Unfortunately, most of the active FG developers are currently very overstretched in terms of the areas that they have ownership of, which is affecting how much can actually be done. Fundamentally we need more core devs.<br />
<br />
If you are interested in contributing as a core developer, please see [[Howto:Start core development]].<br />
<br />
== Release ChangeLog ==<br />
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.<br />
<br />
== Interview with a contributor (NAME) ==<br />
''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.''<br />
<br />
* How long have you been involved in FlightGear?<br />
* What are your major interests in FlightGear?<br />
* What project are you working on right now?<br />
* What do you plan on doing in the future?<br />
* Are you happy with the way the FlightGear project is going?<br />
* What do you enjoy most about developing for FlightGear?<br />
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?<br />
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?<br />
<br />
More questions are being collected here: [[Interview questions]].<br />
<br />
Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX <br />
<br />
== Nasal for newbies ==<br />
<br />
== New software tools and projects ==<br />
<br />
== FlightGear addons and mods ==<br />
<br />
== In the hangar ==<br />
<br />
=== New aircraft ===<br />
<br />
=== Updated aircraft ===<br />
<br />
<br />
==== '''Sikorsky SH-60 Bravo Seahawk''' ====<br />
'''James Cusick, (X7cusick8X)'''<br />
<br />
[[File:SH-60 Bravo.png|thumb|SH-60B Taking off from the USS Carl Vinson]]<br />
[[File:SH-60 Landing.png|thumb|SH-60 Landing]]<br />
[[File:SH-60 Rotor Wash.png|thumb|Rotor Wash]]<br />
<br />
The FG Seahawk is an incredibly easy to fly helicopter designed for naval conditions, with its integrated FCS and FDM landing on carrier decks is a blast. <br />
<br />
Recently i have take a break form FG but I am proud to announce the updated SH-60B Seahawk! <br />
The updates include:<br />
<br />
Integrated Pushback<br />
<br />
Selectable payloads<br />
<br />
95% complete folding animation for carrier deck transit <br />
<br />
New Liveries <br />
<br />
FDM Fixes <br />
<br />
and more<br />
<br />
=== Liveries ===<br />
<br />
== Scenery corner ==<br />
A great work has been done this month for Spain, such as the city of Barcelona.<br />
<br />
=== Airports ===<br />
List of updated airports (mostly in Spain, France, and Brazil):<br />
* LEAB Albecete<br />
* LEAT Alfes<br />
* LEBL Barcelona - El Prat<br />
* LECD La Cerdenya<br />
* LECI Santa Cilia-Los Pirineos<br />
* LECN Pinar de Castellon<br />
* LEDA Lleida<br />
* LEGE Girona<br />
* LELL Sabadell<br />
* LEPP Pamplona<br />
* LERE Requena<br />
* LESL San Luis<br />
* LESU Seo de Urgel<br />
* LETL Teruel Plata<br />
* LFLG Le Versoud<br />
* LFRB Brest Bretagne<br />
* LFRN Rennes St Jacques<br />
* PHNL Honolulu Intl<br />
* SBNF Ministro Victor Konder<br />
* SBPK Pelotas<br />
* SBUR Uberaba<br />
* SPAF Camana<br />
<br />
<br />
=== Models optimizations ===<br />
Since a few months, works have been done on the scenery to clean existing models to make them lighter but keeping or even improving the overall quality. Among the tasks there are deleting unseen faces and making face singled-sided, and reducing texture size.<br />
<br />
== Aircraft of the month ==<br />
== Airport of the month ==<br />
== Screenshot of the month ==<br />
<br />
== Suggested flights ==<br />
== Aircraft reviews ==<br />
<br />
== Wiki updates ==<br />
=== Translators required ===<br />
{|<br />
|[[File:en.gif]]<br />
|The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multi-language then start at [[Help:Translate]].<br />
|-<br />
|[[File:de.gif]]<br />
|Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki Mehrsprachig zu machen, dann fang doch mit [[:de:Help:Übersetzen|Help:Übersetzen]] an.<br />
|-<br />
|[[File:nl.gif]]<br />
|De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].<br />
|-<br />
|[[File:es.gif]]<br />
|La FlightGear wiki todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].<br />
|}<br />
<br />
== Community news ==<br />
=== FlightGear on YouTube ===<br />
You can stay updated with FlightGear news, updates and tutorials by visiting and subscribing to [http://www.youtube.com/user/osjcag osjcag's] channel on YouTube.<br />
<br />
=== New tutorials and screencasts ===<br />
<br />
=== FlightGear &diams; Cross-Country Tutorial II &diams; a VFR guide ===<br />
[[File:Coverwiki2.jpg|250px|thumb|left]]<br />
<br /> <br /> <br /> <br />It's almost been a year since the first release of Cross-Country Tutorial II.<br /><br />
Now with '''version three point zero''' the document is better than ever in many aspects.<br /> <br /><br />
Go to the respective FG Forum thread: http://forum.flightgear.org/viewtopic.php?f=72&t=19600 where you can: <br /> <br />
*download this tutorial <br />
**find out more about it <br />
***'''post your comments and suggestions'''<br />
<br /> <br />coming up soon is the X-Country 2's own wiki page!<br />
<br /> <br /> <br /> <br /> <br /> <br /><br />
=== Forum news ===<br />
=== Multiplayer ===<br />
=== Virtual airlines ===<br />
=== FlightGear events ===<br />
<br />
== Useful links ==<br />
== And finally ... ==<br />
=== Contributing ===<br />
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
To learn more about how the project works, please see [http://flightgear.org/forums/viewtopic.php?f=42&t=15267#p149971 this short essay] written by Thorsten, for a more detailed article see [[How the FlightGear project works]].<br />
<br />
=== YASim looking for a new maintainer ===<br />
<br />
<br />
{{cquote|There are some pending merge requests to add some Yasim features, but we have an issue that since none of the current C++ developers own, or are experts in Yasim, we're reluctant to be the person who merges such changes, and potentially introduces subtle regressions.<br />
<br />
Obviously this is chicken-and-egg, since no one can become expert enough in the code to become a maintainer :)<br />
<br />
So, I'm more than happy to apply patches *providing* I can be convinced they are sane+reasonable from a pure code perspective (happy to help with that, too, <br />
if people are new to C++), and providing we have some assurance that a representative sample of yasim aircraft are unchanged or improved by the patch. <br />
Suggestions for that means in practice, are most welcome!<br />
<br />
Otherwise I worry, given the nature of the solver, we'll keep optimising the solver for some aircraft, and making other existing aircraft worse - until someone tests them, and announced that they're no longer working.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23986.html <br />
|title=YASim and documentation<br />
|author=James Turner |date= Fri, 05 Oct 2012 03:54:43 -0700}}</ref>|James Turner}}<br />
<br />
{{cquote|I am still broadly happy to answer questions if posed (as long as I remember enough to come up with a meaningful answer). Just cc: me if you do, because my<br />
latencies here are measured in weeks. <br />
Bugs can always be fixed. What YASim needs is a maintainer, not really expertise per se. The latter comes from the former.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23986.html <br />
|title=YASim and documentation<br />
|author=Andy Ross |date= Fri, 05 Oct 2012 03:54:43 -0700}}</ref>|Andy Ross}}<br />
<br />
<references/><br />
<br />
<br />
=== Call for volunteers ===<br />
* The [[Target4Today]] team is looking for volunteers to help improving FlightGear's combat support<br />
<br />
=== Did you know ===<br />
<br />
[[Category:FlightGear Newsletter]]<br />
<!-- this needs to be changed after each release, so that newsletters show up in the proper category --><br />
<br />
[[Category:Changes after 2.12]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=Modeling_-_Getting_Started&diff=66312Modeling - Getting Started2014-01-09T22:12:49Z<p>Blackiris: /* Improving Models for Best FlightGear Performance */</p>
<hr />
<div>== Important Notice for Volunteers ==<br />
<br />
Developing scenery and models for use with scenery is an important and very visible contribution to Flightgear. New users of Flightgear often ask how they can contribute, and this is a good place to start. Try looking at some of the following:<br />
<br />
* We need people to go out and take good pictures of all the buildings at their local airports, build models, and create textures (that could be different people for each task).<br />
* We need people to go over paper lists and airport diagrams for countries that don't publish air navigation data free online (i.e. almost everyone but the U.S.) and fill in the blanks in our navaid and airport databases.<br />
* We need people to collect geodata to give us more accurate roads, rivers, etc., especially outside the U.S.<br />
* We need people to start modelling identifiable human-made landmarks like bridges, stadiums, and major buildings. Around the San Francisco Bay area, bridges are especially important. Once you have identified some buildings or objects you would like to have (Aircraft carriers, fuel bowsers, cars, towers, ...) you will need to check out the tools for creating and placing these objects. <br />
<br />
It would be helpful if people would model the area they are interested in. Generally contributions are going to be from Flightgear users who find scenery lacking in some area and choose to improve it. You are encouraged to research your own area for airport, navaid and scenery information, to contribute the data or dive right in to airport and scenery design.<br />
<br />
== Getting Started ==<br />
<br />
Generally one can start with a blueprint using their favorite imaging software like Gimp, Photoshop, or Paint shop pro then separate various views (front, back, etc...) into greyscale jpg files. Then import them as a background for easy modelling in your favorite 3D modelling software program. <br />
<br />
=== 3D Software ===<br />
To begin, you will need to create models in a 3d modeling appliction. Three popular ones are AC3D, Blender and SketchUp. FlightGear can display models in several formats, any format supported by [[PLIB]] is acceptable. AC3D is the most popular format for including scenery in Flightgear. Most or all of the default scenery bundled with a Flightgear release are in AC3D format.<br />
<br />
If you do not have AC3D, Blender offers many import and export tools. See the Blender website for further information.<br />
<br />
==== [[AC3D]] ====<br />
Flightgear uses the ac3d model format for objects such as buildings. To create a model, you will need one of two modelling packages. Either go directly to [http://www.ac3d.org AC3D] itself, or use [http://www.blender.org Blender] and then convert via a Python script (see below). AC3D seems to be a much easier program to learn, while still being very powerful. The downside is that you have to buy a licence to get more than 14 days use.<br />
<br />
* [http://wine.techlab.info/AC3D_Tutorials/ AC3D Modeling Tutorials]<br />
<br />
==== [[Blender]] ====<br />
[http://www.blender.org Blender] is more difficult to learn to use, since it is not quite as intuitive and is far more powerful. However it is GPL'd, and there are lots of tutorials to help with learning.<br />
<br />
* [http://wiki.blender.org Blender Manual]<br />
* [http://blenderartists.org/forum/ Excellent forum for discussing Blender issues]<br />
<br />
==== SketchUp ====<br />
{{Main article|Modeling - SketchUp}}<br />
<br />
SketchUp (http://sketchup.google.com) is the easiest to use of these three programs. But the results are very nice and professional. I recommend SketchUp for users who are not really good at difficult computer programs.<br />
<br />
==== [[Wings 3D]] ====<br />
{{Main article|Modeling - Wings 3D}}<br />
<br />
Wings 3D (http://www.wings3d.com/) is another 3D modeling program, and is free open source software.<br />
<br />
=== Placing Objects on Scenery ===<br />
There are several ways of doing this. The most direct way is to simply [[Adding shared models manually|add the required data by hand]]. <br />
<br />
[[File:Placing objects with UFO html 439816e9.jpg|thumb|270px|The model adjustment dialog of the [[UFO]]]]<br />
The easiest way is to use the [[Placing 3D Objects with the UFO|UFO's object placement feature]] (in version 9.10 or higher). When operating the UFO, left-clicking the mouse anywhere on the ground will place an object, and pressing space-up or down will cycle through the models. Coordinates of placed models can then be dumped to the terminal or written to a configuration file. <br />
<br />
Another method is to use [[FlightGear Scenery Designer]] ([http://fgsd.sourceforge.net/ Project Site]). After setting the paths to your scenery data, simply load up the area where you want to place the object. Load your .ac format model, and right click on the desired spot to place your model there. Export the modifed scenery to save it, rerun Flightgear and your model should be there.<br />
<br />
=== Finding, Creating, or Using Textures ===<br />
Models in Flightgear use textures with PNG format.<br />
<br />
Most image editors support editing PNG files, like [[THE GIMP]], Corel Paintshop Pro, Adobe Photoshop, etc.<br />
<br />
The old SGI rgb format (.rgb extension) is no longer supported. (see http://scenemodels.flightgear.org/)<br />
<br />
Once you have made your model building, you will want to apply some textures to it, so it looks as realistic as possible. This is possibly one of the hardest areas, as a good model with bad textures will still look bad. Since Flightgear and the scenery data are all released under the GPL, any textures that you use must also be able to be released under this license. This will probably prevent you from just using anything you come across on the net, unless it is already under the GPL. It is quite common for people to state that their pictures or textures are free. Since Flightgear can be sold for profit, and is released on Linux distributions that are sold, check that there are no clauses stating that the item can not be sold or used for commercial use.<br />
<br />
=== Generation of textured light objects in Blender ===<br />
<br />
{| style="margin-top:0.1em; margin-bottom:0.1em; margin-left:2em; padding:2px; font-size:95%; text-align:left; background: transparent;"<br />
|-<br />
| [[File:1rightarrow.png|15px]] ''See http://members.aon.at/mfranz/flightgear/blender-textured-lights.html for the main article about this subject.''<br />
|}<br />
<br />
== Problems and Solutions ==<br />
* [[3D Model Rotates Around Nose]]<br />
* [[Howto: Configure views in FlightGear]]<br />
* [[Howto: Decrease the number of faces|Decrease the number of faces]]<br />
<br />
== Improving Models for Best FlightGear Performance ==<br />
[[File:Motor.jpg|thumb|270px|Using Multiple Models with varied detailing]]<br />
[[File:Singlesided_blender.jpg|thumb|270px|To set faces to Singlesided (Blender), deselect the Doublesided button]]<br />
===Mesh===<br />
* Use a single mesh so far as possible, for example, combine all the parts of a building into one Object. Only have the separate objects if you need them for an animation or parts that use a transparent texture. (any object using more then one texture is anyway spitted by the rendering engine in separate objects)<br />
* Delete unseen faces (such as those under the model hidden by the ground, or face inside the model if there are)<br />
* Remove "line faces" which are faces whose points are in the same line<br />
* Don't forget to remove double vertices<br />
<br />
===SingleSided/DoubleSided===<br />
* Set all the faces of the model to SingleSided. DoubleSided faces are very expensive to render properly. If a face needs to be displayed from every view angle use two faces with opposite normals rather than a Doublesided one ( the overhead from the extra geometry is far lower than the overhead of doublesided faces)<br />
*<strike> However, if a face need to be displayed for every view angle, use two-sided display instead of two opposite faces with one-sided</strike><br />
<br />
===Textures/Materials===<br />
* Use Materials on Objects instead of textures where possible.<br />
* Avoid mixing textured and untextured geometry in the same model. Build the coloring into the texture map instead.<br />
* Textures must be a power of two (or it will be resized at loading...)<br />
* Avoid using big textures: 512x512 maximum is mostly enough for most models<br />
* Use a single texture. However, if your model absolutely needs alpha texture and another part of the model is opaque, you should use two textures: one with alpha and the other without.<br />
* Don't use alpha in texture when it is not needed<br />
<br />
===LOD===<br />
* If a model has to be detailed to a High Degree, use multiple Objects with different levels of detailing, and switch between them based on LOD. (very small models, such as fences can even be not displayed when they are far)<br />
<br />
===Other===<br />
* Textures, transparency, .xml included sub-models : The things that kill frame rate in FlightGear. Try to avoid them.<br />
* Also avoid smooth shading when possible (only for curved surface if it really has an impact on model quality).<br />
<br />
== Resources ==<br />
* [[Aircraft Information Resources]] <br />
* [[Modeling Resources]]<br />
<br />
{{3d}}<br />
<br />
[[Category:Modeling]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=Modeling_-_Getting_Started&diff=66302Modeling - Getting Started2014-01-08T22:36:25Z<p>Blackiris: /* Improving Models for Best FlightGear Performance */</p>
<hr />
<div>== Important Notice for Volunteers ==<br />
<br />
Developing scenery and models for use with scenery is an important and very visible contribution to Flightgear. New users of Flightgear often ask how they can contribute, and this is a good place to start. Try looking at some of the following:<br />
<br />
* We need people to go out and take good pictures of all the buildings at their local airports, build models, and create textures (that could be different people for each task).<br />
* We need people to go over paper lists and airport diagrams for countries that don't publish air navigation data free online (i.e. almost everyone but the U.S.) and fill in the blanks in our navaid and airport databases.<br />
* We need people to collect geodata to give us more accurate roads, rivers, etc., especially outside the U.S.<br />
* We need people to start modelling identifiable human-made landmarks like bridges, stadiums, and major buildings. Around the San Francisco Bay area, bridges are especially important. Once you have identified some buildings or objects you would like to have (Aircraft carriers, fuel bowsers, cars, towers, ...) you will need to check out the tools for creating and placing these objects. <br />
<br />
It would be helpful if people would model the area they are interested in. Generally contributions are going to be from Flightgear users who find scenery lacking in some area and choose to improve it. You are encouraged to research your own area for airport, navaid and scenery information, to contribute the data or dive right in to airport and scenery design.<br />
<br />
== Getting Started ==<br />
<br />
Generally one can start with a blueprint using their favorite imaging software like Gimp, Photoshop, or Paint shop pro then separate various views (front, back, etc...) into greyscale jpg files. Then import them as a background for easy modelling in your favorite 3D modelling software program. <br />
<br />
=== 3D Software ===<br />
To begin, you will need to create models in a 3d modeling appliction. Three popular ones are AC3D, Blender and SketchUp. FlightGear can display models in several formats, any format supported by [[PLIB]] is acceptable. AC3D is the most popular format for including scenery in Flightgear. Most or all of the default scenery bundled with a Flightgear release are in AC3D format.<br />
<br />
If you do not have AC3D, Blender offers many import and export tools. See the Blender website for further information.<br />
<br />
==== [[AC3D]] ====<br />
Flightgear uses the ac3d model format for objects such as buildings. To create a model, you will need one of two modelling packages. Either go directly to [http://www.ac3d.org AC3D] itself, or use [http://www.blender.org Blender] and then convert via a Python script (see below). AC3D seems to be a much easier program to learn, while still being very powerful. The downside is that you have to buy a licence to get more than 14 days use.<br />
<br />
* [http://wine.techlab.info/AC3D_Tutorials/ AC3D Modeling Tutorials]<br />
<br />
==== [[Blender]] ====<br />
[http://www.blender.org Blender] is more difficult to learn to use, since it is not quite as intuitive and is far more powerful. However it is GPL'd, and there are lots of tutorials to help with learning.<br />
<br />
* [http://wiki.blender.org Blender Manual]<br />
* [http://blenderartists.org/forum/ Excellent forum for discussing Blender issues]<br />
<br />
==== SketchUp ====<br />
{{Main article|Modeling - SketchUp}}<br />
<br />
SketchUp (http://sketchup.google.com) is the easiest to use of these three programs. But the results are very nice and professional. I recommend SketchUp for users who are not really good at difficult computer programs.<br />
<br />
==== [[Wings 3D]] ====<br />
{{Main article|Modeling - Wings 3D}}<br />
<br />
Wings 3D (http://www.wings3d.com/) is another 3D modeling program, and is free open source software.<br />
<br />
=== Placing Objects on Scenery ===<br />
There are several ways of doing this. The most direct way is to simply [[Adding shared models manually|add the required data by hand]]. <br />
<br />
[[File:Placing objects with UFO html 439816e9.jpg|thumb|270px|The model adjustment dialog of the [[UFO]]]]<br />
The easiest way is to use the [[Placing 3D Objects with the UFO|UFO's object placement feature]] (in version 9.10 or higher). When operating the UFO, left-clicking the mouse anywhere on the ground will place an object, and pressing space-up or down will cycle through the models. Coordinates of placed models can then be dumped to the terminal or written to a configuration file. <br />
<br />
Another method is to use [[FlightGear Scenery Designer]] ([http://fgsd.sourceforge.net/ Project Site]). After setting the paths to your scenery data, simply load up the area where you want to place the object. Load your .ac format model, and right click on the desired spot to place your model there. Export the modifed scenery to save it, rerun Flightgear and your model should be there.<br />
<br />
=== Finding, Creating, or Using Textures ===<br />
Models in Flightgear use textures with PNG format.<br />
<br />
Most image editors support editing PNG files, like [[THE GIMP]], Corel Paintshop Pro, Adobe Photoshop, etc.<br />
<br />
The old SGI rgb format (.rgb extension) is no longer supported. (see http://scenemodels.flightgear.org/)<br />
<br />
Once you have made your model building, you will want to apply some textures to it, so it looks as realistic as possible. This is possibly one of the hardest areas, as a good model with bad textures will still look bad. Since Flightgear and the scenery data are all released under the GPL, any textures that you use must also be able to be released under this license. This will probably prevent you from just using anything you come across on the net, unless it is already under the GPL. It is quite common for people to state that their pictures or textures are free. Since Flightgear can be sold for profit, and is released on Linux distributions that are sold, check that there are no clauses stating that the item can not be sold or used for commercial use.<br />
<br />
=== Generation of textured light objects in Blender ===<br />
<br />
{| style="margin-top:0.1em; margin-bottom:0.1em; margin-left:2em; padding:2px; font-size:95%; text-align:left; background: transparent;"<br />
|-<br />
| [[File:1rightarrow.png|15px]] ''See http://members.aon.at/mfranz/flightgear/blender-textured-lights.html for the main article about this subject.''<br />
|}<br />
<br />
== Problems and Solutions ==<br />
* [[3D Model Rotates Around Nose]]<br />
* [[Howto: Configure views in FlightGear]]<br />
* [[Howto: Decrease the number of faces|Decrease the number of faces]]<br />
<br />
== Improving Models for Best FlightGear Performance ==<br />
[[File:Motor.jpg|thumb|270px|Using Multiple Models with varied detailing]]<br />
[[File:Singlesided_blender.jpg|thumb|270px|To set faces to Singlesided (Blender), deselect the Doublesided button]]<br />
===Mesh===<br />
* Use a single mesh so far as is possible, for example, combine all the parts of a building into one Object.<br />
* Delete unseen faces (such as those under the model hidden by the ground, or face inside the model if there are)<br />
* Remove "line faces" which are faces whose points are in the same line<br />
* Don't forget to remove double vertices<br />
<br />
===SingleSided/DoubleSided===<br />
* Set all the faces of the model to SingleSided. DoubleSided faces are very expensive to render properly.<br />
* However, if a face need to be displayed for every view angle, use two-sided display instead of two opposite faces with one-sided <br />
<br />
===Textures/Materials===<br />
* Use Materials on Objects instead of textures where possible.<br />
* Avoid mixing textured and untextured geometry in the same model. Build the coloring into the texture map instead.<br />
* Textures must be a power of two (or it will be resized at loading...)<br />
* Use a single texture. However, if your model absolutely needs alpha texture and another part of the model is opaque, you can use two textures: one with alpha and the other without.<br />
* Don't use alpha in texture when it is not needed<br />
<br />
===LOD===<br />
* If a model has to be detailed to a High Degree, use multiple Objects with different levels of detailing, and switch between them based on LOD.<br />
<br />
===Other===<br />
* Textures, transparency, .xml included sub-models : The things that kill frame rate in FlightGear. Try to avoid them.<br />
* Also avoid smooth shading when possible.<br />
<br />
== Resources ==<br />
* [[Aircraft Information Resources]] <br />
* [[Modeling Resources]]<br />
<br />
{{3d}}<br />
<br />
[[Category:Modeling]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_August_2013&diff=62103FlightGear Newsletter August 20132013-08-08T18:51:21Z<p>Blackiris: /* Scenery corner */</p>
<hr />
<div>{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
''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 news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter. Core developers are encouraged to add news about their latest work to the newsletter's development section and [[Next Changelog|the changelog of the upcoming release]]. At the end of each month, it's generally a good idea to get in touch with other contributors to ask them to add news about their contributions to the newsletter.''<br />
<br />
== Development news ==<br />
Note to all contributors: Please also copy your newsletter additions to the changelog for the upcoming release: [[Next Changelog]].<br />
=== Independant Ramp Marshall ===<br />
<br />
Omega95 has been working on a [[Nasal]]-based Ramp Marshall script. That was a prototype only to test the general script and the animations. He's now working on a larger system similar to the animated jetways to generalize this and make the animations independant.<br />
<br />
{{#ev:youtube | c_KEbyv_h5A}} {{#ev:youtube | Hz4WU8nsdls}}<br />
<br />
Continue reading at [[Ramp Marshall]]...<br />
<br />
=== Random Buildings ===<br />
<!-- These are currently just a bunch of placeholders for the latest projects (as of 08/2012) --><br />
<br />
=== Project Rembrandt ===<br />
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]].<br />
<br />
=== Canvas System ===<br />
<!--additions should also be added to:http://wiki.flightgear.org/Changelog_3.0.0#Some_of_the_major_changes_include: --><br />
<br />
=== High Level Architecture ===<br />
=== FlightGear an Android ===<br />
<br />
=== Usability Improvements ===<br />
<br />
=== Mailing list digest ===<br />
<br />
(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)<br />
<br />
=== Forum digest ===<br />
<br />
=== Git digest ===<br />
<br />
=== Getting involved as a programmer ===<br />
Unfortunately, most of the active FG developers are currently very overstretched in terms of the areas that they have ownership of, which is affecting how much can actually be done. Fundamentally we need more core devs.<br />
<br />
If you are interested in contributing as a core developer, please see [[Howto:Start core development]].<br />
<br />
== Release ChangeLog ==<br />
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.<br />
<br />
== Interview with a contributor (NAME) ==<br />
''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.''<br />
<br />
* How long have you been involved in FlightGear?<br />
* What are your major interests in FlightGear?<br />
* What project are you working on right now?<br />
* What do you plan on doing in the future?<br />
* Are you happy with the way the FlightGear project is going?<br />
* What do you enjoy most about developing for FlightGear?<br />
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?<br />
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?<br />
<br />
More questions are being collected here: [[Interview questions]].<br />
<br />
Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX <br />
<br />
== Translators required ==<br />
{|<br />
|[[File:en.gif]]<br />
|The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multi-language then start at [[Help:Translate]].<br />
|-<br />
|[[File:de.gif]]<br />
|Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki Mehrsprachig zu machen, dann fang doch mit [[:de:Help:Übersetzen|Help:Übersetzen]] an.<br />
|-<br />
|[[File:nl.gif]]<br />
|De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].<br />
|-<br />
|[[File:es.gif]]<br />
|La FlightGear wiki todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].<br />
|}<br />
<br />
== Nasal for newbies ==<br />
<br />
== New software tools and projects ==<br />
<br />
== FlightGear addons and mods ==<br />
<br />
== In the hangar ==<br />
<br />
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.<br />
<br />
=== New aircraft ===<br />
<br />
=== Updated aircraft ===<br />
<br />
=== Liveries ===<br />
<br />
== Scenery corner ==<br />
=== Scenery model update forms ===<br />
After a few (but long) months of waiting, it is finally possible to update the existing 3D scenery models using the webforms! The form can be found there: [http://scenemodels.flightgear.org/submission/static/index_model_update.php Update a model]<br />
<br />
This means that from now, '''you are able to improve the models''', such as adding details, fixing wrong scale, or even making them lighter and '''improve FlightGear performance'''! Some models indeed had some unseen vertices/faces/meshes or had useless two-sided faces, and fixing this mistakes won't affect overall details '''BUT''' will certainly improve performance!<br />
<br />
Your changes will then be updated to Terrasync.<br />
<br />
=== Airports ===<br />
<br />
== Aircraft of the month ==<br />
== Airport of the month ==<br />
== Screenshot of the month ==<br />
<br />
== Suggested flights ==<br />
== Aircraft reviews ==<br />
<br />
== Wiki updates ==<br />
===New articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
</DynamicArticleList><br />
===New aircraft articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
categoryRoot=Aircraft<br />
</DynamicArticleList><br />
===Most popular newsletters===<br />
<DynamicArticleList><br />
type=hot<br />
count=5<br />
categoryRoot=FlightGear Newsletter<br />
</DynamicArticleList><br />
<br />
== Community news ==<br />
=== FlightGear on YouTube ===<br />
<br />
=== New tutorials and screencasts ===<br />
=== Forum news ===<br />
=== Multiplayer ===<br />
=== Virtual airlines ===<br />
=== FlightGear events ===<br />
<br />
== Useful links ==<br />
== And finally ... ==<br />
=== Contributing ===<br />
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
To learn more about how the project works, please see [http://flightgear.org/forums/viewtopic.php?f=42&t=15267#p149971 this short essay] written by Thorsten, for a more detailed article see [[How the FlightGear project works]].<br />
<br />
=== Call for volunteers ===<br />
* The [[Flightgear On Android]] team is looking for testers<br />
* The [[Target4Today]] team is looking for volunteers to help improving FlightGear's combat support<br />
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.<br />
<br />
=== Did you know ===<br />
<br />
[[Category:FlightGear Newsletter]]<br />
<!-- this needs to be changed after each release, so that newsletters show up in the proper category --><br />
<br />
[[Category:Changes after 2.10]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_March_2013&diff=58869FlightGear Newsletter March 20132013-03-22T19:42:51Z<p>Blackiris: Scenery updates</p>
<hr />
<div>{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
''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 news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter. Core developers are encouraged to add news about their latest work to the newsletter's development section and the changelog of the upcoming release.''<br />
<br />
== Development news ==<br />
Note to all contributors: Please also copy your newsletter additions to the changelog of the upcoming release: [[Changelog_3.0.0]].<br />
<br />
=== Random Buildings ===<br />
<!-- These are currently just a bunch of placeholders for the latest projects (as of 08/2012) --><br />
<br />
=== Project Rembrandt ===<br />
=== Canvas System ===<br />
<!--additions should also be added to:http://wiki.flightgear.org/Changelog_3.0.0#Some_of_the_major_changes_include: --><br />
<br />
=== High Level Architecture ===<br />
=== FlightGear an Android ===<br />
<br />
=== Usability Improvements ===<br />
<br />
=== Mailing list digest ===<br />
<br />
(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)<br />
<br />
=== Forum digest ===<br />
<br />
=== Git digest ===<br />
<br />
=== Getting involved as a programmer ===<br />
<br />
Please see [[Howto:Start core development]]<br />
<br />
== Release ChangeLog ==<br />
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.<br />
<br />
== Interview with a contributor James Turner ==<br />
''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.''<br />
<br />
* How long have you been involved in FlightGear?<br />
<br />
Since 2008 as an active developer, but for years before as a casual user.<br />
<br />
* What are your major interests in FlightGear?<br />
* What project are you working on right now?<br />
* What do you plan on doing in the future?<br />
* Are you happy with the way the FlightGear project is going?<br />
* What do you enjoy most about developing for FlightGear?<br />
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?<br />
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?<br />
<br />
More questions are being collected here: [[Interview questions]].<br />
<br />
Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX<br />
<br />
== Translators required ==<br />
{|<br />
|[[File:en.gif]]<br />
|The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multi-language then start at [[Help:Translate]].<br />
|-<br />
|[[File:de.gif]]<br />
|Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki Mehrsprachig zu machen, dann fang doch mit [[:de:Help:Übersetzen|Help:Übersetzen]] an.<br />
|-<br />
|[[File:nl.gif]]<br />
|De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].<br />
|-<br />
|[[File:es.gif]]<br />
|La FlightGear wiki todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].<br />
|}<br />
<br />
== Nasal for newbies ==<br />
<br />
== New software tools and projects ==<br />
<br />
== FlightGear addons and mods ==<br />
===Hollywood at the EDDF -Triangle===<br />
The regular ATC-events at the [http://www.emmerich-j.de/S1.html|"EDDF Triangle"] have been enriched by taking [http://www.emmerich-j.de/EDDF/Films/Films.html|"movies"] during each session, showing all ongoing actions from different points of views:<br />
<br /><br />
{|<br />
|-<br />
||[[File:EDDF-Triangle-OpenRadar.png|thumb|left|400px|ATC-tool "OpenRadar" in action]]<br />
||The '''First- and Main-View''' shows the “actors” on the newly designed [[OpenRadar]]. In the example you see the following “acts” in parallel:<br />
*Captain alberto (left) is just intercepting the EDDF RW07R ILS.<br />
*Captain Sbyx (center) just Takes Off from the EDDF RW07C<br />
*Captain D-Leon (right) is accurately following the SID SOBRA towards ELLX<br />
*Captain SK-407 is coming in via VOR TAU<br />
This picture shows already the now upcoming version II of OpenRadar. In that one you can define (yourself!) any [[OpenRadar:_Editing_routes|"additional markings"]] you consider needed for (your) ATC-job. In this example are added:<br />
*SID's (Standard Instrument Departures) (in green)<br />
*STAR's (Standard Terminal Arrival Routes) (in rose)<br />
*Holding Patterns (e.g. over RID)<br />
*Hazardous areas in red, e.g. to the north of EDDF where the minimum altitude needs to be 4000/5000 ft, while the airport is on ~400 ft.<br />
For a complete guide to OpenRadar see the [[OpenRadarGuide]]<br />
|-<br />
||[[File:EDDF-Triangle MPmap Overview.png|thumb|left|400px|Add caption here]]<br />
||The '''Second View''' shows the actions within the whole “Triangle Area”. Here you see as an example:<br />
*in the center the “Camera Location” at EDDF (Frankfurt)<br />
*at the left many targets are getting ready at ELLX (Luxembourg)<br />
*also at the bottom at EDDS (Stuttgart) several targets are getting ready <br />
*the traffic from/to the right is heading for EDDP/EDDC (Leipzig-Halle/Dresden), etc.<br />
For this view we use the general [[MPmap]] Utility. It is just for keeping an eye on the overall situation for estimating the upcoming workload.<br />
|-<br />
||[[File:EDDF-Triangle Landing- Closeup.png|thumb|left|400px|Add caption here]]<br />
||And last but not least the '''Third View''' shows CloseUp's onto the most impressive scenes of the leading actors, e.g. at TouchDown, TakeOff, Taxiing etc. <br />
<br /><br /><br />
For this “view through field-glasses” we use the ATC-ML tool. You find that in the list of available models for FlighGear: http://ftp.linux.kiev.ua/pub/fgfs/Aircraft-2.10/ATC-ML_20120519.zip<br />
<br /><br /><br />
''(For explanations see the README.pdf inside that Package.)'' <br />
|}<br />
With these movies (see '''''http://www.emmerich-j.de/EDDF/Films/Films.html''''') we try to initiate a little more understanding between pilots to pilots and ATC's - and thus improve all our performances. We especially hope to increase the sensibility for<br />
*it makes sense (and is even fun!) to “fly controlled” when in an Multiplayer environment<br />
*everybody notices “nobody is perfect” (at least not always!)<br />
*we do not need to laugh about or insult others when <small>''(is “bullshit happens” allowed?)''</small> things go wrong – we always may “smile” about the others – '''and''' about ourselves!<br />
*and most important: Although we do not just “play” but try to “simulate” → we should have fun together!<br />
<br /><br />
'''''A word to all pilots, captains, and trainees:'''''<br />
<br /><br />
Please don't be afraid to try it – there are no major prerequisites needed, BUT:<br />
*You should be able to control your model in regards to altitude, direction, speed, landing, starting. ATC will charge all mistakes against you – ATC will not accept excuses like “the autopilot did...” ''(nor will your <small>(dead?)</small> passengers accept such excuses)!)''<br />
*You must communicate with ATC and follow his advise ''(you may request a deviation from the advise – but you must follow the advise until the deviation is granted)''<br />
*We urge you to use [[FGCOM]] – but also accept communication by MPchat. You always should have an eye on the MPchat-messages, in case a FGCOM communication cannot be established!<br />
*You should have a layout of the airport(s) – especially one for the more complex EDDF (see http://www.emmerich-j.de/EDDF/EDDF-Layout.png) <br />
<br /><br />
'''''Some technicalities:'''''<br />
<br /><br />
You will notice that the films are not in "Best of Quality" - but they are in full HDTV (1920*1072 px), so that you can read all text-informations! Considering that such a format in good HDTV-Quality would need a size from more than 5GB and above → we assume that such a high Quality is not needed - it is just for us to judge and improve ourselves (pilots and ATC) - not to win an Oscar! Also we will not edit - because that would add a huge amount of daily workload – which is not really required for a “working tool”.<br />
<br /><br /><br />
'''The movies''' <br />
<br /><br />
*are recorded on Linux/Ubuntu with RecordMyDesktop (Video/Sound Quality ~50, FpS=4, “Encode on the Fly”)<br />
*are tested on Linux/Ubuntu with Firefox ver.18 and on Windows XP with InternetExplorer 8<br />
*show the following Colors for the targets:<br />
**blue = under EDDF-ATC control<br />
**yellow = must be watched closely<br />
**green = no concern<br />
**white = selected<br />
**gray/invisible = neglected or MP-timed out<br />
<br />
You achieve a “Best Quality Viewing” if you use the "Full Screen" option of your browser (or VLC or MoviePlayer, etc.)!<br />
<br />
== In the hangar ==<br />
<br />
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.<br />
<br />
=== New aircraft ===<br />
<br />
=== Updated aircraft ===<br />
<br />
=== Liveries ===<br />
<br />
== Scenery corner ==<br />
The 3000th model has been submitted this month, two years after reaching 2000 models in January 2011! Help us to make the 4000th model a reality!<br />
=== Airports ===<br />
Works have been added to Le Havre - Octeville Airport (LFOH) airport with many hangars and building, and same for Hong Kong International Airport (VHHH).<br />
<br />
== Aircraft of the month ==<br />
{{#ev:youtube|A3UrVd_nJ_w}}<br />
<br />
== Airport of the month ==<br />
== Screenshot of the month ==<br />
<br />
== Suggested flights ==<br />
== Aircraft reviews ==<br />
<br />
== Wiki updates ==<br />
===New articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
</DynamicArticleList><br />
===New aircraft articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
categoryRoot=Aircraft<br />
</DynamicArticleList><br />
===Most popular newsletters===<br />
<DynamicArticleList><br />
type=hot<br />
count=5<br />
categoryRoot=FlightGear Newsletter<br />
</DynamicArticleList><br />
<br />
== Community news ==<br />
=== FlightGear on YouTube ===<br />
<br />
=== New tutorials and screencasts ===<br />
=== Forum news ===<br />
=== Multiplayer ===<br />
===Virtual Air Traffc Organization===<br />
The newly founded [[Virtual Air Traffic Organization]] promises to create a different dimension to the way FlightGear multiplayer events were organized so far and to also provide more realism within ATC and pilot operations.<br />
<br />
vATO is a complete overhaul and re-brand of Air H5. Air H5 was an organization in FlightGear which consisted of two main event-based virtual airlines, Eurfly which operates in Europe and Fremont which operates in North America. Air H5 was originally founded by Rick Ace in July 2010 and its activity had to end after a few months of success. Air H5 was then reorganized in May 2012 but due to the low standards and lack of pilots and ATCs, it ended its operations in January 2013.<br />
<br />
vATO's new goal is to increase the standards even more and create the best and most realistic multiplayer event experience FlightGear has to offer.<br />
<br />
The new organization is currently seeking for ATCs, pilots and staff members. If you are interested, fill out the registration form on [http://vatofg.x10.mx/ our website.]<br />
<br />
{{#ev:youtube|auj_eA-dTTs}}<br />
<br />
=== Virtual airlines ===<br />
=== FlightGear events ===<br />
<br />
== Useful links ==<br />
== And finally ... ==<br />
=== Contributing ===<br />
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
To learn more about how the project works, please see [http://flightgear.org/forums/viewtopic.php?f=42&t=15267#p149971 this short essay] written by Thorsten, for a more detailed article see [[How the FlightGear project works]].<br />
<br />
=== Call for volunteers ===<br />
* The [[Flightgear On Android]] team is looking for testers<br />
* The [[Target4Today]] team is looking for volunteers to help improving FlightGear's combat support<br />
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.<br />
<br />
=== Did you know ===<br />
<br />
[[Category:FlightGear Newsletter|2013 03]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=TerraGear_GUI&diff=58562TerraGear GUI2013-03-10T14:35:09Z<p>Blackiris: /* Airports */</p>
<hr />
<div>{{Infobox Software<br />
| title = TerraGear GUI<br />
| image = TerraGear GUI download San Francisco.png<br />
| alt = The download page with the San Francisco bay area selected.<br />
| developedby = Gijs de Rooy (original by Alex Park)<br />
| initialrelease = March 24, 2009 (original)<br>March 27, 2010<br />
| latestrelease = 0.9.x (2012)<br />
| writtenin = C++ (Qt)<br />
| os = Windows, Linux, Mac OS X<br />
| website = http://gitorious.org/fgscenery/terrageargui/<br />
}}<br />
The '''GUI''' tool for '''[[TerraGear]]''' allows people to create [[scenery]] for [[FlightGear]] without using commandlines.<br />
<br />
== Obtaining the GUI ==<br />
You can either build the GUI [http://gitorious.org/fgscenery/terrageargui/ from source], or download a pre-compiled build:<br />
* [http://liveries.flightgear.org/terrageargui/ Windows builds]<br />
Please note that you need to download/compile a recent version of [[TerraGear]] as well.<br />
<br />
==== For GNU/Linux users ====<br />
# Grab the sources and store it where you want:<br/><pre>git clone git://gitorious.org/fgscenery/terrageargui.git</pre><br />
# Then go in the source:<br/><pre>cd terrageargui</pre><br />
# Create a build dir:<br/><pre>mkdir build && cd build</pre><br />
# Now build it:<br/><pre>qmake .. && make</pre><br />
# You can now start it with:<br/><pre>./bin/TerraGUI</pre><br />
<br />
You're done!<br />
<br />
== Using the GUI ==<br />
The GUI exist of several tabs. For normal scenery creation, all the tabs should be gone through in the order they are arranged.<br />
<br />
=== Start ===<br />
# Set the TerraGear directory, in which you'll find the subdirectories bin/ and share/. TerraGear must be downloaded/build seperatly from the GUI!<br />
# Set the project's directory. In this directory, all project related stuff will be stored throughout the process. You best choose an empty directory specific to your project.<br />
# Set your FlightGear's root ([[$FG_ROOT]]). This is used to retrieve the list of available terrain materials.<br />
<br />
=== Download ===<br />
Specify boundaries in the boxes on the left, or select an area on the map. Next select a source to download shapefiles for that area. Note that OpenStreetMap only includes line date (roads, rivers), so you'll need some polygon data for the actual terrain. Both [[World Custom Scenery Project|Custom Scenery]] and [[CORINE]] (only Europe) provide that. The GUI downloads and unpacks the package to your <tt>{project's directory}/data/</tt>.<br />
<br />
Alternatively you can download shapefiles from [http://mapserver.flightgear.org/download.psp the mapserver by hand]. Unpack the downloaded file(s) to your <tt>{project's directory}/data/</tt>.<br />
<br />
==== Elevation data ====<br />
Elevation files are optional, but of course required to generate scenery with elevation offsets (even flat countries like the Netherlands need elevation data, since no country is completely at sealevel. Simply select a data source and then click the button to download the HGT files that span your specified area. The original source is usgs.gov, but a cleaned variant of the same data is available from fgx.ch (see [http://downloads.fgx.ch/geodata/data/srtm/README.txt the readme] for more information). The data will be saved in in <tt>{project's directory}/data/SRTM-3</tt>. <br />
<br />
===== By hand =====<br />
[[File:HGT tiles example.png|thumb|An example of HGT file tiles.]]<br />
Downloading tiles by hand is somewhat tricky. If your scenery has a boundary of:<br />
{| class="wikitable"<br />
!<br />
! Min<br />
! max<br />
|-<br />
! Latitude<br />
| 33<br />
| 37<br />
|-<br />
! Longitude<br />
| -2<br />
| 2<br />
|}<br />
The GUI would display the range as <tt>N33W002-N37E002</tt>. This means you have to download all tiles in that range, which are all the tiles as shown in the image on the right. Unpack the downloaded elevation file(s) in <tt>{project's directory}/data/SRTM-3</tt>.<br />
<br />
If you don't know how to find the boundaries range you can use Google Earth with this KMZ file : [http://clemaez.fr/flightgear/grid_1_degree.kmz grid_1_degree.kmz]<br />
# Download KMZ file above<br />
# Open it with Google Earth and active it (if not yet active). A lot of red lines should appears<br />
# Zoom where you want know the boundaries range<br />
# Click on the bottom left boundary wanted and report the displayed value in TerraGear GUI. (i.e: if Google Earth value is "W9_N42", report Minimum Latitude value "42" and Minimum Longitude value "-9")<br />
# Click on the top right boundary wanted and report the displayed value in TerraGear GUI. (i.e: if Google Earth value is "E6_N45", report Maximum Latitude value "45" and Maximum Longitude value "6")<br />
<br />
=== Elevation ===<br />
This will convert the .hgt.zip files (that you have downloaded earlier) into a form that TerraGear can read. Simply select the directory in which you placed the elevation downloads (probably <tt>{project's directory}/data/SRTM-3</tt>). Make sure you do set the correct resolution! For the USA this can be 1 arcsec, while the rest of the world is provided in 3 arcsec resolution.<br />
<br />
=== Airports ===<br />
What is scenery without airports in a flight simulator? If your area does not contain any airports, you can skip this part and continue with [[#ogr-decode|ogr-decode]].<br />
<br />
You can do two things now:<br />
*'''Already-made airports:''' use FlightGear's <tt>apt.dat.gz</tt> file, which is usually in <tt>[[$FG ROOT]]/Airports/</tt>.<br />
*'''Home-made airports:''' if you created an airport in [[TaxiDraw]] or [[WorldEditor]], use the .dat file that you exported.<br />
<br />
Use the button to browse to the .dat file of your choice. Select the format of your .dat file from the dropdown. TaxiDraw created 810 format, while WorldEditor does the 850 format. Apt.dat.gz packaged with FlightGear is currently still in the 810 format. You can find 850 format data in http://data.x-plane.com.<br />
<br />
* '''All airports in area''' generates all the airports within the boundaries as set on the start tab.<br />
* '''Single airport''' to generate the scenery for a specific airport. Enter the ICAO code into the field. <br />
* '''Single tile''' only processes airports that are located on the given tileid.<br />
* '''All airports in apt.dat''' the tool will run through the entire apt.dat file, which can take a long (!) time when using the default apt.dat from FlightGear.<br />
<br />
=== Materials ===<br />
Now we need to decode the shapefiles into TerraGear format, which we do with OGR Decode. After clicking the "Retrieve shapefiles" button, the list will be populated with the shapefiles from your project's data directory. The GUI will try to assign fitting materials. If a shapefile has no material, you'll need to assign it by hand. Each single shapefile must have a material.<br />
<br />
You can delete shapefiles from the list by double-clicking on them. A single click on a material will allow you to edit it; to create custom materials that are not (yet) in materials.xml (do note that FlightGear will apply the default material to those landclasses, untill you create the material in materials.xml!). <br />
<br />
Line width is only used on line-data (like roads, rivers and railroads). If you leave the line width fields empty, a default width of 10 meters is used.<br />
<br />
=== Construct ===<br />
[[Image:TerraGearGUI.png|thumb|270px|The construction page.]]<br />
'''Note: with recent TerraGear builds, it is required to add the used material-names to the default_priorities.txt file.'''<br />
<br />
The tg-construct tool brings all your gathered data together, throws it in a washing machine and spits it out the otherside in a format ready for use with FlightGear. Click the "Update list" button to populate the field with all decoded shapefiles. In the list you select all types that you'd like to include in your scenery.<br />
<br />
After clicking the "Generate scenery" button, it may take a long time for TerraGear to finish. Depending on the size of the area you are creating the scenery for and the level of detail in your shapefiles. Simple and small sceneries will take a couple of minutes, where larger, more detailed areas can take over an hour! So trying new things on small areas first will save you a lot of time.<br />
<br />
=== Running the scenery ===<br />
The folders and files in your project's <tt>output/</tt> directory are ready to use as scenery. You can set the [[$FG_SCENERY|scenery path]] of FlightGear to this directory to check if the scenery is generated correctly. <br />
<br />
== GUI development ==<br />
The current source code can be retrieved [http://gitorious.org/fgscenery/terrageargui/ from Gitorious].<br />
<br />
Feel free to add feature requests and/or bug reports to this page. Anyone interested in helping is invited to contact Gijs at the forum.<br />
<br />
=== Requested features ===<br />
* Multi-threading, so the GUI doesn't freeze when running a process.<br />
<br />
== External link ==<br />
* [http://www.flightgear.org/forums/viewtopic.php?f=5&t=7485 Forum topic]<br />
<br />
[[Category:Scenery enhancement]]<br />
[[Category:Software]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_February_2013&diff=58371FlightGear Newsletter February 20132013-03-02T14:11:41Z<p>Blackiris: Update to scenery models</p>
<hr />
<div>This is a template for future [[FlightGear Newsletter|newsletters]], please feel free to edit/improve!<br />
<br />
{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
''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 news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter. Core developers are encouraged to add news about their latest work to the newsletter's development section and the changelog of the upcoming release.''<br />
<br />
== FlightGear 2.10 ==<br />
<!-- placeholder --><br />
{{#ev:youtube|MZVCmHgAX6Y}} <br />
<br />
== Development news ==<br />
Note to all contributors: Please also copy your newsletter additions to the changelog of the upcoming release: [[Changelog_3.0.0]].<br />
<br />
=== Random Buildings ===<br />
<!-- These are currently just a bunch of placeholders for the latest projects (as of 08/2012) --><br />
<br />
=== Project Rembrandt ===<br />
=== Canvas System ===<br />
<!--additions should also be added to:http://wiki.flightgear.org/Changelog_3.0.0#Some_of_the_major_changes_include: --><br />
<br />
=== High Level Architecture ===<br />
=== FlightGear an Android ===<br />
<br />
=== Usability Improvements ===<br />
<br />
=== Mailing list digest ===<br />
<br />
(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)<br />
<br />
=== Forum digest ===<br />
<br />
=== Git digest ===<br />
<br />
=== Getting involved as a programmer ===<br />
<br />
Please see [[Howto:Start core development]]<br />
<br />
== Release ChangeLog ==<br />
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.<br />
<br />
== Interview with a contributor (NAME) ==<br />
''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.''<br />
<br />
* How long have you been involved in FlightGear?<br />
* What are your major interests in FlightGear?<br />
* What project are you working on right now?<br />
* What do you plan on doing in the future?<br />
* Are you happy with the way the FlightGear project is going?<br />
* What do you enjoy most about developing for FlightGear?<br />
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?<br />
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?<br />
<br />
More questions are being collected here: [[Interview questions]].<br />
<br />
Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX <br />
<br />
== Snapshot releases ==<br />
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].<br />
<br />
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].<br />
<br />
== Translators required ==<br />
{|<br />
|[[File:en.gif]]<br />
|The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multi-language then start at [[Help:Translate]].<br />
|-<br />
|[[File:de.gif]]<br />
|Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki Mehrsprachig zu machen, dann fang doch mit [[:de:Help:Übersetzen|Help:Übersetzen]] an.<br />
|-<br />
|[[File:nl.gif]]<br />
|De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].<br />
|-<br />
|[[File:es.gif]]<br />
|La FlightGear wiki todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].<br />
|}<br />
<br />
== Nasal for newbies ==<br />
<br />
== New software tools and projects ==<br />
<br />
== FlightGear addons and mods ==<br />
<br />
== In the hangar ==<br />
<br />
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.<br />
<br />
=== New aircraft ===<br />
<br />
=== Updated aircraft ===<br />
<br />
<br />
[[File:707AirportOperations.png|thumb|Airport Operations]]<br />
<br />
The Boeing 707 (versions -3J9C and 320C) continues to be updated. The most recent version includes a new livery, contrails, a more efficient navegation system, pitch trim, and a bunch of airport operations (taken mainly from the Airbus 330), including a nice fuel truck system, de-ice truck, catering, and so on.<br />
<br />
There is more information here: [[Boeing_707-320]]<br />
<br />
=== Liveries ===<br />
<br />
== Scenery corner ==<br />
The Scenery models database has seen this month an addition of about 200 new thumbnails of models, bringing the number of thumbnails left down to 152 and making the database more pleasant to browse!<br />
<br />
Moreover, there are an other addition of new models, in Leipzig, China, or Japan.<br />
<br />
=== Airports ===<br />
Dresden Airport - Germany (EDDC) was updated with many signs and hangars, and at Sion Airport - Switzerland (LSGS), a terminal was added .<br />
<br />
== Aircraft of the month ==<br />
<!-- placeholder --><br />
{{#ev:youtube|efDgpPUaTV4}}<br />
<br />
== Airport of the month ==<br />
== Screenshot of the month ==<br />
<br />
== Suggested flights ==<br />
== Aircraft reviews ==<br />
<br />
== Wiki updates ==<br />
===New articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
</DynamicArticleList><br />
===New aircraft articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
categoryRoot=Aircraft<br />
</DynamicArticleList><br />
===Most popular newsletters===<br />
<DynamicArticleList><br />
type=hot<br />
count=5<br />
categoryRoot=FlightGear Newsletter<br />
</DynamicArticleList><br />
<br />
== Community news ==<br />
=== FlightGear on YouTube ===<br />
<br />
=== New tutorials and screencasts ===<br />
=== Forum news ===<br />
=== Multiplayer ===<br />
=== Virtual airlines ===<br />
=== FlightGear events ===<br />
<br />
== Useful links ==<br />
== And finally ... ==<br />
=== Contributing ===<br />
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
To learn more about how the project works, please see [http://flightgear.org/forums/viewtopic.php?f=42&t=15267#p149971 this short essay] written by Thorsten, for a more detailed article see [[How the FlightGear project works]].<br />
<br />
=== Call for volunteers ===<br />
* The [[Flightgear On Android]] team is looking for testers<br />
* The [[Target4Today]] team is looking for volunteers to help improving FlightGear's combat support<br />
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.<br />
<br />
=== Did you know ===<br />
<br />
[[Category:FlightGear Newsletter]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_August_2012&diff=53627FlightGear Newsletter August 20122012-08-30T06:09:39Z<p>Blackiris: /* Scenery corner */</p>
<hr />
<div>{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
''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 news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''<br />
<br />
== FlightGear 2.8.0 Released ! ==<br />
<br />
The FlightGear team is very excited to announce the v2.8.0 Release is now available! I will be brief and simply post the link to the official release announcement.<br />
<br />
http://www.flightgear.org/news/flightgear-v2-8-0-released/<br />
<br />
Some of the notable changes and improvements include:<br />
<br />
Major improvements from v2.6.0 include improved AI aircraft, up to date with all the recent JSBSim flight dynamics model improvements, support for region specific textures, better random 3d buildings, better random object placement, 3d airport signage, in-sim toggling between summer and winter texture sets. The core FlightGear code now supports a flexible 2d rendering system which can be used to accurately model glass cockpit displays and other complex instrumentation. There are many new and improved aircraft to explore. A new automated system is now available for scenery submissions that automatically get rolled into the scenery distribution to be enjoyed by everyone. Version 2.8 has improved atmospheric light scatter modeling, better terrain haze, and improved 3d clouds.<br />
<br />
A very exciting new addition is “Project Rembrandt”. This is still considered “experiemental” and not enabled by default. But when you turn it on you will get real-time shadows, support for multiple light sources (landing lights, instrument lights, directional ground spotlights, even the rotating beacons illuminate the surrounding correctly.) In addition, Project Rembrandt offers a variety of other visual effects such as night vision, film grain effects, depth of field effects, lens (i.e. fisheye) distortion — all in real time.<br />
<br />
For the full change log, please see [[Changelog 2.8.0]].<br />
<br />
Enjoy!!!<br />
<br />
== Development news ==<br />
A view of FlightGear core and fgdata activity in [[Git]] since the 2.6.0 release. Each committer on fg and fg-data is shown here, as well as the part of fg where he's been working on. A big thank to all involved for making FG such a nice fireworks!<br />
{{#ev:youtube|ibO6ruzQ5gM}} {{#ev:youtube|U0Dsgx9-Pbk}}<br />
<br />
=== Project Rembrandt ===<br />
Fred's been working on some fancy new effects, especially useful for our film-making enthusiasts.<br />
<br />
The [[Project Rembrandt|Rembrandt renderer]] has a lot of potentiality when it comes to post processing effects. Indeed, the interesting property of a deferred shader is that all stages of rendering are kept into memory. Post-processing is as simple as using a filter on a camera.<br />
<br />
So currently the effects added in git are :<br />
* Night vision including amplification grain and restrained field of view,<br />
* Cinema effect including :<br />
** Vignetting,<br />
** Color shift, with Sepia as default value,<br />
** Radial distortion (barrel and pincushion distortion, with scale compensation),<br />
** Lateral chromatic aberration (purple fringing),<br />
** Film wear simulation.<br />
<br />
{|<br />
| [[File:Fgfs-rembrandt-old-timer.jpg|thumb|400px|Rembrandt old film style]]<br />
| [[File:Fgfs-rembrandt-distortion.jpg|thumb|400px|Rembrandt ordinary lens simulation]]<br />
| [[File:Fgfs-rembrandt-night-vision-2.png|thumb|400px|Rembrandt night vision simulation]]<br />
|}<br />
This won't make it for the 2.8 release but it's likely that an add-on will be available as it is contained in the data.<br />
<br />
See also :<br />
{|<br />
| {{#ev:youtube|tLZzlLjvDRQ}}<br />
| {{#ev:youtube|_Dm-Xx5tfiE}}<br />
| {{#ev:youtube|8jBvVyiq-D0}}<br />
|}<br />
<br />
=== Unified Weather GUI ===<br />
As most readers will be aware, FG supports two weather models - Basic Weather which represents METAR data directly, and Local Weather which models weather more realistically, with more variation. In 2.8.0 these were configured separately using different UIs. Stuart Buchanan and Thorsten Renk have been working on unifying the user interfaces to provide a more user-friendly and consistent interface. This work is now available in git.<br />
<br />
=== Joystick Configuration GUI ===<br />
<br />
[[File:Joystick Configuration Dialog.jpg|thumb|The new Joystick Configuration Dialog, available in git.]]<br />
<br />
A further usability enhancement has been made by Stuart Buchanan to allow configuration of joysticks through a GUI in-sim. Instead of configuring a joystick using XML, users can now change joystick bindings within the simulator - no XML knowledge required. The updated joystick configuration takes effect immediately. This work is also available in git, and should make it much easier for new users (or those with joysticks unknown to FG) to get flying.<br />
<br />
=== Canvas News ===<br />
<!--additions should also be added to:http://wiki.flightgear.org/Changelog_3.0.0#Some_of_the_major_changes_include: --><br />
<br />
As of 08/2012, the new [[Canvas]] 2D drawing system in FlightGear HEAD has now also support for:<br />
* using raster images (vector images were already supported previously)<br />
* nested canvases, where a canvas may contain images created by another canvas texture [[Howto:Using raster images and nested canvases]]<br />
* creating GUI windows (not just widgets)<br />
* handling GUI events using osgGA<br />
* multiplatfom copy/paste support using two new Nasal functions: [[Howto:Clipboard access using Nasal]]<br />
<br />
Support for nested canvases will make it possible to also load canvas textures into other canvases, so that you can, for example, easily load an instrument into a GUI dialog, or even use GUI widgets in MFD instruments, which is a feature based on real avionics, i.e. as used in modern airliners like the A320 or the 787.<br />
<br />
Nested canvases also make it possible for people to easily implement GUI tools using the Canvas system, for example a GUI instrument or panel editor can be entirely implemented in scripting space now, without touching any C++ code. Similarly, GUI widgets could also be created in a WYSIWYG-fashion, too - so that even dialog editor or full GUI builders can be built using the Canvas system.<br />
<br />
In addition, Tom has now implemented support for window stacking. Check out the demo video below, which demonstrates how "nested" canvases and window stacking works:<br />
<br />
{{#ev:youtube|llVaasTEf44}}<br />
<br />
Also, Tom is currently working on an improved event handling system with support for event-propagation based on the Javascript/DOM model. The event handling systems requires close interaction between the core system and Nasal code. Event propagation and bubbling will be supported like in the W3C DOM standard. We need eg. to be able to mark an event as handled and maybe also other things which change the behavior of the propagation.<br />
<br />
In addition, Tom has started work on some building blocks to provide basic inheritance support for canvas properties, so that styling (CSS/XSL) will be much easier.<br />
<br />
Missing features, and features currently under development, are listed at [[Canvas Widgets#Missing_.2F_Todo|Missing Canvas Features]]<br />
<br />
=== FlightGear Run-Levels ===<br />
<br />
Recently, we were talking about implementing a standalone [[FGCanvas]] client, analogous to [[FGPanel]] - in order to be able to render [[Canvas]] instruments separately, in different processes and also on different computers.<br />
<br />
However, obviously this new startup mode would not need many of the default subsystems, such as the FDM, sound, terrain etc. But, many of these subsystems are initialized in a hard coded fashion so that they cannot currently be made optional even though they may not be stricly required. Also, for a very long time, it's never been possible to fully reset FlightGear properly, this makes many things very difficult or even impossible, including the [[FGCanvas]] idea.<br />
<br />
We have now started collecting ideas on how this could be changed, by making subsystem initialization more explicit using listeners, so that SGSubsystems can be dynamically allocated and freed based on setting signal properties, so that recursive run levels can be implemented. For more information, please see [[FlightGear Run Levels]]. Feedback welcome!<br />
<br />
=== Mailing list digest ===<br />
<br />
(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)<br />
<br />
=== Forum digest ===<br />
<br />
=== '''Flightgear On Android''' ===<br />
<br />
A new developer has achieved a way to run Flightgear on Android phones. [[File:Flightgear Android Launcher.png|thumb|FOA]] <br />
<br />
The project codename will be FOA;he has done a lot of Android and C++ coding. [[File:FOA.jpg|thumb|FOA ingame]] <br />
<br />
His phone is a Samsung Galaxy Nexus and is running Android 4.04 (custom ROM but stock ROM should be OK). If your ready to test with us, please read the technical info then send a email to lacbrc@gmail.com!<br />
<br />
<br />
TECHNICAL INFO:<br />
It should have at least a 1GHz processor and decent graphics chip. Android 2.3 is a <br />
must but a rooted device is not needed but can improve performance.<br />
Not much in this, as we haven't finished it to a release yet. <br />
He tested it on a bluetooth keyboard and a wired one through usb host mode. Hope you are interested in it!<br />
<br />
The first ALPHA release is fresh out of its release, and you can read more here:<br />
http://www.flightgear.org/forums/viewtopic.php?f=18&t=16719&p=163745#p163745<br />
<br />
The FlightGear for Android Team<br />
<br />
Here is a few links:<br />
<br />
Forums:<br />
<br />
http://www.flightgear.org/forums/viewtopic.php?f=18&t=16719<br />
<br />
Website page:<br />
<br />
http://horizonflightgearhangar.yolasite.com/fg-on-android.php<br />
<br />
Wiki page:<br />
<br />
http://wiki.flightgear.org/Flightgear_On_Android<br />
<br />
=== Git digest ===<br />
<br />
=== Getting involved as a programmer ===<br />
<br />
Please see [[Howto:Start core development]]<br />
<br />
=== Translators required ===<br />
{|<br />
|[[File:en.gif]]<br />
|The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multi-language then start at [[Help:Translate]].<br />
|-<br />
|[[File:de.gif]]<br />
|Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki Mehrsprachig zu machen, dann fang doch mit [[:de:Help:Übersetzen|Help:Übersetzen]] an.<br />
|-<br />
|[[File:nl.gif]]<br />
|De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].<br />
|}<br />
<br />
== Interview with a contributor (NAME) ==<br />
''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.''<br />
<br />
* How long have you been involved in FlightGear?<br />
* What are your major interests in FlightGear?<br />
* What project are you working on right now?<br />
* What do you plan on doing in the future?<br />
* Are you happy with the way the FlightGear project is going?<br />
* What do you enjoy most about developing for FlightGear?<br />
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?<br />
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?<br />
<br />
More questions are being collected here: [[Interview questions]].<br />
<br />
Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX<br />
<br />
== Snapshot releases ==<br />
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].<br />
<br />
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].<br />
<br />
== Nasal for newbies ==<br />
<br />
== New software tools and projects ==<br />
<br />
== FlightGear addons and mods ==<br />
<br />
== In the hangar ==<br />
<br />
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.<br />
<br />
=== New hangers ===<br />
<br />
=== New aircraft ===<br />
<br />
At the request by a new user of FG, Helijah has created and made available the Yakovlev Yak 18T in his hangar and GIT.<br />
[[File:Yak18t-splash.png|thumb|Yakovlev Yak 18T]]<br />
<br />
=== Updated aircraft ===<br />
<br />
==== [[ATC-FS]] ====<br />
The Air Traffic Control tool ATC-FS got an update. The old radar screen was replaced by a radar screen, which can display fixes, navaids and ILS localizers. This new radar is resizable, so you can use your big screen more efficient. <br />
<br />
The next version is already being worked on, it will reimplement ATC-FS using the new [[Canvas]] system (scheduled for FG 3.0) so that a fully custom drawn radar screen can be created in scripting space, including custom GUI widgets (e.g. for flight strips) - without depending on any hard coded instruments or dialogs any longer.<br />
<br />
This new design will eventually even make it possible to reuse ATC-FS for other purposes, or even include it in an AWACS aircraft that is multiplayer-enabled.<br />
<br />
[[Image:ATC-FS.jpg|1000px]]<br />
<br />
==== [[Mil_Mi6]] ====<br />
The big old russian helicopter Mi-6 from the Mil design bureau has received a new update. More than a year after the last update a new structure of the Models-subfolder allows new instruments to be added much easier. Also the electrical system has been revisited and new instruments have beed added to the engineer panels. Please keep in mind that this still is a very early development version and therefore a lot of work still needs to be done. It is available from its [https://gitorious.org/mil-mi-6 gitorious-page.]<br />
<br />
=== Liveries ===<br />
<br />
== Scenery corner ==<br />
=== 3D models import webform ===<br />
The webform to import 3D models directly into the DB is in production. Now you can use this tool to send your models to the database used by Terrasync. If everything is fine and your model respects the specifications written in the foreword, then it will quickly be shipped to all FG users worldwide through [[Terrasync]]. Yet another unique feature amongst the flight simulation world held by FlightGear. Thanks to Clément, Julien, Martin, for their help & support, and all of FG users who showed interest and support in those tools.<br />
<br />
Already 100 3D models have been imported with this form in Shanghai, Berlin, Stuttgart, France and in the UK! See the statistics [http://scenemodels.flightgear.org/stats.php here]. Thanks Gijs for the new nice layout.<br />
<br />
With all the forms now working on the scenemodels website, remember you can:<br />
* add a single object (if you only have one!!). Check [http://scenemodels.flightgear.org/submission/index.php here]!<br />
* update an object (for instance, a lot of power pylons are in fact communication pylones). It's [http://scenemodels.flightgear.org/submission/shared/index_update.php here]!<br />
* delete an object (if it does not exist anymore in real life). It's [http://scenemodels.flightgear.org/submission/shared/index_delete.php here]!<br />
* run a mass object positions import (if you added a lot of objets in one place). It's [http://scenemodels.flightgear.org/submission/shared/index_mass_import.php here]!<br />
* add 3D models you created to have them imported into FG scenery via Terrasync. It's [http://scenemodels.flightgear.org/submission/static/index.php here]: they can be specific to a city (for instance: the Eiffel tower), that's what is called 'static' in the FG world, or 'shared' (a new windturbine model, for instance).<br />
<br />
Please read carefully the various forewords on the site:<br />
* all data imported has to comply with the GNU/GPL license ;<br />
* you must use the elevation format used by Terrasync to give your objects/models elevation, and [http://scenemodels.flightgear.org/contribute.php#offset an offset] if necessary, or they could be floating/sunk for most of users.<br />
<br />
We hope to see a lot of scenes not yet available via Terrasync merge into scenemodels. Nothing is now easier, especially when used in conjunction with our Mapserver!<br />
Remember that this is the strength of FG compared to other sims: everything can be in Terrasync and no need to download patches or sceneries here and there.<br />
<br />
Moreover, an Ac3D viewer using Hangar by Juan Mellado is also available for general public for those whose browser supports WebGL (such as Firefox)!<br />
<br />
=== Scenemodels cleanup and update ===<br />
A big cleanup has been done on our scenemodels database. A few thousands of duplicate objects have been removed (they were caused by mass insertion of navigation data, essentially). Nothing urgent but this makes the data in Terrasync lighter and more coherent. A script has also been launched to update the country associated with each object. While not perfect, now a lot more objects have a country!<br />
<br />
=== Airports ===<br />
<br />
== Aircraft of the month ==<br />
== Airport of the month ==<br />
== Screenshot of the month ==<br />
<br />
== Suggested flights ==<br />
<br />
The US state of Idaho is known for its remote airstrips in mountainous terrain. The [http://idahoaviation.com/idahoAirstripNetwork.php Idaho Airstrip Network] has details on many of them, including airstrip diagrams. <br />
<br />
At this time of year, it's important to take into account the temperature and altitude of the airstrips, as they combine to sap the power and lift from GA aircraft. AVWeb recently [http://www.avweb.com/avwebflash/news/stinson_crash_cockpit_video_ntsb_faa_207184-1.html highlighted] the (non-fatal) crash of a [http://en.wikipedia.org/wiki/Stinson_108 Stinson 108], which included a video taken by one of the passengers. Though the NTSB has only produced a preliminary report, it was notable that the aircraft was taking off from a grass airstrip at high altitude on a hot day and appears from the video to struggle to get airborne. The Stinson is broadly similar in performance to the c172p in our base package, and the airstrip (Bruce Meadows Airport, Idaho - U63) exists in our scenery. Those interested can try taking off using the c172p with 4 people on board (2400lbs max gross weight) and high temperatures. McCall Municipal Airport (KMYL) is 44nm away, and a good destination.<br />
<br />
== Aircraft reviews ==<br />
<br />
== Wiki updates ==<br />
===New articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
</DynamicArticleList><br />
===New aircraft articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
categoryRoot=Aircraft<br />
</DynamicArticleList><br />
===Most popular newsletters===<br />
<DynamicArticleList><br />
type=hot<br />
count=5<br />
categoryRoot=FlightGear Newsletter<br />
</DynamicArticleList><br />
<br />
== Community news ==<br />
=== FlightGear on YouTube ===<br />
Lukea made a short promo for the release of FlightGear 2.8<br />
{{#ev:youtube|X2Gq1l8A7iU}}<br />
=== New tutorials and screencasts ===<br />
=== Forum news ===<br />
=== Multiplayer ===<br />
=== Virtual airlines ===<br />
=== FlightGear events ===<br />
<br />
== Useful links ==<br />
== And finally ... ==<br />
=== Did you know? ===<br />
Did you know that the FlightGear project dates back to a discussion among a group of net citizens in 1996 resulting in a proposal written by David Murr? The original proposal is still available<br />
from the FlightGear website and can be found [http://www.flightgear.org/proposal-3.0.1 on the FlightGear website]. Read it, you'll learn a lot about FlightGears' roots which still lead the project spirit.<br />
<br />
=== Contributing ===<br />
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
=== Call for volunteers ===<br />
* The [http://horizonflightgearhangar.yolasite.com/fg-on-android.php FOA] Team is looking for testers.<br />
* The [[Target4Today]] project is looking for volunteers to help improving FlightGear's combat support<br />
* The [[OpenRadar]] project is looking for a new maintainer.<br />
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.<br />
<br />
=== Did you know ===<br />
<br />
[[Category:FlightGear Newsletter|2012 08]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=Landmark_Wish_List&diff=53204Landmark Wish List2012-08-18T08:04:52Z<p>Blackiris: Marina Bay Sands done</p>
<hr />
<div>This page provides a list of important landmarks which are not currently in FlightGear Scenery that the community would like to see modeled. If you are a FlightGear modeler and are looking for something to model, please consider something on this list.<br />
<br />
Feel free to add to this list.<br />
<br />
If you are modeling a landmark, please change the "Completed" column from "No" to "Claimed".<br />
<br />
=== Africa ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
| Pyramids || Cairo || Egypt || No<br />
|-<br />
| Victoria Falls || Victoria Falls || Zimbabwe || No<br />
|-<br />
| [http://en.wikipedia.org/wiki/Table_Mountain Table Mountain] || Cape Town || South Africa || No<br />
|-<br />
| [http://en.wikipedia.org/wiki/Mount_Kilimanjaro Mount Kilimanjaro] || Kilimanjaro National Park || Tanzania || No<br />
|-<br />
| [http://en.wikipedia.org/wiki/Basilica_of_Our_Lady_of_Peace_of_Yamoussoukro Basilica of Our Lady of Peace of Yamoussoukro] || Yamoussoukro || Côte d'Ivoire || No<br />
|-<br />
|}<br />
<br />
=== America ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|National Congress || Brasilia || Brazil || '''Yes'''<br />
|-<br />
|Christ the Redeemer || Rio de Janeiro || Brazil || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Windsor_Atlantica_Hotel Windsor Atlantica Hotel] || Rio de Janeiro || Brazil || '''Claimed'''<br />
|-<br />
|Navy Pier || Chicago || USA || No<br />
|-<br />
|Adler Planetarium || Chicago || USA || No<br />
|-<br />
|Soldier Field || Chicago || USA || No<br />
|-<br />
|McCormick Place || Chicago || USA || No<br />
|-<br />
|U.S. Cellular Field || Chicago || USA || No<br />
|-<br />
|Wrigley Field || Chicago || USA || No<br />
|-<br />
|Shedd Aquarium || Chicago || USA || No<br />
|-<br />
|Union Station || Chicago || USA || No<br />
|-<br />
|Oglivie Transportation Center || Chicago || USA || No<br />
|-<br />
|Smurfit-Stone Building || Chicago || USA || No<br />
|-<br />
|Marina City || Chicago || USA || No<br />
|-<br />
|Millenium Park || Chicago || USA || No<br />
|-<br />
|United Center || Chicago || USA || No<br />
|-<br />
|Brooklyn Bridge || New York || USA || '''Claimed'''<br />
|-<br />
|Empire State Building || New York || USA || '''Yes'''<br />
|-<br />
|Chrysler Building || New York || USA || '''Claimed'''<br />
|-<br />
|United Nations Headquarters || New York || USA || '''Yes'''<br />
|-<br />
|Bank of America Tower || New York || USA || '''Yes'''<br />
|-<br />
|Verizon Center || Washington, D.C. || USA || No<br />
|-<br />
|White House || Washington, D.C. || USA || No<br />
|-<br />
|Space Needle || Seattle || USA || '''Yes'''<br />
|-<br />
|Milwaukee Art Museum || Milwaukee || USA || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Machu_Picchu Machu Picchu] || Aguas Calientes || Peru || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Nazca_Lines Nazca Lines] || Estudiantes || Peru || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Panama_canal Panama canal] and some boats pls|| Panama city - Colòn || Panama || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Hoover_Dam Hoover Dam]|| Boulder|| USA || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Skunk_Works Skunkworks aircraft] hidden in the mountain of KXTA || Area 51 || USA || No<br />
|}<br />
<br />
=== Asia ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Bank of China Tower || Hong Kong || China || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Kai_Tak_Airport "Checkerboard Hill" (VHHX approach)] || Hong Kong || China || No, See [[Talk:Landmark_Wish_List#VHHX request| Talk page]]<br />
|-<br />
|CCTV Tower || Beijing || China || '''Yes'''<br />
|-<br />
|Taj Mahal || Agra || India || '''Yes'''<br />
|-<br />
|Akashi Kaikyo bridge || Kobe || Japan || '''Yes'''<br />
|-<br />
|Petronas Towers || Kuala Lumpur || Malaysia || '''Yes'''<br />
|-<br />
|Ryugyong Hotel || Pyongyang || North Korea || '''Yes'''<br />
|-<br />
|Burj Khalifa || Dubai || UAE || '''Yes'''<br />
|-<br />
|Burj al Arab || Dubai || UAE || '''Yes'''<br />
|-<br />
|Bitexco Financial Tower || Ho Chi Minh City || Vietnam || '''Yes'''<br />
|-<br />
|Sigiriya || Matale District || Sri Lanka || No<br />
|-<br />
|Great Wall of China || Huairou, Peking / Jiuduhezhen, Huairou, Peking || China || No<br />
|-<br />
|Mount Everest || Chukhung || Nepal || No<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| Something]] || Singapore ||Singapore || No<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| Marina Bay Sands]] || Singapore ||Singapore || Yes<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| One George Street]] || Singapore ||Singapore || No<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| One Raffles Place]] || Singapore ||Singapore || No<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| The Pinnacle@Duxton]] || Singapore ||Singapore || No<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| One Shenton Way]] || Singapore ||Singapore || No<br />
|}<br />
<br />
=== Europe ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Stade de France || Saint-Denis || France || No<br />
|-<br />
|Zwischenahner Meer || Zwischenahn, Niedersachsen || Germany || '''CS done'''<br />
|-<br />
|Porta Westfalica/Hermans-Denkmal || Bückeburg (ETHB), Minden || Germany || No<br />
|-<br />
|Lapan || Oldenburg, Niedersachsen || Germany || No<br />
|-<br />
|Schloss || Oldenburg || Germany || No<br />
|-<br />
|Schloss || Neuschwanstein || Germany || '''Claimed'''<br />
|-<br />
|Colosseum || Rome || Italy || No<br />
|-<br />
|Oeresund Bridge || Copenhagen-Malmo || Scandinavia || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Oslo_Plaza Oslo Plaza] || Oslo || Norway || '''Claimed'''<br />
|-<br />
|Big Ben || London || UK || '''Yes'''<br />
|-<br />
|Westminster Abbey || London || UK || '''Yes'''<br />
|-<br />
|North Pole (flag and light) || North Pole || World || No<br />
|}<br />
<br />
=== Australia and Oceania ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Sydney Opera House || Sydney || Australia || '''Yes'''<br />
|-<br />
|Sky Tower || Auckland || New Zealand || '''Claimed'''<br />
|-<br />
|Ayers rock || Uluru || Australia || '''No'''<br />
|}<br />
<br />
== Related ==<br />
<br />
=== Internal links ===<br />
* [[FlightGear Scenery Designer]]<br />
* [[FlightGear Scenery Database]]<br />
* [[UK Scenery Wish List]]<br />
* [[Scenery_Tracker]]<br />
<br />
=== External links ===<br />
* [http://www.flightgear.org/forums/viewtopic.php?f=5&t=2390 The forum topic]<br />
* See [http://scenemodels.flightgear.org/ FGFS Scenery Object Database], for more on models for [[Scenery]]<br />
<br />
[[Category:Scenery]]<br />
[[Category:Community]]<br />
[[Category:Contribution requests]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_August_2012&diff=53092FlightGear Newsletter August 20122012-08-17T08:43:08Z<p>Blackiris: /* 3D models import webform */</p>
<hr />
<div>{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
''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 news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''<br />
<br />
== Development news ==<br />
A view of FlightGear core and fgdata activity in [[Git]] since the 2.6.0 release. A big thank to all involved for making FG such a nice fireworks!<br />
{{#ev:youtube|ibO6ruzQ5gM}} {{#ev:youtube|U0Dsgx9-Pbk}}<br />
<br />
=== Project Rembrandt ===<br />
Fred's been working on some fancy new effects, especially useful for our film-making enthusiasts.<br />
<br />
The [[Project Rembrandt|Rembrandt renderer]] has a lot of potentiality when it comes to post processing effects. Indeed, the interesting property of a deferred shader is that all stages of rendering are kept into memory. Post-processing is as simple as using a filter on a camera.<br />
<br />
So currently the effects added in git are :<br />
* Night vision including amplification grain and restrained field of view,<br />
* Cinema effect including :<br />
** Vignetting,<br />
** Color shift, with Sepia as default value,<br />
** Radial distortion (barrel and pincushion distortion, with scale compensation),<br />
** Lateral chromatic aberration (purple fringing),<br />
** Film wear simulation.<br />
<br />
{|<br />
| [[File:Fgfs-rembrandt-old-timer.jpg|thumb|400px|Rembrandt old film style]]<br />
| [[File:Fgfs-rembrandt-distortion.jpg|thumb|400px|Rembrandt ordinary lens simulation]]<br />
| [[File:Fgfs-rembrandt-night-vision-2.png|thumb|400px|Rembrandt night vision simulation]]<br />
|}<br />
This won't make it for the 2.8 release but it's likely that an add-on will be available as it is contained in the data.<br />
<br />
See also :<br />
{|<br />
| {{#ev:youtube|tLZzlLjvDRQ}}<br />
| {{#ev:youtube|_Dm-Xx5tfiE}}<br />
| {{#ev:youtube|8jBvVyiq-D0}}<br />
|}<br />
<br />
=== Unified Weather GUI ===<br />
As most readers will be aware, FG supports two weather models - Basic Weather which represents METAR data directly, and Local Weather which models weather more realistically, with more variation. In 2.8.0 these were configured separately using different UIs. Stuart Buchanan and Thorsten Renk have been working on unifying the user interfaces to provide a more user-friendly and consistent interface. This work is now available in git.<br />
<br />
=== Canvas News ===<br />
<!--additions should also be added to:http://wiki.flightgear.org/Changelog_3.0.0#Some_of_the_major_changes_include: --><br />
<br />
As of 08/2012, the new [[Canvas]] 2D drawing system in FlightGear HEAD has now also support for:<br />
* using raster images (vector images were already supported previously)<br />
* nested canvases, where a canvas may contain images created by another canvas texture [[Howto:Using raster images and nested canvases]]<br />
* creating GUI windows (not just widgets)<br />
* handling GUI events using osgGA<br />
* multiplatfom copy/paste support using two new Nasal functions: [[Howto:Clipboard access using Nasal]]<br />
<br />
Support for nested canvases will make it possible to also load canvas textures into other canvases, so that you can, for example, easily load an instrument into a GUI dialog, or even use GUI widgets in MFD instruments, which is a feature based on real avionics, i.e. as used in modern airliners like the A320 or the 787.<br />
<br />
Nested canvases also make it possible for people to easily implement GUI tools using the Canvas system, for example a GUI instrument or panel editor can be entirely implemented in scripting space now, without touching any C++ code. Similarly, GUI widgets could also be created in a WYSIWYG-fashion, too - so that even dialog editor or full GUI builders can be built using the Canvas system.<br />
<br />
In addition, Tom has now implemented support for window stacking. Check out the demo video below, which demonstrates how "nested" canvases and window stacking works:<br />
<br />
{{#ev:youtube|llVaasTEf44}}<br />
<br />
Missing features, and features currently under development, are listed at [[Canvas Widgets#Missing_.2F_Todo|Missing Canvas Features]]<br />
<br />
=== Mailing list digest ===<br />
<br />
(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)<br />
<br />
<br />
=== Forum digest ===<br />
<br />
=== '''Flightgear On Android''' ===<br />
<br />
A new developer has achieved a way to run Flightgear on Android phones. [[File:Flightgear Android Launcher.png|thumb|FOA]] <br />
<br />
The project codename will be FOA;he has done a lot of Android and C++ coding. [[File:FOA.jpg|thumb|FOA ingame]] <br />
<br />
His phone is a Samsung Galaxy Nexus and is running Android 4.04 (custom ROM but stock ROM should be OK). If your ready to test with us, please read the technical info then send a email to lacbrc@gmail.com!<br />
<br />
<br />
TECHNICAL INFO:<br />
It should have at least a 1GHz processor and decent graphics chip. Android 2.3 is a <br />
must but a rooted device is not needed but can improve performance.<br />
Not much in this, as we haven't finished it to a release yet. <br />
He tested it on a bluetooth keyboard and a wired one through usb host mode. Hope you are interested in it!<br />
<br />
The first ALPHA release is fresh out of its release, and you can read more here:<br />
http://www.flightgear.org/forums/viewtopic.php?f=18&t=16719&p=163745#p163745<br />
<br />
The FlightGear for Android Team<br />
<br />
Here is a few links:<br />
<br />
Forums:<br />
<br />
http://www.flightgear.org/forums/viewtopic.php?f=18&t=16719<br />
<br />
Website page:<br />
<br />
http://horizonflightgearhangar.yolasite.com/fg-on-android.php<br />
<br />
Wiki page:<br />
<br />
http://wiki.flightgear.org/Flightgear_On_Android<br />
<br />
=== Git digest ===<br />
<br />
=== Getting involved as a programmer ===<br />
<br />
Please see [[Howto:Start core development]]<br />
<br />
== Interview with a contributor (NAME) ==<br />
''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.''<br />
<br />
* How long have you been involved in FlightGear?<br />
* What are your major interests in FlightGear?<br />
* What project are you working on right now?<br />
* What do you plan on doing in the future?<br />
* Are you happy with the way the FlightGear project is going?<br />
* What do you enjoy most about developing for FlightGear?<br />
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?<br />
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?<br />
<br />
More questions are being collected here: [[Interview questions]].<br />
<br />
Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX <br />
<br />
== Snapshot releases ==<br />
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].<br />
<br />
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].<br />
<br />
== Nasal for newbies ==<br />
<br />
== New software tools and projects ==<br />
<br />
== FlightGear addons and mods ==<br />
<br />
== In the hangar ==<br />
<br />
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.<br />
<br />
=== New hangers ===<br />
<br />
=== New aircraft ===<br />
<br />
At the request by a new user of FG, Helijah has created and made available the Yakovlev Yak 18T in his hangar and GIT.<br />
[[File:Yak18t-splash.png|thumb|Yakovlev Yak 18T]]<br />
<br />
=== Updated aircraft ===<br />
<br />
==== [[ATC-FS]] ====<br />
The Air Traffic Control tool ATC-FS got an update. The old radar screen was replaced by a radar screen, which can display fixes, navaids and ILS localizers. This new radar is resizable, so you can use your big screen more efficient. <br />
<br />
The next version is already being worked on, it will reimplement ATC-FS using the new [[Canvas]] system (scheduled for FG 3.0) so that a fully custom drawn radar screen can be created in scripting space, including custom GUI widgets (e.g. for flight strips) - without depending on any hard coded instruments or dialogs any longer.<br />
<br />
This new design will eventually even make it possible to reuse ATC-FS for other purposes, or even include it in an AWACS aircraft that is multiplayer-enabled.<br />
<br />
[[Image:ATC-FS.jpg|1000px]]<br />
<br />
==== [[Mil_Mi6]] ====<br />
The big old russian helicopter Mi-6 from the Mil design bureau has received a new update. More than a year after the last update a new structure of the Models-subfolder allows new instruments to be added much easier. Also the electrical system has been revisited and new instruments have beed added to the engineer panels. Please keep in mind that this still is a very early development version and therefore a lot of work still needs to be done. It is available from its [https://gitorious.org/mil-mi-6 gitorious-page.]<br />
<br />
=== Liveries ===<br />
<br />
== Scenery corner ==<br />
=== 3D models import webform ===<br />
The webform to import 3D models directly into the DB is in production. Now you can use this tool to send your models to the database used by Terrasync. If everything is fine and your model respects the specifications written in the foreword, then it will quickly be shipped to all FG users worldwide through [[Terrasync]]. Yet another unique feature amongst the flight simulation world held by FlightGear. Thanks to Olivier, Clément, Julien, Martin, for their help&support.<br />
<br />
With all the forms now working on the scenemodels website, remember you can:<br />
* add a single object (if you only have one!!). Check here: http://scenemodels.flightgear.org/submission/index.php<br />
* update an object (for instance, a lot of power pylons are in fact communication pylones). It's here: http://scenemodels.flightgear.org/submission/shared/index_update.php<br />
* delete an object (if it does not exist anymore in real life). It's here: http://scenemodels.flightgear.org/submission/shared/index_delete.php<br />
* run a mass object positions import (if you added a lot of objets in one place). It's here: http://scenemodels.flightgear.org/submission/shared/index_mass_import.php<br />
* add 3D models you created to have them imported into FG scenery via Terrasync. It's here: http://scenemodels.flightgear.org/submission/static/index.php They can be specific to a city (for instance : the Eiffel tower), or shared (a new windturbine model, for instance).<br />
<br />
Please read carefully the various forewords on the site:<br />
* all data imported has to comply with the GNU/GPL license ;<br />
* you must use the elevation format used by Terrasync to give your objects/models elevation, or they could be floating/sunk for most of users.<br />
<br />
We hope to see a lot of scenes not yet available via Terrasync merge into scenemodels. Nothing is now easier, especially when used in conjunction with our Mapserver!<br />
Remember that this is the strength of FG compared to other sims: everything can be in Terrasync and no need to download patches or sceneries here and there.<br />
<br />
=== Scenemodels cleanup and update ===<br />
A big cleanup has been done on our scenemodels database. A few thousands of duplicate objects have been removed (they were caused by mass insertion of navigation data, essentially). Nothing urgent but this makes the data in Terrasync lighter and more coherent. A script has also been launched to update the country associated with each object. While not perfect, now a lot more objects have a country!<br />
<br />
=== Airports ===<br />
<br />
== Aircraft of the month ==<br />
== Airport of the month ==<br />
== Screenshot of the month ==<br />
<br />
== Suggested flights ==<br />
<br />
The US state of Idaho is known for its remote airstrips in mountainous terrain. The [http://idahoaviation.com/idahoAirstripNetwork.php Idaho Airstrip Network] has details on many of them, including airstrip diagrams. <br />
<br />
At this time of year, it's important to take into account the temperature and altitude of the airstrips, as they combine to sap the power and lift from GA aircraft. AVWeb recently [http://www.avweb.com/avwebflash/news/stinson_crash_cockpit_video_ntsb_faa_207184-1.html highlighted] the (non-fatal) crash of a [http://en.wikipedia.org/wiki/Stinson_108 Stinson 108], which included a video taken by one of the passengers. Though the NTSB has only produced a preliminary report, it was notable that the aircraft was taking off from a grass airstrip at high altitude on a hot day and appears from the video to struggle to get airborne. The Stinson is broadly similar in performance to the c172p in our base package, and the airstrip (Bruce Meadows Airport, Idaho - U63) exists in our scenery. Those interested can try taking off using the c172p with 4 people on board (2400lbs max gross weight) and high temperatures. McCall Municipal Airport (KMYL) is 44nm away, and a good destination.<br />
<br />
== Aircraft reviews ==<br />
<br />
== Wiki updates ==<br />
===New articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
</DynamicArticleList><br />
===New aircraft articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
categoryRoot=Aircraft<br />
</DynamicArticleList><br />
===Most popular newsletters===<br />
<DynamicArticleList><br />
type=hot<br />
count=5<br />
categoryRoot=FlightGear Newsletter<br />
</DynamicArticleList><br />
<br />
== Community news ==<br />
=== FlightGear on YouTube ===<br />
<br />
=== New tutorials and screencasts ===<br />
=== Forum news ===<br />
=== Multiplayer ===<br />
=== Virtual airlines ===<br />
=== FlightGear events ===<br />
<br />
== Useful links ==<br />
== And finally ... ==<br />
=== Did you know? ===<br />
Did you know that the FlightGear project dates back to a discussion among a group of net citizens in 1996 resulting in a proposal written by David Murr? The original proposal is still available<br />
from the FlightGear website and can be found [http://www.flightgear.org/proposal-3.0.1 on the FlightGear website]. Read it, you'll learn a lot about FlightGears' roots which still lead the project spirit.<br />
<br />
=== Contributing ===<br />
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
=== Call for volunteers ===<br />
* The [http://horizonflightgearhangar.yolasite.com/fg-on-android.php FOA] Team is looking for testers.<br />
* The [[Target4Today]] project is looking for volunteers to help improving FlightGear's combat support<br />
* The [[OpenRadar]] project is looking for a new maintainer.<br />
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.<br />
<br />
=== Did you know ===<br />
<br />
[[Category:FlightGear Newsletter|2012 08]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter&diff=52252FlightGear Newsletter2012-07-30T02:50:39Z<p>Blackiris: Add July link</p>
<hr />
<div>[[File:magagazine.png|right]]<br />
<br />
The '''FlightGear Newsletter''' is intended to provide a collection of the latest developments from around the worldwide [[FlightGear]] community. With so much development ongoing, it's almost impossible for anyone to keep up. The newsletter was started in July of 2009 and is presented on a monthly basis.<br />
<br />
=== Archive ===<br />
{| class="vatop" valign="top"<br />
! align="left" | 2009<br />
! align="left" | 2010<br />
! align="left" | 2011<br />
! align="left" | 2012<br />
|-<br />
|valign="bottom"|<br />
* [[FlightGear Newsletter July 2009|July]]<br />
* [[FlightGear Newsletter August 2009|August]]<br />
* [[FlightGear Newsletter September 2009|September]]<br />
* [[FlightGear Newsletter October 2009|October]]<br />
* [[FlightGear Newsletter November 2009|November]]<br />
* [[FlightGear Newsletter December 2009|December]]<br />
|valign="top"|<br />
* [[FlightGear Newsletter January 2010|January]]<br />
* [[FlightGear Newsletter February 2010|February]]<br />
* [[FlightGear Newsletter March 2010|March]]<br />
* [[FlightGear Newsletter April 2010|April]]<br />
* [[FlightGear Newsletter May 2010|May]]<br />
* [[FlightGear Newsletter June 2010|June]]<br />
* [[FlightGear Newsletter July 2010|July]]<br />
* [[FlightGear Newsletter August 2010|August]]<br />
* [[FlightGear Newsletter September 2010|September]]<br />
* [[FlightGear Newsletter October 2010|October]]<br />
* [[FlightGear Newsletter November 2010|November]]<br />
* [[FlightGear Newsletter December 2010|December]]<br />
|valign="top"|<br />
* [[FlightGear Newsletter January 2011|January]]<br />
* [[FlightGear Newsletter February 2011|February]]<br />
* [[FlightGear Newsletter March 2011|March]]<br />
* [[FlightGear Newsletter April 2011|April]]<br />
* [[FlightGear Newsletter May 2011|May]]<br />
* [[FlightGear Newsletter June 2011|June]]<br />
* [[FlightGear Newsletter July 2011|July]] <br />
* [[FlightGear Newsletter August 2011|August]]<br />
* [[FlightGear Newsletter September 2011|September]]<br />
* [[FlightGear Newsletter October 2011|October]]<br />
* [[FlightGear Newsletter November 2011|November]]<br />
* [[FlightGear Newsletter December 2011|December]] <br />
|valign="top"|<br />
* [[FlightGear Newsletter January 2012|January]]<br />
* [[FlightGear Newsletter February 2012|February]]<br />
* [[FlightGear Newsletter March 2012|March]]<br />
* [[FlightGear Newsletter April 2012|April]]<br />
* [[FlightGear Newsletter May 2012|May]]<br />
* [[FlightGear Newsletter June 2012|June]]<br />
* [[FlightGear Newsletter July 2012|July]] ''- currently being written''<br />
|}<br />
<br />
Some newsletter editions have been translated in other languages:<br />
* [[file:Es.gif|16px|url=:es:FlightGear Newsletter]] [[:es:FlightGear Newsletter|Español]]<br />
* [[file:Fr.gif|16px|url=:fr:FlightGear Newsletter]] [[:fr:FlightGear Newsletter|Français]]<br />
<br />
=== You are invited to contribute! ===<br />
We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. The FlightGear newsletter is a community-driven newsletter, which means that it is created and edited by people like **you**. You don't need to be a long-time FlightGear user (or even developer) to contribute to the newsletter. <br />
<br />
In fact, helping write the monthly FlightGear newsletter is an excellent way for getting started contributing to the FlightGear community very quickly and very easily. <br />
<br />
Even if you don't have to add anything yourself, just reviewing and improving additions by others is also highly appreciated, as are efforts to help translate newsletters or add screen shots (e.g. taken from the forum or mailing lists) to the newsletter. Screen shots can be uploaded at [[Special:Upload]].<br />
<br />
Everyone with a wiki account (free to [[Special:UserLogin|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. <br />
<br />
If you need help using the wiki, please feel free to get in touch with us using [http://www.flightgear.org/forums/viewforum.php?f=50 the forum-section].<br />
<br />
A simple template providing a basic structure for each upcoming newsletter can be taken from [[Talk:Next newsletter]]. This template can be copied/pasted into each new newsletter to help users getting started providing contents.<br />
<br />
The draft for the upcoming newsletter can always be found at [[Next newsletter]].<br />
<br />
If English is not your native language, please don't be concerned about contributing to the newsletter, you can always easily ask fellow FlightGear users to review or proof-read your changes. Also, one of the easiest ways to get started is simply copying/pasting text from forum or mailing list discussions, such as announcements (new aircraft, new scenery etc).<br />
<br />
Another neat option to get started is adding links to FlightGear related YouTube videos. For this, we have a dedicated section in each newsletter - just see: "FlightGear on YouTube": [[Next newsletter#Community news]]<br />
<br />
To directly embed YouTube videos, just use the following syntax:<br />
<nowiki>{{#ev:youtube|VBWZ6JZe_Mw|400|winter video by planetacancun2 showing FlightGear's snow.}}</nowiki><br />
<br />
If you are looking for other ways to get involved, please see [[volunteer]].<br />
<br />
[[Category:FlightGear Newsletter]]<br />
[[Category:Community]]<br />
[[Category:List]]<br />
<br />
[[es:FlightGear Newsletter]]<br />
[[fr:FlightGear Newsletter]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=Fr/Nouvelles_du_projet_FlightGear_-_f%C3%A9vrier_2012&diff=43743Fr/Nouvelles du projet FlightGear - février 20122012-03-05T09:08:41Z<p>Blackiris: /* Airwave Xtreme 150 */</p>
<hr />
<div>{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
''Nous voudrions insister sur le fait que cette newsletter ne peut pas vivre sans les contributions des utilisateurs et développeurs de FlightGear. Il suffit d'ouvrir un compte sur ce wiki pour l'éditer et toutes les contribution sont les bienvenues. Si vous avez connaissance de nouveautés dans FlightGear ou dans un projet parent, comme les avions ou les terrains, vous êtes invité à les partager en éditant cette newsletter.<br />
<br />
== FlightGear 2.6.0 est sorti ==<br />
<br />
Selon notre [[http://wiki.flightgear.org/Release_plan feuille de route]], la version 2.6.0 de notre simulateur est maintenant disponible ! Cette version apporte plusieurs nouvelles fonctionnalités, des améliorations et des correction de bugs. Les grandes améliorations depuis la version 2.4 sont le temps de chargement réduit pour le traffic AI, des ajustements de l'affichage plus faciles, un traffic AI plus sophistiqué et une utilisation plus aisée. Regardez [http://www.flightgear.org/news/flightgear-v2-6-0-released/ l'annonce de la sortie] pour les détails complets des changements effectués depuis la dernière sortie il y a 6 mois.<br />
<br />
Le téléchargement est disponible sur [[http://www.flightgear.org/download/ notre site web]].<br />
<br />
Pour le moment, nous n'avons pas assez de retours de la communauté sur cette version 2.6.0. Votre aide pour mettre à jour ce wiki serait très appréciée. Veuillez regarder les [[Hardware Recommendations | recommandations matérielles]] et les [[Notebooks known to run FlightGear#FlightGear_2.6.0_systems | notebooks connus pour faire tourner FlightGear 2.6.0]].<br />
<br />
== Nouvelles du developpement ==<br />
=== Projet Rembrandt ===<br />
Comme plusieurs on pu le constater, Fred a fait des gros progrès pour ajouter des ombres dans FlightGear avec le [[Project Rembrandt]]. Maintenant, F-JJTH a porté le P92 pour utiliser le nouveau système et a posté une vidéo YouTube qui montre le [[Project Rembrandt]] en action. Parlez-en sur le [http://flightgear.org/forums/viewtopic.php?f=47&t=14883 Forum FlightGear].<br />
<br />
{|<br />
|{{#ev:youtube|v02phoOqWHE|400|Project Rembrandt at work}}<br />
|[[File:Project-rembrandt-cockpit-lighting.png|600px|Cockpit lighting in Project Rembrandt at work (by F-JJTH)]]<br />
|}<br />
<br />
== Interview avec un contribueur: Christian Schmitt ==<br />
''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]]!''<br />
<br />
'''[http://www.flightgear.org/contributors/ Read this and previous interviews at our website's archive].'''<br />
<br />
* '''C'est quoi ton nom sur le forum et l'IRC?'''<br />
Surprise, c'est papillon81. Oui je suis un homme :)<br />
* '''Depuis combien de temps tu t'impliques dans FlightGear?'''<br />
Si je me fie au correspondance de courriel, j'ai commencé à être actif vers 2007/2008. Je n'étais pas satisfait de l'état de la scène de l'aéroport EDDF(Frankfurt) dans FlightGear(pas de bâtiment,des poteaux de lumière partout), j'ai fait équipe avec quelqu'un qui avait déjà commencé le travail sur cet aéroport. J'ai fini de créer tous les bâtiments du Terminal et améliorer la disposition de l'aéroport. A ce moment, peu de pilotes volaient là. Ceci a changé quelques mois après, ça a été bon pour ma motivation.<br />
* '''Qu'est-ce qui t'intéresses le plus dans FlightGear?'''<br />
Ce qui m'intéresse le plus est définitivement les scènes et les technologies qui les entourent, comme GIS. J'ai commencé à créer des scènes supplémentaires, comme Helgoland. Par la suite, j'ai été autorisé à accéder à la base de données Mapserver, j'étais capable de modifier le travail des autres qui arrivaient. Le meilleur FDM(Flight Dynamics Model) ou avion est inutile si vous n'avez pas d'endroit convenable pour voler, décoller et atterrir avec. C'est donc ce domaine qui m'intéresse le plus. <br />
Je maintient aussi les paquets pour la distribution Linux Gentoo (ebuilds) pour la version GIT de FlightGear, SimGear et TerraGear. On les trouve dans les dépots Gentoo Gamerlay.<br />
* '''Sur quel projet tu travailles en ce moment?'''<br />
Il y a quelques mois, j'en avais marre de FlightGear, car il était incapable de lire les données apt.dat 850. J'ai donc commencé à regarder le code de TerraGear. Je n'avais aucune expérience avec le C++. C'était un apprentissage difficile, mais à ma grande surprise, j'ai été capable de convertir l'analyseur de TerraGear pour qu'il peut lire les données des pistes et d'autres fonctionnalité du nouveau format de fichier. J'ai commencé a implanter le plus de fonctionnalité qu'il était possible pour moi d'intégrer. Heureusement, Pete travaillait déjà sur les fonctionnalités pour les voies de circulations et la surface. Nous avons donc fusionné notre travail. Ça été un projet très constructif pour mon apprentissage et pour améliorer FlightGear. J'espère qu'il sera utilisé pour la prochaine version de la scène de FlightGear. Avant que cela arrive, nous avons de plus de testeurs.<br />
* '''Sur quoi prévoies-tu travailler dans le future?'''<br />
Je vais continuer de travailler sur TerraGear, améliorer le concorde(Mon avion favoris dans FlightGear) et m'occuper des demandes de fusion. J'aimerais aussi plonger encore plus dans le code de FlightGear/SimGear et faire quelques ajustements. Voyons ce que le future apportera :)<br />
* '''Est-tu heureux avec la direction que projet FlightGear prends?'''<br />
IJe suis vraiment satisfait avec. Les améliorations des 2 dernières années sont à couper le souffle. C'est vraiment impressionnant parfois, les fonctionnalité sur les quelles certains peuvent travailler, comme le projet Rembrandt. Le travail mit dans le système de météo et de shader, est vraiment impressionnant.<br />
* '''Qu'est-ce que tu aime le plus à propos du développement de FlightGear?'''<br />
Le fait que tout le monde se supporte et que nous avons une forte communauté avec beaucoup de gens compétent dans divers domaines. Savoir que tu peut construire sur le travail des autres que tu va pouvoir avoir de l'aide cas de problème. J'aime beaucoup le cannal IRC de FlightGear.<br />
<br />
* '''Quel conseil donnerais-tu a un nouveau développeur qui veut commencer à travailler sur son premier avion/fonctionnalité/Script Nasal?'''<br />
Tout d'abord, il devrait avoir de l'expérience avec FlightGear en général, il devrait avoir utiliser le logiciel quelques temps. Nous avons souvent des gens qui posent des questions qu'ils auraient pu répondre eux-mêmes s'ils aurait un peu utiliser FlightGear avec différents appareils. Si il a identifié une zone où il veut commencer à développer, il devrait contacté le mainteneur et demandé des conseils avant d'investir plusieurs heures de travail.<br />
'''[http://www.flightgear.org/contributors/ Read this and previous interviews at our website's archive].'''<br />
<br />
== Dans le hangar ==<br />
En mai 2011, nous avons introduit un nouveau système d'évaluation pour le statut des avions. Jusqu'à maintenant, très peu on été évalué, comme un peu voir sur la page de téléchargements des avions:[http://www.flightgear.org/download/aircraft-v2-6/ aircraft download page]. I. Si vous êtes un développeur d'un appareil et que votre appareil n'est pas sur la liste, considérer de l'évaluer son statut. Tout ce que vous avez besoin de faire et de savoir est disponible sur cette page: [http://wiki.flightgear.org/Formalizing_Aircraft_Status]<br />
<br />
=== Un nouvel instrument: Affichage de la situation verticale (VSD) ===<br />
[[File:Omega95-vsd-instrument.jpeg|200px|thumb|Omega95's VSD instrument]]<br />
Omega95 a créé un tout nouveau type instrument qui montre la pente de montée ou de descente ainsi que le terrain. Cet instrument a été entièrement réalisé en Nasal et en animation XML. Il a prouvé qu'il était possible de créer des instruments complexes dans l'espace de script. Il a apparemment réalisé ceci en moins de 24 heures. Sa première question relier à ce projet était comment accéder au fonction trigonométrique, à partir de Nasal, peu de temps après, il a posté des captures d'écrans montrant son VSD.<br />
<br />
Pour lire la discussion au complet, visiter le sujet sur le forum [http://flightgear.org/forums/viewtopic.php?f=30&t=15200 the forum topic]. Il y a du travail pour transformer son travail en tutoriel pour le wiki sur la création d'instrument complexe dans l'espace de script [[Howto: Implement a Vertical Situation Display in Nasal]].<br />
<br />
=== Treuil de remorquage pour planeur ===<br />
[[File:DG-101G_winch_launch_with_rope.png|thumb|200px|A DG-101G during a winch launch.]]<br />
Avant maintenant, FlightGear ne montrait pas le cable pendant le lancement avec le treuil de remorquage. Maintenant, vous n'aurez plus à voler un planeur remorquer par un cable invisible qui vous relie au treuil. <br />
<br />
[[User:Gijs|Gijs]] à commencer à travailler sur un cable animer en 3d attacher au planeur et au treuil. The cable exist of the following parts:<br />
<br />
* '''Strop''' (3 m) attached to the glider with a ring.<br />
* '''Weak link assembly''' designed to break apart before the cable or any other equipment fails.<br />
* '''Trace''' (17 m)<br />
* '''Parachute''' so the cable doesn't drop too quickly after releasing.<br />
* '''Launch cable''' the longest part; all the way to the winch.<br />
<br />
=== Nouveaux avions ===<br />
[[File:Harrier-GR1 Splash.png|thumb|left|200px|Harrier GR.1 splash screen]]<br />
[[File:RAH-66 splash.png|thumb|200px|RAH-66 splash screen]]<br />
==== Hawker Siddeley Harrier GR.1 ====<br />
[[Hawker Siddeley Harrier GR1]] est un projet de pjedvaj, il n'a pas l'intention de remplacer le [[British Aerospace Harrier]] déjà existant. Il a un modèle 3D détaillé et complet avec un cockpit, des animations et une livré de la RAF. Les instruments et le HUD sont assez authentique. L'avion a des armes fonctionnel et un contrôle du poids et carburant de base. Le FDM est adapté du BAe Harrier original, mais les réservoirs externes et internes sont adapté pour le GR.1<br />
==== Boeing-Sikorsky RAH-66 Commanche ====<br />
Le [[Boeing-Sikorsky RAH-66 Commanche]] à été commencé par une prime offert par sgofferj et développer par pjedvaj mais il s'est, plus tard, retiré de la prime. C'était son premier projet d'hélicoptère et le FDM est très peu développer et ce base sur celui de Tatsuhiro Nishioka's pour le Kawasaki OH-1. Il un modèle 3D détaillé, des animations et deux livrés. L'hélicoptère a un canon fonctionnel contrôlé par joystick et un contrôle basique du poids pour l'armement. Vous êtes libre de continuer le développement et de réclamer la prime.<br />
<br />
=== Avions mis-à-jour ===<br />
==== Airwave Xtreme 150 ====<br />
[[File:Airwave Xtreme 150 Innsbruck.png|thumb|200px]]<br />
Dans le hangar de FlightGear depuis 2002, le seul deltaplane de FlightGear a maintenant un pilote animé. D-NXKT a fait un travail formidable. Il a créé des mouvements du corps réaliste pour le pilote du [[Airwave Xtreme 150]]ar le modèle était invisible à cause du passage de FlightGear à OpenSceneGraph. Par la suite, il est prévu de créer un FDM JSBSim. Ceci permettra au deltaplane d'intéragir avec la météo et l'environnement. Merci à la flexibilité de JSBSim, le transfert de poids peut être simulé de façon très réaliste.<br />
<br />
More to follow in future newsletters.<br />
<br />
==== Boeing 787-8 Dreamliner ====<br />
[[File:boeing-787-8-splash.png|thumb|200px|The Boeing 787-8 Splash Screen]]<br />
Le [[Boeing 787-8 Dreamliner]] st dans le hangar de FlightGear depuis la version 1.0. Il a cependant été créer quand le 787 était encore un prototype, il ne montrait pas plusieurs fonctionnalité du 787 actuel, comme un cockpit et des instruments fidèle au vrai 787.<br />
Le nouveau 787 est un projet de la communauté qui offre un nouveau FDM JSBSim, la navigation verticale, un glass cockpit réaliste, un nouveau FMC, TCAS, sac de vol numérique, écran de navigation sophistiqué, VSD et le [[Howto:_Implement a Fly-By-Wire System for Airliners|Fly-by-wire]]. Le projet est encore en développement.<br />
<br />
Pour en savoir plus, visitez l'article sur le wiki FlightGear: [[Boeing 787-8 Dreamliner|its wiki article]]. Un des points positif de ce projet est que la majorité des découvertes et ressources ont été convertis en How-to pour le wiki, pour que d'autre développeur l'utilise dans leurs projets.<br />
<br />
==== Cessna 337G Skymaster ====<br />
[[File:Cessna337-cockpit.png|thumb|200px|General view of the new Cessna 337G Skymaster cockpit]]<br />
Le [[Cessna 337G Skymaster]] de la communauté espagnole «Vive FlightGear» à reçu une mise-à-jour majeure.<br />
<br />
Le cockpit est maintenant complètement modelé, avec presque tout les boutons fonctionnel et animé. Il sont aussi bien identifié. Il profite aussi de nouveau sons, lumières, contrôle, un avionique Bendix/King capable de navigation IFR et de nuit, deux nouvelles livrés et le premier ELT(Emergency Locator Transmitter).<br />
<br />
== Le coin des scènes ==<br />
=== 3D-Model contributors: please read ===<br />
A (long) time ago, specific instructions were given on how to contribute with 3D-models designing withing FG. That is: I want to create nice 3D models for my airport, submit them to the central database, and have them shipped back through Terrasync.<br />
However, it appears that quite a lot of users are still not aware of those guidelines, and sometimes learn about their existence after having created their models.<br />
So please, take some time to (re)read them, and inform the people around you who would like to contribute about the existence of those guidelines. This will save you extra time (and your models will be quickly inserted within the database) and this will also save the (precious) times of the poor guy(s) validating all the models at the other end.<br />
So, here they are: http://scenemodels.flightgear.org/contribute.php .<br />
We also remind you that, to add, edit or delete shared model positions (apart from mass import (that is if you have more than let's say 10 lines to add), you should use our webtools at http://scenemodels.flightgear.org/submission/ .<br />
<br />
=== Object-masking and improved materials ===<br />
For a long time, FlightGear has had the ability to place random objects on the scenery. Previously, these objects were placed completely randomly based on a specific density for the material, defined in materials.xml. This didn't look particularly realistic as the placement never matched the underlying texture. Now object and trees can be placed using a "mask", so buildings will only appear where the texture shows buildings, and trees only in green spaces. Additionally, placement is controlled so that random buildings won't overlap with other random buildings, and buildings don't overlap onto adjacent piece of scenery. This makes the random objects appear more realistic, and moves FG one step closer to the auto-gen scenery of MSFS and X-Plane. Further details can be found in fgdata/Docs/README.materials and on on the [[Howto: Editing tile textures and materials]].<br />
<br />
In addition to this, the materials.xml and materials-dds.xml files have been restructured to make them more maintainable, fixing a number of bugs in the process.<br />
<br />
=== Gratte-ciel de Shanghai ===<br />
Shanghai est une des plus grande ville de Chine et une des villes avec le plus grands nombres de gratte-ciel. Maintenant, cela est aussi vrai pour FlightGear. 25 modèles ont été créé dans les derniers mois par JVC, qui à aussi modelé le pont Akashi-Kaikyo au Japon et le bâtiment des Nations-unies a New-York.<br />
{|<br />
|[[File:SH fgfs-screen-001.png|250px|thumb|A view of the Shanghai skyline]]<br />
|[[File:Shanghai003.png|250px|thumb|Another view of Shanghai]]<br />
|[[File:Shanghai007.png|250px|thumb|A closer view from near the Shanghai Stock Exchange]]<br />
|}<br />
<br />
=== Nouvelle textures pour les portes-conteneur et les bateaux cargos ===<br />
À partir d'un panorama haute résolution qu'il a fait, Critian Marchi(aka penta) a fourni des nouvelles textures pour les deux bateaux AI qui peuple les océans de FlightGear. Pour plus d'information, visitez le sujet sur le forum: [http://www.flightgear.org/forums/viewtopic.php?f=23&t=14856].<br />
{|<br />
|[[File:Ships-comparison.png|200px|thumb|left|Comparison between untextured and textured AI ships (by Cristian Marchi)]]<br />
|}<br />
<br />
=== Scènes photo réaliste ===<br />
Il y a maintenant des scènes photo réaliste pour certain endroit au États-Unis, disponible à cette adresse: http://fgphotoscenery.square7.ch/ Les regions couvertes sont la baie de San-Francisco, Yosmenite, le Grand Canyon, Lake Powell, Sedona, Miami, Everglades et Key Largo. La scène a été créé avec les images du [http://www.usgs.org U.S. Geological Survey]qui sont sous licence GNU GPL. Elles ont une résolution de 3m/pixel. Un total de 1.3 GB d'image son disponible au téléchargement. Vidéos de l'UFO volant dans les scènes: [http://fgphotoscenery.square7.ch#gallery gallery]. <br />
Pour être capable de charger les images dans FlightGear, le programme doit être compiler à partir des sources et le patch de Benoît Laniel pour la scène photo réaliste de Brest doit être appliqué. Des instruction détaillé sont disponible:[http://fgphotoscenery.square7.ch#installation installation instructions] for this process are provided.<br />
<br />
Discussion: [http://www.flightgear.org/forums/viewtopic.php?f=5&t=15174 forum thread].<br />
<br />
[[File:fgphotoscenery_gallery.jpg]]<br />
<br />
== L'Avion du mois ==<br />
Le [[Boeing 787-8 Dreamliner]] a été grandement améliorer, comme vous avez pu le lire dans cette newsletter. Le 787 est l'avion du mois de Février.<br />
{{#ev:youtube|WlzEoCsJvz4|400|Aircraft of the Month - Boeing 787-8}}<br />
<br />
== L'aéroport du mois ==<br />
<br />
[[File:LFRJ.png|800px]]<br />
<br />
La [[Landivisiau Naval Air Base|Base d'aéronautique navale de Landivisiau]] (LFRJ) est au milieu d'une scène formidable. Si quelqu'un veux essayer le vol [[VFR]] l devrait le faire ici, en Bretagne en France. Mémoriser la scène, les églises, les lignes électriques et mettez les sur une carte et essayer de retrouver votre chemin. L'aéroport est la base pour les avions qui vont à la mer, c'est pourquoi vous retrouverez deux cable d'arrêt sur la piste, ne trébucher par dessus. L'aéroport aussi la base pour des hélicoptères comme le Super Frelon et le Westland Lynx. L'aéroport à une tour de contrôle modelé, des entrepôts et les abris pour le Rafale.<br />
<br />
== La capture d'écran du mois ==<br />
<br />
[[File: Lightfield-1.1-14.jpg | 800px]]<br />
<br />
Un P-51D volant à 20 000 pieds au-dessus de Juneau (Alaska) à l'aube avec les lightfield shaders pour rendre le lever du soleil. (Téléchargements des shaders: [http://www.flightgear.org/forums/viewtopic.php?f=47&t=14755 ici] ).<br />
<br />
== Suggestion de vol ==<br />
===Copacabana à San Rafael au-dessus du lac Titicaca===<br />
De la Bolivie au Pérou, le voyage va vous amenez au-dessus d'un des lacs le plus haut et le plus profond dans le monde vers un des aéroports le plus haut du monde. C'est une démonstration du vol [[IFR]] via un FIX et démontre comment FlightGear simule les effets de la densité d'air sur un avion.<br />
[[File:Slcc-sprf.jpg|thumb|200px|left|Flight and fix SLCC to SPRF]]<br />
Placez votre avion sur l'aéroport de Copacabana (SLCC) qui est situé à une hauteur de 12 593 pieds. FlightGear va mettre de la neige tout autour, mais ce n'est pas très réaliste, donc réglons cela: <br />
View=> Rendering Options=> Snow line=> Set to max. (5,000M). <br />
<br />
Nous allons voler vers et atterrir à SPRF. Préparation de l'équipement. Configurer le NAV1 sur le VOR-DME Juliaca sur 155.55 avec un radial de 311° (Magnétique). Configurer le NAV2 sur le VOR-DME Arequipa sur 113.7 avec un radial de 212°. Pendant le vol, nous allons voler avec la vrai altitude (Par rapport au niveau de la mer). Configuré bien votre altimètre et garder le a jour. Configurer le pilote automatique avec le cap 311° et un altitude initial de 13 500 pieds.<br />
<br />
Décollez et si vous avez pris la mauvaise piste, tiré fort sur le manche. Faite un petit tour au-dessus du [http://en.wikipedia.org/wiki/Titicaca lac Titicaca], regarder les îles flottantes et essayer de trouver le trésor d'or perdu. Intercepté le radial le plus proche sur le NAV1 vers Juliaca (Environ 311). <br />
<br />
Juste avant Juliaca, il y a une montagne, donc quand vous êtes sur le lac, montez à 14 200 pieds, la partie [[VFR]] est terminé. Après avoir passé Juliaca, fixé le radial du NAV1 a 353° et configurer l'altitude à 17 422 pieds. Nous allons voler à partir du NAV1 et monter tranquillement.<br />
<br />
À une distance de 60 NM, fixé le cap sur le cap actuel. Vérifiez la distance du NAV1, le radial du NAV2 et sa distance. À une distance de 74.5 NM du NAV1 et 140.7 NM du NAV2 et l'interception du radial du NAV2, la piste devrait être la. Donc à partir de 60 NM, commencez à regarder par la fenêtre, à NAV1 et NAV2.<br />
<br />
Si vous êtes à 80 NM de NAV1, vous avez manqué la piste, mais vous n'allez pas frapper de montagne (sauf si vous avez tourné à gauche). Tournez à droite et mettez le cap a 172°, volez vers le NAV1 et interceptez le radial 352° à 50 NM. Répétez la recherche.<br />
<br />
La piste de SPRF, San Rafael, est à une altitude de 14 422 pieds et un cap de 297°/117°. Notre altitude à été configurer 3 000 pieds au-dessus de la piste. Ceci devrait être suffisant pour la navigation.<br />
Après que vous avez vu la piste, fixé le radial du NAV1 à 297°, le cap de la piste, comme aide visuel. Atterrissez sur la piste 30. Il y a une petite colline en face de la piste 30.<br />
<br />
Réduire sa vitesse à cette altitude n'est pas facile. L'air n'offre pas beaucoup de résistance. La différence entre la vitesse air indiqué et la vitesse sol est grande. La vitesse sol est beaucoup plus haute que la vitesse air indiqué.<br />
<br />
Après un atterrissage réussi, vous pouvez tentez de trouver l'origine du Fleuve Amazone, car nous sommes au point de départ de ce vol: [[Suggested_Flights#Origin_of_the_Amazon_River | origin of the Amazon river]] s<br />
<br />
*More places you can visit can be found at [[Suggested Flights]].<br />
<br />
== Wiki updates ==<br />
=== Categorizing images ===<br />
[[User:Johan G|Johan G]] did a great job starting to categorise all images. The sub-categories are listed under [[:Category:Images]]. <br />
<br />
Please keep the following things in mind when uploading images:<br />
* Give the file a descriptive name. That'll make it easier for others to find your file and use it in articles.<br />
* Categorize your image right when you upload it. That saves others from digging up uncategorized images later on. Placing your image in a category is as simple as adding the following line to the "description" field:<br />
: <code><nowiki>[[Category:Name of the category]]</nowiki></code><br />
: A list of available categories can be found under [[:Category:Images]].<br />
<br />
=== Documentating templates ===<br />
[[User:Gijs|Gijs]] documentated most [[:Category:Templates|templates]], making use of a global [[Template:Informative template|documentation template]]. The documentation tells you what the template does and how to use it.<br />
<br />
=== Feature icons ===<br />
Michat has designed small logos for Airport of the Month, Screenshot of the Month, Aircraft of the Month, [[Dual Control]], [[Bombable]], [[Soaring]], [[Howto:_Do_aerotow_over_the_net|Aerotow]], [[Howto:_Aerial_refueling|Air refueling]] and [[:Category:Aerospace|Aerospace]] aircraft, allowing you to see at a glance which aircraft has some of those interesting features.<br />
<br />
[[File:Dualcontrolready2.png|Dual_control]] [[File:BombableReady.png|Bombable]] [[File:Aerotowready.png|Doing aerotow over the net]] [[File:Thermalready.png|Soaring]] [[File:Spacetripready.png|Aerospace]]<br />
[[File:Aircraftofthemonth.png|IAR80]] [[File:Airrefuelingready.png]] [[File:Airportofthemonth.png]] [[File:Screenshotofthemonth.png]].<br />
<br />
== Nouvelles de la communauté ==<br />
=== FlightGear sur FSBreak ===<br />
Deux développeur de FlightGear, Stuart et Curt ont été interviewé sur un épisode de FSBreak, enregistré le 25 Février. FSBreak est un podcast sur la simulation de vol. Les animateurs Eric et Brendan, on pris près de 1 heure pour parler du projet FlightGear. Vous pouvez l'écouter ici: [http://www.fsbreak.net/podcast/2012/3/2/fsbreak-107-we-talk-flightgear-and-accufeel-released.html this link].<br />
<br />
=== FlightGear on YouTube ===<br />
* [http://youtu.be/hBEaOMzBq6E KSFO Thermal Demo] by MD-BFC Going on their way for Bocian certification<br />
* [http://youtu.be/-yI5PzC5RE8 Sukhoi 37 'The russian dream'] by Águilas de FlightGear performing "Balalaika amok" master tune by Aleksei Arkhipovsky.<br />
<br />
=== Forum news ===<br />
Triggered by the new release, we've had more [http://flightgear.org/forums forum] visitors then ever before in the week of 19-25 February! 17,123 people visited the forum in these seven days to be precise. When looking at "unique visitors", only 13-19 February 2011 was a busier week (9548 against 9076 visitors) (a possible reason for the high number might be that people expected 2.2.0 to be released, which was canceled).<br />
<br />
== And finally ... ==<br />
=== Contributing ===<br />
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
=== Call for volunteers ===<br />
* The [[OpenRadar]] project is looking for a new maintainer.<br />
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.<br />
<br />
=== Did you know ===<br />
...that you can use expressions to create complex animations of objects in your 3d models or even drive them from multiple properties?<br />
Usually, an animation looks like this<br />
<syntaxhighlight lang="xml"><br />
<animation><br />
<type>translate</type><br />
<property>foo/bar</property><br />
[..]more elements[..]<br />
</animation><br />
</syntaxhighlight><br />
You can add a scaling factor or an offset to it, but that's basically all you can do that way. <br />
If you want to animate your object following a complex function, most people create complex Nasal scripts to compute the driving properties, probably not knowing that there is another way to achieve the goal: Expressions. <br />
Here is an example for a translate animation depending on two properties and the cosine function<br />
<syntaxhighlight lang="xml"><br />
<animation><br />
<type>translate</type><br />
<expression><br />
<product><br />
<property>/my/factor-property</property><br />
<cos><br />
<deg2rad><br />
<property>/my/angular-property</property><br />
</deg2rad><br />
</cos><br />
</product><br />
</expression><br />
[..]more elements[..]<br />
</animation><br />
</syntaxhighlight><br />
A rich set of predefined functions is available, including almost all those you have on your scientific pocket calculator.<br />
<br />
[[Category:FlightGear Newsletter|2012 02]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=Fr/Nouvelles_du_projet_FlightGear_-_f%C3%A9vrier_2012&diff=43742Fr/Nouvelles du projet FlightGear - février 20122012-03-05T09:07:39Z<p>Blackiris: /* Interview avec un contribueur: Christian Schmitt */</p>
<hr />
<div>{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
''Nous voudrions insister sur le fait que cette newsletter ne peut pas vivre sans les contributions des utilisateurs et développeurs de FlightGear. Il suffit d'ouvrir un compte sur ce wiki pour l'éditer et toutes les contribution sont les bienvenues. Si vous avez connaissance de nouveautés dans FlightGear ou dans un projet parent, comme les avions ou les terrains, vous êtes invité à les partager en éditant cette newsletter.<br />
<br />
== FlightGear 2.6.0 est sorti ==<br />
<br />
Selon notre [[http://wiki.flightgear.org/Release_plan feuille de route]], la version 2.6.0 de notre simulateur est maintenant disponible ! Cette version apporte plusieurs nouvelles fonctionnalités, des améliorations et des correction de bugs. Les grandes améliorations depuis la version 2.4 sont le temps de chargement réduit pour le traffic AI, des ajustements de l'affichage plus faciles, un traffic AI plus sophistiqué et une utilisation plus aisée. Regardez [http://www.flightgear.org/news/flightgear-v2-6-0-released/ l'annonce de la sortie] pour les détails complets des changements effectués depuis la dernière sortie il y a 6 mois.<br />
<br />
Le téléchargement est disponible sur [[http://www.flightgear.org/download/ notre site web]].<br />
<br />
Pour le moment, nous n'avons pas assez de retours de la communauté sur cette version 2.6.0. Votre aide pour mettre à jour ce wiki serait très appréciée. Veuillez regarder les [[Hardware Recommendations | recommandations matérielles]] et les [[Notebooks known to run FlightGear#FlightGear_2.6.0_systems | notebooks connus pour faire tourner FlightGear 2.6.0]].<br />
<br />
== Nouvelles du developpement ==<br />
=== Projet Rembrandt ===<br />
Comme plusieurs on pu le constater, Fred a fait des gros progrès pour ajouter des ombres dans FlightGear avec le [[Project Rembrandt]]. Maintenant, F-JJTH a porté le P92 pour utiliser le nouveau système et a posté une vidéo YouTube qui montre le [[Project Rembrandt]] en action. Parlez-en sur le [http://flightgear.org/forums/viewtopic.php?f=47&t=14883 Forum FlightGear].<br />
<br />
{|<br />
|{{#ev:youtube|v02phoOqWHE|400|Project Rembrandt at work}}<br />
|[[File:Project-rembrandt-cockpit-lighting.png|600px|Cockpit lighting in Project Rembrandt at work (by F-JJTH)]]<br />
|}<br />
<br />
== Interview avec un contribueur: Christian Schmitt ==<br />
''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]]!''<br />
<br />
'''[http://www.flightgear.org/contributors/ Read this and previous interviews at our website's archive].'''<br />
<br />
* '''C'est quoi ton nom sur le forum et l'IRC?'''<br />
Surprise, c'est papillon81. Oui je suis un homme :)<br />
* '''Depuis combien de temps tu t'impliques dans FlightGear?'''<br />
Si je me fie au correspondance de courriel, j'ai commencé à être actif vers 2007/2008. Je n'étais pas satisfait de l'état de la scène de l'aéroport EDDF(Frankfurt) dans FlightGear(pas de bâtiment,des poteaux de lumière partout), j'ai fait équipe avec quelqu'un qui avait déjà commencé le travail sur cet aéroport. J'ai fini de créer tous les bâtiments du Terminal et améliorer la disposition de l'aéroport. A ce moment, peu de pilotes volaient là. Ceci a changé quelques mois après, ça a été bon pour ma motivation.<br />
* '''Qu'est-ce qui t'intéresses le plus dans FlightGear?'''<br />
Ce qui m'intéresse le plus est définitivement les scènes et les technologies qui les entourent, comme GIS. J'ai commencé à créer des scènes supplémentaires, comme Helgoland. Par la suite, j'ai été autorisé à accéder à la base de données Mapserver, j'étais capable de modifier le travail des autres qui arrivaient. Le meilleur FDM(Flight Dynamics Model) ou avion est inutile si vous n'avez pas d'endroit convenable pour voler, décoller et atterrir avec. C'est donc ce domaine qui m'intéresse le plus. <br />
Je maintient aussi les paquets pour la distribution Linux Gentoo (ebuilds) pour la version GIT de FlightGear, SimGear et TerraGear. On les trouve dans les dépots Gentoo Gamerlay.<br />
* '''Sur quel projet tu travailles en ce moment?'''<br />
Il y a quelques mois, j'en avais marre de FlightGear, car il était incapable de lire les données apt.dat 850. J'ai donc commencé à regarder le code de TerraGear. Je n'avais aucune expérience avec le C++. C'était un apprentissage difficile, mais à ma grande surprise, j'ai été capable de convertir l'analyseur de TerraGear pour qu'il peut lire les données des pistes et d'autres fonctionnalité du nouveau format de fichier. J'ai commencé a implanter le plus de fonctionnalité qu'il était possible pour moi d'intégrer. Heureusement, Pete travaillait déjà sur les fonctionnalités pour les voies de circulations et la surface. Nous avons donc fusionné notre travail. Ça été un projet très constructif pour mon apprentissage et pour améliorer FlightGear. J'espère qu'il sera utilisé pour la prochaine version de la scène de FlightGear. Avant que cela arrive, nous avons de plus de testeurs.<br />
* '''Sur quoi prévoies-tu travailler dans le future?'''<br />
Je vais continuer de travailler sur TerraGear, améliorer le concorde(Mon avion favoris dans FlightGear) et m'occuper des demandes de fusion. J'aimerais aussi plonger encore plus dans le code de FlightGear/SimGear et faire quelques ajustements. Voyons ce que le future apportera :)<br />
* '''Est-tu heureux avec la direction que projet FlightGear prends?'''<br />
IJe suis vraiment satisfait avec. Les améliorations des 2 dernières années sont à couper le souffle. C'est vraiment impressionnant parfois, les fonctionnalité sur les quelles certains peuvent travailler, comme le projet Rembrandt. Le travail mit dans le système de météo et de shader, est vraiment impressionnant.<br />
* '''Qu'est-ce que tu aime le plus à propos du développement de FlightGear?'''<br />
Le fait que tout le monde se supporte et que nous avons une forte communauté avec beaucoup de gens compétent dans divers domaines. Savoir que tu peut construire sur le travail des autres que tu va pouvoir avoir de l'aide cas de problème. J'aime beaucoup le cannal IRC de FlightGear.<br />
<br />
* '''Quel conseil donnerais-tu a un nouveau développeur qui veut commencer à travailler sur son premier avion/fonctionnalité/Script Nasal?'''<br />
Tout d'abord, il devrait avoir de l'expérience avec FlightGear en général, il devrait avoir utiliser le logiciel quelques temps. Nous avons souvent des gens qui posent des questions qu'ils auraient pu répondre eux-mêmes s'ils aurait un peu utiliser FlightGear avec différents appareils. Si il a identifié une zone où il veut commencer à développer, il devrait contacté le mainteneur et demandé des conseils avant d'investir plusieurs heures de travail.<br />
'''[http://www.flightgear.org/contributors/ Read this and previous interviews at our website's archive].'''<br />
<br />
== Dans le hangar ==<br />
En mai 2011, nous avons introduit un nouveau système d'évaluation pour le statut des avions. Jusqu'à maintenant, très peu on été évalué, comme un peu voir sur la page de téléchargements des avions:[http://www.flightgear.org/download/aircraft-v2-6/ aircraft download page]. I. Si vous êtes un développeur d'un appareil et que votre appareil n'est pas sur la liste, considérer de l'évaluer son statut. Tout ce que vous avez besoin de faire et de savoir est disponible sur cette page: [http://wiki.flightgear.org/Formalizing_Aircraft_Status]<br />
<br />
=== Un nouvel instrument: Affichage de la situation verticale (VSD) ===<br />
[[File:Omega95-vsd-instrument.jpeg|200px|thumb|Omega95's VSD instrument]]<br />
Omega95 a créé un tout nouveau type instrument qui montre la pente de montée ou de descente ainsi que le terrain. Cet instrument a été entièrement réalisé en Nasal et en animation XML. Il a prouvé qu'il était possible de créer des instruments complexes dans l'espace de script. Il a apparemment réalisé ceci en moins de 24 heures. Sa première question relier à ce projet était comment accéder au fonction trigonométrique, à partir de Nasal, peu de temps après, il a posté des captures d'écrans montrant son VSD.<br />
<br />
Pour lire la discussion au complet, visiter le sujet sur le forum [http://flightgear.org/forums/viewtopic.php?f=30&t=15200 the forum topic]. Il y a du travail pour transformer son travail en tutoriel pour le wiki sur la création d'instrument complexe dans l'espace de script [[Howto: Implement a Vertical Situation Display in Nasal]].<br />
<br />
=== Treuil de remorquage pour planeur ===<br />
[[File:DG-101G_winch_launch_with_rope.png|thumb|200px|A DG-101G during a winch launch.]]<br />
Avant maintenant, FlightGear ne montrait pas le cable pendant le lancement avec le treuil de remorquage. Maintenant, vous n'aurez plus à voler un planeur remorquer par un cable invisible qui vous relie au treuil. <br />
<br />
[[User:Gijs|Gijs]] à commencer à travailler sur un cable animer en 3d attacher au planeur et au treuil. The cable exist of the following parts:<br />
<br />
* '''Strop''' (3 m) attached to the glider with a ring.<br />
* '''Weak link assembly''' designed to break apart before the cable or any other equipment fails.<br />
* '''Trace''' (17 m)<br />
* '''Parachute''' so the cable doesn't drop too quickly after releasing.<br />
* '''Launch cable''' the longest part; all the way to the winch.<br />
<br />
=== Nouveaux avions ===<br />
[[File:Harrier-GR1 Splash.png|thumb|left|200px|Harrier GR.1 splash screen]]<br />
[[File:RAH-66 splash.png|thumb|200px|RAH-66 splash screen]]<br />
==== Hawker Siddeley Harrier GR.1 ====<br />
[[Hawker Siddeley Harrier GR1]] est un projet de pjedvaj, il n'a pas l'intention de remplacer le [[British Aerospace Harrier]] déjà existant. Il a un modèle 3D détaillé et complet avec un cockpit, des animations et une livré de la RAF. Les instruments et le HUD sont assez authentique. L'avion a des armes fonctionnel et un contrôle du poids et carburant de base. Le FDM est adapté du BAe Harrier original, mais les réservoirs externes et internes sont adapté pour le GR.1<br />
==== Boeing-Sikorsky RAH-66 Commanche ====<br />
Le [[Boeing-Sikorsky RAH-66 Commanche]] à été commencé par une prime offert par sgofferj et développer par pjedvaj mais il s'est, plus tard, retiré de la prime. C'était son premier projet d'hélicoptère et le FDM est très peu développer et ce base sur celui de Tatsuhiro Nishioka's pour le Kawasaki OH-1. Il un modèle 3D détaillé, des animations et deux livrés. L'hélicoptère a un canon fonctionnel contrôlé par joystick et un contrôle basique du poids pour l'armement. Vous êtes libre de continuer le développement et de réclamer la prime.<br />
<br />
=== Avions mis-à-jour ===<br />
==== Airwave Xtreme 150 ====<br />
[[File:Airwave Xtreme 150 Innsbruck.png|thumb|200px]]<br />
HDans le hangar de FlightGear depuis 2002, le seul deltaplane de FlightGear à maintenant un pilote animé. D-NXKT a fait un travail formidable. Il a créer des movements du corps réaliste pour le pilote du [[Airwave Xtreme 150]]ar le modèle était invisible à cause du passage de FlightGear à OpenSceneGraph. Par la suite, il est prévue de créer un FDM JSBSim. Ceci permettra au deltaplane d'intéragir avec la météo et l'environnement. Merci à la flexibilité de JSBSim, le transfert de poids peu être simuler de façon très réaliste.<br />
<br />
More to follow in future newsletters.<br />
<br />
==== Boeing 787-8 Dreamliner ====<br />
[[File:boeing-787-8-splash.png|thumb|200px|The Boeing 787-8 Splash Screen]]<br />
Le [[Boeing 787-8 Dreamliner]] st dans le hangar de FlightGear depuis la version 1.0. Il a cependant été créer quand le 787 était encore un prototype, il ne montrait pas plusieurs fonctionnalité du 787 actuel, comme un cockpit et des instruments fidèle au vrai 787.<br />
Le nouveau 787 est un projet de la communauté qui offre un nouveau FDM JSBSim, la navigation verticale, un glass cockpit réaliste, un nouveau FMC, TCAS, sac de vol numérique, écran de navigation sophistiqué, VSD et le [[Howto:_Implement a Fly-By-Wire System for Airliners|Fly-by-wire]]. Le projet est encore en développement.<br />
<br />
Pour en savoir plus, visitez l'article sur le wiki FlightGear: [[Boeing 787-8 Dreamliner|its wiki article]]. Un des points positif de ce projet est que la majorité des découvertes et ressources ont été convertis en How-to pour le wiki, pour que d'autre développeur l'utilise dans leurs projets.<br />
<br />
==== Cessna 337G Skymaster ====<br />
[[File:Cessna337-cockpit.png|thumb|200px|General view of the new Cessna 337G Skymaster cockpit]]<br />
Le [[Cessna 337G Skymaster]] de la communauté espagnole «Vive FlightGear» à reçu une mise-à-jour majeure.<br />
<br />
Le cockpit est maintenant complètement modelé, avec presque tout les boutons fonctionnel et animé. Il sont aussi bien identifié. Il profite aussi de nouveau sons, lumières, contrôle, un avionique Bendix/King capable de navigation IFR et de nuit, deux nouvelles livrés et le premier ELT(Emergency Locator Transmitter).<br />
<br />
== Le coin des scènes ==<br />
=== 3D-Model contributors: please read ===<br />
A (long) time ago, specific instructions were given on how to contribute with 3D-models designing withing FG. That is: I want to create nice 3D models for my airport, submit them to the central database, and have them shipped back through Terrasync.<br />
However, it appears that quite a lot of users are still not aware of those guidelines, and sometimes learn about their existence after having created their models.<br />
So please, take some time to (re)read them, and inform the people around you who would like to contribute about the existence of those guidelines. This will save you extra time (and your models will be quickly inserted within the database) and this will also save the (precious) times of the poor guy(s) validating all the models at the other end.<br />
So, here they are: http://scenemodels.flightgear.org/contribute.php .<br />
We also remind you that, to add, edit or delete shared model positions (apart from mass import (that is if you have more than let's say 10 lines to add), you should use our webtools at http://scenemodels.flightgear.org/submission/ .<br />
<br />
=== Object-masking and improved materials ===<br />
For a long time, FlightGear has had the ability to place random objects on the scenery. Previously, these objects were placed completely randomly based on a specific density for the material, defined in materials.xml. This didn't look particularly realistic as the placement never matched the underlying texture. Now object and trees can be placed using a "mask", so buildings will only appear where the texture shows buildings, and trees only in green spaces. Additionally, placement is controlled so that random buildings won't overlap with other random buildings, and buildings don't overlap onto adjacent piece of scenery. This makes the random objects appear more realistic, and moves FG one step closer to the auto-gen scenery of MSFS and X-Plane. Further details can be found in fgdata/Docs/README.materials and on on the [[Howto: Editing tile textures and materials]].<br />
<br />
In addition to this, the materials.xml and materials-dds.xml files have been restructured to make them more maintainable, fixing a number of bugs in the process.<br />
<br />
=== Gratte-ciel de Shanghai ===<br />
Shanghai est une des plus grande ville de Chine et une des villes avec le plus grands nombres de gratte-ciel. Maintenant, cela est aussi vrai pour FlightGear. 25 modèles ont été créé dans les derniers mois par JVC, qui à aussi modelé le pont Akashi-Kaikyo au Japon et le bâtiment des Nations-unies a New-York.<br />
{|<br />
|[[File:SH fgfs-screen-001.png|250px|thumb|A view of the Shanghai skyline]]<br />
|[[File:Shanghai003.png|250px|thumb|Another view of Shanghai]]<br />
|[[File:Shanghai007.png|250px|thumb|A closer view from near the Shanghai Stock Exchange]]<br />
|}<br />
<br />
=== Nouvelle textures pour les portes-conteneur et les bateaux cargos ===<br />
À partir d'un panorama haute résolution qu'il a fait, Critian Marchi(aka penta) a fourni des nouvelles textures pour les deux bateaux AI qui peuple les océans de FlightGear. Pour plus d'information, visitez le sujet sur le forum: [http://www.flightgear.org/forums/viewtopic.php?f=23&t=14856].<br />
{|<br />
|[[File:Ships-comparison.png|200px|thumb|left|Comparison between untextured and textured AI ships (by Cristian Marchi)]]<br />
|}<br />
<br />
=== Scènes photo réaliste ===<br />
Il y a maintenant des scènes photo réaliste pour certain endroit au États-Unis, disponible à cette adresse: http://fgphotoscenery.square7.ch/ Les regions couvertes sont la baie de San-Francisco, Yosmenite, le Grand Canyon, Lake Powell, Sedona, Miami, Everglades et Key Largo. La scène a été créé avec les images du [http://www.usgs.org U.S. Geological Survey]qui sont sous licence GNU GPL. Elles ont une résolution de 3m/pixel. Un total de 1.3 GB d'image son disponible au téléchargement. Vidéos de l'UFO volant dans les scènes: [http://fgphotoscenery.square7.ch#gallery gallery]. <br />
Pour être capable de charger les images dans FlightGear, le programme doit être compiler à partir des sources et le patch de Benoît Laniel pour la scène photo réaliste de Brest doit être appliqué. Des instruction détaillé sont disponible:[http://fgphotoscenery.square7.ch#installation installation instructions] for this process are provided.<br />
<br />
Discussion: [http://www.flightgear.org/forums/viewtopic.php?f=5&t=15174 forum thread].<br />
<br />
[[File:fgphotoscenery_gallery.jpg]]<br />
<br />
== L'Avion du mois ==<br />
Le [[Boeing 787-8 Dreamliner]] a été grandement améliorer, comme vous avez pu le lire dans cette newsletter. Le 787 est l'avion du mois de Février.<br />
{{#ev:youtube|WlzEoCsJvz4|400|Aircraft of the Month - Boeing 787-8}}<br />
<br />
== L'aéroport du mois ==<br />
<br />
[[File:LFRJ.png|800px]]<br />
<br />
La [[Landivisiau Naval Air Base|Base d'aéronautique navale de Landivisiau]] (LFRJ) est au milieu d'une scène formidable. Si quelqu'un veux essayer le vol [[VFR]] l devrait le faire ici, en Bretagne en France. Mémoriser la scène, les églises, les lignes électriques et mettez les sur une carte et essayer de retrouver votre chemin. L'aéroport est la base pour les avions qui vont à la mer, c'est pourquoi vous retrouverez deux cable d'arrêt sur la piste, ne trébucher par dessus. L'aéroport aussi la base pour des hélicoptères comme le Super Frelon et le Westland Lynx. L'aéroport à une tour de contrôle modelé, des entrepôts et les abris pour le Rafale.<br />
<br />
== La capture d'écran du mois ==<br />
<br />
[[File: Lightfield-1.1-14.jpg | 800px]]<br />
<br />
Un P-51D volant à 20 000 pieds au-dessus de Juneau (Alaska) à l'aube avec les lightfield shaders pour rendre le lever du soleil. (Téléchargements des shaders: [http://www.flightgear.org/forums/viewtopic.php?f=47&t=14755 ici] ).<br />
<br />
== Suggestion de vol ==<br />
===Copacabana à San Rafael au-dessus du lac Titicaca===<br />
De la Bolivie au Pérou, le voyage va vous amenez au-dessus d'un des lacs le plus haut et le plus profond dans le monde vers un des aéroports le plus haut du monde. C'est une démonstration du vol [[IFR]] via un FIX et démontre comment FlightGear simule les effets de la densité d'air sur un avion.<br />
[[File:Slcc-sprf.jpg|thumb|200px|left|Flight and fix SLCC to SPRF]]<br />
Placez votre avion sur l'aéroport de Copacabana (SLCC) qui est situé à une hauteur de 12 593 pieds. FlightGear va mettre de la neige tout autour, mais ce n'est pas très réaliste, donc réglons cela: <br />
View=> Rendering Options=> Snow line=> Set to max. (5,000M). <br />
<br />
Nous allons voler vers et atterrir à SPRF. Préparation de l'équipement. Configurer le NAV1 sur le VOR-DME Juliaca sur 155.55 avec un radial de 311° (Magnétique). Configurer le NAV2 sur le VOR-DME Arequipa sur 113.7 avec un radial de 212°. Pendant le vol, nous allons voler avec la vrai altitude (Par rapport au niveau de la mer). Configuré bien votre altimètre et garder le a jour. Configurer le pilote automatique avec le cap 311° et un altitude initial de 13 500 pieds.<br />
<br />
Décollez et si vous avez pris la mauvaise piste, tiré fort sur le manche. Faite un petit tour au-dessus du [http://en.wikipedia.org/wiki/Titicaca lac Titicaca], regarder les îles flottantes et essayer de trouver le trésor d'or perdu. Intercepté le radial le plus proche sur le NAV1 vers Juliaca (Environ 311). <br />
<br />
Juste avant Juliaca, il y a une montagne, donc quand vous êtes sur le lac, montez à 14 200 pieds, la partie [[VFR]] est terminé. Après avoir passé Juliaca, fixé le radial du NAV1 a 353° et configurer l'altitude à 17 422 pieds. Nous allons voler à partir du NAV1 et monter tranquillement.<br />
<br />
À une distance de 60 NM, fixé le cap sur le cap actuel. Vérifiez la distance du NAV1, le radial du NAV2 et sa distance. À une distance de 74.5 NM du NAV1 et 140.7 NM du NAV2 et l'interception du radial du NAV2, la piste devrait être la. Donc à partir de 60 NM, commencez à regarder par la fenêtre, à NAV1 et NAV2.<br />
<br />
Si vous êtes à 80 NM de NAV1, vous avez manqué la piste, mais vous n'allez pas frapper de montagne (sauf si vous avez tourné à gauche). Tournez à droite et mettez le cap a 172°, volez vers le NAV1 et interceptez le radial 352° à 50 NM. Répétez la recherche.<br />
<br />
La piste de SPRF, San Rafael, est à une altitude de 14 422 pieds et un cap de 297°/117°. Notre altitude à été configurer 3 000 pieds au-dessus de la piste. Ceci devrait être suffisant pour la navigation.<br />
Après que vous avez vu la piste, fixé le radial du NAV1 à 297°, le cap de la piste, comme aide visuel. Atterrissez sur la piste 30. Il y a une petite colline en face de la piste 30.<br />
<br />
Réduire sa vitesse à cette altitude n'est pas facile. L'air n'offre pas beaucoup de résistance. La différence entre la vitesse air indiqué et la vitesse sol est grande. La vitesse sol est beaucoup plus haute que la vitesse air indiqué.<br />
<br />
Après un atterrissage réussi, vous pouvez tentez de trouver l'origine du Fleuve Amazone, car nous sommes au point de départ de ce vol: [[Suggested_Flights#Origin_of_the_Amazon_River | origin of the Amazon river]] s<br />
<br />
*More places you can visit can be found at [[Suggested Flights]].<br />
<br />
== Wiki updates ==<br />
=== Categorizing images ===<br />
[[User:Johan G|Johan G]] did a great job starting to categorise all images. The sub-categories are listed under [[:Category:Images]]. <br />
<br />
Please keep the following things in mind when uploading images:<br />
* Give the file a descriptive name. That'll make it easier for others to find your file and use it in articles.<br />
* Categorize your image right when you upload it. That saves others from digging up uncategorized images later on. Placing your image in a category is as simple as adding the following line to the "description" field:<br />
: <code><nowiki>[[Category:Name of the category]]</nowiki></code><br />
: A list of available categories can be found under [[:Category:Images]].<br />
<br />
=== Documentating templates ===<br />
[[User:Gijs|Gijs]] documentated most [[:Category:Templates|templates]], making use of a global [[Template:Informative template|documentation template]]. The documentation tells you what the template does and how to use it.<br />
<br />
=== Feature icons ===<br />
Michat has designed small logos for Airport of the Month, Screenshot of the Month, Aircraft of the Month, [[Dual Control]], [[Bombable]], [[Soaring]], [[Howto:_Do_aerotow_over_the_net|Aerotow]], [[Howto:_Aerial_refueling|Air refueling]] and [[:Category:Aerospace|Aerospace]] aircraft, allowing you to see at a glance which aircraft has some of those interesting features.<br />
<br />
[[File:Dualcontrolready2.png|Dual_control]] [[File:BombableReady.png|Bombable]] [[File:Aerotowready.png|Doing aerotow over the net]] [[File:Thermalready.png|Soaring]] [[File:Spacetripready.png|Aerospace]]<br />
[[File:Aircraftofthemonth.png|IAR80]] [[File:Airrefuelingready.png]] [[File:Airportofthemonth.png]] [[File:Screenshotofthemonth.png]].<br />
<br />
== Nouvelles de la communauté ==<br />
=== FlightGear sur FSBreak ===<br />
Deux développeur de FlightGear, Stuart et Curt ont été interviewé sur un épisode de FSBreak, enregistré le 25 Février. FSBreak est un podcast sur la simulation de vol. Les animateurs Eric et Brendan, on pris près de 1 heure pour parler du projet FlightGear. Vous pouvez l'écouter ici: [http://www.fsbreak.net/podcast/2012/3/2/fsbreak-107-we-talk-flightgear-and-accufeel-released.html this link].<br />
<br />
=== FlightGear on YouTube ===<br />
* [http://youtu.be/hBEaOMzBq6E KSFO Thermal Demo] by MD-BFC Going on their way for Bocian certification<br />
* [http://youtu.be/-yI5PzC5RE8 Sukhoi 37 'The russian dream'] by Águilas de FlightGear performing "Balalaika amok" master tune by Aleksei Arkhipovsky.<br />
<br />
=== Forum news ===<br />
Triggered by the new release, we've had more [http://flightgear.org/forums forum] visitors then ever before in the week of 19-25 February! 17,123 people visited the forum in these seven days to be precise. When looking at "unique visitors", only 13-19 February 2011 was a busier week (9548 against 9076 visitors) (a possible reason for the high number might be that people expected 2.2.0 to be released, which was canceled).<br />
<br />
== And finally ... ==<br />
=== Contributing ===<br />
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
=== Call for volunteers ===<br />
* The [[OpenRadar]] project is looking for a new maintainer.<br />
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.<br />
<br />
=== Did you know ===<br />
...that you can use expressions to create complex animations of objects in your 3d models or even drive them from multiple properties?<br />
Usually, an animation looks like this<br />
<syntaxhighlight lang="xml"><br />
<animation><br />
<type>translate</type><br />
<property>foo/bar</property><br />
[..]more elements[..]<br />
</animation><br />
</syntaxhighlight><br />
You can add a scaling factor or an offset to it, but that's basically all you can do that way. <br />
If you want to animate your object following a complex function, most people create complex Nasal scripts to compute the driving properties, probably not knowing that there is another way to achieve the goal: Expressions. <br />
Here is an example for a translate animation depending on two properties and the cosine function<br />
<syntaxhighlight lang="xml"><br />
<animation><br />
<type>translate</type><br />
<expression><br />
<product><br />
<property>/my/factor-property</property><br />
<cos><br />
<deg2rad><br />
<property>/my/angular-property</property><br />
</deg2rad><br />
</cos><br />
</product><br />
</expression><br />
[..]more elements[..]<br />
</animation><br />
</syntaxhighlight><br />
A rich set of predefined functions is available, including almost all those you have on your scientific pocket calculator.<br />
<br />
[[Category:FlightGear Newsletter|2012 02]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=Fr/Nouvelles_du_projet_FlightGear_-_f%C3%A9vrier_2012&diff=43741Fr/Nouvelles du projet FlightGear - février 20122012-03-05T09:01:23Z<p>Blackiris: /* FlightGear 2.6.0 est sorti */</p>
<hr />
<div>{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
''Nous voudrions insister sur le fait que cette newsletter ne peut pas vivre sans les contributions des utilisateurs et développeurs de FlightGear. Il suffit d'ouvrir un compte sur ce wiki pour l'éditer et toutes les contribution sont les bienvenues. Si vous avez connaissance de nouveautés dans FlightGear ou dans un projet parent, comme les avions ou les terrains, vous êtes invité à les partager en éditant cette newsletter.<br />
<br />
== FlightGear 2.6.0 est sorti ==<br />
<br />
Selon notre [[http://wiki.flightgear.org/Release_plan feuille de route]], la version 2.6.0 de notre simulateur est maintenant disponible ! Cette version apporte plusieurs nouvelles fonctionnalités, des améliorations et des correction de bugs. Les grandes améliorations depuis la version 2.4 sont le temps de chargement réduit pour le traffic AI, des ajustements de l'affichage plus faciles, un traffic AI plus sophistiqué et une utilisation plus aisée. Regardez [http://www.flightgear.org/news/flightgear-v2-6-0-released/ l'annonce de la sortie] pour les détails complets des changements effectués depuis la dernière sortie il y a 6 mois.<br />
<br />
Le téléchargement est disponible sur [[http://www.flightgear.org/download/ notre site web]].<br />
<br />
Pour le moment, nous n'avons pas assez de retours de la communauté sur cette version 2.6.0. Votre aide pour mettre à jour ce wiki serait très appréciée. Veuillez regarder les [[Hardware Recommendations | recommandations matérielles]] et les [[Notebooks known to run FlightGear#FlightGear_2.6.0_systems | notebooks connus pour faire tourner FlightGear 2.6.0]].<br />
<br />
== Nouvelles du developpement ==<br />
=== Projet Rembrandt ===<br />
Comme plusieurs on pu le constater, Fred a fait des gros progrès pour ajouter des ombres dans FlightGear avec le [[Project Rembrandt]]. Maintenant, F-JJTH a porté le P92 pour utiliser le nouveau système et a posté une vidéo YouTube qui montre le [[Project Rembrandt]] en action. Parlez-en sur le [http://flightgear.org/forums/viewtopic.php?f=47&t=14883 Forum FlightGear].<br />
<br />
{|<br />
|{{#ev:youtube|v02phoOqWHE|400|Project Rembrandt at work}}<br />
|[[File:Project-rembrandt-cockpit-lighting.png|600px|Cockpit lighting in Project Rembrandt at work (by F-JJTH)]]<br />
|}<br />
<br />
== Interview avec un contribueur: Christian Schmitt ==<br />
''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]]!''<br />
<br />
'''[http://www.flightgear.org/contributors/ Read this and previous interviews at our website's archive].'''<br />
<br />
* '''C'est quoi ton nom sur le forum et l'IRC?'''<br />
Surprise, c'est papillon81. Oui je suis un homme :)<br />
* '''Depuis combien de temps tu t'implique dans FlightGear?'''<br />
Si je me fie au correspondance de courriel, j'ai commencé à être actif vers 2007/2008. Je n'était pas satisfait de l'état de le scène de l'aéroport EDDF(Frankfurt) dans FlightGear(pas de bâtiment,des poteau de lumière partout), j'ai fait équipe avec quelqu'un qui avait déjà commencé du travail sur cet aéroport. J'ai fini de créer tout les bâtiments du Terminal et améliorer la disposition de l'aéroport. A ce moment, peu de pilote volait là. Ceci a changé quelques mois après, ça été bon pour ma motivation.<br />
* '''Qu'est-ce qui t'intéresse le plus dans FlightGear?'''<br />
Ce qui m'intéresse le plus est définitivement les scènes et les technologies qui les entoures, comme GIS. J'ai commencé à créer des scènes supplémentaires, comme Helgoland. Par la suite, j'ai été autorisé à accéder à la base de données Mapserver, j'étais capable de modifier le travail des autres qui arrivait. Le meilleur FDM(Flight Dynamics Model) ou avion ne serve à rien si tu n'as pas d'endroit convenable pour voler, décoller et atterrir avec. C'est donc ce domaine qui m'intéresse le plus. <br />
IJe maintient aussi les paquets pour la distribution Linux Gentoo (ebuilds) pour la version GIT de FlightGear, SimGear et TerraGear. Ont les trouvent dans les dépots Gentoo Gamerlay.<br />
* '''Sur quel projet tu travail en ce moment?'''<br />
Il y a quelques mois, j'en avais marre de FlightGear, car j'étais incapable de lire apt.dat 850 data. J'ai donc commencé à regarder le code de TerraGear. Je n'avais aucune expérience avec le C++. C'était un apprentissage difficile, mais à ma grande surprise, j'ai été capable de convertir l'analyseur de TerraGear pour qu'il peut lire les données des pistes et d'autres fonctionnalité du nouveau format de fichier. J'ai commencé a implanter le plus de fonctionnalité qu'il était possible pour moi d'intégrer. Heureusement, Pete travaillait déjà sur les fonctionnalités pour les voies de circulations et la surface. Nous avons donc fusionné notre travail. Ça été un projet très constructif pour mon apprentissage et pour améliorer FlightGear. J'espère qu'il sera utilisé pour la prochaine version de la scène de FlightGear. Avant que cela arrive, nous avons de plus de testeurs.<br />
* '''Sur quoi prévoie-tu travailler dans le future?'''<br />
Je vais continuer de travailler sur TerraGear, améliorer le concorde(Mon avion favoris dans FlightGear) et m'occuper des demandes de fusion. J'aimerais aussi plonger encore plus dans le code de FlightGear/SimGear et faire quelques ajustements. Voyons ce que le future apportera :)<br />
* '''Est-tu heureux avec la direction que projet FlightGear prends?'''<br />
IJe suis vraiment satisfait avec. Les améliorations des 2 dernières années sont à couper le souffle. C'est vraiment impressionnant parfois, les fonctionnalité sur les quelles certains peuvent travailler, comme le projet Rembrandt. Le travail mit dans le système de météo et de shader, est vraiment impressionnant.<br />
* '''Qu'est-ce que tu aime le plus à propos du développement de FlightGear?'''<br />
Le fait que tout le monde se supporte et que nous avons une forte communauté avec beaucoup de gens compétent dans divers domaines. Savoir que tu peut construire sur le travail des autres que tu va pouvoir avoir de l'aide cas de problème. J'aime beaucoup le cannal IRC de FlightGear.<br />
<br />
* '''Quel conseil donnerais-tu a un nouveau développeur qui veut commencer à travailler sur son premier avion/fonctionnalité/Script Nasal?'''<br />
Tout d'abord, il devrait avoir de l'expérience avec FlightGear en général, il devrait avoir utiliser le logiciel quelques temps. Nous avons souvent des gens qui posent des questions qu'ils auraient pu répondre eux-mêmes s'ils aurait un peu utiliser FlightGear avec différents appareils. Si il a identifié une zone où il veut commencer à développer, il devrait contacté le mainteneur et demandé des conseils avant d'investir plusieurs heures de travail.<br />
'''[http://www.flightgear.org/contributors/ Read this and previous interviews at our website's archive].'''<br />
<br />
== Dans le hangar ==<br />
En mai 2011, nous avons introduit un nouveau système d'évaluation pour le statut des avions. Jusqu'à maintenant, très peu on été évalué, comme un peu voir sur la page de téléchargements des avions:[http://www.flightgear.org/download/aircraft-v2-6/ aircraft download page]. I. Si vous êtes un développeur d'un appareil et que votre appareil n'est pas sur la liste, considérer de l'évaluer son statut. Tout ce que vous avez besoin de faire et de savoir est disponible sur cette page: [http://wiki.flightgear.org/Formalizing_Aircraft_Status]<br />
<br />
=== Un nouvel instrument: Affichage de la situation verticale (VSD) ===<br />
[[File:Omega95-vsd-instrument.jpeg|200px|thumb|Omega95's VSD instrument]]<br />
Omega95 a créé un tout nouveau type instrument qui montre la pente de montée ou de descente ainsi que le terrain. Cet instrument a été entièrement réalisé en Nasal et en animation XML. Il a prouvé qu'il était possible de créer des instruments complexes dans l'espace de script. Il a apparemment réalisé ceci en moins de 24 heures. Sa première question relier à ce projet était comment accéder au fonction trigonométrique, à partir de Nasal, peu de temps après, il a posté des captures d'écrans montrant son VSD.<br />
<br />
Pour lire la discussion au complet, visiter le sujet sur le forum [http://flightgear.org/forums/viewtopic.php?f=30&t=15200 the forum topic]. Il y a du travail pour transformer son travail en tutoriel pour le wiki sur la création d'instrument complexe dans l'espace de script [[Howto: Implement a Vertical Situation Display in Nasal]].<br />
<br />
=== Treuil de remorquage pour planeur ===<br />
[[File:DG-101G_winch_launch_with_rope.png|thumb|200px|A DG-101G during a winch launch.]]<br />
Avant maintenant, FlightGear ne montrait pas le cable pendant le lancement avec le treuil de remorquage. Maintenant, vous n'aurez plus à voler un planeur remorquer par un cable invisible qui vous relie au treuil. <br />
<br />
[[User:Gijs|Gijs]] à commencer à travailler sur un cable animer en 3d attacher au planeur et au treuil. The cable exist of the following parts:<br />
<br />
* '''Strop''' (3 m) attached to the glider with a ring.<br />
* '''Weak link assembly''' designed to break apart before the cable or any other equipment fails.<br />
* '''Trace''' (17 m)<br />
* '''Parachute''' so the cable doesn't drop too quickly after releasing.<br />
* '''Launch cable''' the longest part; all the way to the winch.<br />
<br />
=== Nouveaux avions ===<br />
[[File:Harrier-GR1 Splash.png|thumb|left|200px|Harrier GR.1 splash screen]]<br />
[[File:RAH-66 splash.png|thumb|200px|RAH-66 splash screen]]<br />
==== Hawker Siddeley Harrier GR.1 ====<br />
[[Hawker Siddeley Harrier GR1]] est un projet de pjedvaj, il n'a pas l'intention de remplacer le [[British Aerospace Harrier]] déjà existant. Il a un modèle 3D détaillé et complet avec un cockpit, des animations et une livré de la RAF. Les instruments et le HUD sont assez authentique. L'avion a des armes fonctionnel et un contrôle du poids et carburant de base. Le FDM est adapté du BAe Harrier original, mais les réservoirs externes et internes sont adapté pour le GR.1<br />
==== Boeing-Sikorsky RAH-66 Commanche ====<br />
Le [[Boeing-Sikorsky RAH-66 Commanche]] à été commencé par une prime offert par sgofferj et développer par pjedvaj mais il s'est, plus tard, retiré de la prime. C'était son premier projet d'hélicoptère et le FDM est très peu développer et ce base sur celui de Tatsuhiro Nishioka's pour le Kawasaki OH-1. Il un modèle 3D détaillé, des animations et deux livrés. L'hélicoptère a un canon fonctionnel contrôlé par joystick et un contrôle basique du poids pour l'armement. Vous êtes libre de continuer le développement et de réclamer la prime.<br />
<br />
=== Avions mis-à-jour ===<br />
==== Airwave Xtreme 150 ====<br />
[[File:Airwave Xtreme 150 Innsbruck.png|thumb|200px]]<br />
HDans le hangar de FlightGear depuis 2002, le seul deltaplane de FlightGear à maintenant un pilote animé. D-NXKT a fait un travail formidable. Il a créer des movements du corps réaliste pour le pilote du [[Airwave Xtreme 150]]ar le modèle était invisible à cause du passage de FlightGear à OpenSceneGraph. Par la suite, il est prévue de créer un FDM JSBSim. Ceci permettra au deltaplane d'intéragir avec la météo et l'environnement. Merci à la flexibilité de JSBSim, le transfert de poids peu être simuler de façon très réaliste.<br />
<br />
More to follow in future newsletters.<br />
<br />
==== Boeing 787-8 Dreamliner ====<br />
[[File:boeing-787-8-splash.png|thumb|200px|The Boeing 787-8 Splash Screen]]<br />
Le [[Boeing 787-8 Dreamliner]] st dans le hangar de FlightGear depuis la version 1.0. Il a cependant été créer quand le 787 était encore un prototype, il ne montrait pas plusieurs fonctionnalité du 787 actuel, comme un cockpit et des instruments fidèle au vrai 787.<br />
Le nouveau 787 est un projet de la communauté qui offre un nouveau FDM JSBSim, la navigation verticale, un glass cockpit réaliste, un nouveau FMC, TCAS, sac de vol numérique, écran de navigation sophistiqué, VSD et le [[Howto:_Implement a Fly-By-Wire System for Airliners|Fly-by-wire]]. Le projet est encore en développement.<br />
<br />
Pour en savoir plus, visitez l'article sur le wiki FlightGear: [[Boeing 787-8 Dreamliner|its wiki article]]. Un des points positif de ce projet est que la majorité des découvertes et ressources ont été convertis en How-to pour le wiki, pour que d'autre développeur l'utilise dans leurs projets.<br />
<br />
==== Cessna 337G Skymaster ====<br />
[[File:Cessna337-cockpit.png|thumb|200px|General view of the new Cessna 337G Skymaster cockpit]]<br />
Le [[Cessna 337G Skymaster]] de la communauté espagnole «Vive FlightGear» à reçu une mise-à-jour majeure.<br />
<br />
Le cockpit est maintenant complètement modelé, avec presque tout les boutons fonctionnel et animé. Il sont aussi bien identifié. Il profite aussi de nouveau sons, lumières, contrôle, un avionique Bendix/King capable de navigation IFR et de nuit, deux nouvelles livrés et le premier ELT(Emergency Locator Transmitter).<br />
<br />
== Le coin des scènes ==<br />
=== 3D-Model contributors: please read ===<br />
A (long) time ago, specific instructions were given on how to contribute with 3D-models designing withing FG. That is: I want to create nice 3D models for my airport, submit them to the central database, and have them shipped back through Terrasync.<br />
However, it appears that quite a lot of users are still not aware of those guidelines, and sometimes learn about their existence after having created their models.<br />
So please, take some time to (re)read them, and inform the people around you who would like to contribute about the existence of those guidelines. This will save you extra time (and your models will be quickly inserted within the database) and this will also save the (precious) times of the poor guy(s) validating all the models at the other end.<br />
So, here they are: http://scenemodels.flightgear.org/contribute.php .<br />
We also remind you that, to add, edit or delete shared model positions (apart from mass import (that is if you have more than let's say 10 lines to add), you should use our webtools at http://scenemodels.flightgear.org/submission/ .<br />
<br />
=== Object-masking and improved materials ===<br />
For a long time, FlightGear has had the ability to place random objects on the scenery. Previously, these objects were placed completely randomly based on a specific density for the material, defined in materials.xml. This didn't look particularly realistic as the placement never matched the underlying texture. Now object and trees can be placed using a "mask", so buildings will only appear where the texture shows buildings, and trees only in green spaces. Additionally, placement is controlled so that random buildings won't overlap with other random buildings, and buildings don't overlap onto adjacent piece of scenery. This makes the random objects appear more realistic, and moves FG one step closer to the auto-gen scenery of MSFS and X-Plane. Further details can be found in fgdata/Docs/README.materials and on on the [[Howto: Editing tile textures and materials]].<br />
<br />
In addition to this, the materials.xml and materials-dds.xml files have been restructured to make them more maintainable, fixing a number of bugs in the process.<br />
<br />
=== Gratte-ciel de Shanghai ===<br />
Shanghai est une des plus grande ville de Chine et une des villes avec le plus grands nombres de gratte-ciel. Maintenant, cela est aussi vrai pour FlightGear. 25 modèles ont été créé dans les derniers mois par JVC, qui à aussi modelé le pont Akashi-Kaikyo au Japon et le bâtiment des Nations-unies a New-York.<br />
{|<br />
|[[File:SH fgfs-screen-001.png|250px|thumb|A view of the Shanghai skyline]]<br />
|[[File:Shanghai003.png|250px|thumb|Another view of Shanghai]]<br />
|[[File:Shanghai007.png|250px|thumb|A closer view from near the Shanghai Stock Exchange]]<br />
|}<br />
<br />
=== Nouvelle textures pour les portes-conteneur et les bateaux cargos ===<br />
À partir d'un panorama haute résolution qu'il a fait, Critian Marchi(aka penta) a fourni des nouvelles textures pour les deux bateaux AI qui peuple les océans de FlightGear. Pour plus d'information, visitez le sujet sur le forum: [http://www.flightgear.org/forums/viewtopic.php?f=23&t=14856].<br />
{|<br />
|[[File:Ships-comparison.png|200px|thumb|left|Comparison between untextured and textured AI ships (by Cristian Marchi)]]<br />
|}<br />
<br />
=== Scènes photo réaliste ===<br />
Il y a maintenant des scènes photo réaliste pour certain endroit au États-Unis, disponible à cette adresse: http://fgphotoscenery.square7.ch/ Les regions couvertes sont la baie de San-Francisco, Yosmenite, le Grand Canyon, Lake Powell, Sedona, Miami, Everglades et Key Largo. La scène a été créé avec les images du [http://www.usgs.org U.S. Geological Survey]qui sont sous licence GNU GPL. Elles ont une résolution de 3m/pixel. Un total de 1.3 GB d'image son disponible au téléchargement. Vidéos de l'UFO volant dans les scènes: [http://fgphotoscenery.square7.ch#gallery gallery]. <br />
Pour être capable de charger les images dans FlightGear, le programme doit être compiler à partir des sources et le patch de Benoît Laniel pour la scène photo réaliste de Brest doit être appliqué. Des instruction détaillé sont disponible:[http://fgphotoscenery.square7.ch#installation installation instructions] for this process are provided.<br />
<br />
Discussion: [http://www.flightgear.org/forums/viewtopic.php?f=5&t=15174 forum thread].<br />
<br />
[[File:fgphotoscenery_gallery.jpg]]<br />
<br />
== L'Avion du mois ==<br />
Le [[Boeing 787-8 Dreamliner]] a été grandement améliorer, comme vous avez pu le lire dans cette newsletter. Le 787 est l'avion du mois de Février.<br />
{{#ev:youtube|WlzEoCsJvz4|400|Aircraft of the Month - Boeing 787-8}}<br />
<br />
== L'aéroport du mois ==<br />
<br />
[[File:LFRJ.png|800px]]<br />
<br />
La [[Landivisiau Naval Air Base|Base d'aéronautique navale de Landivisiau]] (LFRJ) est au milieu d'une scène formidable. Si quelqu'un veux essayer le vol [[VFR]] l devrait le faire ici, en Bretagne en France. Mémoriser la scène, les églises, les lignes électriques et mettez les sur une carte et essayer de retrouver votre chemin. L'aéroport est la base pour les avions qui vont à la mer, c'est pourquoi vous retrouverez deux cable d'arrêt sur la piste, ne trébucher par dessus. L'aéroport aussi la base pour des hélicoptères comme le Super Frelon et le Westland Lynx. L'aéroport à une tour de contrôle modelé, des entrepôts et les abris pour le Rafale.<br />
<br />
== La capture d'écran du mois ==<br />
<br />
[[File: Lightfield-1.1-14.jpg | 800px]]<br />
<br />
Un P-51D volant à 20 000 pieds au-dessus de Juneau (Alaska) à l'aube avec les lightfield shaders pour rendre le lever du soleil. (Téléchargements des shaders: [http://www.flightgear.org/forums/viewtopic.php?f=47&t=14755 ici] ).<br />
<br />
== Suggestion de vol ==<br />
===Copacabana à San Rafael au-dessus du lac Titicaca===<br />
De la Bolivie au Pérou, le voyage va vous amenez au-dessus d'un des lacs le plus haut et le plus profond dans le monde vers un des aéroports le plus haut du monde. C'est une démonstration du vol [[IFR]] via un FIX et démontre comment FlightGear simule les effets de la densité d'air sur un avion.<br />
[[File:Slcc-sprf.jpg|thumb|200px|left|Flight and fix SLCC to SPRF]]<br />
Placez votre avion sur l'aéroport de Copacabana (SLCC) qui est situé à une hauteur de 12 593 pieds. FlightGear va mettre de la neige tout autour, mais ce n'est pas très réaliste, donc réglons cela: <br />
View=> Rendering Options=> Snow line=> Set to max. (5,000M). <br />
<br />
Nous allons voler vers et atterrir à SPRF. Préparation de l'équipement. Configurer le NAV1 sur le VOR-DME Juliaca sur 155.55 avec un radial de 311° (Magnétique). Configurer le NAV2 sur le VOR-DME Arequipa sur 113.7 avec un radial de 212°. Pendant le vol, nous allons voler avec la vrai altitude (Par rapport au niveau de la mer). Configuré bien votre altimètre et garder le a jour. Configurer le pilote automatique avec le cap 311° et un altitude initial de 13 500 pieds.<br />
<br />
Décollez et si vous avez pris la mauvaise piste, tiré fort sur le manche. Faite un petit tour au-dessus du [http://en.wikipedia.org/wiki/Titicaca lac Titicaca], regarder les îles flottantes et essayer de trouver le trésor d'or perdu. Intercepté le radial le plus proche sur le NAV1 vers Juliaca (Environ 311). <br />
<br />
Juste avant Juliaca, il y a une montagne, donc quand vous êtes sur le lac, montez à 14 200 pieds, la partie [[VFR]] est terminé. Après avoir passé Juliaca, fixé le radial du NAV1 a 353° et configurer l'altitude à 17 422 pieds. Nous allons voler à partir du NAV1 et monter tranquillement.<br />
<br />
À une distance de 60 NM, fixé le cap sur le cap actuel. Vérifiez la distance du NAV1, le radial du NAV2 et sa distance. À une distance de 74.5 NM du NAV1 et 140.7 NM du NAV2 et l'interception du radial du NAV2, la piste devrait être la. Donc à partir de 60 NM, commencez à regarder par la fenêtre, à NAV1 et NAV2.<br />
<br />
Si vous êtes à 80 NM de NAV1, vous avez manqué la piste, mais vous n'allez pas frapper de montagne (sauf si vous avez tourné à gauche). Tournez à droite et mettez le cap a 172°, volez vers le NAV1 et interceptez le radial 352° à 50 NM. Répétez la recherche.<br />
<br />
La piste de SPRF, San Rafael, est à une altitude de 14 422 pieds et un cap de 297°/117°. Notre altitude à été configurer 3 000 pieds au-dessus de la piste. Ceci devrait être suffisant pour la navigation.<br />
Après que vous avez vu la piste, fixé le radial du NAV1 à 297°, le cap de la piste, comme aide visuel. Atterrissez sur la piste 30. Il y a une petite colline en face de la piste 30.<br />
<br />
Réduire sa vitesse à cette altitude n'est pas facile. L'air n'offre pas beaucoup de résistance. La différence entre la vitesse air indiqué et la vitesse sol est grande. La vitesse sol est beaucoup plus haute que la vitesse air indiqué.<br />
<br />
Après un atterrissage réussi, vous pouvez tentez de trouver l'origine du Fleuve Amazone, car nous sommes au point de départ de ce vol: [[Suggested_Flights#Origin_of_the_Amazon_River | origin of the Amazon river]] s<br />
<br />
*More places you can visit can be found at [[Suggested Flights]].<br />
<br />
== Wiki updates ==<br />
=== Categorizing images ===<br />
[[User:Johan G|Johan G]] did a great job starting to categorise all images. The sub-categories are listed under [[:Category:Images]]. <br />
<br />
Please keep the following things in mind when uploading images:<br />
* Give the file a descriptive name. That'll make it easier for others to find your file and use it in articles.<br />
* Categorize your image right when you upload it. That saves others from digging up uncategorized images later on. Placing your image in a category is as simple as adding the following line to the "description" field:<br />
: <code><nowiki>[[Category:Name of the category]]</nowiki></code><br />
: A list of available categories can be found under [[:Category:Images]].<br />
<br />
=== Documentating templates ===<br />
[[User:Gijs|Gijs]] documentated most [[:Category:Templates|templates]], making use of a global [[Template:Informative template|documentation template]]. The documentation tells you what the template does and how to use it.<br />
<br />
=== Feature icons ===<br />
Michat has designed small logos for Airport of the Month, Screenshot of the Month, Aircraft of the Month, [[Dual Control]], [[Bombable]], [[Soaring]], [[Howto:_Do_aerotow_over_the_net|Aerotow]], [[Howto:_Aerial_refueling|Air refueling]] and [[:Category:Aerospace|Aerospace]] aircraft, allowing you to see at a glance which aircraft has some of those interesting features.<br />
<br />
[[File:Dualcontrolready2.png|Dual_control]] [[File:BombableReady.png|Bombable]] [[File:Aerotowready.png|Doing aerotow over the net]] [[File:Thermalready.png|Soaring]] [[File:Spacetripready.png|Aerospace]]<br />
[[File:Aircraftofthemonth.png|IAR80]] [[File:Airrefuelingready.png]] [[File:Airportofthemonth.png]] [[File:Screenshotofthemonth.png]].<br />
<br />
== Nouvelles de la communauté ==<br />
=== FlightGear sur FSBreak ===<br />
Deux développeur de FlightGear, Stuart et Curt ont été interviewé sur un épisode de FSBreak, enregistré le 25 Février. FSBreak est un podcast sur la simulation de vol. Les animateurs Eric et Brendan, on pris près de 1 heure pour parler du projet FlightGear. Vous pouvez l'écouter ici: [http://www.fsbreak.net/podcast/2012/3/2/fsbreak-107-we-talk-flightgear-and-accufeel-released.html this link].<br />
<br />
=== FlightGear on YouTube ===<br />
* [http://youtu.be/hBEaOMzBq6E KSFO Thermal Demo] by MD-BFC Going on their way for Bocian certification<br />
* [http://youtu.be/-yI5PzC5RE8 Sukhoi 37 'The russian dream'] by Águilas de FlightGear performing "Balalaika amok" master tune by Aleksei Arkhipovsky.<br />
<br />
=== Forum news ===<br />
Triggered by the new release, we've had more [http://flightgear.org/forums forum] visitors then ever before in the week of 19-25 February! 17,123 people visited the forum in these seven days to be precise. When looking at "unique visitors", only 13-19 February 2011 was a busier week (9548 against 9076 visitors) (a possible reason for the high number might be that people expected 2.2.0 to be released, which was canceled).<br />
<br />
== And finally ... ==<br />
=== Contributing ===<br />
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
=== Call for volunteers ===<br />
* The [[OpenRadar]] project is looking for a new maintainer.<br />
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.<br />
<br />
=== Did you know ===<br />
...that you can use expressions to create complex animations of objects in your 3d models or even drive them from multiple properties?<br />
Usually, an animation looks like this<br />
<syntaxhighlight lang="xml"><br />
<animation><br />
<type>translate</type><br />
<property>foo/bar</property><br />
[..]more elements[..]<br />
</animation><br />
</syntaxhighlight><br />
You can add a scaling factor or an offset to it, but that's basically all you can do that way. <br />
If you want to animate your object following a complex function, most people create complex Nasal scripts to compute the driving properties, probably not knowing that there is another way to achieve the goal: Expressions. <br />
Here is an example for a translate animation depending on two properties and the cosine function<br />
<syntaxhighlight lang="xml"><br />
<animation><br />
<type>translate</type><br />
<expression><br />
<product><br />
<property>/my/factor-property</property><br />
<cos><br />
<deg2rad><br />
<property>/my/angular-property</property><br />
</deg2rad><br />
</cos><br />
</product><br />
</expression><br />
[..]more elements[..]<br />
</animation><br />
</syntaxhighlight><br />
A rich set of predefined functions is available, including almost all those you have on your scientific pocket calculator.<br />
<br />
[[Category:FlightGear Newsletter|2012 02]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_February_2012&diff=43182FlightGear Newsletter February 20122012-02-27T21:32:35Z<p>Blackiris: /* Shanghai Skylines: FG's New (not-so-)Hidden Gem */</p>
<hr />
<div>{{draft|newsletter|Feel free to contribute! Or [[FlightGear Newsletter January 2012|read the latest edition]].}}<br />
{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
''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 news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''<br />
<br />
== FlightGear 2.6.0 released ==<br />
Following our [[release plan]], version 2.6.0 of our simulator has been released. Please check the [[changelog 2.6.0]] for what has changed since our last release 6 months ago.<br />
<br />
== Development news ==<br />
<br />
=== Heads up: Project Rembrandt ===<br />
As many of you may have heard already, Fred is currently making huge progress on adding shadows to FlightGear in [[Project Rembrandt]]. Now, F-JJTH ported the P92 to use the new system and posted a youtube video demonstrating [[Project Rembrandt]] at work. To provide feedback, please check out the the [http://flightgear.org/forums/viewtopic.php?f=47&t=14883 forum thread].<br />
<br />
{|<br />
|{{#ev:youtube|v02phoOqWHE|400|Project Rembrandt at work}}<br />
|[[File:Project-rembrandt-cockpit-lighting.png|600px|Cockpit lighting in Project Rembrandt at work (by F-JJTH)]]<br />
|}<br />
<br />
<br />
== Interview with a contributor (Christian Schmitt) ==<br />
''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.''<br />
<br />
* How long have you been involved in FlightGear?<br />
Acording to my mail correspondence it must have been in 2007/2008 when I became an active part. I was unsatisfied with the state of EDDF in the FG scenery (no buildings, lightpoles everywhere), so I teamed up with a guy who had already started some work there. I ended up creating all of the terminal buildings and improving the airport layout. In those days, noone was flying there. This changed in the months afterwards, which was a big boost of motivation, too.<br />
* What are your major interests in FlightGear?<br />
My main interest is clearly the scenery and technology connected with it, like GIS. I started to create some custom scenery, like Helgoland, and after I was granted direct access to the mapserver database, I was able to proxy-commit other peoples work, which followed. IMHO, the best FDM or aircraft models are useless if you don't have a nice place to fly, takeoff and land :) So this area is what motivates me the most.<br />
* What project are you working on right now?<br />
<br />
* What do you plan on doing in the future?<br />
* Are you happy with the way the FlightGear project is going?<br />
* What do you enjoy most about developing for FlightGear?<br />
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?<br />
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?<br />
<br />
More questions are being collected here: [[Interview questions]].<br />
<br />
Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX<br />
<br />
== Snapshot releases ==<br />
Every now and then, easy-to-install development snapshots are created (usually, twice montlhy). These snapshots 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].<br />
<br />
The snapshot can be downloaded 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].<br />
<br />
== Nasal for newbies ==<br />
<br />
== New software tools and projects ==<br />
<br />
== FlightGear addons and mods ==<br />
<br />
== In the hangar ==<br />
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.<br />
<br />
=== A new instrument: Vertical Situation Display ===<br />
[[File:Omega95-vsd-instrument.jpeg|200px|thumb|Omega95's VSD instrument]]<br />
Omega95 has created an entirely new instrument type for FlightGear, a so called Vertical Situation Display (VSD).<br />
<br />
This was done entirely in scripting space using Nasal and XML animations. He's basically proven everbody wrong who ever claimed that complex instruments couldn't yet be created in scripting space. Apparently, he managed to create this instrument in less than 24 hrs. His first question related to this was about accessing trigonometric functions from Nasal, shortly thereafter he posted screen shots depicting his VSD. <br />
<br />
To read up on the whole discussion, please see [http://flightgear.org/forums/viewtopic.php?f=30&t=15200 the forum topic]. There's work ongoing to turn his project into a new tutorial for the wiki on creating complex instruments in scripting space: [[Howto: Implement a Vertical Situation Display in Nasal]].<br />
<br />
=== Glider winch launching ropes ===<br />
[[File:DG-101G_winch_launch_with_rope.png|thumb|200px|A DG-101G during a winch launch.]]<br />
Before now, FlightGear never showed ropes during winch launching. However, now, you will no longer have to fly gliders while being pulled by some invisible connection between you and the winch. <br />
<br />
[[User:Gijs|Gijs]] started working on an animated 3D rope, attached to the glider and winch. The cable exist of the following parts:<br />
<br />
* '''Strop''' (3 m) attached to the glider with a ring.<br />
* '''Weak link assembly''' designed to break apart before the cable or any other equipment fails.<br />
* '''Trace''' (17 m)<br />
* '''Parachute''' so the cable doesn't drop too quickly after releasing.<br />
* '''Launch cable''' the longest part; all the way to the winch.<br />
<br />
<br />
=== New aircraft ===<br />
==== Hawker Siddeley Harrier GR.1 ====<br />
[[File:Harrier-GR1 Splash.png|thumb|200px|Harrier GR.1 splash screen]]<br />
[[Hawker Siddeley Harrier GR1]] is a private project by pjedvaj, it was not intended to replace or update the existing [[British Aerospace Harrier]]. It has a detailed 3D model complete with a cockpit, animations and RAF livery. Instruments and HUD are also fairly authentic. The aircraft has working ADEN guns and basic fuel and weight control. The FDM is adapted from the original BAe Harrier, but internal and external fuel tank capacities are modified to match the GR.1 version.<br />
<br />
==== Boeing-Sikorsky RAH-66 Commanche ====<br />
[[File:RAH-66 splash.png|thumb|200px|RAH-66 splash screen]]<br />
[[Boeing-Sikorsky RAH-66 Commanche]] was started as a [[Bounty/RAH-66 Comanche|bounty]] by sgofferj and developed by pjedvaj but I later withdraw from the bounty. This was my first helicopter project and FDM development is curently in stub (RAH-66 is using adapted FDM from Tatsuhiro Nishioka's [[Kawasaki OH-1]]). It has a detailed 3D model, animations and two liveries used to present different variants of RAH-66. Helicopter has a working XM301 cannon controled by joystick and basic weight control for armament in internal bays. AFCS includes SAS, CAS and Auto Hover. You're free to continue the development to fully claim the bounty.<br />
<br />
=== Updated aircraft ===<br />
==== Boeing 787-8 Dreamliner ====<br />
[[File:boeing-787-8-splash.png|thumb|200px|The Boeing 787-8 Splash Screen]]<br />
The Boeing 787-8 Dreamliner has already been there in FlightGear for a very long time -it has been in the FG official hangar since version 1.0. <br />
However, it was created while the 787 was still a prototype aircraft; it did not correctly show many of the 787's actual features like a realistic glass cockpit and accurate instruments.<br />
<br />
The new/updated Boeing 787-8 is a community project that features new JSBSim flight dynamics, Vertical Navigation, a realistic 787 glass cockpit, new CDUs, Electronic Flight Bags, TCAS, advanced Nav Displays, [[Howto:_Implement_a_Vertical_Situation_Display_in_Nasal|Vertical Situation Display]], [[Howto:_Implement_a_Fly-By-Wire_System_for_Airliners|Fly-by-wire]] and a lot of other neat features. It has not exactly been completed and the project is still running.<br />
<br />
You can find out more about the Boeing 787-8 Project HERE or wait for a while till a wiki page is created for it. One of the really good points of this project is how most of our findings and resources have been converted into Wiki HowTos for other aircraft developers to use for their projects.<br />
<br />
<br />
==== Cessna 337G Skymaster ====<br />
[[File:Cessna337-cockpit.png|thumb|200px|General view of the new Cessna 337G Skymaster cockpit]]<br />
The [[Cessna 337G Skymaster]] from the Spain-Latinamerica "Vive FlightGear" factory have received a major update. <br />
<br />
The new cockpit is now totally modelled, almost buttons and knobs are functional, animated, and properly labeled for easy identification.<br />
<br />
New custom sounds, lights, controls, a Bendix/King avionics pack capable of full IFR and night navigation, 2 new HQ liveries and the first FlightGear's working [[ELT]] (Emergency Locator Transmitter) are part of this great improvement on a FlightGear aircraft.<br />
<br />
=== Liveries ===<br />
<br />
== Scenery corner ==<br />
=== 3D-Model contributors: please read ===<br />
A (long) time ago, specific instructions were given on how to contribute with 3D-models designing withing FG. That is: I want to create nice 3D models for my airport, submit them to the central database, and have them shipped back through Terrasync.<br />
However, it appears that quite a lot of users are still not aware of those guidelines, and sometimes learn about their existence after having created their models.<br />
So please, take some time to (re)read them, and inform the people around you who would like to contribute about the existence of those guidelines. This will save you extra time (and your models will be quickly inserted within the database) and this will also save the (precious) times of the poor guy(s) validating all the models at the other end.<br />
So, here they are: http://scenemodels.flightgear.org/contribute.php .<br />
We also remind you that, to add, edit or delete shared model positions (apart from mass import (that is if you have more than let's say 10 lines to add), you should use our webtools at http://scenemodels.flightgear.org/submission/ .<br />
<br />
=== Object-masking and improved materials ===<br />
For a long time, FlightGear has had the ability to place random objects on the scenery. Previously, these objects were placed completely randomly based on a specific density for the material, defined in materials.xml. This didn't look particularly realistic as the placement never matched the underlying texture. Now object and trees can be placed using a "mask", so buildings will only appear where the texture shows buildings, and trees only in green spaces. Additionally, placement is controlled so that random buildings won't overlap with other random buildings, and buildings don't overlap onto adjacent piece of scenery. This makes the random objects appear more realistic, and moves FG one step closer to the auto-gen scenery of MSFS and X-Plane. Further details can be found in fgdata/Docs/README.materials.<br />
<br />
In addition to this, the materials.xml and materials-dds.xml files have been restructured to make them more maintainable, fixing a number of bugs in the process.<br />
<br />
=== Shanghai Skylines: FG's New (not-so-)Hidden Gem ===<br />
Shanghai is one of the biggest city in China and is among the cities with the highest number of skyscrapers -this is now also true for FlightGear.<br />
25 models were created over the past few months by JVC, who also modeled the Akashi-Kaikyo Bridge in Japan and the United Nations building in New York.<br />
{|<br />
|[[File:SH fgfs-screen-001.png|250px|thumb|A view of the Shanghai skyline]]<br />
|[[File:Shanghai003.png|250px|thumb|Another view of Shanghai]]<br />
|[[File:Shanghai007.png|250px|thumb|A closer view from near the Shanghai Stock Exchange]]<br />
|}<br />
<br />
=== New textures for container ship and freighter AI models ===<br />
Starting from a hi-res panorama that he made, user Cristian Marchi (aka penta) provided new skins for the two AI ships that populates seas in flightgear. More info on the [http://www.flightgear.org/forums/viewtopic.php?f=23&t=14856 forum thread].<br />
{|<br />
|[[File:Ships-comparison.png|200px|thumb|left|Comparison between untextured and textured AI ships (by Cristian Marchi)]]<br />
|}<br />
<br />
=== Photographic scenery ===<br />
Photographic scenery for selected places in the US is now available at http://fgphotoscenery.square7.ch . The covered regions currently include San Francisco Bay, Yosemite NP, Grand Canyon NP, Lake Powell, Sedona, Miami, Everglades NP and Key Largo. The scenery has been created from the public domain imagery courtesy of the [http://www.usgs.org U.S. Geological Survey], has a resolution of about 3m/pixel (10ft/pixel) and is released under the GNU General Public Licence (GPL). In total, more than 1.3GB of imagery are ready for download. Videos of UFO flights through the photographic senery are available in the [http://fgphotoscenery.square7.ch#gallery gallery]. <br />
<br />
In order to be able to load the photographic scenery into flightgear, the program has to be compiled from source and the patch developed by Benoît Laniel for the Brest photographic scenery has to be applied. Step-by-step [http://fgphotoscenery.square7.ch#installation installation instructions] for this process are provided.<br />
<br />
Discussions about fgphotoscenery take place this [http://www.flightgear.org/forums/viewtopic.php?f=5&t=15174 forum thread].<br />
<br />
[[File:fgphotoscenery_gallery.jpg]]<br />
<br />
=== Airports ===<br />
<br />
== Aircraft of the month ==<br />
== Airport of the month ==<br />
[[File:LFRJ.png|800px]]<br />
<br />
[[Landivisiau Naval Air Base|Base d'aéronautique navale de Landivisiau]] (LFRJ) is set in the middle of some amazing scenery. Anyone that wants to try [[VFR]] flight should start here in [http://en.wikipedia.org/wiki/Bretagne Bretagne], France. Memorise the scenery, the churches, the power lines, map them and find your way back easy. It's amazing here. The airfield is home to aircraft that belong on the [http://en.wikipedia.org/wiki/French_Naval_Aviation seas] that is why you will see two arresting cables over the runway, don't trip over them. The airfield also holds a EH101 Merlin helicopter (or is it a Westland Lynx?), a perfect modelled tower, the warehouses and all the shelters to protect the Rafale and the SEM attack aircraft.<br />
<br />
== Screenshot of the month ==<br />
<br />
[[File: Lightfield-1.1-14.jpg | 800px]]<br />
<br />
A P-51D flying at 20.000 ft over Juneau (Alaska) at dawn using lightfield shaders to render the sunrise (see [http://www.flightgear.org/forums/viewtopic.php?f=47&t=14755 here] for the shader package for download).<br />
<br />
== Suggested flights ==<br />
===Copacabana to San Rafael over Lake Titicaca===<br />
Bolivia to Peru. This trip will lead you over one of the highest and deepest lakes in the world towards the highest airfield in the world. It a demonstration of a [[IFR]] flight towards a fix and a demonstration how accurate FlightGear simulates air density and the effects it has on aircraft.<br />
[[File:Slcc-sprf.jpg|thumb|200px|left|Flight and fix SLCC to SPRF]]<br />
Place your aircraft on the airfield [http://en.wikipedia.org/wiki/Copacabana,_Bolivia SLCC, Copacabana], with an [[elevation]] of 12,592 feet. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M). <br />
<br />
We will fly towards and land at SPRF. If you would enter SLCC and SPRF in [[Kelpie]] planner you probably would not be able to find SPRF. To find SPRF I am adding an additional VOR-DME station and for a good fix give you another VOR-DME. Try Kelpie planner to plan this route and compare with this suggestion.<br />
<br />
Equipment preparation. Set [[NAV1]] to [http://en.wikipedia.org/wiki/Juliaca Juliaca] VOR-DME on 155.55 with a radial of 311° (magnetic). Set [[NAV2]] to Arequipa VOR-DME on 113.7 with a radial of 212°. During our flight we will fly with [[true altitude]] as set with [[QNH]], keep QNH updated. Arm the autopilot with the [[heading bug]] at 311° and an initial altitude of 13,500 feet.<br />
<br />
Take off and if you took the wrong RW pull up hard. Take a small tour over [http://en.wikipedia.org/wiki/Titicaca lake Titicaca], see the floating islands and try to find the lost golden treasure. Intercept the nearest radial on NAV1 towards Juliaca (about 311°). <br />
<br />
Just before Juliaca is a hill so while on lake Titicaca increase altitude to 14,200 feet, the [[VFR]] part of this trip is over. After passing Juliaca set the radial of NAV1 to 352° and set the altitude to 17,422 feet. We will fly from NAV1 and slowly increase altitude.<br />
<br />
At a distance of about 60 NM set the heading bug on the current course. Monitor the distance to NAV1, the radial of NAV2 and the distance to NAV2. At a distance of 74.5 NM to NAV1, a distance of 140.7 NM and at the '''radial''' intercept of NAV2 should be the runway. So, from 60 NM onwards, look outside the window, then at NAV1 and then NAV2 etc.<br />
<br />
If you are at 80NM to NAV1 you have missed the airfield but you still won't hit any hills (unless you bank left). Bank right and set the heading bug to 172°. Fly back towards NAV1 and intercept the radial 352° at about 50NM again to repeat the search.<br />
<br />
The runway SPRF, San Rafael, has a elevation of 14,422 feet and a heading of 297°/ 117°. Our initial altitude has been set 3,000NM above the RW elevation. That should give sufficient room for navigation.<br />
<br />
After you have seen the airfield set the radial of NAV1 to 297°, the heading of the runway (not the course to the runway) as a visual aid. Land on RW 30 (and not on RW 12 unless you are a show-off). Oh, there is a small hill in front of RW 30, just so you know.<br />
<br />
Decreasing speed at this altitude can be a bit tricky. The air is thin and does not give much resistance. Next to that, the difference between [[indicated airspeed]] and [[ground speed]] is very noticeable. The ground speed is much higher as the indicated airspeed.<br />
<br />
After a successful landing, try to discover the [[Suggested_Flights#Origin_of_the_Amazon_River | origin of the Amazon river]] since we are now at the starting point of that trip.<br />
<br />
*More places you can visit can be found at [[Suggested Flights]].<br />
<br />
== Aircraft reviews ==<br />
<br />
== Wiki updates ==<br />
=== Categorizing images ===<br />
[[User:Johan G|Johan G]] did a great job starting to categorise all images. The sub-categories are listed under [[:Category:Images]]. <br />
<br />
Please keep the following things in mind when uploading images:<br />
* Give the file a descriptive name. That'll make it easier for others to find your file and use it in articles.<br />
* Categorize your image right when you upload it. That saves others from digging up uncatigorized images later on. Placing your image in a category is as simple as adding the following line to the "description" field:<br />
: <code><nowiki>[[Category:Name of the category]]</nowiki></code><br />
: A list of available categories can be found under [[:Category:Images]].<br />
<br />
=== Documentating templates ===<br />
[[User:Gijs|Gijs]] documentated most [[:Category:Templates|templates]], making use of a global [[Template:Informative template|documentation template]]. The documentation tells you what the template does and how to use it.<br />
<br />
=== Feature icons ===<br />
Michat has designed small logos for Aircraft of the Month, [[Dual Control]], [[Bombable]], [[Soaring]], [[Howto:_Do_aerotow_over_the_net|Aerotow]] and [[:Category:Aerospace|Aerospace]] aircraft, allowing you to see at a glance which aircraft has some of those interesting features.<br />
<br />
[[File:Dualcontrolready2.png|Dual_control]] [[File:BombableReady.png|Bombable]] [[File:Aerotowready.png|Doing aerotow over the net]] [[File:Thermalready.png|Soaring]] [[File:Spacetripready.png|Aerospace]]<br />
[[File:Aircraftofthemonth.png|IAR80]].<br />
<br />
===New articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
</DynamicArticleList><br />
===New aircraft articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
categoryRoot=Aircraft<br />
</DynamicArticleList><br />
===Most popular newsletters===<br />
<DynamicArticleList><br />
type=hot<br />
count=5<br />
categoryRoot=FlightGear Newsletter<br />
</DynamicArticleList><br />
<br />
== Community news ==<br />
=== FlightGear on FSBreak ===<br />
Two of FlightGear's developers, Stuart and Curt were interviewed on one of this month's episodes of [http://www.fsbreak.net FSBreak], recorded on 25th February. FSBreak is a flight simulator podcast that discusses recent flight sim developments and reviews. The hosts, Eric and Brendan, spent almost an hour taking about the project with Curt and Stuart. While most of the content won't be new to readers of this newsletter, it was a great way to promote FlightGear 2.6.0 to the wider flight simulation community.<br />
<br />
=== FlightGear on YouTube ===<br />
* [http://youtu.be/hBEaOMzBq6E KSFO Thermal Demo] by MD-BFC Going on their way for Bocian certification<br />
* [http://youtu.be/-yI5PzC5RE8 Sukhoi 37 'The russian dream'] by Águilas de FlightGear performing "Balalaika amok" master tune by Aleksei Arkhipovsky.<br />
<br />
=== New tutorials and screencasts ===<br />
=== Forum news ===<br />
Triggered by the new release, we've had more [http://flightgear.org/forums forum] visitors then ever before in the week of 19-25 February! 17,123 people visited the forum in these seven days to be precise. When looking at "unique visitors", only 13-19 February 2011 was a bussier week (9548 against 9076 visitors) (a possible reason for the high number might be that people expected 2.2.0 to be released, which was canceled).<br />
<br />
=== Multiplayer ===<br />
=== Virtual airlines ===<br />
=== FlightGear events ===<br />
<br />
== Useful links ==<br />
== And finally ... ==<br />
=== Contributing ===<br />
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
=== Call for volunteers ===<br />
* The [[OpenRadar]] project is looking for a new maintainer.<br />
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.<br />
<br />
=== Did you know ===<br />
...that you can use expressions to create complex animations of objects in your 3d models or even drive them from multiple properties?<br />
Usually, an animation looks like this<br />
<syntaxhighlight lang="xml"><br />
<animation><br />
<type>translate</type><br />
<property>foo/bar</property><br />
[..]more elements[..]<br />
</animation><br />
</syntaxhighlight><br />
You can add a scaling factor or an offset to it, but that's basically all you can do that way. <br />
If you want to animate your object following a complex function, most people create complex Nasal scripts to compute the driving properties, probably not knowing that there is another way to achieve the goal: Expressions. <br />
Here is an example for a translate animation depending on two properties and the cosine function<br />
<syntaxhighlight lang="xml"><br />
<animation><br />
<type>translate</type><br />
<expression><br />
<product><br />
<property>/my/factor-property</property><br />
<cos><br />
<deg2rad><br />
<property>/my/angular-property</property><br />
</deg2rad><br />
</cos><br />
</product><br />
</expression><br />
[..]more elements[..]<br />
</animation><br />
</syntaxhighlight><br />
A rich set of predefined functions is available, including almost all those you have on your scientific pocket calculator.<br />
<br />
[[Category:FlightGear Newsletter|2012 02]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_February_2012&diff=43181FlightGear Newsletter February 20122012-02-27T21:16:32Z<p>Blackiris: /* Shanghai Skylines: FG's New (not-so-)Hidden Gem */</p>
<hr />
<div>{{draft|newsletter|Feel free to contribute! Or [[FlightGear Newsletter January 2012|read the latest edition]].}}<br />
{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
''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 news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''<br />
<br />
== FlightGear 2.6.0 released ==<br />
Following our [[release plan]], version 2.6.0 of our simulator has been released. Please check the [[changelog 2.6.0]] for what has changed since our last release 6 months ago.<br />
<br />
== Development news ==<br />
<br />
=== Heads up: Project Rembrandt ===<br />
As many of you may have heard already, Fred is currently making huge progress on adding shadows to FlightGear in [[Project Rembrandt]]. Now, F-JJTH ported the P92 to use the new system and posted a youtube video demonstrating [[Project Rembrandt]] at work. To provide feedback, please check out the the [http://flightgear.org/forums/viewtopic.php?f=47&t=14883 forum thread].<br />
<br />
{|<br />
|{{#ev:youtube|v02phoOqWHE|400|Project Rembrandt at work}}<br />
|[[File:Project-rembrandt-cockpit-lighting.png|600px|Cockpit lighting in Project Rembrandt at work (by F-JJTH)]]<br />
|}<br />
<br />
<br />
== Interview with a contributor (Christian Schmitt) ==<br />
''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.''<br />
<br />
* How long have you been involved in FlightGear?<br />
Acording to my mail correspondence it must have been in 2007/2008 when I became an active part. I was unsatisfied with the state of EDDF in the FG scenery (no buildings, lightpoles everywhere), so I teamed up with a guy who had already started some work there. I ended up creating all of the terminal buildings and improving the airport layout. In those days, noone was flying there. This changed in the months afterwards, which was a big boost of motivation, too.<br />
* What are your major interests in FlightGear?<br />
My main interest is clearly the scenery and technology connected with it, like GIS. I started to create some custom scenery, like Helgoland, and after I was granted direct access to the mapserver database, I was able to proxy-commit other peoples work, which followed. IMHO, the best FDM or aircraft models are useless if you don't have a nice place to fly, takeoff and land :) So this area is what motivates me the most.<br />
* What project are you working on right now?<br />
<br />
* What do you plan on doing in the future?<br />
* Are you happy with the way the FlightGear project is going?<br />
* What do you enjoy most about developing for FlightGear?<br />
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?<br />
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?<br />
<br />
More questions are being collected here: [[Interview questions]].<br />
<br />
Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX<br />
<br />
== Snapshot releases ==<br />
Every now and then, easy-to-install development snapshots are created (usually, twice montlhy). These snapshots 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].<br />
<br />
The snapshot can be downloaded 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].<br />
<br />
== Nasal for newbies ==<br />
<br />
== New software tools and projects ==<br />
<br />
== FlightGear addons and mods ==<br />
<br />
== In the hangar ==<br />
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.<br />
<br />
=== A new instrument: Vertical Situation Display ===<br />
[[File:Omega95-vsd-instrument.jpeg|200px|thumb|Omega95's VSD instrument]]<br />
Omega95 has created an entirely new instrument type for FlightGear, a so called Vertical Situation Display (VSD).<br />
<br />
This was done entirely in scripting space using Nasal and XML animations. He's basically proven everbody wrong who ever claimed that complex instruments couldn't yet be created in scripting space. Apparently, he managed to create this instrument in less than 24 hrs. His first question related to this was about accessing trigonometric functions from Nasal, shortly thereafter he posted screen shots depicting his VSD. <br />
<br />
To read up on the whole discussion, please see [http://flightgear.org/forums/viewtopic.php?f=30&t=15200 the forum topic]. There's work ongoing to turn his project into a new tutorial for the wiki on creating complex instruments in scripting space: [[Howto: Implement a Vertical Situation Display in Nasal]].<br />
<br />
=== Glider winch launching ropes ===<br />
[[File:DG-101G_winch_launch_with_rope.png|thumb|200px|A DG-101G during a winch launch.]]<br />
Before now, FlightGear never showed ropes during winch launching. However, now, you will no longer have to fly gliders while being pulled by some invisible connection between you and the winch. <br />
<br />
[[User:Gijs|Gijs]] started working on an animated 3D rope, attached to the glider and winch. The cable exist of the following parts:<br />
<br />
* '''Strop''' (3 m) attached to the glider with a ring.<br />
* '''Weak link assembly''' designed to break apart before the cable or any other equipment fails.<br />
* '''Trace''' (17 m)<br />
* '''Parachute''' so the cable doesn't drop too quickly after releasing.<br />
* '''Launch cable''' the longest part; all the way to the winch.<br />
<br />
<br />
=== New aircraft ===<br />
==== Hawker Siddeley Harrier GR.1 ====<br />
[[File:Harrier-GR1 Splash.png|thumb|200px|Harrier GR.1 splash screen]]<br />
[[Hawker Siddeley Harrier GR1]] is a private project by pjedvaj, it was not intended to replace or update the existing [[British Aerospace Harrier]]. It has a detailed 3D model complete with a cockpit, animations and RAF livery. Instruments and HUD are also fairly authentic. The aircraft has working ADEN guns and basic fuel and weight control. The FDM is adapted from the original BAe Harrier, but internal and external fuel tank capacities are modified to match the GR.1 version.<br />
<br />
==== Boeing-Sikorsky RAH-66 Commanche ====<br />
[[File:RAH-66 splash.png|thumb|200px|RAH-66 splash screen]]<br />
[[Boeing-Sikorsky RAH-66 Commanche]] was started as a [[Bounty/RAH-66 Comanche|bounty]] by sgofferj and developed by pjedvaj but I later withdraw from the bounty. This was my first helicopter project and FDM development is curently in stub (RAH-66 is using adapted FDM from Tatsuhiro Nishioka's [[Kawasaki OH-1]]). It has a detailed 3D model, animations and two liveries used to present different variants of RAH-66. Helicopter has a working XM301 cannon controled by joystick and basic weight control for armament in internal bays. AFCS includes SAS, CAS and Auto Hover. You're free to continue the development to fully claim the bounty.<br />
<br />
=== Updated aircraft ===<br />
==== Boeing 787-8 Dreamliner ====<br />
[[File:boeing-787-8-splash.png|thumb|200px|The Boeing 787-8 Splash Screen]]<br />
The Boeing 787-8 Dreamliner has already been there in FlightGear for a very long time -it has been in the FG official hangar since version 1.0. <br />
However, it was created while the 787 was still a prototype aircraft; it did not correctly show many of the 787's actual features like a realistic glass cockpit and accurate instruments.<br />
<br />
The new/updated Boeing 787-8 is a community project that features new JSBSim flight dynamics, Vertical Navigation, a realistic 787 glass cockpit, new CDUs, Electronic Flight Bags, TCAS, advanced Nav Displays, [[Howto:_Implement_a_Vertical_Situation_Display_in_Nasal|Vertical Situation Display]], [[Howto:_Implement_a_Fly-By-Wire_System_for_Airliners|Fly-by-wire]] and a lot of other neat features. It has not exactly been completed and the project is still running.<br />
<br />
You can find out more about the Boeing 787-8 Project HERE or wait for a while till a wiki page is created for it. One of the really good points of this project is how most of our findings and resources have been converted into Wiki HowTos for other aircraft developers to use for their projects.<br />
<br />
<br />
==== Cessna 337G Skymaster ====<br />
[[File:Cessna337-cockpit.png|thumb|200px|General view of the new Cessna 337G Skymaster cockpit]]<br />
The [[Cessna 337G Skymaster]] from the Spain-Latinamerica "Vive FlightGear" factory have received a major update. <br />
<br />
The new cockpit is now totally modelled, almost buttons and knobs are functional, animated, and properly labeled for easy identification.<br />
<br />
New custom sounds, lights, controls, a Bendix/King avionics pack capable of full IFR and night navigation, 2 new HQ liveries and the first FlightGear's working [[ELT]] (Emergency Locator Transmitter) are part of this great improvement on a FlightGear aircraft.<br />
<br />
=== Liveries ===<br />
<br />
== Scenery corner ==<br />
=== 3D-Model contributors: please read ===<br />
A (long) time ago, specific instructions were given on how to contribute with 3D-models designing withing FG. That is: I want to create nice 3D models for my airport, submit them to the central database, and have them shipped back through Terrasync.<br />
However, it appears that quite a lot of users are still not aware of those guidelines, and sometimes learn about their existence after having created their models.<br />
So please, take some time to (re)read them, and inform the people around you who would like to contribute about the existence of those guidelines. This will save you extra time (and your models will be quickly inserted within the database) and this will also save the (precious) times of the poor guy(s) validating all the models at the other end.<br />
So, here they are: http://scenemodels.flightgear.org/contribute.php .<br />
We also remind you that, to add, edit or delete shared model positions (apart from mass import (that is if you have more than let's say 10 lines to add), you should use our webtools at http://scenemodels.flightgear.org/submission/ .<br />
<br />
=== Object-masking and improved materials ===<br />
For a long time, FlightGear has had the ability to place random objects on the scenery. Previously, these objects were placed completely randomly based on a specific density for the material, defined in materials.xml. This didn't look particularly realistic as the placement never matched the underlying texture. Now object and trees can be placed using a "mask", so buildings will only appear where the texture shows buildings, and trees only in green spaces. Additionally, placement is controlled so that random buildings won't overlap with other random buildings, and buildings don't overlap onto adjacent piece of scenery. This makes the random objects appear more realistic, and moves FG one step closer to the auto-gen scenery of MSFS and X-Plane. Further details can be found in fgdata/Docs/README.materials.<br />
<br />
In addition to this, the materials.xml and materials-dds.xml files have been restructured to make them more maintainable, fixing a number of bugs in the process.<br />
<br />
=== Shanghai Skylines: FG's New (not-so-)Hidden Gem ===<br />
Shanghai is one of the biggest city in China and is among the cities with the most number of skyscrapers -this is now also true for FlightGear.<br />
25 models were created over the past few months by JVC, who also modeled the Akashi-Kaikyo Bridge in Japan and the United Nations building in New York.<br />
{|<br />
|[[File:SH fgfs-screen-001.png|250px|thumb|A view of the Shanghai skyline]]<br />
|[[File:Shanghai003.png|250px|thumb|Another view of Shanghai]]<br />
|[[File:Shanghai007.png|250px|thumb|A closer view from near the Shanghai Stock Exchange]]<br />
|}<br />
<br />
=== New textures for container ship and freighter AI models ===<br />
Starting from a hi-res panorama that he made, user Cristian Marchi (aka penta) provided new skins for the two AI ships that populates seas in flightgear. More info on the [http://www.flightgear.org/forums/viewtopic.php?f=23&t=14856 forum thread].<br />
{|<br />
|[[File:Ships-comparison.png|200px|thumb|left|Comparison between untextured and textured AI ships (by Cristian Marchi)]]<br />
|}<br />
<br />
=== Photographic scenery ===<br />
Photographic scenery for selected places in the US is now available at http://fgphotoscenery.square7.ch . The covered regions currently include San Francisco Bay, Yosemite NP, Grand Canyon NP, Lake Powell, Sedona, Miami, Everglades NP and Key Largo. The scenery has been created from the public domain imagery courtesy of the [http://www.usgs.org U.S. Geological Survey], has a resolution of about 3m/pixel (10ft/pixel) and is released under the GNU General Public Licence (GPL). In total, more than 1.3GB of imagery are ready for download. Videos of UFO flights through the photographic senery are available in the [http://fgphotoscenery.square7.ch#gallery gallery]. <br />
<br />
In order to be able to load the photographic scenery into flightgear, the program has to be compiled from source and the patch developed by Benoît Laniel for the Brest photographic scenery has to be applied. Step-by-step [http://fgphotoscenery.square7.ch#installation installation instructions] for this process are provided.<br />
<br />
Discussions about fgphotoscenery take place this [http://www.flightgear.org/forums/viewtopic.php?f=5&t=15174 forum thread].<br />
<br />
[[File:fgphotoscenery_gallery.jpg]]<br />
<br />
=== Airports ===<br />
<br />
== Aircraft of the month ==<br />
== Airport of the month ==<br />
[[File:LFRJ.png|800px]]<br />
<br />
[[Landivisiau Naval Air Base|Base d'aéronautique navale de Landivisiau]] (LFRJ) is set in the middle of some amazing scenery. Anyone that wants to try [[VFR]] flight should start here in [http://en.wikipedia.org/wiki/Bretagne Bretagne], France. Memorise the scenery, the churches, the power lines, map them and find your way back easy. It's amazing here. The airfield is home to aircraft that belong on the [http://en.wikipedia.org/wiki/French_Naval_Aviation seas] that is why you will see two arresting cables over the runway, don't trip over them. The airfield also holds a EH101 Merlin helicopter (or is it a Westland Lynx?), a perfect modelled tower, the warehouses and all the shelters to protect the Rafale and the SEM attack aircraft.<br />
<br />
== Screenshot of the month ==<br />
<br />
[[File: Lightfield-1.1-14.jpg | 800px]]<br />
<br />
A P-51D flying at 20.000 ft over Juneau (Alaska) at dawn using lightfield shaders to render the sunrise (see [http://www.flightgear.org/forums/viewtopic.php?f=47&t=14755 here] for the shader package for download).<br />
<br />
== Suggested flights ==<br />
===Copacabana to San Rafael over Lake Titicaca===<br />
Bolivia to Peru. This trip will lead you over one of the highest and deepest lakes in the world towards the highest airfield in the world. It a demonstration of a [[IFR]] flight towards a fix and a demonstration how accurate FlightGear simulates air density and the effects it has on aircraft.<br />
[[File:Slcc-sprf.jpg|thumb|200px|left|Flight and fix SLCC to SPRF]]<br />
Place your aircraft on the airfield [http://en.wikipedia.org/wiki/Copacabana,_Bolivia SLCC, Copacabana], with an [[elevation]] of 12,592 feet. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M). <br />
<br />
We will fly towards and land at SPRF. If you would enter SLCC and SPRF in [[Kelpie]] planner you probably would not be able to find SPRF. To find SPRF I am adding an additional VOR-DME station and for a good fix give you another VOR-DME. Try Kelpie planner to plan this route and compare with this suggestion.<br />
<br />
Equipment preparation. Set [[NAV1]] to [http://en.wikipedia.org/wiki/Juliaca Juliaca] VOR-DME on 155.55 with a radial of 311° (magnetic). Set [[NAV2]] to Arequipa VOR-DME on 113.7 with a radial of 212°. During our flight we will fly with [[true altitude]] as set with [[QNH]], keep QNH updated. Arm the autopilot with the [[heading bug]] at 311° and an initial altitude of 13,500 feet.<br />
<br />
Take off and if you took the wrong RW pull up hard. Take a small tour over [http://en.wikipedia.org/wiki/Titicaca lake Titicaca], see the floating islands and try to find the lost golden treasure. Intercept the nearest radial on NAV1 towards Juliaca (about 311°). <br />
<br />
Just before Juliaca is a hill so while on lake Titicaca increase altitude to 14,200 feet, the [[VFR]] part of this trip is over. After passing Juliaca set the radial of NAV1 to 352° and set the altitude to 17,422 feet. We will fly from NAV1 and slowly increase altitude.<br />
<br />
At a distance of about 60 NM set the heading bug on the current course. Monitor the distance to NAV1, the radial of NAV2 and the distance to NAV2. At a distance of 74.5 NM to NAV1, a distance of 140.7 NM and at the '''radial''' intercept of NAV2 should be the runway. So, from 60 NM onwards, look outside the window, then at NAV1 and then NAV2 etc.<br />
<br />
If you are at 80NM to NAV1 you have missed the airfield but you still won't hit any hills (unless you bank left). Bank right and set the heading bug to 172°. Fly back towards NAV1 and intercept the radial 352° at about 50NM again to repeat the search.<br />
<br />
The runway SPRF, San Rafael, has a elevation of 14,422 feet and a heading of 297°/ 117°. Our initial altitude has been set 3,000NM above the RW elevation. That should give sufficient room for navigation.<br />
<br />
After you have seen the airfield set the radial of NAV1 to 297°, the heading of the runway (not the course to the runway) as a visual aid. Land on RW 30 (and not on RW 12 unless you are a show-off). Oh, there is a small hill in front of RW 30, just so you know.<br />
<br />
Decreasing speed at this altitude can be a bit tricky. The air is thin and does not give much resistance. Next to that, the difference between [[indicated airspeed]] and [[ground speed]] is very noticeable. The ground speed is much higher as the indicated airspeed.<br />
<br />
After a successful landing, try to discover the [[Suggested_Flights#Origin_of_the_Amazon_River | origin of the Amazon river]] since we are now at the starting point of that trip.<br />
<br />
*More places you can visit can be found at [[Suggested Flights]].<br />
<br />
== Aircraft reviews ==<br />
<br />
== Wiki updates ==<br />
=== Categorizing images ===<br />
[[User:Johan G|Johan G]] did a great job starting to categorise all images. The sub-categories are listed under [[:Category:Images]]. <br />
<br />
Please keep the following things in mind when uploading images:<br />
* Give the file a descriptive name. That'll make it easier for others to find your file and use it in articles.<br />
* Categorize your image right when you upload it. That saves others from digging up uncatigorized images later on. Placing your image in a category is as simple as adding the following line to the "description" field:<br />
: <code><nowiki>[[Category:Name of the category]]</nowiki></code><br />
: A list of available categories can be found under [[:Category:Images]].<br />
<br />
=== Documentating templates ===<br />
[[User:Gijs|Gijs]] documentated most [[:Category:Templates|templates]], making use of a global [[Template:Informative template|documentation template]]. The documentation tells you what the template does and how to use it.<br />
<br />
=== Feature icons ===<br />
Michat has designed small logos for Aircraft of the Month, [[Dual Control]], [[Bombable]], [[Soaring]], [[Howto:_Do_aerotow_over_the_net|Aerotow]] and [[:Category:Aerospace|Aerospace]] aircraft, allowing you to see at a glance which aircraft has some of those interesting features.<br />
<br />
[[File:Dualcontrolready2.png|Dual_control]] [[File:BombableReady.png|Bombable]] [[File:Aerotowready.png|Doing aerotow over the net]] [[File:Thermalready.png|Soaring]] [[File:Spacetripready.png|Aerospace]]<br />
[[File:Aircraftofthemonth.png|IAR80]].<br />
<br />
===New articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
</DynamicArticleList><br />
===New aircraft articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
categoryRoot=Aircraft<br />
</DynamicArticleList><br />
===Most popular newsletters===<br />
<DynamicArticleList><br />
type=hot<br />
count=5<br />
categoryRoot=FlightGear Newsletter<br />
</DynamicArticleList><br />
<br />
== Community news ==<br />
=== FlightGear on FSBreak ===<br />
Two of FlightGear's developers, Stuart and Curt were interviewed on one of this month's episodes of [http://www.fsbreak.net FSBreak], recorded on 25th February. FSBreak is a flight simulator podcast that discusses recent flight sim developments and reviews. The hosts, Eric and Brendan, spent almost an hour taking about the project with Curt and Stuart. While most of the content won't be new to readers of this newsletter, it was a great way to promote FlightGear 2.6.0 to the wider flight simulation community.<br />
<br />
=== FlightGear on YouTube ===<br />
* [http://youtu.be/hBEaOMzBq6E KSFO Thermal Demo] by MD-BFC Going on their way for Bocian certification<br />
* [http://youtu.be/-yI5PzC5RE8 Sukhoi 37 'The russian dream'] by Águilas de FlightGear performing "Balalaika amok" master tune by Aleksei Arkhipovsky.<br />
<br />
=== New tutorials and screencasts ===<br />
=== Forum news ===<br />
Triggered by the new release, we've had more [http://flightgear.org/forums forum] visitors then ever before in the week of 19-25 February! 17,123 people visited the forum in these seven days to be precise. When looking at "unique visitors", only 13-19 February 2011 was a bussier week (9548 against 9076 visitors) (a possible reason for the high number might be that people expected 2.2.0 to be released, which was canceled).<br />
<br />
=== Multiplayer ===<br />
=== Virtual airlines ===<br />
=== FlightGear events ===<br />
<br />
== Useful links ==<br />
== And finally ... ==<br />
=== Contributing ===<br />
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
=== Call for volunteers ===<br />
* The [[OpenRadar]] project is looking for a new maintainer.<br />
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.<br />
<br />
=== Did you know ===<br />
...that you can use expressions to create complex animations of objects in your 3d models or even drive them from multiple properties?<br />
Usually, an animation looks like this<br />
<syntaxhighlight lang="xml"><br />
<animation><br />
<type>translate</type><br />
<property>foo/bar</property><br />
[..]more elements[..]<br />
</animation><br />
</syntaxhighlight><br />
You can add a scaling factor or an offset to it, but that's basically all you can do that way. <br />
If you want to animate your object following a complex function, most people create complex Nasal scripts to compute the driving properties, probably not knowing that there is another way to achieve the goal: Expressions. <br />
Here is an example for a translate animation depending on two properties and the cosine function<br />
<syntaxhighlight lang="xml"><br />
<animation><br />
<type>translate</type><br />
<expression><br />
<product><br />
<property>/my/factor-property</property><br />
<cos><br />
<deg2rad><br />
<property>/my/angular-property</property><br />
</deg2rad><br />
</cos><br />
</product><br />
</expression><br />
[..]more elements[..]<br />
</animation><br />
</syntaxhighlight><br />
A rich set of predefined functions is available, including almost all those you have on your scientific pocket calculator.<br />
<br />
[[Category:FlightGear Newsletter|2012 02]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_February_2012&diff=43180FlightGear Newsletter February 20122012-02-27T21:12:36Z<p>Blackiris: /* Snapshot releases */</p>
<hr />
<div>{{draft|newsletter|Feel free to contribute! Or [[FlightGear Newsletter January 2012|read the latest edition]].}}<br />
{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
''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 news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''<br />
<br />
== FlightGear 2.6.0 released ==<br />
Following our [[release plan]], version 2.6.0 of our simulator has been released. Please check the [[changelog 2.6.0]] for what has changed since our last release 6 months ago.<br />
<br />
== Development news ==<br />
<br />
=== Heads up: Project Rembrandt ===<br />
As many of you may have heard already, Fred is currently making huge progress on adding shadows to FlightGear in [[Project Rembrandt]]. Now, F-JJTH ported the P92 to use the new system and posted a youtube video demonstrating [[Project Rembrandt]] at work. To provide feedback, please check out the the [http://flightgear.org/forums/viewtopic.php?f=47&t=14883 forum thread].<br />
<br />
{|<br />
|{{#ev:youtube|v02phoOqWHE|400|Project Rembrandt at work}}<br />
|[[File:Project-rembrandt-cockpit-lighting.png|600px|Cockpit lighting in Project Rembrandt at work (by F-JJTH)]]<br />
|}<br />
<br />
<br />
== Interview with a contributor (Christian Schmitt) ==<br />
''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.''<br />
<br />
* How long have you been involved in FlightGear?<br />
Acording to my mail correspondence it must have been in 2007/2008 when I became an active part. I was unsatisfied with the state of EDDF in the FG scenery (no buildings, lightpoles everywhere), so I teamed up with a guy who had already started some work there. I ended up creating all of the terminal buildings and improving the airport layout. In those days, noone was flying there. This changed in the months afterwards, which was a big boost of motivation, too.<br />
* What are your major interests in FlightGear?<br />
My main interest is clearly the scenery and technology connected with it, like GIS. I started to create some custom scenery, like Helgoland, and after I was granted direct access to the mapserver database, I was able to proxy-commit other peoples work, which followed. IMHO, the best FDM or aircraft models are useless if you don't have a nice place to fly, takeoff and land :) So this area is what motivates me the most.<br />
* What project are you working on right now?<br />
<br />
* What do you plan on doing in the future?<br />
* Are you happy with the way the FlightGear project is going?<br />
* What do you enjoy most about developing for FlightGear?<br />
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?<br />
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?<br />
<br />
More questions are being collected here: [[Interview questions]].<br />
<br />
Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX<br />
<br />
== Snapshot releases ==<br />
Every now and then, easy-to-install development snapshots are created (usually, twice montlhy). These snapshots 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].<br />
<br />
The snapshot can be downloaded 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].<br />
<br />
== Nasal for newbies ==<br />
<br />
== New software tools and projects ==<br />
<br />
== FlightGear addons and mods ==<br />
<br />
== In the hangar ==<br />
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.<br />
<br />
=== A new instrument: Vertical Situation Display ===<br />
[[File:Omega95-vsd-instrument.jpeg|200px|thumb|Omega95's VSD instrument]]<br />
Omega95 has created an entirely new instrument type for FlightGear, a so called Vertical Situation Display (VSD).<br />
<br />
This was done entirely in scripting space using Nasal and XML animations. He's basically proven everbody wrong who ever claimed that complex instruments couldn't yet be created in scripting space. Apparently, he managed to create this instrument in less than 24 hrs. His first question related to this was about accessing trigonometric functions from Nasal, shortly thereafter he posted screen shots depicting his VSD. <br />
<br />
To read up on the whole discussion, please see [http://flightgear.org/forums/viewtopic.php?f=30&t=15200 the forum topic]. There's work ongoing to turn his project into a new tutorial for the wiki on creating complex instruments in scripting space: [[Howto: Implement a Vertical Situation Display in Nasal]].<br />
<br />
=== Glider winch launching ropes ===<br />
[[File:DG-101G_winch_launch_with_rope.png|thumb|200px|A DG-101G during a winch launch.]]<br />
Before now, FlightGear never showed ropes during winch launching. However, now, you will no longer have to fly gliders while being pulled by some invisible connection between you and the winch. <br />
<br />
[[User:Gijs|Gijs]] started working on an animated 3D rope, attached to the glider and winch. The cable exist of the following parts:<br />
<br />
* '''Strop''' (3 m) attached to the glider with a ring.<br />
* '''Weak link assembly''' designed to break apart before the cable or any other equipment fails.<br />
* '''Trace''' (17 m)<br />
* '''Parachute''' so the cable doesn't drop too quickly after releasing.<br />
* '''Launch cable''' the longest part; all the way to the winch.<br />
<br />
<br />
=== New aircraft ===<br />
==== Hawker Siddeley Harrier GR.1 ====<br />
[[File:Harrier-GR1 Splash.png|thumb|200px|Harrier GR.1 splash screen]]<br />
[[Hawker Siddeley Harrier GR1]] is a private project by pjedvaj, it was not intended to replace or update the existing [[British Aerospace Harrier]]. It has a detailed 3D model complete with a cockpit, animations and RAF livery. Instruments and HUD are also fairly authentic. The aircraft has working ADEN guns and basic fuel and weight control. The FDM is adapted from the original BAe Harrier, but internal and external fuel tank capacities are modified to match the GR.1 version.<br />
<br />
==== Boeing-Sikorsky RAH-66 Commanche ====<br />
[[File:RAH-66 splash.png|thumb|200px|RAH-66 splash screen]]<br />
[[Boeing-Sikorsky RAH-66 Commanche]] was started as a [[Bounty/RAH-66 Comanche|bounty]] by sgofferj and developed by pjedvaj but I later withdraw from the bounty. This was my first helicopter project and FDM development is curently in stub (RAH-66 is using adapted FDM from Tatsuhiro Nishioka's [[Kawasaki OH-1]]). It has a detailed 3D model, animations and two liveries used to present different variants of RAH-66. Helicopter has a working XM301 cannon controled by joystick and basic weight control for armament in internal bays. AFCS includes SAS, CAS and Auto Hover. You're free to continue the development to fully claim the bounty.<br />
<br />
=== Updated aircraft ===<br />
==== Boeing 787-8 Dreamliner ====<br />
[[File:boeing-787-8-splash.png|thumb|200px|The Boeing 787-8 Splash Screen]]<br />
The Boeing 787-8 Dreamliner has already been there in FlightGear for a very long time -it has been in the FG official hangar since version 1.0. <br />
However, it was created while the 787 was still a prototype aircraft; it did not correctly show many of the 787's actual features like a realistic glass cockpit and accurate instruments.<br />
<br />
The new/updated Boeing 787-8 is a community project that features new JSBSim flight dynamics, Vertical Navigation, a realistic 787 glass cockpit, new CDUs, Electronic Flight Bags, TCAS, advanced Nav Displays, [[Howto:_Implement_a_Vertical_Situation_Display_in_Nasal|Vertical Situation Display]], [[Howto:_Implement_a_Fly-By-Wire_System_for_Airliners|Fly-by-wire]] and a lot of other neat features. It has not exactly been completed and the project is still running.<br />
<br />
You can find out more about the Boeing 787-8 Project HERE or wait for a while till a wiki page is created for it. One of the really good points of this project is how most of our findings and resources have been converted into Wiki HowTos for other aircraft developers to use for their projects.<br />
<br />
<br />
==== Cessna 337G Skymaster ====<br />
[[File:Cessna337-cockpit.png|thumb|200px|General view of the new Cessna 337G Skymaster cockpit]]<br />
The [[Cessna 337G Skymaster]] from the Spain-Latinamerica "Vive FlightGear" factory have received a major update. <br />
<br />
The new cockpit is now totally modelled, almost buttons and knobs are functional, animated, and properly labeled for easy identification.<br />
<br />
New custom sounds, lights, controls, a Bendix/King avionics pack capable of full IFR and night navigation, 2 new HQ liveries and the first FlightGear's working [[ELT]] (Emergency Locator Transmitter) are part of this great improvement on a FlightGear aircraft.<br />
<br />
=== Liveries ===<br />
<br />
== Scenery corner ==<br />
=== 3D-Model contributors: please read ===<br />
A (long) time ago, specific instructions were given on how to contribute with 3D-models designing withing FG. That is: I want to create nice 3D models for my airport, submit them to the central database, and have them shipped back through Terrasync.<br />
However, it appears that quite a lot of users are still not aware of those guidelines, and sometimes learn about their existence after having created their models.<br />
So please, take some time to (re)read them, and inform the people around you who would like to contribute about the existence of those guidelines. This will save you extra time (and your models will be quickly inserted within the database) and this will also save the (precious) times of the poor guy(s) validating all the models at the other end.<br />
So, here they are: http://scenemodels.flightgear.org/contribute.php .<br />
We also remind you that, to add, edit or delete shared model positions (apart from mass import (that is if you have more than let's say 10 lines to add), you should use our webtools at http://scenemodels.flightgear.org/submission/ .<br />
<br />
=== Object-masking and improved materials ===<br />
For a long time, FlightGear has had the ability to place random objects on the scenery. Previously, these objects were placed completely randomly based on a specific density for the material, defined in materials.xml. This didn't look particularly realistic as the placement never matched the underlying texture. Now object and trees can be placed using a "mask", so buildings will only appear where the texture shows buildings, and trees only in green spaces. Additionally, placement is controlled so that random buildings won't overlap with other random buildings, and buildings don't overlap onto adjacent piece of scenery. This makes the random objects appear more realistic, and moves FG one step closer to the auto-gen scenery of MSFS and X-Plane. Further details can be found in fgdata/Docs/README.materials.<br />
<br />
In addition to this, the materials.xml and materials-dds.xml files have been restructured to make them more maintainable, fixing a number of bugs in the process.<br />
<br />
=== Shanghai Skylines: FG's New (not-so-)Hidden Gem ===<br />
Shanghai is one of the biggest city in China and is among the cities with the most number of skyscrapers -this is now also true for FlightGear.<br />
21 models were created over the past few months by JVC, who also modeled the Akashi-Kaikyo Bridge in Japan and the United Nations building in New York.<br />
{|<br />
|[[File:SH fgfs-screen-001.png|250px|thumb|A view of the Shanghai skyline]]<br />
|[[File:Shanghai003.png|250px|thumb|Another view of Shanghai]]<br />
|[[File:Shanghai007.png|250px|thumb|A closer view from near the Shanghai Stock Exchange]]<br />
|}<br />
<br />
=== New textures for container ship and freighter AI models ===<br />
Starting from a hi-res panorama that he made, user Cristian Marchi (aka penta) provided new skins for the two AI ships that populates seas in flightgear. More info on the [http://www.flightgear.org/forums/viewtopic.php?f=23&t=14856 forum thread].<br />
{|<br />
|[[File:Ships-comparison.png|200px|thumb|left|Comparison between untextured and textured AI ships (by Cristian Marchi)]]<br />
|}<br />
<br />
=== Photographic scenery ===<br />
Photographic scenery for selected places in the US is now available at http://fgphotoscenery.square7.ch . The covered regions currently include San Francisco Bay, Yosemite NP, Grand Canyon NP, Lake Powell, Sedona, Miami, Everglades NP and Key Largo. The scenery has been created from the public domain imagery courtesy of the [http://www.usgs.org U.S. Geological Survey], has a resolution of about 3m/pixel (10ft/pixel) and is released under the GNU General Public Licence (GPL). In total, more than 1.3GB of imagery are ready for download. Videos of UFO flights through the photographic senery are available in the [http://fgphotoscenery.square7.ch#gallery gallery]. <br />
<br />
In order to be able to load the photographic scenery into flightgear, the program has to be compiled from source and the patch developed by Benoît Laniel for the Brest photographic scenery has to be applied. Step-by-step [http://fgphotoscenery.square7.ch#installation installation instructions] for this process are provided.<br />
<br />
Discussions about fgphotoscenery take place this [http://www.flightgear.org/forums/viewtopic.php?f=5&t=15174 forum thread].<br />
<br />
[[File:fgphotoscenery_gallery.jpg]]<br />
<br />
=== Airports ===<br />
<br />
== Aircraft of the month ==<br />
== Airport of the month ==<br />
[[File:LFRJ.png|800px]]<br />
<br />
[[Landivisiau Naval Air Base|Base d'aéronautique navale de Landivisiau]] (LFRJ) is set in the middle of some amazing scenery. Anyone that wants to try [[VFR]] flight should start here in [http://en.wikipedia.org/wiki/Bretagne Bretagne], France. Memorise the scenery, the churches, the power lines, map them and find your way back easy. It's amazing here. The airfield is home to aircraft that belong on the [http://en.wikipedia.org/wiki/French_Naval_Aviation seas] that is why you will see two arresting cables over the runway, don't trip over them. The airfield also holds a EH101 Merlin helicopter (or is it a Westland Lynx?), a perfect modelled tower, the warehouses and all the shelters to protect the Rafale and the SEM attack aircraft.<br />
<br />
== Screenshot of the month ==<br />
<br />
[[File: Lightfield-1.1-14.jpg | 800px]]<br />
<br />
A P-51D flying at 20.000 ft over Juneau (Alaska) at dawn using lightfield shaders to render the sunrise (see [http://www.flightgear.org/forums/viewtopic.php?f=47&t=14755 here] for the shader package for download).<br />
<br />
== Suggested flights ==<br />
===Copacabana to San Rafael over Lake Titicaca===<br />
Bolivia to Peru. This trip will lead you over one of the highest and deepest lakes in the world towards the highest airfield in the world. It a demonstration of a [[IFR]] flight towards a fix and a demonstration how accurate FlightGear simulates air density and the effects it has on aircraft.<br />
[[File:Slcc-sprf.jpg|thumb|200px|left|Flight and fix SLCC to SPRF]]<br />
Place your aircraft on the airfield [http://en.wikipedia.org/wiki/Copacabana,_Bolivia SLCC, Copacabana], with an [[elevation]] of 12,592 feet. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M). <br />
<br />
We will fly towards and land at SPRF. If you would enter SLCC and SPRF in [[Kelpie]] planner you probably would not be able to find SPRF. To find SPRF I am adding an additional VOR-DME station and for a good fix give you another VOR-DME. Try Kelpie planner to plan this route and compare with this suggestion.<br />
<br />
Equipment preparation. Set [[NAV1]] to [http://en.wikipedia.org/wiki/Juliaca Juliaca] VOR-DME on 155.55 with a radial of 311° (magnetic). Set [[NAV2]] to Arequipa VOR-DME on 113.7 with a radial of 212°. During our flight we will fly with [[true altitude]] as set with [[QNH]], keep QNH updated. Arm the autopilot with the [[heading bug]] at 311° and an initial altitude of 13,500 feet.<br />
<br />
Take off and if you took the wrong RW pull up hard. Take a small tour over [http://en.wikipedia.org/wiki/Titicaca lake Titicaca], see the floating islands and try to find the lost golden treasure. Intercept the nearest radial on NAV1 towards Juliaca (about 311°). <br />
<br />
Just before Juliaca is a hill so while on lake Titicaca increase altitude to 14,200 feet, the [[VFR]] part of this trip is over. After passing Juliaca set the radial of NAV1 to 352° and set the altitude to 17,422 feet. We will fly from NAV1 and slowly increase altitude.<br />
<br />
At a distance of about 60 NM set the heading bug on the current course. Monitor the distance to NAV1, the radial of NAV2 and the distance to NAV2. At a distance of 74.5 NM to NAV1, a distance of 140.7 NM and at the '''radial''' intercept of NAV2 should be the runway. So, from 60 NM onwards, look outside the window, then at NAV1 and then NAV2 etc.<br />
<br />
If you are at 80NM to NAV1 you have missed the airfield but you still won't hit any hills (unless you bank left). Bank right and set the heading bug to 172°. Fly back towards NAV1 and intercept the radial 352° at about 50NM again to repeat the search.<br />
<br />
The runway SPRF, San Rafael, has a elevation of 14,422 feet and a heading of 297°/ 117°. Our initial altitude has been set 3,000NM above the RW elevation. That should give sufficient room for navigation.<br />
<br />
After you have seen the airfield set the radial of NAV1 to 297°, the heading of the runway (not the course to the runway) as a visual aid. Land on RW 30 (and not on RW 12 unless you are a show-off). Oh, there is a small hill in front of RW 30, just so you know.<br />
<br />
Decreasing speed at this altitude can be a bit tricky. The air is thin and does not give much resistance. Next to that, the difference between [[indicated airspeed]] and [[ground speed]] is very noticeable. The ground speed is much higher as the indicated airspeed.<br />
<br />
After a successful landing, try to discover the [[Suggested_Flights#Origin_of_the_Amazon_River | origin of the Amazon river]] since we are now at the starting point of that trip.<br />
<br />
*More places you can visit can be found at [[Suggested Flights]].<br />
<br />
== Aircraft reviews ==<br />
<br />
== Wiki updates ==<br />
=== Categorizing images ===<br />
[[User:Johan G|Johan G]] did a great job starting to categorise all images. The sub-categories are listed under [[:Category:Images]]. <br />
<br />
Please keep the following things in mind when uploading images:<br />
* Give the file a descriptive name. That'll make it easier for others to find your file and use it in articles.<br />
* Categorize your image right when you upload it. That saves others from digging up uncatigorized images later on. Placing your image in a category is as simple as adding the following line to the "description" field:<br />
: <code><nowiki>[[Category:Name of the category]]</nowiki></code><br />
: A list of available categories can be found under [[:Category:Images]].<br />
<br />
=== Documentating templates ===<br />
[[User:Gijs|Gijs]] documentated most [[:Category:Templates|templates]], making use of a global [[Template:Informative template|documentation template]]. The documentation tells you what the template does and how to use it.<br />
<br />
=== Feature icons ===<br />
Michat has designed small logos for Aircraft of the Month, [[Dual Control]], [[Bombable]], [[Soaring]], [[Howto:_Do_aerotow_over_the_net|Aerotow]] and [[:Category:Aerospace|Aerospace]] aircraft, allowing you to see at a glance which aircraft has some of those interesting features.<br />
<br />
[[File:Dualcontrolready2.png|Dual_control]] [[File:BombableReady.png|Bombable]] [[File:Aerotowready.png|Doing aerotow over the net]] [[File:Thermalready.png|Soaring]] [[File:Spacetripready.png|Aerospace]]<br />
[[File:Aircraftofthemonth.png|IAR80]].<br />
<br />
===New articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
</DynamicArticleList><br />
===New aircraft articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
categoryRoot=Aircraft<br />
</DynamicArticleList><br />
===Most popular newsletters===<br />
<DynamicArticleList><br />
type=hot<br />
count=5<br />
categoryRoot=FlightGear Newsletter<br />
</DynamicArticleList><br />
<br />
== Community news ==<br />
=== FlightGear on FSBreak ===<br />
Two of FlightGear's developers, Stuart and Curt were interviewed on one of this month's episodes of [http://www.fsbreak.net FSBreak], recorded on 25th February. FSBreak is a flight simulator podcast that discusses recent flight sim developments and reviews. The hosts, Eric and Brendan, spent almost an hour taking about the project with Curt and Stuart. While most of the content won't be new to readers of this newsletter, it was a great way to promote FlightGear 2.6.0 to the wider flight simulation community.<br />
<br />
=== FlightGear on YouTube ===<br />
* [http://youtu.be/hBEaOMzBq6E KSFO Thermal Demo] by MD-BFC Going on their way for Bocian certification<br />
* [http://youtu.be/-yI5PzC5RE8 Sukhoi 37 'The russian dream'] by Águilas de FlightGear performing "Balalaika amok" master tune by Aleksei Arkhipovsky.<br />
<br />
=== New tutorials and screencasts ===<br />
=== Forum news ===<br />
Triggered by the new release, we've had more [http://flightgear.org/forums forum] visitors then ever before in the week of 19-25 February! 17,123 people visited the forum in these seven days to be precise. When looking at "unique visitors", only 13-19 February 2011 was a bussier week (9548 against 9076 visitors) (a possible reason for the high number might be that people expected 2.2.0 to be released, which was canceled).<br />
<br />
=== Multiplayer ===<br />
=== Virtual airlines ===<br />
=== FlightGear events ===<br />
<br />
== Useful links ==<br />
== And finally ... ==<br />
=== Contributing ===<br />
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
=== Call for volunteers ===<br />
* The [[OpenRadar]] project is looking for a new maintainer.<br />
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.<br />
<br />
=== Did you know ===<br />
...that you can use expressions to create complex animations of objects in your 3d models or even drive them from multiple properties?<br />
Usually, an animation looks like this<br />
<syntaxhighlight lang="xml"><br />
<animation><br />
<type>translate</type><br />
<property>foo/bar</property><br />
[..]more elements[..]<br />
</animation><br />
</syntaxhighlight><br />
You can add a scaling factor or an offset to it, but that's basically all you can do that way. <br />
If you want to animate your object following a complex function, most people create complex Nasal scripts to compute the driving properties, probably not knowing that there is another way to achieve the goal: Expressions. <br />
Here is an example for a translate animation depending on two properties and the cosine function<br />
<syntaxhighlight lang="xml"><br />
<animation><br />
<type>translate</type><br />
<expression><br />
<product><br />
<property>/my/factor-property</property><br />
<cos><br />
<deg2rad><br />
<property>/my/angular-property</property><br />
</deg2rad><br />
</cos><br />
</product><br />
</expression><br />
[..]more elements[..]<br />
</animation><br />
</syntaxhighlight><br />
A rich set of predefined functions is available, including almost all those you have on your scientific pocket calculator.<br />
<br />
[[Category:FlightGear Newsletter|2012 02]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=Landmark_Wish_List&diff=43136Landmark Wish List2012-02-27T13:31:43Z<p>Blackiris: /* Asia */</p>
<hr />
<div>This page provides a list of important landmarks which are not currently in FlightGear Scenery that the community would like to see modeled. If you are a FlightGear modeler and are looking for something to model, please consider something on this list.<br />
<br />
Feel free to add to this list.<br />
<br />
If you are modeling a landmark, please change the "Completed" column from "No" to "Claimed".<br />
<br />
=== Africa ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
| Pyramids || Cairo || Egypt || No<br />
|-<br />
| Victoria Falls || Victoria Falls || Zimbabwe || No<br />
|-<br />
|}<br />
<br />
=== America ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|National Congress || Brasilia || Brazil || '''Yes'''<br />
|-<br />
|Christ the Redeemer || Rio de Janeiro || Brazil || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Windsor_Atlantica_Hotel Windsor Atlantica Hotel] || Rio de Janeiro || Brazil || '''Claimed'''<br />
|-<br />
|Navy Pier || Chicago || USA || No<br />
|-<br />
|Adler Planetarium || Chicago || USA || No<br />
|-<br />
|Soldier Field || Chicago || USA || No<br />
|-<br />
|McCormick Place || Chicago || USA || No<br />
|-<br />
|U.S. Cellular Field || Chicago || USA || No<br />
|-<br />
|Wrigley Field || Chicago || USA || No<br />
|-<br />
|Shedd Aquarium || Chicago || USA || No<br />
|-<br />
|Union Station || Chicago || USA || No<br />
|-<br />
|Oglivie Transportation Center || Chicago || USA || No<br />
|-<br />
|Smurfit-Stone Building || Chicago || USA || No<br />
|-<br />
|Marina City || Chicago || USA || No<br />
|-<br />
|Millenium Park || Chicago || USA || No<br />
|-<br />
|United Center || Chicago || USA || No<br />
|-<br />
|Brooklyn Bridge || New York || USA || '''Claimed'''<br />
|-<br />
|Empire State Building || New York || USA || '''Yes'''<br />
|-<br />
|Chrysler Building || New York || USA || '''Claimed'''<br />
|-<br />
|United Nations Headquarters || New York || USA || '''Yes'''<br />
|-<br />
|Bank of America Tower || New York || USA || '''Yes'''<br />
|-<br />
|Verizon Center || Washington, D.C. || USA || No<br />
|-<br />
|White House || Washington, D.C. || USA || No<br />
|-<br />
|Space Needle || Seattle || USA || '''Yes'''<br />
|-<br />
|Milwaukee Art Museum || Milwaukee || USA || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Machu_Picchu Machu Picchu] || Aguas Calientes || Peru || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Nazca_Lines Nazca Lines] || Estudiantes || Peru || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Panama_canal Panama canal] and some boats pls|| Panama city - Colòn || Panama || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Hoover_Dam Hoover Dam]|| Boulder|| USA || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Skunk_Works Skunkworks aircraft] hidden in the mountain of KXTA || Area 51 || USA || No<br />
|}<br />
<br />
=== Asia ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Bank of China Tower || Hong Kong || China || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Kai_Tak_Airport "Checkerboard Hill" (VHHX approach)] || Hong Kong || China || No, See [[Talk:Landmark_Wish_List#VHHX request| Talk page]]<br />
|-<br />
|CCTV Tower || Beijing || China || '''Yes'''<br />
|-<br />
|Taj Mahal || Agra || India || '''Yes'''<br />
|-<br />
|Akashi Kaikyo bridge || Kobe || Japan || '''Yes'''<br />
|-<br />
|Petronas Towers || Kuala Lumpur || Malaysia || '''Yes'''<br />
|-<br />
|Ryugyong Hotel || Pyongyang || North Korea || '''Yes'''<br />
|-<br />
|Burj Khalifa || Dubai || UAE || '''Yes'''<br />
|-<br />
|Burj al Arab || Dubai || UAE || '''Yes'''<br />
|-<br />
|Bitexco Financial Tower || Ho Chi Minh City || Vietnam || '''Yes'''<br />
|-<br />
|Sigiriya || Matale District || Sri Lanka || No<br />
|-<br />
|Great Wall of China || Huairou, Peking / Jiuduhezhen, Huairou, Peking || China || No<br />
|-<br />
|Mount Everest || Chukhung || Nepal || No<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| Something]] || Singapore ||Singapore || No<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| Marina Bay Sands]] || Singapore ||Singapore || No<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| One George Street]] || Singapore ||Singapore || No<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| One Raffles Place]] || Singapore ||Singapore || No<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| The Pinnacle@Duxton]] || Singapore ||Singapore || No<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| One Shenton Way]] || Singapore ||Singapore || No<br />
|}<br />
<br />
=== Europe ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Stade de France || Saint-Denis || France || No<br />
|-<br />
|Zwischenahner Meer || Zwischenahn, Niedersachsen || Germany || '''CS done'''<br />
|-<br />
|Porta Westfalica/Hermans-Denkmal || Bückeburg (ETHB), Minden || Germany || No<br />
|-<br />
|Lapan || Oldenburg, Niedersachsen || Germany || No<br />
|-<br />
|Schloss || Oldenburg || Germany || No<br />
|-<br />
|Schloss || Neuschwanstein || Germany || '''Claimed'''<br />
|-<br />
|Colosseum || Rome || Italy || No<br />
|-<br />
|Oeresund Bridge || Copenhagen-Malmo || Scandinavia || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Oslo_Plaza Oslo Plaza] || Oslo || Norway || '''Claimed'''<br />
|-<br />
|Big Ben || London || UK || '''Yes'''<br />
|-<br />
|Westminster Abbey || London || UK || '''Yes'''<br />
|-<br />
|North Pole (flag and light) || North Pole || World || No<br />
|}<br />
<br />
=== Australia and Oceania ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Sydney Opera House || Sydney || Australia || '''Yes'''<br />
|-<br />
|Sky Tower || Auckland || New Zealand || '''Claimed'''<br />
|-<br />
|Ayers rock || Uluru || Australia || '''No'''<br />
|}<br />
<br />
== Related ==<br />
<br />
=== Internal links ===<br />
* [[FlightGear Scenery Designer]]<br />
* [[FlightGear Scenery Database]]<br />
* [[UK Scenery Wish List]]<br />
* [[Scenery_Tracker]]<br />
<br />
=== External links ===<br />
* [http://www.flightgear.org/forums/viewtopic.php?f=5&t=2390 The forum topic]<br />
* See [http://scenemodels.flightgear.org/ FGFS Scenery Object Database], for more on models for [[Scenery]]<br />
<br />
[[Category:Scenery]]<br />
[[Category:Community]]<br />
[[Category:Contribution requests]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=Landmark_Wish_List&diff=42578Landmark Wish List2012-02-25T10:06:04Z<p>Blackiris: /* Europe */</p>
<hr />
<div>This page provides a list of important landmarks which are not currently in FlightGear Scenery that the community would like to see modeled. If you are a FlightGear modeler and are looking for something to model, please consider something on this list.<br />
<br />
Feel free to add to this list.<br />
<br />
If you are modeling a landmark, please change the "Completed" column from "No" to "Claimed".<br />
<br />
=== Africa ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
| Pyramids || Cairo || Egypt || No<br />
|-<br />
| Victoria Falls || Victoria Falls || Zimbabwe || No<br />
|-<br />
|}<br />
<br />
=== America ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|National Congress || Brasilia || Brazil || '''Yes'''<br />
|-<br />
|Christ the Redeemer || Rio de Janeiro || Brazil || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Windsor_Atlantica_Hotel Windsor Atlantica Hotel] || Rio de Janeiro || Brazil || '''Claimed'''<br />
|-<br />
|Navy Pier || Chicago || USA || No<br />
|-<br />
|Adler Planetarium || Chicago || USA || No<br />
|-<br />
|Soldier Field || Chicago || USA || No<br />
|-<br />
|McCormick Place || Chicago || USA || No<br />
|-<br />
|U.S. Cellular Field || Chicago || USA || No<br />
|-<br />
|Wrigley Field || Chicago || USA || No<br />
|-<br />
|Shedd Aquarium || Chicago || USA || No<br />
|-<br />
|Union Station || Chicago || USA || No<br />
|-<br />
|Oglivie Transportation Center || Chicago || USA || No<br />
|-<br />
|Smurfit-Stone Building || Chicago || USA || No<br />
|-<br />
|Marina City || Chicago || USA || No<br />
|-<br />
|Millenium Park || Chicago || USA || No<br />
|-<br />
|United Center || Chicago || USA || No<br />
|-<br />
|Brooklyn Bridge || New York || USA || '''Claimed'''<br />
|-<br />
|Empire State Building || New York || USA || '''Yes'''<br />
|-<br />
|Chrysler Building || New York || USA || '''Claimed'''<br />
|-<br />
|United Nations Headquarters || New York || USA || '''Yes'''<br />
|-<br />
|Bank of America Tower || New York || USA || '''Yes'''<br />
|-<br />
|Verizon Center || Washington, D.C. || USA || No<br />
|-<br />
|White House || Washington, D.C. || USA || No<br />
|-<br />
|Space Needle || Seattle || USA || '''Yes'''<br />
|-<br />
|Milwaukee Art Museum || Milwaukee || USA || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Machu_Picchu Machu Picchu] || Aguas Calientes || Peru || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Nazca_Lines Nazca Lines] || Estudiantes || Peru || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Panama_canal Panama canal] and some boats pls|| Panama city - Colòn || Panama || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Hoover_Dam Hoover Dam]|| Boulder|| USA || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Skunk_Works Skunkworks aircraft] hidden in the mountain of KXTA || Area 51 || USA || No<br />
|}<br />
<br />
=== Asia ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Bank of China Tower || Hong Kong || China || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Kai_Tak_Airport "Checkerboard Hill" (VHHX approach)] || Hong Kong || China || No, See [[Talk:Landmark_Wish_List#VHHX request| Talk page]]<br />
|-<br />
|CCTV Tower || Beijing || China || '''Yes'''<br />
|-<br />
|Taj Mahal || Agra || India || '''Yes'''<br />
|-<br />
|Akashi Kaikyo bridge || Kobe || Japan || '''Yes'''<br />
|-<br />
|Petronas Towers || Kuala Lumpur || Malaysia || '''Yes'''<br />
|-<br />
|Ryugyong Hotel || Pyongyang || North Korea || '''Yes'''<br />
|-<br />
|Burj Khalifa || Dubai || UAE || '''Yes'''<br />
|-<br />
|Burj al Arab || Dubai || UAE || '''Yes'''<br />
|-<br />
|Bitexco Financial Tower || Ho Chi Minh City || Vietnam || '''Yes'''<br />
|-<br />
|Sigiriya || Matale District || Sri Lanka || No<br />
|-<br />
|Great Wall of China || Huairou, Peking / Jiuduhezhen, Huairou, Peking || China || No<br />
|-<br />
|Mount Everest || Chukhung || Nepal || No<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| Something]] || Singapore ||Singapore || '''Claimed'''<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| Marina Bay Sands]] || Singapore ||Singapore || '''Claimed'''<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| One George Street]] || Singapore ||Singapore || '''Claimed'''<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| One Raffles Place]] || Singapore ||Singapore || '''Claimed'''<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| The Pinnacle@Duxton]] || Singapore ||Singapore || '''Claimed'''<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| One Shenton Way]] || Singapore ||Singapore || '''Claimed'''<br />
|}<br />
<br />
=== Europe ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Stade de France || Saint-Denis || France || No<br />
|-<br />
|Zwischenahner Meer || Zwischenahn, Niedersachsen || Germany || '''CS done'''<br />
|-<br />
|Porta Westfalica/Hermans-Denkmal || Bückeburg (ETHB), Minden || Germany || No<br />
|-<br />
|Lapan || Oldenburg, Niedersachsen || Germany || No<br />
|-<br />
|Schloss || Oldenburg || Germany || No<br />
|-<br />
|Schloss || Neuschwanstein || Germany || '''Claimed'''<br />
|-<br />
|Colosseum || Rome || Italy || No<br />
|-<br />
|Oeresund Bridge || Copenhagen-Malmo || Scandinavia || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Oslo_Plaza Oslo Plaza] || Oslo || Norway || '''Claimed'''<br />
|-<br />
|Big Ben || London || UK || '''Yes'''<br />
|-<br />
|Westminster Abbey || London || UK || '''Yes'''<br />
|-<br />
|North Pole (flag and light) || North Pole || World || No<br />
|}<br />
<br />
=== Australia and Oceania ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Sydney Opera House || Sydney || Australia || '''Yes'''<br />
|-<br />
|Sky Tower || Auckland || New Zealand || '''Claimed'''<br />
|-<br />
|Ayers rock || Uluru || Australia || '''No'''<br />
|}<br />
<br />
== Related ==<br />
<br />
=== Internal links ===<br />
* [[FlightGear Scenery Designer]]<br />
* [[FlightGear Scenery Database]]<br />
* [[UK Scenery Wish List]]<br />
* [[Scenery_Tracker]]<br />
<br />
=== External links ===<br />
* [http://www.flightgear.org/forums/viewtopic.php?f=5&t=2390 The forum topic]<br />
* See [http://scenemodels.flightgear.org/ FGFS Scenery Object Database], for more on models for [[Scenery]]<br />
<br />
[[Category:Scenery]]<br />
[[Category:Community]]<br />
[[Category:Contribution requests]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=Landmark_Wish_List&diff=42577Landmark Wish List2012-02-25T10:05:35Z<p>Blackiris: /* Asia */</p>
<hr />
<div>This page provides a list of important landmarks which are not currently in FlightGear Scenery that the community would like to see modeled. If you are a FlightGear modeler and are looking for something to model, please consider something on this list.<br />
<br />
Feel free to add to this list.<br />
<br />
If you are modeling a landmark, please change the "Completed" column from "No" to "Claimed".<br />
<br />
=== Africa ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
| Pyramids || Cairo || Egypt || No<br />
|-<br />
| Victoria Falls || Victoria Falls || Zimbabwe || No<br />
|-<br />
|}<br />
<br />
=== America ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|National Congress || Brasilia || Brazil || '''Yes'''<br />
|-<br />
|Christ the Redeemer || Rio de Janeiro || Brazil || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Windsor_Atlantica_Hotel Windsor Atlantica Hotel] || Rio de Janeiro || Brazil || '''Claimed'''<br />
|-<br />
|Navy Pier || Chicago || USA || No<br />
|-<br />
|Adler Planetarium || Chicago || USA || No<br />
|-<br />
|Soldier Field || Chicago || USA || No<br />
|-<br />
|McCormick Place || Chicago || USA || No<br />
|-<br />
|U.S. Cellular Field || Chicago || USA || No<br />
|-<br />
|Wrigley Field || Chicago || USA || No<br />
|-<br />
|Shedd Aquarium || Chicago || USA || No<br />
|-<br />
|Union Station || Chicago || USA || No<br />
|-<br />
|Oglivie Transportation Center || Chicago || USA || No<br />
|-<br />
|Smurfit-Stone Building || Chicago || USA || No<br />
|-<br />
|Marina City || Chicago || USA || No<br />
|-<br />
|Millenium Park || Chicago || USA || No<br />
|-<br />
|United Center || Chicago || USA || No<br />
|-<br />
|Brooklyn Bridge || New York || USA || '''Claimed'''<br />
|-<br />
|Empire State Building || New York || USA || '''Yes'''<br />
|-<br />
|Chrysler Building || New York || USA || '''Claimed'''<br />
|-<br />
|United Nations Headquarters || New York || USA || '''Yes'''<br />
|-<br />
|Bank of America Tower || New York || USA || '''Yes'''<br />
|-<br />
|Verizon Center || Washington, D.C. || USA || No<br />
|-<br />
|White House || Washington, D.C. || USA || No<br />
|-<br />
|Space Needle || Seattle || USA || '''Yes'''<br />
|-<br />
|Milwaukee Art Museum || Milwaukee || USA || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Machu_Picchu Machu Picchu] || Aguas Calientes || Peru || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Nazca_Lines Nazca Lines] || Estudiantes || Peru || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Panama_canal Panama canal] and some boats pls|| Panama city - Colòn || Panama || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Hoover_Dam Hoover Dam]|| Boulder|| USA || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Skunk_Works Skunkworks aircraft] hidden in the mountain of KXTA || Area 51 || USA || No<br />
|}<br />
<br />
=== Asia ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Bank of China Tower || Hong Kong || China || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Kai_Tak_Airport "Checkerboard Hill" (VHHX approach)] || Hong Kong || China || No, See [[Talk:Landmark_Wish_List#VHHX request| Talk page]]<br />
|-<br />
|CCTV Tower || Beijing || China || '''Yes'''<br />
|-<br />
|Taj Mahal || Agra || India || '''Yes'''<br />
|-<br />
|Akashi Kaikyo bridge || Kobe || Japan || '''Yes'''<br />
|-<br />
|Petronas Towers || Kuala Lumpur || Malaysia || '''Yes'''<br />
|-<br />
|Ryugyong Hotel || Pyongyang || North Korea || '''Yes'''<br />
|-<br />
|Burj Khalifa || Dubai || UAE || '''Yes'''<br />
|-<br />
|Burj al Arab || Dubai || UAE || '''Yes'''<br />
|-<br />
|Bitexco Financial Tower || Ho Chi Minh City || Vietnam || '''Yes'''<br />
|-<br />
|Sigiriya || Matale District || Sri Lanka || No<br />
|-<br />
|Great Wall of China || Huairou, Peking / Jiuduhezhen, Huairou, Peking || China || No<br />
|-<br />
|Mount Everest || Chukhung || Nepal || No<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| Something]] || Singapore ||Singapore || '''Claimed'''<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| Marina Bay Sands]] || Singapore ||Singapore || '''Claimed'''<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| One George Street]] || Singapore ||Singapore || '''Claimed'''<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| One Raffles Place]] || Singapore ||Singapore || '''Claimed'''<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| The Pinnacle@Duxton]] || Singapore ||Singapore || '''Claimed'''<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| One Shenton Way]] || Singapore ||Singapore || '''Claimed'''<br />
|}<br />
<br />
=== Europe ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Stade de France || Saint-Denis || France || No<br />
|-<br />
|Zwischenahner Meer || Zwischenahn, Niedersachsen || Germany || '''CS done'''<br />
|-<br />
|Porta Westfalica/Hermans-Denkmal || Bückeburg (ETHB), Minden || Germany || No<br />
|-<br />
|Lapan || Oldenburg, Niedersachsen || Germany || No<br />
|-<br />
|Schloss || Oldenburg || Germany || No<br />
|-<br />
|Schloss || Neuschwanstein || Germany || Claimed<br />
|-<br />
|Colosseum || Rome || Italy || No<br />
|-<br />
|Oeresund Bridge || Copenhagen-Malmo || Scandinavia || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Oslo_Plaza Oslo Plaza] || Oslo || Norway || Claimed<br />
|-<br />
|Big Ben || London || UK || '''Yes'''<br />
|-<br />
|Westminster Abbey || London || UK || '''Yes'''<br />
|-<br />
|North Pole (flag and light) || North Pole || World || No<br />
|}<br />
<br />
=== Australia and Oceania ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Sydney Opera House || Sydney || Australia || '''Yes'''<br />
|-<br />
|Sky Tower || Auckland || New Zealand || '''Claimed'''<br />
|-<br />
|Ayers rock || Uluru || Australia || '''No'''<br />
|}<br />
<br />
== Related ==<br />
<br />
=== Internal links ===<br />
* [[FlightGear Scenery Designer]]<br />
* [[FlightGear Scenery Database]]<br />
* [[UK Scenery Wish List]]<br />
* [[Scenery_Tracker]]<br />
<br />
=== External links ===<br />
* [http://www.flightgear.org/forums/viewtopic.php?f=5&t=2390 The forum topic]<br />
* See [http://scenemodels.flightgear.org/ FGFS Scenery Object Database], for more on models for [[Scenery]]<br />
<br />
[[Category:Scenery]]<br />
[[Category:Community]]<br />
[[Category:Contribution requests]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=Landmark_Wish_List&diff=42576Landmark Wish List2012-02-25T09:40:23Z<p>Blackiris: /* Asia */</p>
<hr />
<div>This page provides a list of important landmarks which are not currently in FlightGear Scenery that the community would like to see modeled. If you are a FlightGear modeler and are looking for something to model, please consider something on this list.<br />
<br />
Feel free to add to this list.<br />
<br />
If you are modeling a landmark, please change the "Completed" column from "No" to "Claimed".<br />
<br />
=== Africa ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
| Pyramids || Cairo || Egypt || No<br />
|-<br />
| Victoria Falls || Victoria Falls || Zimbabwe || No<br />
|-<br />
|}<br />
<br />
=== America ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|National Congress || Brasilia || Brazil || '''Yes'''<br />
|-<br />
|Christ the Redeemer || Rio de Janeiro || Brazil || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Windsor_Atlantica_Hotel Windsor Atlantica Hotel] || Rio de Janeiro || Brazil || '''Claimed'''<br />
|-<br />
|Navy Pier || Chicago || USA || No<br />
|-<br />
|Adler Planetarium || Chicago || USA || No<br />
|-<br />
|Soldier Field || Chicago || USA || No<br />
|-<br />
|McCormick Place || Chicago || USA || No<br />
|-<br />
|U.S. Cellular Field || Chicago || USA || No<br />
|-<br />
|Wrigley Field || Chicago || USA || No<br />
|-<br />
|Shedd Aquarium || Chicago || USA || No<br />
|-<br />
|Union Station || Chicago || USA || No<br />
|-<br />
|Oglivie Transportation Center || Chicago || USA || No<br />
|-<br />
|Smurfit-Stone Building || Chicago || USA || No<br />
|-<br />
|Marina City || Chicago || USA || No<br />
|-<br />
|Millenium Park || Chicago || USA || No<br />
|-<br />
|United Center || Chicago || USA || No<br />
|-<br />
|Brooklyn Bridge || New York || USA || '''Claimed'''<br />
|-<br />
|Empire State Building || New York || USA || '''Yes'''<br />
|-<br />
|Chrysler Building || New York || USA || '''Claimed'''<br />
|-<br />
|United Nations Headquarters || New York || USA || '''Yes'''<br />
|-<br />
|Bank of America Tower || New York || USA || '''Yes'''<br />
|-<br />
|Verizon Center || Washington, D.C. || USA || No<br />
|-<br />
|White House || Washington, D.C. || USA || No<br />
|-<br />
|Space Needle || Seattle || USA || '''Yes'''<br />
|-<br />
|Milwaukee Art Museum || Milwaukee || USA || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Machu_Picchu Machu Picchu] || Aguas Calientes || Peru || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Nazca_Lines Nazca Lines] || Estudiantes || Peru || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Panama_canal Panama canal] and some boats pls|| Panama city - Colòn || Panama || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Hoover_Dam Hoover Dam]|| Boulder|| USA || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Skunk_Works Skunkworks aircraft] hidden in the mountain of KXTA || Area 51 || USA || No<br />
|}<br />
<br />
=== Asia ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Bank of China Tower || Hong Kong || China || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Kai_Tak_Airport "Checkerboard Hill" (VHHX approach)] || Hong Kong || China || No, See [[Talk:Landmark_Wish_List#VHHX request| Talk page]]<br />
|-<br />
|CCTV Tower || Beijing || China || '''Yes'''<br />
|-<br />
|Taj Mahal || Agra || India || '''Yes'''<br />
|-<br />
|Akashi Kaikyo bridge || Kobe || Japan || '''Yes'''<br />
|-<br />
|Petronas Towers || Kuala Lumpur || Malaysia || '''Yes'''<br />
|-<br />
|Ryugyong Hotel || Pyongyang || North Korea || '''Yes'''<br />
|-<br />
|Burj Khalifa || Dubai || UAE || '''Yes'''<br />
|-<br />
|Burj al Arab || Dubai || UAE || '''Yes'''<br />
|-<br />
|Bitexco Financial Tower || Ho Chi Minh City || Vietnam || '''Yes'''<br />
|-<br />
|Sigiriya || Matale District || Sri Lanka || No<br />
|-<br />
|Great Wall of China || Huairou, Peking / Jiuduhezhen, Huairou, Peking || China || No<br />
|-<br />
|Mount Everest || Chukhung || Nepal || No<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| Something]] || Singapore ||Singapore || '''Claimed'''<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| Marina Bay Sands]] || Singapore ||Singapore || '''Claimed'''<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| One George Street]] || Singapore ||Singapore || '''Claimed'''<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| One Raffles Place]] || Singapore ||Singapore || '''Claimed'''<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| The Pinnacle Duxton]] || Singapore ||Singapore || '''Claimed'''<br />
[-<br />
|[[Talk:Landmark_Wish_List#Singapore| One Shenton Way]] || Singapore ||Singapore || '''Claimed'''<br />
|}<br />
<br />
=== Europe ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Stade de France || Saint-Denis || France || No<br />
|-<br />
|Zwischenahner Meer || Zwischenahn, Niedersachsen || Germany || '''CS done'''<br />
|-<br />
|Porta Westfalica/Hermans-Denkmal || Bückeburg (ETHB), Minden || Germany || No<br />
|-<br />
|Lapan || Oldenburg, Niedersachsen || Germany || No<br />
|-<br />
|Schloss || Oldenburg || Germany || No<br />
|-<br />
|Schloss || Neuschwanstein || Germany || Claimed<br />
|-<br />
|Colosseum || Rome || Italy || No<br />
|-<br />
|Oeresund Bridge || Copenhagen-Malmo || Scandinavia || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Oslo_Plaza Oslo Plaza] || Oslo || Norway || Claimed<br />
|-<br />
|Big Ben || London || UK || '''Yes'''<br />
|-<br />
|Westminster Abbey || London || UK || '''Yes'''<br />
|-<br />
|North Pole (flag and light) || North Pole || World || No<br />
|}<br />
<br />
=== Australia and Oceania ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Sydney Opera House || Sydney || Australia || '''Yes'''<br />
|-<br />
|Sky Tower || Auckland || New Zealand || '''Claimed'''<br />
|-<br />
|Ayers rock || Uluru || Australia || '''No'''<br />
|}<br />
<br />
== Related ==<br />
<br />
=== Internal links ===<br />
* [[FlightGear Scenery Designer]]<br />
* [[FlightGear Scenery Database]]<br />
* [[UK Scenery Wish List]]<br />
* [[Scenery_Tracker]]<br />
<br />
=== External links ===<br />
* [http://www.flightgear.org/forums/viewtopic.php?f=5&t=2390 The forum topic]<br />
* See [http://scenemodels.flightgear.org/ FGFS Scenery Object Database], for more on models for [[Scenery]]<br />
<br />
[[Category:Scenery]]<br />
[[Category:Community]]<br />
[[Category:Contribution requests]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=Landmark_Wish_List&diff=42575Landmark Wish List2012-02-25T09:38:14Z<p>Blackiris: /* Asia */</p>
<hr />
<div>This page provides a list of important landmarks which are not currently in FlightGear Scenery that the community would like to see modeled. If you are a FlightGear modeler and are looking for something to model, please consider something on this list.<br />
<br />
Feel free to add to this list.<br />
<br />
If you are modeling a landmark, please change the "Completed" column from "No" to "Claimed".<br />
<br />
=== Africa ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
| Pyramids || Cairo || Egypt || No<br />
|-<br />
| Victoria Falls || Victoria Falls || Zimbabwe || No<br />
|-<br />
|}<br />
<br />
=== America ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|National Congress || Brasilia || Brazil || '''Yes'''<br />
|-<br />
|Christ the Redeemer || Rio de Janeiro || Brazil || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Windsor_Atlantica_Hotel Windsor Atlantica Hotel] || Rio de Janeiro || Brazil || '''Claimed'''<br />
|-<br />
|Navy Pier || Chicago || USA || No<br />
|-<br />
|Adler Planetarium || Chicago || USA || No<br />
|-<br />
|Soldier Field || Chicago || USA || No<br />
|-<br />
|McCormick Place || Chicago || USA || No<br />
|-<br />
|U.S. Cellular Field || Chicago || USA || No<br />
|-<br />
|Wrigley Field || Chicago || USA || No<br />
|-<br />
|Shedd Aquarium || Chicago || USA || No<br />
|-<br />
|Union Station || Chicago || USA || No<br />
|-<br />
|Oglivie Transportation Center || Chicago || USA || No<br />
|-<br />
|Smurfit-Stone Building || Chicago || USA || No<br />
|-<br />
|Marina City || Chicago || USA || No<br />
|-<br />
|Millenium Park || Chicago || USA || No<br />
|-<br />
|United Center || Chicago || USA || No<br />
|-<br />
|Brooklyn Bridge || New York || USA || '''Claimed'''<br />
|-<br />
|Empire State Building || New York || USA || '''Yes'''<br />
|-<br />
|Chrysler Building || New York || USA || '''Claimed'''<br />
|-<br />
|United Nations Headquarters || New York || USA || '''Yes'''<br />
|-<br />
|Bank of America Tower || New York || USA || '''Yes'''<br />
|-<br />
|Verizon Center || Washington, D.C. || USA || No<br />
|-<br />
|White House || Washington, D.C. || USA || No<br />
|-<br />
|Space Needle || Seattle || USA || '''Yes'''<br />
|-<br />
|Milwaukee Art Museum || Milwaukee || USA || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Machu_Picchu Machu Picchu] || Aguas Calientes || Peru || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Nazca_Lines Nazca Lines] || Estudiantes || Peru || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Panama_canal Panama canal] and some boats pls|| Panama city - Colòn || Panama || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Hoover_Dam Hoover Dam]|| Boulder|| USA || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Skunk_Works Skunkworks aircraft] hidden in the mountain of KXTA || Area 51 || USA || No<br />
|}<br />
<br />
=== Asia ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Bank of China Tower || Hong Kong || China || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Kai_Tak_Airport "Checkerboard Hill" (VHHX approach)] || Hong Kong || China || No, See [[Talk:Landmark_Wish_List#VHHX request| Talk page]]<br />
|-<br />
|CCTV Tower || Beijing || China || '''Yes'''<br />
|-<br />
|Taj Mahal || Agra || India || '''Yes'''<br />
|-<br />
|Akashi Kaikyo bridge || Kobe || Japan || '''Yes'''<br />
|-<br />
|Petronas Towers || Kuala Lumpur || Malaysia || '''Yes'''<br />
|-<br />
|Ryugyong Hotel || Pyongyang || North Korea || '''Yes'''<br />
|-<br />
|Burj Khalifa || Dubai || UAE || '''Yes'''<br />
|-<br />
|Burj al Arab || Dubai || UAE || '''Yes'''<br />
|-<br />
|Bitexco Financial Tower || Ho Chi Minh City || Vietnam || '''Yes'''<br />
|-<br />
|Sigiriya || Matale District || Sri Lanka || No<br />
|-<br />
|Great Wall of China || Huairou, Peking / Jiuduhezhen, Huairou, Peking || China || No<br />
|-<br />
|Mount Everest || Chukhung || Nepal || No<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| Something]] || Singapore ||Singapore || '''Claimed'''<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| Marina Bay Sands]] || Singapore ||Singapore || '''Claimed'''<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| One George Street]] || Singapore ||Singapore || '''Claimed'''<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| One Raffles Place]] || Singapore ||Singapore || '''Claimed'''<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| The Pinnacle@Duxton]] || Singapore ||Singapore || '''Claimed'''<br />
[-<br />
|[[Talk:Landmark_Wish_List#Singapore| One Shenton Way]] || Singapore ||Singapore || '''Claimed'''<br />
|}<br />
<br />
=== Europe ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Stade de France || Saint-Denis || France || No<br />
|-<br />
|Zwischenahner Meer || Zwischenahn, Niedersachsen || Germany || '''CS done'''<br />
|-<br />
|Porta Westfalica/Hermans-Denkmal || Bückeburg (ETHB), Minden || Germany || No<br />
|-<br />
|Lapan || Oldenburg, Niedersachsen || Germany || No<br />
|-<br />
|Schloss || Oldenburg || Germany || No<br />
|-<br />
|Schloss || Neuschwanstein || Germany || Claimed<br />
|-<br />
|Colosseum || Rome || Italy || No<br />
|-<br />
|Oeresund Bridge || Copenhagen-Malmo || Scandinavia || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Oslo_Plaza Oslo Plaza] || Oslo || Norway || Claimed<br />
|-<br />
|Big Ben || London || UK || '''Yes'''<br />
|-<br />
|Westminster Abbey || London || UK || '''Yes'''<br />
|-<br />
|North Pole (flag and light) || North Pole || World || No<br />
|}<br />
<br />
=== Australia and Oceania ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Sydney Opera House || Sydney || Australia || '''Yes'''<br />
|-<br />
|Sky Tower || Auckland || New Zealand || '''Claimed'''<br />
|-<br />
|Ayers rock || Uluru || Australia || '''No'''<br />
|}<br />
<br />
== Related ==<br />
<br />
=== Internal links ===<br />
* [[FlightGear Scenery Designer]]<br />
* [[FlightGear Scenery Database]]<br />
* [[UK Scenery Wish List]]<br />
* [[Scenery_Tracker]]<br />
<br />
=== External links ===<br />
* [http://www.flightgear.org/forums/viewtopic.php?f=5&t=2390 The forum topic]<br />
* See [http://scenemodels.flightgear.org/ FGFS Scenery Object Database], for more on models for [[Scenery]]<br />
<br />
[[Category:Scenery]]<br />
[[Category:Community]]<br />
[[Category:Contribution requests]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=Landmark_Wish_List&diff=42574Landmark Wish List2012-02-25T09:34:53Z<p>Blackiris: /* Asia */</p>
<hr />
<div>This page provides a list of important landmarks which are not currently in FlightGear Scenery that the community would like to see modeled. If you are a FlightGear modeler and are looking for something to model, please consider something on this list.<br />
<br />
Feel free to add to this list.<br />
<br />
If you are modeling a landmark, please change the "Completed" column from "No" to "Claimed".<br />
<br />
=== Africa ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
| Pyramids || Cairo || Egypt || No<br />
|-<br />
| Victoria Falls || Victoria Falls || Zimbabwe || No<br />
|-<br />
|}<br />
<br />
=== America ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|National Congress || Brasilia || Brazil || '''Yes'''<br />
|-<br />
|Christ the Redeemer || Rio de Janeiro || Brazil || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Windsor_Atlantica_Hotel Windsor Atlantica Hotel] || Rio de Janeiro || Brazil || '''Claimed'''<br />
|-<br />
|Navy Pier || Chicago || USA || No<br />
|-<br />
|Adler Planetarium || Chicago || USA || No<br />
|-<br />
|Soldier Field || Chicago || USA || No<br />
|-<br />
|McCormick Place || Chicago || USA || No<br />
|-<br />
|U.S. Cellular Field || Chicago || USA || No<br />
|-<br />
|Wrigley Field || Chicago || USA || No<br />
|-<br />
|Shedd Aquarium || Chicago || USA || No<br />
|-<br />
|Union Station || Chicago || USA || No<br />
|-<br />
|Oglivie Transportation Center || Chicago || USA || No<br />
|-<br />
|Smurfit-Stone Building || Chicago || USA || No<br />
|-<br />
|Marina City || Chicago || USA || No<br />
|-<br />
|Millenium Park || Chicago || USA || No<br />
|-<br />
|United Center || Chicago || USA || No<br />
|-<br />
|Brooklyn Bridge || New York || USA || '''Claimed'''<br />
|-<br />
|Empire State Building || New York || USA || '''Yes'''<br />
|-<br />
|Chrysler Building || New York || USA || '''Claimed'''<br />
|-<br />
|United Nations Headquarters || New York || USA || '''Yes'''<br />
|-<br />
|Bank of America Tower || New York || USA || '''Yes'''<br />
|-<br />
|Verizon Center || Washington, D.C. || USA || No<br />
|-<br />
|White House || Washington, D.C. || USA || No<br />
|-<br />
|Space Needle || Seattle || USA || '''Yes'''<br />
|-<br />
|Milwaukee Art Museum || Milwaukee || USA || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Machu_Picchu Machu Picchu] || Aguas Calientes || Peru || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Nazca_Lines Nazca Lines] || Estudiantes || Peru || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Panama_canal Panama canal] and some boats pls|| Panama city - Colòn || Panama || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Hoover_Dam Hoover Dam]|| Boulder|| USA || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Skunk_Works Skunkworks aircraft] hidden in the mountain of KXTA || Area 51 || USA || No<br />
|}<br />
<br />
=== Asia ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Bank of China Tower || Hong Kong || China || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Kai_Tak_Airport "Checkerboard Hill" (VHHX approach)] || Hong Kong || China || No, See [[Talk:Landmark_Wish_List#VHHX request| Talk page]]<br />
|-<br />
|CCTV Tower || Beijing || China || '''Yes'''<br />
|-<br />
|Taj Mahal || Agra || India || '''Yes'''<br />
|-<br />
|Akashi Kaikyo bridge || Kobe || Japan || '''Yes'''<br />
|-<br />
|Petronas Towers || Kuala Lumpur || Malaysia || '''Yes'''<br />
|-<br />
|Ryugyong Hotel || Pyongyang || North Korea || '''Yes'''<br />
|-<br />
|Burj Khalifa || Dubai || UAE || '''Yes'''<br />
|-<br />
|Burj al Arab || Dubai || UAE || '''Yes'''<br />
|-<br />
|Bitexco Financial Tower || Ho Chi Minh City || Vietnam || '''Yes'''<br />
|-<br />
|Sigiriya || Matale District || Sri Lanka || No<br />
|-<br />
|Great Wall of China || Huairou, Peking / Jiuduhezhen, Huairou, Peking || China || No<br />
|-<br />
|Mount Everest || Chukhung || Nepal || No<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| Something]] || Singapore ||Singapore || '''Claimed'''<br />
|}<br />
<br />
=== Europe ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Stade de France || Saint-Denis || France || No<br />
|-<br />
|Zwischenahner Meer || Zwischenahn, Niedersachsen || Germany || '''CS done'''<br />
|-<br />
|Porta Westfalica/Hermans-Denkmal || Bückeburg (ETHB), Minden || Germany || No<br />
|-<br />
|Lapan || Oldenburg, Niedersachsen || Germany || No<br />
|-<br />
|Schloss || Oldenburg || Germany || No<br />
|-<br />
|Schloss || Neuschwanstein || Germany || Claimed<br />
|-<br />
|Colosseum || Rome || Italy || No<br />
|-<br />
|Oeresund Bridge || Copenhagen-Malmo || Scandinavia || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Oslo_Plaza Oslo Plaza] || Oslo || Norway || Claimed<br />
|-<br />
|Big Ben || London || UK || '''Yes'''<br />
|-<br />
|Westminster Abbey || London || UK || '''Yes'''<br />
|-<br />
|North Pole (flag and light) || North Pole || World || No<br />
|}<br />
<br />
=== Australia and Oceania ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Sydney Opera House || Sydney || Australia || '''Yes'''<br />
|-<br />
|Sky Tower || Auckland || New Zealand || '''Claimed'''<br />
|-<br />
|Ayers rock || Uluru || Australia || '''No'''<br />
|}<br />
<br />
== Related ==<br />
<br />
=== Internal links ===<br />
* [[FlightGear Scenery Designer]]<br />
* [[FlightGear Scenery Database]]<br />
* [[UK Scenery Wish List]]<br />
* [[Scenery_Tracker]]<br />
<br />
=== External links ===<br />
* [http://www.flightgear.org/forums/viewtopic.php?f=5&t=2390 The forum topic]<br />
* See [http://scenemodels.flightgear.org/ FGFS Scenery Object Database], for more on models for [[Scenery]]<br />
<br />
[[Category:Scenery]]<br />
[[Category:Community]]<br />
[[Category:Contribution requests]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=Landmark_Wish_List&diff=42567Landmark Wish List2012-02-25T09:00:24Z<p>Blackiris: /* Asia */</p>
<hr />
<div>This page provides a list of important landmarks which are not currently in FlightGear Scenery that the community would like to see modeled. If you are a FlightGear modeler and are looking for something to model, please consider something on this list.<br />
<br />
Feel free to add to this list.<br />
<br />
If you are modeling a landmark, please change the "Completed" column from "No" to "Claimed".<br />
<br />
=== Africa ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
| Pyramids || Cairo || Egypt || No<br />
|-<br />
| Victoria Falls || Victoria Falls || Zimbabwe || No<br />
|-<br />
|}<br />
<br />
=== America ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|National Congress || Brasilia || Brazil || '''Yes'''<br />
|-<br />
|Christ the Redeemer || Rio de Janeiro || Brazil || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Windsor_Atlantica_Hotel Windsor Atlantica Hotel] || Rio de Janeiro || Brazil || '''Claimed'''<br />
|-<br />
|Navy Pier || Chicago || USA || No<br />
|-<br />
|Adler Planetarium || Chicago || USA || No<br />
|-<br />
|Soldier Field || Chicago || USA || No<br />
|-<br />
|McCormick Place || Chicago || USA || No<br />
|-<br />
|U.S. Cellular Field || Chicago || USA || No<br />
|-<br />
|Wrigley Field || Chicago || USA || No<br />
|-<br />
|Shedd Aquarium || Chicago || USA || No<br />
|-<br />
|Union Station || Chicago || USA || No<br />
|-<br />
|Oglivie Transportation Center || Chicago || USA || No<br />
|-<br />
|Smurfit-Stone Building || Chicago || USA || No<br />
|-<br />
|Marina City || Chicago || USA || No<br />
|-<br />
|Millenium Park || Chicago || USA || No<br />
|-<br />
|United Center || Chicago || USA || No<br />
|-<br />
|Brooklyn Bridge || New York || USA || '''Claimed'''<br />
|-<br />
|Empire State Building || New York || USA || '''Yes'''<br />
|-<br />
|Chrysler Building || New York || USA || '''Claimed'''<br />
|-<br />
|United Nations Headquarters || New York || USA || '''Yes'''<br />
|-<br />
|Bank of America Tower || New York || USA || '''Yes'''<br />
|-<br />
|Verizon Center || Washington, D.C. || USA || No<br />
|-<br />
|White House || Washington, D.C. || USA || No<br />
|-<br />
|Space Needle || Seattle || USA || '''Yes'''<br />
|-<br />
|Milwaukee Art Museum || Milwaukee || USA || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Machu_Picchu Machu Picchu] || Aguas Calientes || Peru || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Nazca_Lines Nazca Lines] || Estudiantes || Peru || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Panama_canal Panama canal] and some boats pls|| Panama city - Colòn || Panama || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Hoover_Dam Hoover Dam]|| Boulder|| USA || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Skunk_Works Skunkworks aircraft] hidden in the mountain of KXTA || Area 51 || USA || No<br />
|}<br />
<br />
=== Asia ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Bank of China Tower || Hong Kong || China || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Kai_Tak_Airport "Checkerboard Hill" (VHHX approach)] || Hong Kong || China || No, See [[Talk:Landmark_Wish_List#VHHX request| Talk page]]<br />
|-<br />
|CCTV Tower || Beijing || China || '''Yes'''<br />
|-<br />
|Taj Mahal || Agra || India || '''Yes'''<br />
|-<br />
|Akashi Kaikyo bridge || Kobe || Japan || '''Yes'''<br />
|-<br />
|Petronas Towers || Kuala Lumpur || Malaysia || '''Yes'''<br />
|-<br />
|Ryugyong Hotel || Pyongyang || North Korea || '''Yes'''<br />
|-<br />
|Burj Khalifa || Dubai || UAE || '''Yes'''<br />
|-<br />
|Burj al Arab || Dubai || UAE || '''Yes'''<br />
|-<br />
|Bitexco Financial Tower || Ho Chi Minh City || Vietnam || '''Yes'''<br />
|-<br />
|Sigiriya || Matale District || Sri Lanka || No<br />
|-<br />
|Great Wall of China || Huairou, Peking / Jiuduhezhen, Huairou, Peking || China || No<br />
|-<br />
|Mount Everest || Chukhung || Nepal || No<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| Something]] || Singapore ||Singapore || No<br />
|}<br />
<br />
=== Europe ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Stade de France || Saint-Denis || France || No<br />
|-<br />
|Zwischenahner Meer || Zwischenahn, Niedersachsen || Germany || '''CS done'''<br />
|-<br />
|Porta Westfalica/Hermans-Denkmal || Bückeburg (ETHB), Minden || Germany || No<br />
|-<br />
|Lapan || Oldenburg, Niedersachsen || Germany || No<br />
|-<br />
|Schloss || Oldenburg || Germany || No<br />
|-<br />
|Schloss || Neuschwanstein || Germany || Claimed<br />
|-<br />
|Colosseum || Rome || Italy || No<br />
|-<br />
|Oeresund Bridge || Copenhagen-Malmo || Scandinavia || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Oslo_Plaza Oslo Plaza] || Oslo || Norway || Claimed<br />
|-<br />
|Big Ben || London || UK || '''Yes'''<br />
|-<br />
|Westminster Abbey || London || UK || '''Yes'''<br />
|-<br />
|North Pole (flag and light) || North Pole || World || No<br />
|}<br />
<br />
=== Australia and Oceania ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Sydney Opera House || Sydney || Australia || '''Yes'''<br />
|-<br />
|Sky Tower || Auckland || New Zealand || '''Claimed'''<br />
|-<br />
|Ayers rock || Uluru || Australia || '''No'''<br />
|}<br />
<br />
== Related ==<br />
<br />
=== Internal links ===<br />
* [[FlightGear Scenery Designer]]<br />
* [[FlightGear Scenery Database]]<br />
* [[UK Scenery Wish List]]<br />
* [[Scenery_Tracker]]<br />
<br />
=== External links ===<br />
* [http://www.flightgear.org/forums/viewtopic.php?f=5&t=2390 The forum topic]<br />
* See [http://scenemodels.flightgear.org/ FGFS Scenery Object Database], for more on models for [[Scenery]]<br />
<br />
[[Category:Scenery]]<br />
[[Category:Community]]<br />
[[Category:Contribution requests]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=Landmark_Wish_List&diff=42566Landmark Wish List2012-02-25T08:59:41Z<p>Blackiris: /* Asia */</p>
<hr />
<div>This page provides a list of important landmarks which are not currently in FlightGear Scenery that the community would like to see modeled. If you are a FlightGear modeler and are looking for something to model, please consider something on this list.<br />
<br />
Feel free to add to this list.<br />
<br />
If you are modeling a landmark, please change the "Completed" column from "No" to "Claimed".<br />
<br />
=== Africa ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
| Pyramids || Cairo || Egypt || No<br />
|-<br />
| Victoria Falls || Victoria Falls || Zimbabwe || No<br />
|-<br />
|}<br />
<br />
=== America ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|National Congress || Brasilia || Brazil || '''Yes'''<br />
|-<br />
|Christ the Redeemer || Rio de Janeiro || Brazil || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Windsor_Atlantica_Hotel Windsor Atlantica Hotel] || Rio de Janeiro || Brazil || '''Claimed'''<br />
|-<br />
|Navy Pier || Chicago || USA || No<br />
|-<br />
|Adler Planetarium || Chicago || USA || No<br />
|-<br />
|Soldier Field || Chicago || USA || No<br />
|-<br />
|McCormick Place || Chicago || USA || No<br />
|-<br />
|U.S. Cellular Field || Chicago || USA || No<br />
|-<br />
|Wrigley Field || Chicago || USA || No<br />
|-<br />
|Shedd Aquarium || Chicago || USA || No<br />
|-<br />
|Union Station || Chicago || USA || No<br />
|-<br />
|Oglivie Transportation Center || Chicago || USA || No<br />
|-<br />
|Smurfit-Stone Building || Chicago || USA || No<br />
|-<br />
|Marina City || Chicago || USA || No<br />
|-<br />
|Millenium Park || Chicago || USA || No<br />
|-<br />
|United Center || Chicago || USA || No<br />
|-<br />
|Brooklyn Bridge || New York || USA || '''Claimed'''<br />
|-<br />
|Empire State Building || New York || USA || '''Yes'''<br />
|-<br />
|Chrysler Building || New York || USA || '''Claimed'''<br />
|-<br />
|United Nations Headquarters || New York || USA || '''Yes'''<br />
|-<br />
|Bank of America Tower || New York || USA || '''Yes'''<br />
|-<br />
|Verizon Center || Washington, D.C. || USA || No<br />
|-<br />
|White House || Washington, D.C. || USA || No<br />
|-<br />
|Space Needle || Seattle || USA || '''Yes'''<br />
|-<br />
|Milwaukee Art Museum || Milwaukee || USA || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Machu_Picchu Machu Picchu] || Aguas Calientes || Peru || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Nazca_Lines Nazca Lines] || Estudiantes || Peru || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Panama_canal Panama canal] and some boats pls|| Panama city - Colòn || Panama || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Hoover_Dam Hoover Dam]|| Boulder|| USA || No<br />
|-<br />
|[http://en.wikipedia.org/wiki/Skunk_Works Skunkworks aircraft] hidden in the mountain of KXTA || Area 51 || USA || No<br />
|}<br />
<br />
=== Asia ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Bank of China Tower || Hong Kong || China || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Kai_Tak_Airport "Checkerboard Hill" (VHHX approach)] || Hong Kong || China || '''no''', See [[Talk:Landmark_Wish_List#VHHX request| Talk page]]<br />
|-<br />
|CCTV Tower || Beijing || China || '''Yes'''<br />
|-<br />
|Taj Mahal || Agra || India || '''Yes'''<br />
|-<br />
|Akashi Kaikyo bridge || Kobe || Japan || '''Yes'''<br />
|-<br />
|Petronas Towers || Kuala Lumpur || Malaysia || '''Yes'''<br />
|-<br />
|Ryugyong Hotel || Pyongyang || North Korea || '''Yes'''<br />
|-<br />
|Burj Khalifa || Dubai || UAE || '''Yes'''<br />
|-<br />
|Burj al Arab || Dubai || UAE || '''Yes'''<br />
|-<br />
|Bitexco Financial Tower || Ho Chi Minh City || Vietnam || '''Yes'''<br />
|-<br />
|Sigiriya || Matale District || Sri Lanka || No<br />
|-<br />
|Great Wall of China || Huairou, Peking / Jiuduhezhen, Huairou, Peking || China || No<br />
|-<br />
|Mount Everest || Chukhung || Nepal || No<br />
|-<br />
|[[Talk:Landmark_Wish_List#Singapore| Something]] || Singapore ||Singapore || No<br />
|}<br />
<br />
=== Europe ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Stade de France || Saint-Denis || France || No<br />
|-<br />
|Zwischenahner Meer || Zwischenahn, Niedersachsen || Germany || '''CS done'''<br />
|-<br />
|Porta Westfalica/Hermans-Denkmal || Bückeburg (ETHB), Minden || Germany || No<br />
|-<br />
|Lapan || Oldenburg, Niedersachsen || Germany || No<br />
|-<br />
|Schloss || Oldenburg || Germany || No<br />
|-<br />
|Schloss || Neuschwanstein || Germany || Claimed<br />
|-<br />
|Colosseum || Rome || Italy || No<br />
|-<br />
|Oeresund Bridge || Copenhagen-Malmo || Scandinavia || '''Yes'''<br />
|-<br />
|[http://en.wikipedia.org/wiki/Oslo_Plaza Oslo Plaza] || Oslo || Norway || Claimed<br />
|-<br />
|Big Ben || London || UK || '''Yes'''<br />
|-<br />
|Westminster Abbey || London || UK || '''Yes'''<br />
|-<br />
|North Pole (flag and light) || North Pole || World || No<br />
|}<br />
<br />
=== Australia and Oceania ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Sydney Opera House || Sydney || Australia || '''Yes'''<br />
|-<br />
|Sky Tower || Auckland || New Zealand || '''Claimed'''<br />
|-<br />
|Ayers rock || Uluru || Australia || '''No'''<br />
|}<br />
<br />
== Related ==<br />
<br />
=== Internal links ===<br />
* [[FlightGear Scenery Designer]]<br />
* [[FlightGear Scenery Database]]<br />
* [[UK Scenery Wish List]]<br />
* [[Scenery_Tracker]]<br />
<br />
=== External links ===<br />
* [http://www.flightgear.org/forums/viewtopic.php?f=5&t=2390 The forum topic]<br />
* See [http://scenemodels.flightgear.org/ FGFS Scenery Object Database], for more on models for [[Scenery]]<br />
<br />
[[Category:Scenery]]<br />
[[Category:Community]]<br />
[[Category:Contribution requests]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_February_2012&diff=42109FlightGear Newsletter February 20122012-02-19T15:49:40Z<p>Blackiris: /* Scenery corner */</p>
<hr />
<div>{{draft|newsletter|Feel free to contribute! Or [[FlightGear Newsletter January 2012|read the latest edition]].}}<br />
{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
''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 news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''<br />
<br />
== Development news ==<br />
<br />
=== Heads up: Project Rembrandt ===<br />
As many of you may have heard already, Fred is currently making huge progress on adding shadows to FlightGear in [[Project Rembrandt]]. Now, F-JJTH ported the P92 to use the new system and posted a youtube video demonstrating [[Project Rembrandt]] at work. To provide feedback, please check out the the [http://flightgear.org/forums/viewtopic.php?f=47&t=14883 forum thread].<br />
<br />
{{#ev:youtube|v02phoOqWHE|400|Project Rembrandt at work}} [[File:Project-rembrandt-cockpit-lighting.png|400px|Cockpit lighting in Project Rembrandt at work (by F-JJTH)]]<br />
<br />
== Interview with a contributor (NAME) ==<br />
''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.''<br />
<br />
* How long have you been involved in FlightGear?<br />
* What are your major interests in FlightGear?<br />
* What project are you working on right now?<br />
* What do you plan on doing in the future?<br />
* Are you happy with the way the FlightGear project is going?<br />
* What do you enjoy most about developing for FlightGear?<br />
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?<br />
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?<br />
<br />
More questions are being collected here: [[Interview questions]].<br />
<br />
Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX <br />
<br />
== Snapshot releases ==<br />
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].<br />
<br />
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].<br />
<br />
== Nasal for newbies ==<br />
<br />
== New software tools and projects ==<br />
<br />
== FlightGear addons and mods ==<br />
<br />
== In the hangar ==<br />
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.<br />
<br />
=== A new instrument: Vertical Situation Display ===<br />
[[File:Omega95-vsd-instrument.jpeg|250px|thumb|Omega95's VSD instrument]]<br />
Omega95 has created an entirely new instrument type for FlightGear, a so called Vertical Situation Display (VSD). This was done entirely in scripting space using Nasal and XML animations. He's basically proven everbody wrong who ever claimed that complex instruments couldn't yet be created in scripting space. Apparently, he managed to create this instrument in less than 24 hrs. His first question related to this was about accessing trigonometric functions from Nasal, shortly thereafter he posted screen shots depicting his VSD. <br />
<br />
To read up on the whole discussion, please see [http://flightgear.org/forums/viewtopic.php?f=30&t=15200 the forum topic]. There's work ongoing to turn his project into a new tutorial for the wiki on creating complex instruments in scripting space: [[Howto: Implement a Vertical Situation Display in Nasal]].<br />
<br />
=== Glider winch launching ropes ===<br />
[[File:DG-101G_winch_launch_with_rope.png|thumb|250px|A DG-101G during a winch launch.]]<br />
FlightGear never showed ropes during winch launching. [[User:Gijs|Gijs]] started working on an animated 3D rope, attached to the glider and winch. The cable exist of the following parts:<br />
* '''Strop''' (3 m) attached to the glider with a ring.<br />
* '''Weak link assembly''' designed to break apart before the cable or any other equipment fails.<br />
* '''Trace''' (17 m)<br />
* '''Parachute''' so the cable doesn't drop too quickly after releasing.<br />
* '''Launch cable''' the longest part; all the way to the winch.<br />
<br />
=== New aircraft ===<br />
==== Hawker Siddeley Harrier GR.1 ====<br />
[[File:Harrier-GR1 Splash.png|thumb|250px|Harrier GR.1 splash screen]]<br />
[[Hawker Siddeley Harrier GR1]] is a private project by pjedvaj, it was not intended to replace or update the existing [[British Aerospace Harrier]]. It has a detailed 3D model, animations and RAF livery. Instruments and HUD are fairly authentic. The aircraft has working ADEN guns and basic fuel and weight control. FDM is adapted from the original BAe Harrier, internal and external fuel tank capacities are modified to match the GR.1 version.<br />
<br />
=== Updated aircraft ===<br />
<br />
==== Boeing 787-8 Dreamliner ====<br />
[[File:boeing-787-8-splash.png|thumb|250px|The Boeing 787-8 Splash Screen]]<br />
The Boeing 787-8 Dreamliner has already been there in FlightGear for a very long time but then it didn't have many of the 787's features like a realistic glass cockpit and many of the instruments. The new/updated Boeing 787-8 is a community project that features new JSBSim flight dynamics, Vertical Navigation, realistic 787 glass cockpit, new CDU, Electronic Flight Bag, TCAS, advanced Nav Displays, [http://wiki.flightgear.org/Howto:_Implement_a_Vertical_Situation_Display_in_Nasal|Vertical Situation Display], [http://wiki.flightgear.org/Howto:_Implement_a_Fly-By-Wire_System_for_Airliners|Fly-by-wire] and a lot of other neat features. It has not exactly been completed and the project is still running. You can find out more about the Boeing 787-8 Project HERE or wait for a while till a wiki page is created for it. One of the really good points of this project is how most of our findings and resources have been converted into Wiki HowTos for other aircraft developers to use for their projects.<br />
<br />
==== Cessna 337G Skymaster ====<br />
[[File:Cessna337-cockpit.png|thumb|250px|General view of the new Cessna 337G Skymaster cockpit]]<br />
The [[Cessna 337G Skymaster]] from the Spain-Latinamerica "Vive FlightGear" factory have received a major update. The new cockpit is now totally modelled, almost buttons and knobs are functional, animated, and properly labeled for easy identification. New custom sounds, lights, controls, a Bendix/King avionics pack capable of full IFR and night navigation, 2 new HQ liveries and the first FlightGear's working [[ELT]] (Emergency Locator Transmitter) are part of this great improvement on a FlightGear aircraft.<br />
<br />
=== Liveries ===<br />
<br />
== Scenery corner ==<br />
=== Shanghai ===<br />
[[File:SH fgfs-screen-001.png|250px|thumb|Shanghai skyline]]<br />
Shanghai is one of the biggest city in China and is among the cities with the most number of skyscrapers. Some work were done over the last few months to model the city's skylines, with 21 custom models.<br />
=== Airports ===<br />
<br />
== Aircraft of the month ==<br />
== Airport of the month ==<br />
== Screenshot of the month ==<br />
<br />
== Suggested flights ==<br />
===Copacabana to San Rafael over Lake Titicaca===<br />
Bolivia to Peru. This trip will lead you over one of the highest and deepest lakes in the world towards the highest airfield in the world. It a demonstration of a [[IFR]] flight towards a fix and a demonstration how accurate FlightGear simulates air density and the effects it has on aircraft.<br />
[[File:Slcc-sprf.jpg|thumb|200px|left|Flight and fix SLCC to SPRF]]<br />
Place your aircraft on the airfield [http://en.wikipedia.org/wiki/Copacabana,_Bolivia SLCC, Copacabana], with an [[elevation]] of 12,592 feet. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M). <br />
<br />
We will fly towards and land at SPRF. If you would enter SLCC and SPRF in [[Kelpie]] planner you probably would not be able to find SPRF. To find SPRF I am adding an additional VOR-DME station and for a good fix give you another VOR-DME. Try Kelpie planner to plan this route and compare with this suggestion.<br />
<br />
Equipment preparation. Set [[NAV1]] to [http://en.wikipedia.org/wiki/Juliaca Juliaca] VOR-DME on 155.55 with a radial of 311° (magnetic). Set [[NAV2]] to Arequipa VOR-DME on 113.7 with a radial of 212°. During our flight we will fly with [[true altitude]] as set with [[QNH]], keep QNH updated. Arm the autopilot with the [[heading bug]] at 311° and an initial altitude of 13,500 feet.<br />
<br />
Take off and if you took the wrong RW pull up hard. Take a small tour over [http://en.wikipedia.org/wiki/Titicaca lake Titicaca], see the floating islands and try to find the lost golden treasure. Intercept the nearest radial on NAV1 towards Juliaca (about 311°). <br />
<br />
Just before Juliaca is a hill so while on lake Titicaca increase altitude to 14,200 feet, the [[VFR]] part of this trip is over. After passing Juliaca set the radial of NAV1 to 352° and set the altitude to 17,422 feet. We will fly from NAV1 and slowly increase altitude.<br />
<br />
At a distance of about 60 NM set the heading bug on the current course. Monitor the distance to NAV1, the radial of NAV2 and the distance to NAV2. At a distance of 74.5 NM to NAV1, a distance of 140.7 NM and at the '''radial''' intercept of NAV2 should be the runway. So, from 60 NM onwards, look outside the window, then at NAV1 and then NAV2 etc.<br />
<br />
If you are at 80NM to NAV1 you have missed the airfield but you still won't hit any hills (unless you bank left). Bank right and set the heading bug to 172°. Fly back towards NAV1 and intercept the radial 352° at about 50NM again to repeat the search.<br />
<br />
The runway SPRF, San Rafael, has a elevation of 14,422 feet and a heading of 297°/ 117°. Our initial altitude has been set 3,000NM above the RW elevation. That should give sufficient room for navigation.<br />
<br />
After you have seen the airfield set the radial of NAV1 to 297°, the heading of the runway (not the course to the runway) as a visual aid. Land on RW 30 (and not on RW 12 unless you are a show-off). Oh, there is a small hill in front of RW 30, just so you know.<br />
<br />
Decreasing speed at this altitude can be a bit tricky. The air is thin and does not give much resistance. Next to that, the difference between [[indicated airspeed]] and [[ground speed]] is very noticeable. The ground speed is much higher as the indicated airspeed.<br />
<br />
After a successful landing, try to discover the [[Suggested_Flights#Origin_of_the_Amazon_River | origin of the Amazon river]] since we are now at the starting point of that trip.<br />
<br />
*More places you can visit can be found at [[Suggested Flights]].<br />
<br />
== Aircraft reviews ==<br />
<br />
== Wiki updates ==<br />
[[User:Johan G|Johan G]] did a great job categorising all images. All sub-categories are listed under [[:Category:Images]]. Please note when uploading images that it's important to give the file a descriptive name. That'll make it easier for others to find your file and use it in articles.<br />
<br />
A good example comes from Michat who has designed new small logos for [[Dual Control]] and [[Bombable]] aircrafts allowing you to see at a glance if aircraft has some of those interesting features.<br />
<br />
[[File:Dualcontrolready2.png|Dual_control]] [[File:BombableReady.png|Bombable]].<br />
<br />
<br />
<br />
===New articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
</DynamicArticleList><br />
===New aircraft articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
categoryRoot=Aircraft<br />
</DynamicArticleList><br />
===Most popular newsletters===<br />
<DynamicArticleList><br />
type=hot<br />
count=5<br />
categoryRoot=FlightGear Newsletter<br />
</DynamicArticleList><br />
<br />
== Community news ==<br />
=== FlightGear on YouTube ===<br />
* [http://youtu.be/hBEaOMzBq6E KSFO Thermal Demo] by MD-BFC Going on their way for Bocian certification<br />
* [http://youtu.be/-yI5PzC5RE8 Sukhoi 37 'The russian dream'] by Águilas de FlightGear performing "Balalaika amok" master tune by Aleksei Arkhipovsky.<br />
<br />
=== New tutorials and screencasts ===<br />
=== Forum news ===<br />
=== Multiplayer ===<br />
=== Virtual airlines ===<br />
=== FlightGear events ===<br />
<br />
== Useful links ==<br />
== And finally ... ==<br />
=== Contributing ===<br />
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
=== Call for volunteers ===<br />
* The [[OpenRadar]] project is looking for a new maintainer.<br />
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.<br />
<br />
=== Did you know ===<br />
...that you can use expressions to create complex animations of objects in your 3d models or even drive them from multiple properties?<br />
Usually, an animation looks like this<br />
<syntaxhighlight lang="xml"><br />
<animation><br />
<type>translate</type><br />
<property>foo/bar</property><br />
[..]more elements[..]<br />
</animation><br />
</syntaxhighlight><br />
You can add a scaling factor or an offset to it, but that's basically all you can do that way. <br />
If you want to animate your object following a complex function, most people create complex Nasal scripts to compute the driving properties, probably not knowing that there is another way to achieve the goal: Expressions. <br />
Here is an example for a translate animation depending on two properties and the cosine function<br />
<syntaxhighlight lang="xml"><br />
<animation><br />
<type>translate</type><br />
<expression><br />
<product><br />
<property>/my/factor-property</property><br />
<cos><br />
<deg2rad><br />
<property>/my/angular-property</property><br />
</deg2rad><br />
</cos><br />
</product><br />
</expression><br />
[..]more elements[..]<br />
</animation><br />
</syntaxhighlight><br />
A rich set of predefined functions is available, including almost all those you have on your scientific pocket calculator.<br />
<br />
[[Category:FlightGear Newsletter|2012 02]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=File:SH_fgfs-screen-001.png&diff=42107File:SH fgfs-screen-001.png2012-02-19T15:48:05Z<p>Blackiris: </p>
<hr />
<div></div>Blackirishttps://wiki.flightgear.org/w/index.php?title=User:Blackiris&diff=36630User:Blackiris2011-10-31T08:51:51Z<p>Blackiris: Created page with "I'm still a student, but I like working on scenery models, especially skyscrapers in Asia."</p>
<hr />
<div>I'm still a student, but I like working on scenery models, especially skyscrapers in Asia.</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=User_talk:PH-JBO&diff=36629User talk:PH-JBO2011-10-31T08:50:29Z<p>Blackiris: </p>
<hr />
<div>==Place your comments and replies here==<br />
Use the + next to edit in the top bar, insert <nowiki>~~~~</nowiki> to sign a comment)<br />
<br />
==Something about suggested flight==<br />
Hi, I have seen you have posted a suggested flight in the september 2011 newsletter, since I am working on a [[Places_to_fly]] page, do you mind on adding your suggested flight on that page too ? I will then add charts and stuff if you wish...<BR/><br />
[[User:Francescobrisa|Francescobrisa]] 14:09, 6 September 2011 (EDT)<br />
<br />
*Sure, add that suggested flight. Great Idea! [[User:PH-JBO|PH-JBO]] 17:50, 6 September 2011 (EDT)<br />
*Oh, and all flights are free to use on your page naturally :) [[User:PH-JBO|PH-JBO]] 17:56, 6 September 2011 (EDT)<br />
<br />
Sorry, I was not notified by email about wiki changes (Wrong email address in my account); I saw you replays only now, I will try to follow your suggestions.<BR/><br />
thanks<BR/><br />
--[[User:Francescobrisa|Francescobrisa]] 12:14, 14 September 2011 (EDT)<br />
<br />
== Air speeds ==<br />
<br />
Good work on the air speeds. I believe that collecting all the relevant terms in one page is the way to go. :-) [[User:Johan G|Johan G]] 13:29, 8 October 2011 (EDT)<br />
*Thank you :) I reworked the existing article that was quite hidden on the wiki. [[User:PH-JBO|PH-JBO]] 06:19, 9 October 2011 (EDT)<br />
<br />
== Scenery suggestion ==<br />
Hi, I saw that you suggested "something" for Singapore. can you be more precise? Thanks! [[User:Blackiris|Blackiris]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=User_talk:PH-JBO&diff=36628User talk:PH-JBO2011-10-31T08:49:35Z<p>Blackiris: </p>
<hr />
<div>==Place your comments and replies here==<br />
Use the + next to edit in the top bar, insert <nowiki>~~~~</nowiki> to sign a comment)<br />
<br />
==Something about suggested flight==<br />
Hi, I have seen you have posted a suggested flight in the september 2011 newsletter, since I am working on a [[Places_to_fly]] page, do you mind on adding your suggested flight on that page too ? I will then add charts and stuff if you wish...<BR/><br />
[[User:Francescobrisa|Francescobrisa]] 14:09, 6 September 2011 (EDT)<br />
<br />
*Sure, add that suggested flight. Great Idea! [[User:PH-JBO|PH-JBO]] 17:50, 6 September 2011 (EDT)<br />
*Oh, and all flights are free to use on your page naturally :) [[User:PH-JBO|PH-JBO]] 17:56, 6 September 2011 (EDT)<br />
<br />
Sorry, I was not notified by email about wiki changes (Wrong email address in my account); I saw you replays only now, I will try to follow your suggestions.<BR/><br />
thanks<BR/><br />
--[[User:Francescobrisa|Francescobrisa]] 12:14, 14 September 2011 (EDT)<br />
<br />
== Air speeds ==<br />
<br />
Good work on the air speeds. I believe that collecting all the relevant terms in one page is the way to go. :-) [[User:Johan G|Johan G]] 13:29, 8 October 2011 (EDT)<br />
*Thank you :) I reworked the existing article that was quite hidden on the wiki. [[User:PH-JBO|PH-JBO]] 06:19, 9 October 2011 (EDT)<br />
<br />
== Scenery suggestion ==<br />
Hi, I saw that you suggested "something" for Singapore. can you be more precise? Thanks!</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=Landmark_Wish_List&diff=32290Landmark Wish List2011-06-12T10:00:25Z<p>Blackiris: </p>
<hr />
<div>This page provides a list of important landmarks which are not currently in FlightGear Scenery that the community would like to see modeled. If you are a FlightGear modeler and are looking for something to model, please consider something on this list.<br />
<br />
Feel free to add to this list.<br />
<br />
If you are modeling a landmark, please change the "Completed" column from "No" to "Claimed".<br />
<br />
=== Africa ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|}<br />
=== America ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|National Congress || Brasilia || Brazil || '''Yes'''<br />
|-<br />
|Christ the Redeemer || Rio de Janeiro || Brazil || '''Yes'''<br />
|-<br />
|Navy Pier || Chicago || USA || No<br />
|-<br />
|Adler Planetarium || Chicago || USA || No<br />
|-<br />
|Soldier Field || Chicago || USA || No<br />
|-<br />
|McCormick Place || Chicago || USA || No<br />
|-<br />
|U.S. Cellular Field || Chicago || USA || No<br />
|-<br />
|Wrigley Field || Chicago || USA || No<br />
|-<br />
|Shedd Aquarium || Chicago || USA || No<br />
|-<br />
|Union Station || Chicago || USA || No<br />
|-<br />
|Oglivie Transportation Center || Chicago || USA || No<br />
|-<br />
|Smurfit-Stone Building || Chicago || USA || No<br />
|-<br />
|Marina City || Chicago || USA || No<br />
|-<br />
|Millenium Park || Chicago || USA || No<br />
|-<br />
|United Center || Chicago || USA || No<br />
|-<br />
|Brooklyn Bridge || New York || USA || '''Claimed'''<br />
|-<br />
|Empire State Building || New York || USA || '''Yes'''<br />
|-<br />
|Chrysler Building || New York || USA || '''Claimed'''<br />
|-<br />
|United Nations Headquarters || New York || USA || '''Yes'''<br />
|-<br />
|Bank of America Tower || New York || USA || '''Yes'''<br />
|-<br />
|Verizon Center || Washington, D.C. || USA || No<br />
|-<br />
|White House || Washington, D.C. || USA || No<br />
|-<br />
|Space Needle || Seattle || USA || '''Yes'''<br />
|-<br />
|Milwaukee Art Museum || Milwaukee || USA || No<br />
|}<br />
<br />
=== Asia ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Bank of China Tower || Hong Kong || China || '''Yes'''<br />
|-<br />
|CCTV Tower || Beijing || China || '''Yes'''<br />
|-<br />
|Taj Mahal || Agra || India || '''Yes'''<br />
|-<br />
|Akashi Kaikyo bridge || Kobe || Japan || '''Yes'''<br />
|-<br />
|Petronas Towers || Kuala Lumpur || Malaysia || '''Yes'''<br />
|-<br />
|Ryugyong Hotel || Pyongyang || North Korea || '''Yes'''<br />
|-<br />
|Burj Khalifa || Dubai || UAE || '''Yes'''<br />
|-<br />
|Burj al Arab || Dubai || UAE || '''Yes'''<br />
|-<br />
|Bitexco Financial Tower || Ho Chi Minh City || Vietnam || '''Yes'''<br />
|-<br />
|Sigiriya || Matale District || Sri Lanka || '''No'''<br />
|}<br />
<br />
=== Europe ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Stade de France || Saint-Denis || France || No<br />
|-<br />
|Zwischenahner Meer || Zwischenahn, Niedersachsen || Germany || '''CS done'''<br />
|-<br />
|Porta Westfalica/Hermans-Denkmal || Bückeburg (ETHB), Minden || Germany || No<br />
|-<br />
|Lapan || Oldenburg, Niedersachsen || Germany || No<br />
|-<br />
|Schloss || Oldenburg || Germany || No<br />
|-<br />
|Colosseum || Rome || Italy || No<br />
|-<br />
|Oeresund Bridge || Copenhagen-Malmo || Scandinavia || '''Yes'''<br />
|-<br />
|Big Ben || London || UK || '''Yes'''<br />
|-<br />
|Westminster Abbey || London || UK || '''Yes'''<br />
|}<br />
=== Oceania ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Sydney Opera House || Sydney || Australia || '''Yes'''<br />
|-<br />
|Sky Tower || Auckland || New Zealand || '''Claimed'''<br />
|}<br />
<br />
<br />
== Related ==<br />
<br />
=== Internal links ===<br />
* [[FlightGear Scenery Designer]]<br />
* [[FlightGear Scenery Database]]<br />
* [[UK Scenery Wish List]]<br />
=== External links ===<br />
* [http://www.flightgear.org/forums/viewtopic.php?f=5&t=2390 The forum topic]<br />
* See [http://scenemodels.flightgear.org/ FGFS Scenery Object Database], for more on models for [[Scenery]]<br />
<br />
[[Category:Scenery]]<br />
[[Category:Community]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=Landmark_Wish_List&diff=32289Landmark Wish List2011-06-12T08:29:49Z<p>Blackiris: /* America */</p>
<hr />
<div>This page provides a list of important landmarks which are not currently in FlightGear Scenery that the community would like to see modeled. If you are a FlightGear modeler and are looking for something to model, please consider something on this list.<br />
<br />
Feel free to add to this list.<br />
<br />
If you are modeling a landmark, please change the "Completed" column from "No" to "Claimed".<br />
<br />
=== Africa ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|}<br />
=== America ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|National Congress || Brasilia || Brazil || '''Yes'''<br />
|-<br />
|Christ the Redeemer || Rio de Janeiro || Brazil || '''Yes'''<br />
|-<br />
|Navy Pier || Chicago || USA || No<br />
|-<br />
|Adler Planetarium || Chicago || USA || No<br />
|-<br />
|Soldier Field || Chicago || USA || No<br />
|-<br />
|McCormick Place || Chicago || USA || No<br />
|-<br />
|U.S. Cellular Field || Chicago || USA || No<br />
|-<br />
|Wrigley Field || Chicago || USA || No<br />
|-<br />
|Shedd Aquarium || Chicago || USA || No<br />
|-<br />
|Union Station || Chicago || USA || No<br />
|-<br />
|Oglivie Transportation Center || Chicago || USA || No<br />
|-<br />
|Smurfit-Stone Building || Chicago || USA || No<br />
|-<br />
|Marina City || Chicago || USA || No<br />
|-<br />
|Millenium Park || Chicago || USA || No<br />
|-<br />
|United Center || Chicago || USA || No<br />
|-<br />
|Brooklyn Bridge || New York || USA || '''Claimed'''<br />
|-<br />
|Empire State Building || New York || USA || '''Yes'''<br />
|-<br />
|Chrysler Building || New York || USA || '''Claimed'''<br />
|-<br />
|United Nations Headquarters || New York || USA || '''Yes'''<br />
|-<br />
|Bank of America Tower || New York || USA || '''Claimed'''<br />
|-<br />
|Verizon Center || Washington, D.C. || USA || No<br />
|-<br />
|White House || Washington, D.C. || USA || No<br />
|-<br />
|Space Needle || Seattle || USA || '''Yes'''<br />
|-<br />
|Milwaukee Art Museum || Milwaukee || USA || No<br />
|}<br />
<br />
=== Asia ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Bank of China Tower || Hong Kong || China || '''Yes'''<br />
|-<br />
|CCTV Tower || Beijing || China || '''Yes'''<br />
|-<br />
|Taj Mahal || Agra || India || '''Yes'''<br />
|-<br />
|Akashi Kaikyo bridge || Kobe || Japan || '''Yes'''<br />
|-<br />
|Petronas Towers || Kuala Lumpur || Malaysia || '''Yes'''<br />
|-<br />
|Ryugyong Hotel || Pyongyang || North Korea || '''Yes'''<br />
|-<br />
|Burj Khalifa || Dubai || UAE || '''Yes'''<br />
|-<br />
|Burj al Arab || Dubai || UAE || '''Yes'''<br />
|-<br />
|Bitexco Financial Tower || Ho Chi Minh City || Vietnam || '''Yes'''<br />
|-<br />
|Sigiriya || Matale District || Sri Lanka || '''No'''<br />
|}<br />
<br />
=== Europe ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Stade de France || Saint-Denis || France || No<br />
|-<br />
|Zwischenahner Meer || Zwischenahn, Niedersachsen || Germany || '''CS done'''<br />
|-<br />
|Porta Westfalica/Hermans-Denkmal || Bückeburg (ETHB), Minden || Germany || No<br />
|-<br />
|Lapan || Oldenburg, Niedersachsen || Germany || No<br />
|-<br />
|Schloss || Oldenburg || Germany || No<br />
|-<br />
|Colosseum || Rome || Italy || No<br />
|-<br />
|Oeresund Bridge || Copenhagen-Malmo || Scandinavia || '''Yes'''<br />
|-<br />
|Big Ben || London || UK || '''Yes'''<br />
|-<br />
|Westminster Abbey || London || UK || '''Yes'''<br />
|}<br />
=== Oceania ===<br />
{| class="wikitable sortable" border="1" cellspacing="0" <br />
|-<br />
! style="background:#efefef" | Landmark<br />
! style="background:#efefef" | City<br />
! style="background:#efefef" | Country<br />
! style="background:#efefef" | Completed<br />
|-<br />
|Sydney Opera House || Sydney || Australia || '''Yes'''<br />
|-<br />
|Sky Tower || Auckland || New Zealand || '''Claimed'''<br />
|}<br />
<br />
<br />
== Related ==<br />
<br />
=== Internal links ===<br />
* [[FlightGear Scenery Designer]]<br />
* [[FlightGear Scenery Database]]<br />
* [[UK Scenery Wish List]]<br />
=== External links ===<br />
* [http://www.flightgear.org/forums/viewtopic.php?f=5&t=2390 The forum topic]<br />
* See [http://scenemodels.flightgear.org/ FGFS Scenery Object Database], for more on models for [[Scenery]]<br />
<br />
[[Category:Scenery]]<br />
[[Category:Community]]</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_May_2011&diff=31680FlightGear Newsletter May 20112011-05-14T12:09:46Z<p>Blackiris: /* Seoul */</p>
<hr />
<div>{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
''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.''<br />
<br />
== Development news ==<br />
== Nasal for newbies ==<br />
== New software tools and projects ==<br />
<br />
== FlightGear addons and mods ==<br />
== In the hangar ==<br />
=== New aircraft ===<br />
=== Updated aircraft ===<br />
<br />
====Airbus A340-600====<br />
<br />
More work has continued on developing an [http://en.wikipedia.org/wiki/A340-600 Airbus A340-600] for FlightGear. The aircraft has been given a new lease of life with a new JSBsim FDM which replicates better the size and control of such a large bird, and there is much more work on it to come. The model itself is looking very attractive with a newly modelled fuselage from British user Simon (MOJO), and some nice new reflection coding, lights and external models. It has a 3D cockpit which is currently identical to that of the A320-family in FlightGear (by Skyop and Ampere), as an A340 cockpit is being built from scratch by Skyop himself; This doesn't spoil it as they share 99% of similarities in real life. The aircraft was the first in FlightGear to incorporate aircraft operation equipment, and Cabin announcements; back in 2009.. and now these have been improved with new recordings by the author (Liam, if you're wondering who's voice that is), and work is continuing to make the aircraft one of the most enjoyable heavy metal birds to fly in FlightGear simulator. Thanks to all the users who have helped this slow moving project progress. If you are wondering where you can download this new version.. check out the Aircraft section in the FlightGear forums, where there is a special topic dedicated to it.<br />
<br />
[[Image:Airbus1.png|200px]] [[Image:Airbus.png|200px]]<br />
<br />
=== Liveries ===<br />
<br />
== Scenery corner ==<br />
===Seoul===<br />
Seoul is an impressive city where modern buildings with amazing design are mixed with the Korean traditional architecture of old buildings. Here are the buildings added this month: [[File:Yeouido-005.png|220px|thumb|right|Yeouido island]] [[File:Gyeongbok Palace.png|220px|thumb|right|Gyeongbok Palace]] <br />
* Modern buildings<br />
** Dongbu Finance Building<br />
** GT Tower East<br />
** S-Trenue Tower<br />
** SK T-tower<br />
** Jongno Tower<br />
** Seoul World Cup Stadium<br />
*Old buildings<br />
** Namdaemun<br />
** Gyeonghoeru Pavillon<br />
** Geunjeongjeon<br />
*Others<br />
** National Assembly Building<br />
<br />
In addition to that, about 150 generic buildings have been added in Yeouido island, one of Seoul's main business districts. It should be available in Terrasync very soon.<br />
<br />
=== Airports ===<br />
<br />
== Aircraft of the month ==<br />
== Airport of the month ==<br />
== Screenshot of the month ==<br />
<br />
[[File:Winner.jpg|400px|]]<br><br />
Screenshot which won Contest for the Best Screenshot of 2011 on Polish FlightGear forum.<br><br />
Congratulations for viper29!<br />
<br />
== Suggested flights ==<br />
== Aircraft reviews ==<br />
<br />
== Wiki updates ==<br />
===New articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
</DynamicArticleList><br />
===New aircraft articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
categoryRoot=Aircraft<br />
</DynamicArticleList><br />
===Most popular newsletters===<br />
<DynamicArticleList><br />
type=hot<br />
count=5<br />
categoryRoot=FlightGear Newsletter<br />
</DynamicArticleList><br />
<br />
== Community news ==<br />
=== FlightGear on youtube ===<br />
=== FlightGear on Flickr ===<br />
* http://www.flickr.com/groups/flightgear_simulator/<br />
* http://www.flickr.com/groups/flightgear/<br />
=== New tutorials and screencasts ===<br />
=== Forum news ===<br />
=== Multiplayer ===<br />
=== Virtual airlines ===<br />
=== FlightGear events ===<br />
<br />
== Useful links ==<br />
== And finally ... ==<br />
=== Contributing ===<br />
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
=== Call for volunteers ===<br />
* The [[OpenRadar]] project is looking for a new maintainer.<br />
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.<br />
<br />
=== Did you know ===</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_May_2011&diff=31679FlightGear Newsletter May 20112011-05-14T12:08:17Z<p>Blackiris: /* Seoul */</p>
<hr />
<div>{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
''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.''<br />
<br />
== Development news ==<br />
== Nasal for newbies ==<br />
== New software tools and projects ==<br />
<br />
== FlightGear addons and mods ==<br />
== In the hangar ==<br />
=== New aircraft ===<br />
=== Updated aircraft ===<br />
<br />
====Airbus A340-600====<br />
<br />
More work has continued on developing an [http://en.wikipedia.org/wiki/A340-600 Airbus A340-600] for FlightGear. The aircraft has been given a new lease of life with a new JSBsim FDM which replicates better the size and control of such a large bird, and there is much more work on it to come. The model itself is looking very attractive with a newly modelled fuselage from British user Simon (MOJO), and some nice new reflection coding, lights and external models. It has a 3D cockpit which is currently identical to that of the A320-family in FlightGear (by Skyop and Ampere), as an A340 cockpit is being built from scratch by Skyop himself; This doesn't spoil it as they share 99% of similarities in real life. The aircraft was the first in FlightGear to incorporate aircraft operation equipment, and Cabin announcements; back in 2009.. and now these have been improved with new recordings by the author (Liam, if you're wondering who's voice that is), and work is continuing to make the aircraft one of the most enjoyable heavy metal birds to fly in FlightGear simulator. Thanks to all the users who have helped this slow moving project progress. If you are wondering where you can download this new version.. check out the Aircraft section in the FlightGear forums, where there is a special topic dedicated to it.<br />
<br />
[[Image:Airbus1.png|200px]] [[Image:Airbus.png|200px]]<br />
<br />
=== Liveries ===<br />
<br />
== Scenery corner ==<br />
===Seoul===<br />
Seoul is an impressive city where modern buildings with amazing design are mixed with the Korean traditional architecture of old buildings. Here are the buildings added this month: [[File:Yeouido-005.png|220px|thumb|right|Yeouido island]] [[File:Gyeongbok Palace.png|220px|thumb|right|Gyeongbok Palace]] <br />
* Modern buildings<br />
** Dongbu Finance Building<br />
** GT Tower East<br />
** S-Trenue Tower<br />
** SK T-tower<br />
** Jongno Tower<br />
** Seoul World Cup Stadium<br />
*Old buildings<br />
** Namdaemun<br />
** Gyeonghoeru Pavillon<br />
** Geunjeongjeon<br />
*Others<br />
** National Assembly Building<br />
<br />
In addition to that, about 150 generic buildings have been added in Yeouido island, one of Seoul's main business district. It should be available in Terrasync very soon.<br />
<br />
=== Airports ===<br />
<br />
== Aircraft of the month ==<br />
== Airport of the month ==<br />
== Screenshot of the month ==<br />
<br />
[[File:Winner.jpg|400px|]]<br><br />
Screenshot which won Contest for the Best Screenshot of 2011 on Polish FlightGear forum.<br><br />
Congratulations for viper29!<br />
<br />
== Suggested flights ==<br />
== Aircraft reviews ==<br />
<br />
== Wiki updates ==<br />
===New articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
</DynamicArticleList><br />
===New aircraft articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
categoryRoot=Aircraft<br />
</DynamicArticleList><br />
===Most popular newsletters===<br />
<DynamicArticleList><br />
type=hot<br />
count=5<br />
categoryRoot=FlightGear Newsletter<br />
</DynamicArticleList><br />
<br />
== Community news ==<br />
=== FlightGear on youtube ===<br />
=== FlightGear on Flickr ===<br />
* http://www.flickr.com/groups/flightgear_simulator/<br />
* http://www.flickr.com/groups/flightgear/<br />
=== New tutorials and screencasts ===<br />
=== Forum news ===<br />
=== Multiplayer ===<br />
=== Virtual airlines ===<br />
=== FlightGear events ===<br />
<br />
== Useful links ==<br />
== And finally ... ==<br />
=== Contributing ===<br />
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
=== Call for volunteers ===<br />
* The [[OpenRadar]] project is looking for a new maintainer.<br />
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.<br />
<br />
=== Did you know ===</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_May_2011&diff=31678FlightGear Newsletter May 20112011-05-14T12:07:13Z<p>Blackiris: /* Seoul */</p>
<hr />
<div>{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
''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.''<br />
<br />
== Development news ==<br />
== Nasal for newbies ==<br />
== New software tools and projects ==<br />
<br />
== FlightGear addons and mods ==<br />
== In the hangar ==<br />
=== New aircraft ===<br />
=== Updated aircraft ===<br />
<br />
====Airbus A340-600====<br />
<br />
More work has continued on developing an [http://en.wikipedia.org/wiki/A340-600 Airbus A340-600] for FlightGear. The aircraft has been given a new lease of life with a new JSBsim FDM which replicates better the size and control of such a large bird, and there is much more work on it to come. The model itself is looking very attractive with a newly modelled fuselage from British user Simon (MOJO), and some nice new reflection coding, lights and external models. It has a 3D cockpit which is currently identical to that of the A320-family in FlightGear (by Skyop and Ampere), as an A340 cockpit is being built from scratch by Skyop himself; This doesn't spoil it as they share 99% of similarities in real life. The aircraft was the first in FlightGear to incorporate aircraft operation equipment, and Cabin announcements; back in 2009.. and now these have been improved with new recordings by the author (Liam, if you're wondering who's voice that is), and work is continuing to make the aircraft one of the most enjoyable heavy metal birds to fly in FlightGear simulator. Thanks to all the users who have helped this slow moving project progress. If you are wondering where you can download this new version.. check out the Aircraft section in the FlightGear forums, where there is a special topic dedicated to it.<br />
<br />
[[Image:Airbus1.png|200px]] [[Image:Airbus.png|200px]]<br />
<br />
=== Liveries ===<br />
<br />
== Scenery corner ==<br />
===Seoul===<br />
Seoul is an impressive city where modern buildings with amazing design are mixed with the Korean traditional architecture of old buildings. Here are the buildings added this month: [[File:Yeouido-005.png|220px|thumb|right|Yeouido island]] [[File:Gyeongbok Palace.png|220px|thumb|right|Gyeongbok Palace]] <br />
* Modern buildings<br />
** Dongbu Finance Building<br />
** GT Tower East<br />
** S-Trenue Tower<br />
** SK T-tower<br />
** Jongno Tower<br />
** Seoul World Cup Stadium<br />
*Old buildings<br />
** Namdaemun<br />
** Gyeonghoeru Pavillon<br />
** Geunjeongjeon<br />
*Others<br />
** National Assembly Building<br />
<br />
In addition to that, about 150 generic buildings have been added in Yeouido island, one of Seoul's main business district<br />
<br />
=== Airports ===<br />
<br />
== Aircraft of the month ==<br />
== Airport of the month ==<br />
== Screenshot of the month ==<br />
<br />
[[File:Winner.jpg|400px|]]<br><br />
Screenshot which won Contest for the Best Screenshot of 2011 on Polish FlightGear forum.<br><br />
Congratulations for viper29!<br />
<br />
== Suggested flights ==<br />
== Aircraft reviews ==<br />
<br />
== Wiki updates ==<br />
===New articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
</DynamicArticleList><br />
===New aircraft articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
categoryRoot=Aircraft<br />
</DynamicArticleList><br />
===Most popular newsletters===<br />
<DynamicArticleList><br />
type=hot<br />
count=5<br />
categoryRoot=FlightGear Newsletter<br />
</DynamicArticleList><br />
<br />
== Community news ==<br />
=== FlightGear on youtube ===<br />
=== FlightGear on Flickr ===<br />
* http://www.flickr.com/groups/flightgear_simulator/<br />
* http://www.flickr.com/groups/flightgear/<br />
=== New tutorials and screencasts ===<br />
=== Forum news ===<br />
=== Multiplayer ===<br />
=== Virtual airlines ===<br />
=== FlightGear events ===<br />
<br />
== Useful links ==<br />
== And finally ... ==<br />
=== Contributing ===<br />
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
=== Call for volunteers ===<br />
* The [[OpenRadar]] project is looking for a new maintainer.<br />
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.<br />
<br />
=== Did you know ===</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_May_2011&diff=31677FlightGear Newsletter May 20112011-05-14T12:05:18Z<p>Blackiris: /* Seoul */</p>
<hr />
<div>{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
''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.''<br />
<br />
== Development news ==<br />
== Nasal for newbies ==<br />
== New software tools and projects ==<br />
<br />
== FlightGear addons and mods ==<br />
== In the hangar ==<br />
=== New aircraft ===<br />
=== Updated aircraft ===<br />
<br />
====Airbus A340-600====<br />
<br />
More work has continued on developing an [http://en.wikipedia.org/wiki/A340-600 Airbus A340-600] for FlightGear. The aircraft has been given a new lease of life with a new JSBsim FDM which replicates better the size and control of such a large bird, and there is much more work on it to come. The model itself is looking very attractive with a newly modelled fuselage from British user Simon (MOJO), and some nice new reflection coding, lights and external models. It has a 3D cockpit which is currently identical to that of the A320-family in FlightGear (by Skyop and Ampere), as an A340 cockpit is being built from scratch by Skyop himself; This doesn't spoil it as they share 99% of similarities in real life. The aircraft was the first in FlightGear to incorporate aircraft operation equipment, and Cabin announcements; back in 2009.. and now these have been improved with new recordings by the author (Liam, if you're wondering who's voice that is), and work is continuing to make the aircraft one of the most enjoyable heavy metal birds to fly in FlightGear simulator. Thanks to all the users who have helped this slow moving project progress. If you are wondering where you can download this new version.. check out the Aircraft section in the FlightGear forums, where there is a special topic dedicated to it.<br />
<br />
[[Image:Airbus1.png|200px]] [[Image:Airbus.png|200px]]<br />
<br />
=== Liveries ===<br />
<br />
== Scenery corner ==<br />
===Seoul===<br />
Seoul is an impressive city where modern buildings with amazing design are mixed with the Korean traditional architecture of old buildings. Here are the buildings added this month: [[File:Yeouido-005.png|220px|thumb|right|Yeouido island]] [[File:Gyeongbok Palace.png|220px|thumb|right|Gyeongbok Palace]] <br />
* Modern buildings<br />
** Dongbu Finance Building<br />
** GT Tower East<br />
** S-Trenue Tower<br />
** SK T-tower<br />
** Jongno Tower<br />
** Seoul World Cup Stadium<br />
*Old buildings<br />
** Namdaemun<br />
** Gyeonghoeru Pavillon<br />
** Geunjeongjeon<br />
*Others<br />
** National Assembly Building<br />
<br />
Moreover, about 150 generic buildings have been added in Yeouido island.<br />
<br />
=== Airports ===<br />
<br />
== Aircraft of the month ==<br />
== Airport of the month ==<br />
== Screenshot of the month ==<br />
<br />
[[File:Winner.jpg|400px|]]<br><br />
Screenshot which won Contest for the Best Screenshot of 2011 on Polish FlightGear forum.<br><br />
Congratulations for viper29!<br />
<br />
== Suggested flights ==<br />
== Aircraft reviews ==<br />
<br />
== Wiki updates ==<br />
===New articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
</DynamicArticleList><br />
===New aircraft articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
categoryRoot=Aircraft<br />
</DynamicArticleList><br />
===Most popular newsletters===<br />
<DynamicArticleList><br />
type=hot<br />
count=5<br />
categoryRoot=FlightGear Newsletter<br />
</DynamicArticleList><br />
<br />
== Community news ==<br />
=== FlightGear on youtube ===<br />
=== FlightGear on Flickr ===<br />
* http://www.flickr.com/groups/flightgear_simulator/<br />
* http://www.flickr.com/groups/flightgear/<br />
=== New tutorials and screencasts ===<br />
=== Forum news ===<br />
=== Multiplayer ===<br />
=== Virtual airlines ===<br />
=== FlightGear events ===<br />
<br />
== Useful links ==<br />
== And finally ... ==<br />
=== Contributing ===<br />
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
=== Call for volunteers ===<br />
* The [[OpenRadar]] project is looking for a new maintainer.<br />
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.<br />
<br />
=== Did you know ===</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=File:Gyeongbok_Palace.png&diff=31676File:Gyeongbok Palace.png2011-05-14T12:04:02Z<p>Blackiris: Gyeongbok Palace - Seoul
Not really finished but main building are here.</p>
<hr />
<div>Gyeongbok Palace - Seoul<br />
Not really finished but main building are here.</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_May_2011&diff=31675FlightGear Newsletter May 20112011-05-14T11:53:59Z<p>Blackiris: /* Seoul */</p>
<hr />
<div>{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
''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.''<br />
<br />
== Development news ==<br />
== Nasal for newbies ==<br />
== New software tools and projects ==<br />
<br />
== FlightGear addons and mods ==<br />
== In the hangar ==<br />
=== New aircraft ===<br />
=== Updated aircraft ===<br />
<br />
====Airbus A340-600====<br />
<br />
More work has continued on developing an [http://en.wikipedia.org/wiki/A340-600 Airbus A340-600] for FlightGear. The aircraft has been given a new lease of life with a new JSBsim FDM which replicates better the size and control of such a large bird, and there is much more work on it to come. The model itself is looking very attractive with a newly modelled fuselage from British user Simon (MOJO), and some nice new reflection coding, lights and external models. It has a 3D cockpit which is currently identical to that of the A320-family in FlightGear (by Skyop and Ampere), as an A340 cockpit is being built from scratch by Skyop himself; This doesn't spoil it as they share 99% of similarities in real life. The aircraft was the first in FlightGear to incorporate aircraft operation equipment, and Cabin announcements; back in 2009.. and now these have been improved with new recordings by the author (Liam, if you're wondering who's voice that is), and work is continuing to make the aircraft one of the most enjoyable heavy metal birds to fly in FlightGear simulator. Thanks to all the users who have helped this slow moving project progress. If you are wondering where you can download this new version.. check out the Aircraft section in the FlightGear forums, where there is a special topic dedicated to it.<br />
<br />
[[Image:Airbus1.png|200px]] [[Image:Airbus.png|200px]]<br />
<br />
=== Liveries ===<br />
<br />
== Scenery corner ==<br />
===Seoul===<br />
Seoul is an impressive city where modern buildings with amazing design are mixed with the Korean traditional architecture of old buildings. Here are the buildings added this month: [[File:Yeouido-005.png|200px|thumb|right|Yeouido island]]<br />
* Modern buildings<br />
** Dongbu Finance Building<br />
** GT Tower East<br />
** S-Trenue Tower<br />
** SK T-tower<br />
** Jongno Tower<br />
** Seoul World Cup Stadium<br />
*Old buildings<br />
** Namdaemun<br />
** Gyeonghoeru Pavillon<br />
** Geunjeongjeon<br />
*Others<br />
** National Assembly Building<br />
<br />
Moreover, about 150 generic buildings have been added in Yeouido island.<br />
<br />
=== Airports ===<br />
<br />
== Aircraft of the month ==<br />
== Airport of the month ==<br />
== Screenshot of the month ==<br />
<br />
[[File:Winner.jpg|400px|]]<br><br />
Screenshot which won Contest for the Best Screenshot of 2011 on Polish FlightGear forum.<br><br />
Congratulations for viper29!<br />
<br />
== Suggested flights ==<br />
== Aircraft reviews ==<br />
<br />
== Wiki updates ==<br />
===New articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
</DynamicArticleList><br />
===New aircraft articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
categoryRoot=Aircraft<br />
</DynamicArticleList><br />
===Most popular newsletters===<br />
<DynamicArticleList><br />
type=hot<br />
count=5<br />
categoryRoot=FlightGear Newsletter<br />
</DynamicArticleList><br />
<br />
== Community news ==<br />
=== FlightGear on youtube ===<br />
=== FlightGear on Flickr ===<br />
* http://www.flickr.com/groups/flightgear_simulator/<br />
* http://www.flickr.com/groups/flightgear/<br />
=== New tutorials and screencasts ===<br />
=== Forum news ===<br />
=== Multiplayer ===<br />
=== Virtual airlines ===<br />
=== FlightGear events ===<br />
<br />
== Useful links ==<br />
== And finally ... ==<br />
=== Contributing ===<br />
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
=== Call for volunteers ===<br />
* The [[OpenRadar]] project is looking for a new maintainer.<br />
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.<br />
<br />
=== Did you know ===</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_May_2011&diff=31674FlightGear Newsletter May 20112011-05-14T11:53:15Z<p>Blackiris: /* Seoul */</p>
<hr />
<div>{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
''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.''<br />
<br />
== Development news ==<br />
== Nasal for newbies ==<br />
== New software tools and projects ==<br />
<br />
== FlightGear addons and mods ==<br />
== In the hangar ==<br />
=== New aircraft ===<br />
=== Updated aircraft ===<br />
<br />
====Airbus A340-600====<br />
<br />
More work has continued on developing an [http://en.wikipedia.org/wiki/A340-600 Airbus A340-600] for FlightGear. The aircraft has been given a new lease of life with a new JSBsim FDM which replicates better the size and control of such a large bird, and there is much more work on it to come. The model itself is looking very attractive with a newly modelled fuselage from British user Simon (MOJO), and some nice new reflection coding, lights and external models. It has a 3D cockpit which is currently identical to that of the A320-family in FlightGear (by Skyop and Ampere), as an A340 cockpit is being built from scratch by Skyop himself; This doesn't spoil it as they share 99% of similarities in real life. The aircraft was the first in FlightGear to incorporate aircraft operation equipment, and Cabin announcements; back in 2009.. and now these have been improved with new recordings by the author (Liam, if you're wondering who's voice that is), and work is continuing to make the aircraft one of the most enjoyable heavy metal birds to fly in FlightGear simulator. Thanks to all the users who have helped this slow moving project progress. If you are wondering where you can download this new version.. check out the Aircraft section in the FlightGear forums, where there is a special topic dedicated to it.<br />
<br />
[[Image:Airbus1.png|200px]] [[Image:Airbus.png|200px]]<br />
<br />
=== Liveries ===<br />
<br />
== Scenery corner ==<br />
===Seoul===<br />
Seoul is an impressive city where modern buildings with amazing design are mixed with the Korean traditional architecture of old buildings. Here are the buildings added this month: [[File:Yeouido-005.png|200px|thumb|right|alt Yeouido island]]<br />
* Modern buildings<br />
** Dongbu Finance Building<br />
** GT Tower East<br />
** S-Trenue Tower<br />
** SK T-tower<br />
** Jongno Tower<br />
** Seoul World Cup Stadium<br />
*Old buildings<br />
** Namdaemun<br />
** Gyeonghoeru Pavillon<br />
** Geunjeongjeon<br />
*Others<br />
** National Assembly Building<br />
<br />
Moreover, about 150 generic buildings have been added in Yeouido island.<br />
<br />
=== Airports ===<br />
<br />
== Aircraft of the month ==<br />
== Airport of the month ==<br />
== Screenshot of the month ==<br />
<br />
[[File:Winner.jpg|400px|]]<br><br />
Screenshot which won Contest for the Best Screenshot of 2011 on Polish FlightGear forum.<br><br />
Congratulations for viper29!<br />
<br />
== Suggested flights ==<br />
== Aircraft reviews ==<br />
<br />
== Wiki updates ==<br />
===New articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
</DynamicArticleList><br />
===New aircraft articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
categoryRoot=Aircraft<br />
</DynamicArticleList><br />
===Most popular newsletters===<br />
<DynamicArticleList><br />
type=hot<br />
count=5<br />
categoryRoot=FlightGear Newsletter<br />
</DynamicArticleList><br />
<br />
== Community news ==<br />
=== FlightGear on youtube ===<br />
=== FlightGear on Flickr ===<br />
* http://www.flickr.com/groups/flightgear_simulator/<br />
* http://www.flickr.com/groups/flightgear/<br />
=== New tutorials and screencasts ===<br />
=== Forum news ===<br />
=== Multiplayer ===<br />
=== Virtual airlines ===<br />
=== FlightGear events ===<br />
<br />
== Useful links ==<br />
== And finally ... ==<br />
=== Contributing ===<br />
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
=== Call for volunteers ===<br />
* The [[OpenRadar]] project is looking for a new maintainer.<br />
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.<br />
<br />
=== Did you know ===</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=File:Yeouido-005.png&diff=31673File:Yeouido-005.png2011-05-14T11:51:34Z<p>Blackiris: Yeouido Island - Seoul
The island is detailed with many generic buildings but also custom models, such as the famous 63 building.</p>
<hr />
<div>Yeouido Island - Seoul<br />
The island is detailed with many generic buildings but also custom models, such as the famous 63 building.</div>Blackirishttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_May_2011&diff=31531FlightGear Newsletter May 20112011-05-07T13:54:41Z<p>Blackiris: /* Seoul */</p>
<hr />
<div>{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
''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.''<br />
<br />
== Development news ==<br />
== Nasal for newbies ==<br />
== New software tools and projects ==<br />
<br />
== FlightGear addons and mods ==<br />
== In the hangar ==<br />
=== New aircraft ===<br />
=== Updated aircraft ===<br />
<br />
====Airbus A340-600====<br />
<br />
More work has continued on developing an [http://en.wikipedia.org/wiki/A340-600 Airbus A340-600] for FlightGear. The aircraft has been given a new lease of life with a new JSBsim FDM which replicates better the size and control of such a large bird, and there is much more work on it to come. The model itself is looking very attractive with a newly modelled fuselage from British user Simon (MOJO), and some nice new reflection coding, lights and external models. It has a 3D cockpit which is currently identical to that of the A320-family in FlightGear (by Skyop and Ampere), as an A340 cockpit is being built from scratch by Skyop himself; This doesn't spoil it as they share 99% of similarities in real life. The aircraft was the first in FlightGear to incorporate aircraft operation equipment, and Cabin announcements; back in 2009.. and now these have been improved with new recordings by the author (Liam, if you're wondering who's voice that is), and work is continuing to make the aircraft one of the most enjoyable heavy metal birds to fly in FlightGear simulator. Thanks to all the users who have helped this slow moving project progress. If you are wondering where you can download this new version.. check out the Aircraft section in the FlightGear forums, where there is a special topic dedicated to it.<br />
<br />
[[Image:Airbus1.png|200px]] [[Image:Airbus.png|200px]]<br />
<br />
=== Liveries ===<br />
<br />
== Scenery corner ==<br />
===Seoul===<br />
Seoul is an impressive city where modern buildings with amazing design are mixed with the Korean traditional architecture of old buildings. Here are the buildings added this month:<br />
* Modern buildings<br />
** Dongbu Finance Building<br />
** GT Tower East<br />
** S-Trenue Tower<br />
** SK T-tower<br />
** Jongno Tower<br />
** Seoul World Cup Stadium<br />
*Old buildings<br />
** Namdaemun<br />
** Gyeonghoeru Pavillon<br />
** Geunjeongjeon<br />
*Others<br />
** National Assembly Building<br />
<br />
=== Airports ===<br />
<br />
== Aircraft of the month ==<br />
== Airport of the month ==<br />
== Screenshot of the month ==<br />
<br />
[[File:Winner.jpg|400px|]]<br><br />
Screenshot which won Contest for the Best Screenshot of 2011 on Polish FlightGear forum.<br><br />
Congratulations for viper29!<br />
<br />
== Suggested flights ==<br />
== Aircraft reviews ==<br />
<br />
== Wiki updates ==<br />
===New articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
</DynamicArticleList><br />
===New aircraft articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
categoryRoot=Aircraft<br />
</DynamicArticleList><br />
===Most popular newsletters===<br />
<DynamicArticleList><br />
type=hot<br />
count=5<br />
categoryRoot=FlightGear Newsletter<br />
</DynamicArticleList><br />
<br />
== Community news ==<br />
=== FlightGear on youtube ===<br />
=== New tutorials and screencasts ===<br />
=== Forum news ===<br />
=== Multiplayer ===<br />
=== Virtual airlines ===<br />
=== FlightGear events ===<br />
<br />
== Useful links ==<br />
== And finally ... ==<br />
=== Contributing ===<br />
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
=== Call for volunteers ===<br />
* The [[OpenRadar]] project is looking for a new maintainer.<br />
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.<br />
<br />
=== Did you know ===</div>Blackiris