FlightGear wiki - User contributions [en]

User:Vs/Gallery

2021-12-21T13:04:41Z

Vs:

== At least somewhat high-ish settings screenshot gallery (2018-2021) ==

''If you want to know what modern FlightGear looks like in parts of the world with well developed scenery, on GPUs and other hardware from the last 5-6 years.''

A flight simulator needs galleries for different categories of performance, settings and hardware - when it comes to visuals people want to know how a simulator looks on the hardware they '''actually''' have. FlightGear scales to run on a huge range of hardware - from reasonably fast integrated laptop graphics cards (GPUs), to needing mid range or high end discrete GPUs at high settings. This means, for example, that a person with a faster CPU and a slow GPU can still visualise a simulation using a flight-dynamics engine benchmark tested [link here] by NASA (JSBSim) on a flight-model with wind-tunnel data, and a weather simulation. Being a volunteer project, we don't have people to note performance, note download bandwidth at different flight speeds, and change settings to take multiple screenshots of the same view. On the other hand, FlightGear is freely available for you to see on your hardware! For a discussion on performance targets, settings, and hardware - as well as a high-ish settings hardware/performance profile for 2018.3 LTS - see the [[Hardware recommendations]] wiki page.

Feel free to use these to represent the FlightGear.org project.

''Caveats:''

Screenshots are what ended up in the wiki for one reason or another - a quick collection from glancing through thumbnails of recent wiki uploads, and screenshot of the month entries.

Not all screenshots have all settings turned up significantly (e.g tree density, or Anti-Aliasing). Visuals depend completely on how well people have looked into configuring settings, and learned things like the Advanced Weather and Environment simulations at the time they took the screenshot. Some screenshots have been taken on (old) laptops etc.

A lot of craft have been updated since these screenshots were posted.

Craft shown are just whatever the people taking high settings screenshots that ended up on the wiki were developing or flying regularly at the time, and show more of certain craft. There are over 900 aircraft projects at different stages are available through the launcher (Nov 2021), and many more projects are hosted on development repositories and 3rd party hangars - being a volunteer project, we don't have people to take screenshots of them all in the latest FlightGear every few years.

'''<big>[link to gallery here]</big>'''

== Space Shuttle gallery ==
Gallery for FlightGear's [[Space Shuttle]] - articles: see [https://www.flightgear.org/tours/an-experience-like-no-other/ this](2015) and [https://www.flightgear.org/tours/the-grand-view/ this] (2018).

'''<big>[link to Space Shuttle and orbital view gallery here]</big>'''

== Screenshot of the month gallery ==
From a forum thread competition. This isn't a settings competition, and people post without modern renderers or using old FlightGear versions. Screenshots are often about new or work-in-progress aircraft, multiplayer events, or humour - not necessarily for showcasing or finished work.

'''<big>[link to gallery here]</big>'''

User:Vs/Gallery

2021-12-21T13:03:21Z

Vs:

== At least somewhat high-ish settings screenshot gallery (2018-2021) ==

''If you want to know what modern FlightGear looks like in parts of the world with well developed scenery, on GPUs and other hardware from the last 5-6 years.''

A flight simulator needs galleries for different categories of performance, settings and hardware - when it comes to visuals people want to know how a simulator looks on the hardware they '''actually''' have. FlightGear scales to run on a huge range of hardware - from reasonably fast integrated laptop GPUs, to needing mid or high end discrete GPUs at high settings. This means, for example, that a person with a faster CPU and a slow GPU can still visualise a simulation using a flight-dynamics engine benchmark tested [link here] by NASA (JSBSim) on a flight-model with wind-tunnel data, and a weather simulation. Being a volunteer project, we don't have people to note performance, note download bandwidth at different flight speeds, and change settings to take multiple screenshots of the same view. On the other hand, FlightGear is freely available for you to see on your hardware! For a discussion on performance targets, settings, and hardware - as well as a high-ish settings hardware/performance profile for 2018.3 LTS - see the [[Hardware recommendations]] wiki page.

Feel free to use these to represent the FlightGear.org project.

''Caveats:''

Screenshots are what ended up in the wiki for one reason or another - a quick collection from glancing through thumbnails of recent wiki uploads, and screenshot of the month entries.

Not all screenshots have all settings turned up significantly (e.g tree density, or Anti-Aliasing). Visuals depend completely on how well people have looked into configuring settings, and learned things like the Advanced Weather and Environment simulations at the time they took the screenshot. Some screenshots have been taken on (old) laptops etc.

A lot of craft have been updated since these screenshots were posted.

Craft shown are just whatever the people taking high settings screenshots that ended up on the wiki were developing or flying regularly at the time, and show more of certain craft. There are over 900 aircraft projects at different stages are available through the launcher (Nov 2021), and many more projects are hosted on development repositories and 3rd party hangars - being a volunteer project, we don't have people to take screenshots of them all in the latest FlightGear every few years.

'''<big>[link to gallery here]</big>'''

== Space Shuttle gallery ==
Gallery for FlightGear's [[Space Shuttle]] - articles: see [https://www.flightgear.org/tours/an-experience-like-no-other/ this](2015) and [https://www.flightgear.org/tours/the-grand-view/ this] (2018).

'''<big>[link to Space Shuttle and orbital view gallery here]</big>'''

== Screenshot of the month gallery ==
From a forum thread competition. This isn't a settings competition, and people post without modern renderers or using old FlightGear versions. Screenshots are often about new or work-in-progress aircraft, multiplayer events, or humour - not necessarily for showcasing or finished work.

'''<big>[link to gallery here]</big>'''

FlightGear Newsletter November 2021

2021-12-20T13:15:45Z

Vs: cleanup

{{User:Skybike/Template:Newsletter-header-translate|2021-11}}
{{TOC_right|limit=2}}
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter. 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.''

''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''

== Development news ==

{{Disclaimer|id=final-fixed-function-release}}




===The road ahead===
''See '''[[FlightGear Newsletter November 2021#Help wanted|Help Wanted]]'''.''

There are a lot of big projects that are currently under way - see the [[FlightGear Newsletter January 2021#The%20road%20ahead|January newsletter]] for details for some of these projects. A lot of work (but not all) is already on the next branch (i.e. nightly builds). See the [[FlightGear Newsletter July 2021#New rendering pipeline for Compositor - HDR pipeline|July newsletter]] for info on an experimental rendering pipeline that has just been added to the next branch, as well as a new project to add [[Virtual Reality]] headset support to FlightGear.

There is a lot to check out if you are curious - power users can run [[$FG HOME#Parallel%20installs%20of%20FlightGear|multiple installs]] of FlightGear in parallel. To contribute to any aspect of these projects, get in touch via the "[[Mailing lists|fg-devel]]" mailing list.

Nightly builds with some of the big changes are available at [http://download.flightgear.org/builds/nightly/ download.flightgear.org] as usual.

Nightly builds and the "next" branch are building towards a "development preview" release currently planned for sometime in the 1st half of 2022 - see the [[FlightGear Newsletter April 2021#World Scenery 3.0 update .26 FG 2021.x preview release plans|April newsletter]]. As usual, plans can change and progress depends on the availability of contributors (including testing).

Please report bugs and issues via the sourceforge [https://sourceforge.net/p/flightgear/codetickets/ tickets] system if you come across any on the next branch, or LTS.
=== New features on next ===

* [[Instant Replay]] - New Record/replay functionality. See this [https://www.youtube.com/watch?v=NEm5Oboy3wc youtube video] (polish audio) for a test of an early version.
* [[Highlighting]] - highlight animated parts of the user aircraft and show associated properties.
* [[ExtraViewWindows|Information about Extra View windows]].
* [[SimpleTime]] - an alternative to [[Real_Time_manual|Real time]] mode.
* [[Carrier_over_MP#Pilot_Using_the_Carrier|Simplifications to Multiplayer carrier operation]].
=== World Scenery 3.0 Update===
====Scenery generation for world-build====
The scenery generation part of [[World Scenery 3.0 roadmap|World Scenery 3.0]] (WS30) is at an advanced stage.

StuartB has written a guide on how to build WS30 scenery - see the [[Virtual Planet Builder|Virtual Planet Builder (VPB)]] page. See this [https://drive.google.com/file/d/1tGXSI8RwQxFL0_AFhXaFRVA6go-u7YBW/view?usp=sharing download] for a sample of the latest quality scenery from mid October - covering most of the United Kingdom (you can start at EGPH).

People interested in generating WS3 scenery for the WS30 world build should start learning the process of using [[Virtual Planet Builder]]. There are no Windows binaries at this stage, so VPB needs to be compiled. This includes people who are working on custom landclass and elevation data for their home regions, and areas of interest. The resolution or output format may change for the final world-build, but the process of getting/preparing/cleaning data, and putting it into the tool chain is roughly the same.

Building scenery with VPB is extremely fast compared to the old TerraGear. Scott was able to build the whole of UK in a matter of hours - [https://sourceforge.net/p/flightgear/mailman/message/37259618/ see his post]. A group of volunteers should be able to to do the entire worldbuild.

There is a vast improvement in the general availability of terrain elevation and landcover data in 2021, compared to the very old WS2 build.

=== Virtual reality (VR) support project ===
James Hogan has added visibility mask support, and has started working on basic VR controller support - see the mailing list [https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/CAAG0J9-D2voNCmd6p1hFh%3DWR-NZDQEenerUYOUu_%3D9ie3AJ6_w%40mail.gmail.com/#msg37380733 thread]. See the [[Virtual Reality#Status|Virtual Reality]] status page for the latest information. Using VR requires compiling from source currently, and is not available in Windows/Mac nightly builds yet.

As always with volunteer projects, progress depends on the availability of volunteers including testing, and plans can change in various ways - so there is no timeline. FlightGear development is coordinated via the "fg-devel" mailing-list and people who want to get involved with any aspect of the VR project should get in touch via the mailing lists.

=== Video rendering support ===
Julian Smith is working on the ability to natively render and output videos, without using 3rd party software - see the [[video encoding]] wiki page. He has created the functionality to add a timestamp to each rendered frame so that FlightGear's exact frame rates and spacing are reproduced - this will help with performance profiling and debugging. He has also created a 'fixed dt' mode which changes simulation times so the time between frames is constant, so that videos can be rendered perfectly even on an extremely old machine. See the mailinglist [https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/20211129014900.0db94c4a%40jules-obsd/#msg37392490 thread] for more information.

=== C172SP with FG1000 ===
Wayne has created a video of the [[Compositor]] lighting in the [[Cessna 172P|C172 SP]] retrofit with [[FG1000]] glass cockpit. This needs the next branch of FlightGear. The C172 is the aircraft shipped with the base package of FlightGear - over 900 aircraft are available with a 1 click install in the launcher from the FGAddon hangar, and a lot more are available in other hangars or git repos.

{{#ev:youtube|4zroudg99pk|600px||[[Cessna 172P|C172 SP]] lighting test.}}

== In the hangar ==


=== Boeing 777 update ===
Franck has been doing a overhaul focusing on modelling and animation, with the intention of getting it out by Christmas 2021. He has already released a version on sourceforge - as an early Christmas present for those wanting to test the in-development version. See the [https://forum.flightgear.org/viewtopic.php?f=4&t=38988 forum thread] for more information and downloads.

This is a large overhaul done over a long time, and you can see updates and progress with time in his [https://www.youtube.com/c/ThePalpatine59/videos youtube channel].

{{#ev:youtube|7qVpbbwSf3o|600px|| Boeing 777 update. By Franck VMD}}

{{#ev:youtube|YycCCrrlXCU|600px||Boeing 777 update. By Franck VMD}}
{{#ev:youtube|APTrxocLvz0|600px||Boeing 777 update - view manager. By Franck VMD}}
{{#ev:youtube|Pap6h1AAOmQ|600px||Boeing 777 update - cockpit clickables}}
{{#ev:youtube|Q4WPLEx3_Rs|600px||Boeing 777 update - Ground services, aircraft maintenance access}}

=== Lazarus Mk2 ===
Wayne has created some videos showing improvements to the work-in-progress Lazarus Mk2, a human powered aircraft. This is on the FlightGear "next" branch. The aircraft is being used to train pilots [https://forum.flightgear.org/viewtopic.php?f=4&t=39892#p394230] - this includes tournaments and challenges for human powered aircraft (like the {{Wikipedia|Kremer prize|Kremer prize}}). This is similar to how the FlightGear virtual environment and the JSBSim driven Zivko Edge 540 is used to introduce pilots to the [[Red Bull Air Race]] track, as well as planning and preparing the races.
There is some work being done on interfacing the Lazarus Mk2 with consumer exercise bikes as these types of aircraft are pedal powered - this can be used by people at home wanting a visualisation as they exercise.

See the [https://forum.flightgear.org/viewtopic.php?f=4&t=39892 forum thread] for more information on the project.

You can see videos of the real version on the Human Powered Aircraft Society [https://www.youtube.com/channel/UCFGHyCbL7Mgr2dXvOCj6uAA/videos youtube channel].

{{#ev:youtube|kWfvPEjfwbw|600px||Lazarus Mk2 wingflex in FlightGear. By Wayne Bragg}}
{{#ev:youtube|ll0OtdxAoIE|600px||Lazarus Mk2 multiplayer demo in FlightGear. by Wayne Bragg.}}

=== Millesime 1 ===
Wayne has created a video of the Millesime 1 from Bordeaux University, another human powered aircraft.

{{#ev:youtube|RKPOJISyKVs|600px||Millesime 1 a human powered aircraft from Bordeaux University, initial simulation test in FlightGear. By Wayne Bragg.}}

===G91R1B Compositor lighting===
Adriano has a video of the latest development on the [[FIAT G91R1B]], showing [[Compositor]] lighting at night:

{{#ev:youtube|L_RmE91HKps|600px||G91R1B for Flightgear: Take-Off and Landing in the Dublin airport from to rw 10. By Adriano Bassignana.}}
{{#ev:youtube|KM2OKgeBKcc|600px||G91R1B for FlightGear: Showing a test of automated external illuminators, which can track the aircraft as it moves. These will be part of the ground accessories.}}

=== FGUK website updated ===
FGUK have finished updating their website, including the hangar which hosts a lot of aircraft. The website was offline while the new one was being worked on.

The new website is available https://www.fguk.me/ .

The hangar is available at: https://www.fguk.me/hangar-main/

===Boeing 727-200 Available again===
The [[727-200|Boeing 727-200]] is once again available to use.

===C-17 Rediscovered===
The C-17 that has been lost in the Bermuda Triangle hangar has been found and rediscovered!!!!! - [[C-17 Globemaster III]] for the latest version ([https://www.fguk.me/hangar/boeing-c-17-globemaster-iii/ direct link] to hangar)

===C-5 Available===
The [[C-5 Galaxy]] is now available. According to the repository comments and commit descriptions as well as the README, the aircraft should be able to fly.


=== Aircrafts updated ===
==== Awaiting approval for main hangar availability ====
* 757-200 PF and SF are now completed, and are awaiting approval to be uploaded to the main FlightGear hangar. (Updated 757-200)




=== Aircrafts in Development ===
* There are two different development groups making their own version of the 757 Freighter. One group is making the 757-F while the other is making both (757-Production Frieghter and 757-Passenger Converted Freighter). The later group's aircrafts are different in performance.
* Doorknob747 is making the Boeing 727-200 Advanced Frieghter.
* Doorknob747 is creating the 737-800 Freighters. There are two versions, Bleing's Passenger Converted To Freighter and a Special Frieghter variant. https://en.wikipedia.org/wiki/Boeing_737_Next_Generation#737-800

== Scenery corner ==

=== Detailed Gregorio Luperon International Airport ===
flc972 has released a detailed version of [[Gregorio Luperon International Airport]] / Puerto Plata Airport (MDPP) as a [[Suggested custom scenery|custom scenery]] . This airport features detailed modeling of interiors, night lightmaps, ground net and animated jetways. It is located in the Dominican republic on the island of Hispaniola in the Caribbean.

See the forum thread for [https://forum.flightgear.org/viewtopic.php?f=5&t=39179 more information and download].<gallery mode="packed" caption="Gregorio Luperon International Airport (MDPP) in FlightGear (Compositor shadows on next branch)">
File:Gregorio Luperon International Airport (MDPP) in FlightGear 02.jpg
File:Gregorio Luperon International Airport (MDPP) in FlightGear 01.jpg
File:Gregorio Luperon International Airport (MDPP) in FlightGear 04.jpg
File:Gregorio Luperon International Airport (MDPP) in FlightGear 05.jpg
</gallery>

=== Frankfurt Airports update ===
D-Sven has released an update [[Frankfurt am Main Airport|Frankfurt am Main]] (EDDF) and other airports around Frankfurt including [[Frankfurt-Hahn Airport]] (EDFH) and [[Kassel Airport]] (EDVK) - see [https://forum.flightgear.org/viewtopic.php?f=5&t=38286 forum thread] for more information and [https://github.com/D-Sven/Frankfurt github download] ([https://github.com/D-Sven/Frankfurt/archive/refs/heads/main.zip direct link]). EDDF includes modelling of buildings surrounding the main terminal, which are lacking in TerraSync. It's part of his ongoing project.
[[File:FrankfurtHHN.png|none|thumb|480x480px|[[Frankfurt-Hahn Airport]] (EDFH) update by D-Sven.]]















== Help wanted ==
{{Help wanted}}

=== Growth in new landmark wish list ===
There has been a lot of growth since the last wish list object had been added to FlightGear. The list is available here. [[Landmark Wish List]]

== AI ==


The AI team makes FlightGear more realistic, colorful and lively every month. You can support the development of ''Interactive Traffic'' and contribute at the FlightGear {{forum link|title=AI|f=23}}.



== Community news ==








=== FlightGear on Facebook ===
Since early December 2010, FlightGear has an [https://www.facebook.com/FlightGear official Facebook page]. If you have a Facebook account please feel free to join the page.

=== FlightGear on Instagram ===
In January 2018 the [https://www.instagram.com/flightgear_sim/ @flightgear_sim Instagram account] was brought back to life. If you've got nice screenshots to be featured, feel free to {{forum link|text=contact the maintainer|t=33636}}.

=== FlightGear on FlightSim.com ===
FlightGear has also a [https://www.flightsim.com/vbfs/forumdisplay.php?102-FlightGear sub-forum] on flightsim.com - just like the commercial flight sims. It is an opportunity to showcase what FG can do, get people curious and answer any questions they may have with regard to the software or the project.

== Multiplayer events ==

The Wednesday-GA flying is still alive! Everyone welcome! Info in the multiplayer section in the forums :)










== Contributing ==
=== Translators needed ===
{|
| [[File:en.gif]]
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].
|-
| [[File:fr.gif]]
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].
|-
| [[File:de.gif]]
| 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 mit dem [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
| [[File:nl.gif]]
| 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]].
|-
| [[File:es.gif]]
| La wiki de FlightGear 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]].
|-
| [[File:cat.gif]]
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].
|-
| [[File:pt.gif]]
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].
|-
| [[File:zh.gif]]
| FlightGear 百科仍然需要志愿者将其翻译为各种语言。如果你有兴趣让FlightGear百科支持更多语言, 你可以查看 [[Help:Translate]].
|}

=== FlightGear logos ===
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.

=== Screenshots ===
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].

==== Screenshot of the Month ====

If you want to participate in the screenshot contest, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.

''Thanks for reading {{PAGENAME}}!''

{{Appendix}}


[[Category:Changes after 2020.3]]
[[Category:FlightGear Newsletter|2021 11]]

FlightGear Newsletter November 2021

2021-12-20T13:14:00Z

Vs: cleanup

{{User:Skybike/Template:Newsletter-header-translate|2021-11}}
{{TOC_right|limit=2}}
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter. 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.''

''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''

== Development news ==

{{Disclaimer|id=final-fixed-function-release}}




===The road ahead===
''See '''[[FlightGear Newsletter November 2021#Help wanted|Help Wanted]]'''.''

There are a lot of big projects that are currently under way - see the [[FlightGear Newsletter January 2021#The%20road%20ahead|January newsletter]] for details for some of these projects. A lot of work (but not all) is already on the next branch (i.e. nightly builds). See the [[FlightGear Newsletter July 2021#New rendering pipeline for Compositor - HDR pipeline|July newsletter]] for info on an experimental rendering pipeline that has just been added to the next branch, as well as a new project to add [[Virtual Reality]] headset support to FlightGear.

There is a lot to check out if you are curious - power users can run [[$FG HOME#Parallel%20installs%20of%20FlightGear|multiple installs]] of FlightGear in parallel. To contribute to any aspect of these projects, get in touch via the "[[Mailing lists|fg-devel]]" mailing list.

Nightly builds with some of the big changes are available at [http://download.flightgear.org/builds/nightly/ download.flightgear.org] as usual.

Nightly builds and the "next" branch are building towards a "development preview" release currently planned for sometime in the 1st half of 2022 - see the [[FlightGear Newsletter April 2021#World Scenery 3.0 update .26 FG 2021.x preview release plans|April newsletter]]. As usual, plans can change and progress depends on the availability of contributors (including testing).

Please report bugs and issues via the sourceforge [https://sourceforge.net/p/flightgear/codetickets/ tickets] system if you come across any on the next branch, or LTS.
=== New features on next ===

* [[Instant Replay]] - New Record/replay functionality. See this [https://www.youtube.com/watch?v=NEm5Oboy3wc youtube video] (polish audio) for a test of an early version.
* [[Highlighting]] - highlight animated parts of the user aircraft and show associated properties.
* [[ExtraViewWindows|Information about Extra View windows]].
* [[SimpleTime]] - an alternative to [[Real_Time_manual|Real time]] mode.
* [[Carrier_over_MP#Pilot_Using_the_Carrier|Simplifications to Multiplayer carrier operation]].
=== World Scenery 3.0 Update===
====Scenery generation for world-build====
The scenery generation part of [[World Scenery 3.0 roadmap|World Scenery 3.0]] (WS30) is at an advanced stage.

StuartB has written a guide on how to build WS30 scenery - see the [[Virtual Planet Builder|Virtual Planet Builder (VPB)]] page. See this [https://drive.google.com/file/d/1tGXSI8RwQxFL0_AFhXaFRVA6go-u7YBW/view?usp=sharing download] for a sample of the latest quality scenery from mid October - covering most of the United Kingdom (you can start at EGPH).

People interested in generating WS3 scenery for the WS30 world build should start learning the process of using [[Virtual Planet Builder]]. There are no Windows binaries at this stage, so VPB needs to be compiled. This includes people who are working on custom landclass and elevation data for their home regions, and areas of interest. The resolution or output format may change for the final world-build, but the process of getting/preparing/cleaning data, and putting it into the tool chain is roughly the same.

Building scenery with VPB is extremely fast compared to the old TerraGear. Scott was able to build the whole of UK in a matter of hours - [https://sourceforge.net/p/flightgear/mailman/message/37259618/ see his post]. A group of volunteers should be able to to do the entire worldbuild.

There is a vast improvement in the general availability of terrain elevation and landcover data in 2021, compared to the very old WS2 build.

=== Virtual reality (VR) support project ===
James Hogan has added visibility mask support, and has started working on basic VR controller support - see the mailing list [https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/CAAG0J9-D2voNCmd6p1hFh%3DWR-NZDQEenerUYOUu_%3D9ie3AJ6_w%40mail.gmail.com/#msg37380733 thread]. See the [[Virtual Reality#Status|Virtual Reality]] status page for the latest information. Using VR requires compiling from source currently, and is not available in Windows/Mac nightly builds yet.

As always with volunteer projects, progress depends on the availability of volunteers including testing, and plans can change in various ways - so there is no timeline. FlightGear development is coordinated via the "fg-devel" mailing-list and people who want to get involved with any aspect of the VR project should get in touch via the mailing lists.

=== Video rendering support ===
Julian Smith is working on the ability to natively render and output videos, without using 3rd party software. He has created the functionality to add a timestamp to each rendered frame so that FlightGear's exact frame rates and spacing are reproduced - this will help with performance profiling and debugging. He has also created a 'fixed dt' mode which changes simulation times so the time between frames is constant, so that videos can be rendered perfectly even on an extremely old machine. See the mailinglist [https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/20211129014900.0db94c4a%40jules-obsd/#msg37392490 thread] for more information.

=== C172SP with FG1000 ===
Wayne has created a video of the [[Compositor]] lighting in the [[Cessna 172P|C172 SP]] retrofit with [[FG1000]] glass cockpit. This needs the next branch of FlightGear. The C172 is the aircraft shipped with the base package of FlightGear - over 900 aircraft are available with a 1 click install in the launcher from the FGAddon hangar, and a lot more are available in other hangars or git repos.

{{#ev:youtube|4zroudg99pk|600px||[[Cessna 172P|C172 SP]] lighting test.}}

== In the hangar ==


=== Boeing 777 update ===
Franck has been doing a overhaul focusing on modelling and animation, with the intention of getting it out by Christmas 2021. He has already released a version on sourceforge - as an early Christmas present for those wanting to test the in-development version. See the [https://forum.flightgear.org/viewtopic.php?f=4&t=38988 forum thread] for more information and downloads.

This is a large overhaul done over a long time, and you can see updates and progress with time in his [https://www.youtube.com/c/ThePalpatine59/videos youtube channel].

{{#ev:youtube|7qVpbbwSf3o|600px|| Boeing 777 update. By Franck VMD}}

{{#ev:youtube|YycCCrrlXCU|600px||Boeing 777 update. By Franck VMD}}
{{#ev:youtube|APTrxocLvz0|600px||Boeing 777 update - view manager. By Franck VMD}}
{{#ev:youtube|Pap6h1AAOmQ|600px||Boeing 777 update - cockpit clickables}}
{{#ev:youtube|Q4WPLEx3_Rs|600px||Boeing 777 update - Ground services, aircraft maintenance access}}

=== Lazarus Mk2 ===
Wayne has created some videos showing improvements to the work-in-progress Lazarus Mk2, a human powered aircraft. This is on the FlightGear "next" branch. The aircraft is being used to train pilots [https://forum.flightgear.org/viewtopic.php?f=4&t=39892#p394230] - this includes tournaments and challenges for human powered aircraft (like the {{Wikipedia|Kremer prize|Kremer prize}}). This is similar to how the FlightGear virtual environment and the JSBSim driven Zivko Edge 540 is used to introduce pilots to the [[Red Bull Air Race]] track, as well as planning and preparing the races.
There is some work being done on interfacing the Lazarus Mk2 with consumer exercise bikes as these types of aircraft are pedal powered - this can be used by people at home wanting a visualisation as they exercise.

See the [https://forum.flightgear.org/viewtopic.php?f=4&t=39892 forum thread] for more information on the project.

You can see videos of the real version on the Human Powered Aircraft Society [https://www.youtube.com/channel/UCFGHyCbL7Mgr2dXvOCj6uAA/videos youtube channel].

{{#ev:youtube|kWfvPEjfwbw|600px||Lazarus Mk2 wingflex in FlightGear. By Wayne Bragg}}
{{#ev:youtube|ll0OtdxAoIE|600px||Lazarus Mk2 multiplayer demo in FlightGear. by Wayne Bragg.}}

=== Millesime 1 ===
Wayne has created a video of the Millesime 1 from Bordeaux University, another human powered aircraft.

{{#ev:youtube|RKPOJISyKVs|600px||Millesime 1 a human powered aircraft from Bordeaux University, initial simulation test in FlightGear. By Wayne Bragg.}}

===G91R1B Compositor lighting===
Adriano has a video of the latest development on the [[FIAT G91R1B]], showing [[Compositor]] lighting at night:

{{#ev:youtube|L_RmE91HKps|600px||G91R1B for Flightgear: Take-Off and Landing in the Dublin airport from to rw 10. By Adriano Bassignana.}}
{{#ev:youtube|KM2OKgeBKcc|600px||G91R1B for FlightGear: Showing a test of automated external illuminators, which can track the aircraft as it moves. These will be part of the ground accessories.}}

=== FGUK website updated ===
FGUK have finished updating their website, including the hangar which hosts a lot of aircraft. The website was offline while the new one was being worked on.

The new website is available https://www.fguk.me/ .

The hangar is available at: https://www.fguk.me/hangar-main/

===Boeing 727-200 Available again===
The [[727-200|Boeing 727-200]] is once again available to use.

===C-17 Rediscovered===
The C-17 that has been lost in the Bermuda Triangle hangar has been found and rediscovered!!!!! - [[C-17 Globemaster III]] for the latest version ([https://www.fguk.me/hangar/boeing-c-17-globemaster-iii/ direct link] to hangar)

===C-5 Available===
The [[C-5 Galaxy]] is now available. According to the repository comments and commit descriptions as well as the README, the aircraft should be able to fly.


=== Aircrafts updated ===
==== Awaiting approval for main hangar availability ====
* 757-200 PF and SF are now completed, and are awaiting approval to be uploaded to the main FlightGear hangar. (Updated 757-200)




=== Aircrafts in Development ===
* There are two different development groups making their own version of the 757 Freighter. One group is making the 757-F while the other is making both (757-Production Frieghter and 757-Passenger Converted Freighter). The later group's aircrafts are different in performance.
* Doorknob747 is making the Boeing 727-200 Advanced Frieghter.
* Doorknob747 is creating the 737-800 Freighters. There are two versions, Bleing's Passenger Converted To Freighter and a Special Frieghter variant. https://en.wikipedia.org/wiki/Boeing_737_Next_Generation#737-800

== Scenery corner ==

=== Detailed Gregorio Luperon International Airport ===
flc972 has released a detailed version of [[Gregorio Luperon International Airport]] / Puerto Plata Airport (MDPP) as a [[Suggested custom scenery|custom scenery]] . This airport features detailed modeling of interiors, night lightmaps, ground net and animated jetways. It is located in the Dominican republic on the island of Hispaniola in the Caribbean.

See the forum thread for [https://forum.flightgear.org/viewtopic.php?f=5&t=39179 more information and download].<gallery mode="packed" caption="Gregorio Luperon International Airport (MDPP) in FlightGear (Compositor shadows on next branch)">
File:Gregorio Luperon International Airport (MDPP) in FlightGear 02.jpg
File:Gregorio Luperon International Airport (MDPP) in FlightGear 01.jpg
File:Gregorio Luperon International Airport (MDPP) in FlightGear 04.jpg
File:Gregorio Luperon International Airport (MDPP) in FlightGear 05.jpg
</gallery>

=== Frankfurt Airports update ===
D-Sven has released an update [[Frankfurt am Main Airport|Frankfurt am Main]] (EDDF) and other airports around Frankfurt including [[Frankfurt-Hahn Airport]] (EDFH) and [[Kassel Airport]] (EDVK) - see [https://forum.flightgear.org/viewtopic.php?f=5&t=38286 forum thread] for more information and [https://github.com/D-Sven/Frankfurt github download] ([https://github.com/D-Sven/Frankfurt/archive/refs/heads/main.zip direct link]). EDDF includes modelling of buildings surrounding the main terminal, which are lacking in TerraSync. It's part of his ongoing project.
[[File:FrankfurtHHN.png|none|thumb|480x480px|[[Frankfurt-Hahn Airport]] (EDFH) update by D-Sven.]]















== Help wanted ==
{{Help wanted}}

=== Growth in new landmark wish list ===
There has been a lot of growth since the last wish list object had been added to FlightGear. The list is available here. [[Landmark Wish List]]

== AI ==


The AI team makes FlightGear more realistic, colorful and lively every month. You can support the development of ''Interactive Traffic'' and contribute at the FlightGear {{forum link|title=AI|f=23}}.



== Community news ==








=== FlightGear on Facebook ===
Since early December 2010, FlightGear has an [https://www.facebook.com/FlightGear official Facebook page]. If you have a Facebook account please feel free to join the page.

=== FlightGear on Instagram ===
In January 2018 the [https://www.instagram.com/flightgear_sim/ @flightgear_sim Instagram account] was brought back to life. If you've got nice screenshots to be featured, feel free to {{forum link|text=contact the maintainer|t=33636}}.

=== FlightGear on FlightSim.com ===
FlightGear has also a [https://www.flightsim.com/vbfs/forumdisplay.php?102-FlightGear sub-forum] on flightsim.com - just like the commercial flight sims. It is an opportunity to showcase what FG can do, get people curious and answer any questions they may have with regard to the software or the project.

== Multiplayer events ==

The Wednesday-GA flying is still alive! Everyone welcome! Info in the multiplayer section in the forums :)










== Contributing ==
=== Translators needed ===
{|
| [[File:en.gif]]
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].
|-
| [[File:fr.gif]]
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].
|-
| [[File:de.gif]]
| 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 mit dem [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
| [[File:nl.gif]]
| 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]].
|-
| [[File:es.gif]]
| La wiki de FlightGear 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]].
|-
| [[File:cat.gif]]
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].
|-
| [[File:pt.gif]]
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].
|-
| [[File:zh.gif]]
| FlightGear 百科仍然需要志愿者将其翻译为各种语言。如果你有兴趣让FlightGear百科支持更多语言, 你可以查看 [[Help:Translate]].
|}

=== FlightGear logos ===
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.

=== Screenshots ===
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].

==== Screenshot of the Month ====

If you want to participate in the screenshot contest, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.

''Thanks for reading {{PAGENAME}}!''

{{Appendix}}


[[Category:Changes after 2020.3]]
[[Category:FlightGear Newsletter|2021 11]]

User:Vs/Gallery

2021-12-20T12:31:59Z

Vs:

== At least somewhat high-ish settings screenshot gallery (2018-2021) ==

''If you want to know what modern FlightGear looks like in parts of the world with well developed scenery, on GPUs and other hardware from the last 5-6 years.''

A flight simulator needs galleries for different categories of performance, settings and hardware - when it comes to visuals people want to know how a simulator looks on the hardware they '''actually''' have. FlightGear scales to run on a huge range of hardware - from reasonably fast integrated laptop GPUs, to needing mid or high end discrete GPUs at high settings. This means, for example, that a person with a faster CPU and a slow GPU can still visualise a simulation using a flight-dynamics engine benchmark tested [link here] by NASA (JSBSim) on a flight-model with wind-tunnel data, and a weather simulation. Being a volunteer project, we don't have people to note performance, note download bandwidth at different flight speeds, and change settings to take multiple screenshots of the same view. On the other hand, FlightGear is freely available for you to see on your hardware! For a discussion on performance targets, settings, and hardware - as well as a high-ish settings hardware/performance profile for 2018.3 LTS - see the [[Hardware recommendations]] wiki page.

Feel free to use these to represent the FlightGear.org project.

''Caveats:''

Screenshots are what ended up in the wiki for one reason or another - a quick collection from glancing through thumbnails of recent wiki uploads, and screenshot of the month entries.

Not all screenshots have all settings turned up significantly (e.g tree density, or Anti-Aliasing). Visuals depend completely on how well people have looked into configuring settings, and learned things like the Advanced Weather and Environment simulations at the time they took the screenshot. Some screenshots have been taken on (old) laptops etc.

A lot of craft have been updated since these screenshots were posted.

Craft shown are just whatever the people taking high settings screenshots that ended up on the wiki were developing or flying regularly at the time, and show more of certain types of craft.

'''<big>[link to gallery here]</big>'''

== Space Shuttle gallery ==
Gallery for FlightGear's [[Space Shuttle]] - articles: see [https://www.flightgear.org/tours/an-experience-like-no-other/ this](2015) and [https://www.flightgear.org/tours/the-grand-view/ this] (2018).

'''<big>[link to Space Shuttle and orbital view gallery here]</big>'''

== Screenshot of the month gallery ==
From a forum thread competition. This isn't a settings competition, and people post without modern renderers or using old FlightGear versions. Screenshots are often about new or work-in-progress aircraft, multiplayer events, or humour - not necessarily for showcasing or finished work.

'''<big>[link to gallery here]</big>'''

User:Vs/Gallery

2021-12-20T08:34:14Z

Vs:

== At least somewhat high-ish settings screenshot gallery (2018-2021) ==

''If you want to know what modern FlightGear looks like in parts of the world with well developed scenery, on GPUs and other hardware from the last 5-6 years.''

A flight simulator needs galleries for different categories of performance, settings and hardware - when it comes to visuals people want to know how a simulator looks on the hardware they '''actually''' have. FlightGear scales to run on a huge range of hardware - from reasonably fast integrated laptop GPUs, to needing mid or high end discrete GPUs at high settings. This means, for example, that a person with a faster CPU and a slow GPU can still visualise a simulation using a flight-dynamics engine benchmark tested [link here] by NASA (JSBSim) on a flight-model with wind-tunnel data, and a weather simulation. Being a volunteer project, we don't have people to note performance, note download bandwidth at different flight speeds, and change settings to take multiple screenshots of the same view. On the other hand, FlightGear is freely available for you to see on your hardware! For a discussion on performance targets, settings, and hardware - as well as a high-ish settings hardware/performance profile for 2018.3 LTS - see the [[Hardware recommendations]] wiki page.

Feel free to use these to represent the FlightGear.org project.

''Caveats:''

Screenshots are what ended up in the wiki for one reason or another - a quick collection from glancing through thumbnails of recent wiki uploads, and screenshot of the month entries.

Not all screenshots have all settings turned up significantly (e.g tree density, or Anti-Aliasing). Visuals depend completely on how well people have looked into configuring settings, and learned things like the Advanced Weather and Environment simulations at the time they took the screenshot. Some screenshots have been taken on (old) laptops etc.

A lot of craft have been updated since these screenshots were posted.

Craft shown are just whatever the people taking high settings screenshots that ended up on the wiki were developing or flying regularly at the time, and show more of certain types of craft.

'''<big>[link to gallery here]</big>'''

== Screenshot of the month gallery ==
From a forum thread competition. This isn't a settings competition, and people post without modern renderers or using old FlightGear versions. Screenshots are often about new or work-in-progress aircraft, multiplayer events, or humour - not necessarily for showcasing or finished work.

'''<big>[link to gallery here]</big>'''

User:Vs/Gallery

2021-12-20T08:20:17Z

Vs:

== At least somewhat high-ish settings screenshot gallery (2018-2021) ==

''If you want to know what modern FlightGear looks like in parts of the world with well developed scenery, on GPUs and other hardware from the last 5-6 years.''

A flight simulator needs galleries for different categories of performance, settings and hardware - when it comes to visuals people want to know how a simulator looks on the hardware they '''actually''' have. FlightGear scales to run on a huge range of hardware - from reasonably fast integrated laptop GPUs, to needing mid or high end discrete GPUs at high settings. This means that a person with a faster CPU and a slow GPU can still visualise a simulation with a flight-dynamics engine benchmark tested [link here] by NASA (JSBSim) on a flight-model with wind-tunnel data, and a weather simulation. Being a volunteer project, we don't have people to note performance, note download bandwidth at different flight speeds, and change settings to take multiple screenshots of the same view. On the other hand, FlightGear is freely available for you to see on your hardware! For a discussion on performance targets, settings, and hardware - as well as a high-ish settings hardware/performance profile for 2018.3 LTS - see the [[Hardware recommendations]] wiki page.

Feel free to use these to represent the FlightGear.org project.

''Caveats:''

Screenshots are what ended up in the wiki for one reason or another - a quick collection from glancing through thumbnails of recent wiki uploads, and screenshot of the month entries.

Not all screenshots have all settings turned up significantly (e.g tree density, or Anti-Aliasing). Visuals depend completely on how well people have looked into configuring settings, and learned things like the Advanced Weather and Environment simulations at the time they took the screenshot. Some screenshots have been taken on (old) laptops etc.

A lot of craft have been updated since these screenshots were posted.

Craft shown are just whatever the people taking high settings screenshots that ended up on the wiki were developing or flying regularly at the time, and show more of certain types of craft.

'''<big>[link to gallery here]</big>'''

== Screenshot of the month gallery ==
From a forum thread competition. This isn't a settings competition, and people post without modern renderers or using old FlightGear versions. Screenshots are often about new or work-in-progress aircraft, multiplayer events, or humour - not necessarily for showcasing or finished work.

'''<big>[link to gallery here]</big>'''

User:Vs/Gallery

2021-12-20T08:14:45Z

Vs: cleanup

== At least somewhat high-ish settings screenshot gallery (2018-2021) ==

''If you want to know what modern FlightGear looks like in parts of the world with well developed scenery, on GPUs and other hardware from the last 5-6 years.''

A flight simulator needs galleries for different categories of performance, settings and hardware - when it comes to visuals people want to know how a simulator looks on the hardware they '''actually''' have. FlightGear scales to run on a huge range of hardware - from reasonably fast integrated laptop GPUs, to needing mid or high end discrete GPUs at high settings. This means that a person with a faster CPU and a slow GPU can still visualise a simulation with a flight-dynamics engine benchmark tested [link here] by NASA (JSBSim) on a flight-model with wind-tunnel data, and a weather simulation. Being a volunteer project, we don't have people to note performance, note download bandwidth at different flight speeds, and change settings to take multiple screenshots of the same view. On the other hand, FlightGear is freely available for you to see on your hardware! For a discussion on performance targets, settings, and hardware - as well as a high-ish settings hardware/performance profile for 2018.3 LTS - see the [[Hardware recommendations]] wiki page.

''Caveats:''

Screenshots are what ended up in the wiki for one reason or another - a quick collection from glancing through thumbnails of recent wiki uploads, and screenshot of the month entries.

Not all screenshots have all settings turned up significantly (e.g tree density, or Anti-Aliasing). Visuals depend completely on how well people have looked into configuring settings, and learned things like the Advanced Weather and Environment simulations at the time they took the screenshot. Some screenshots have been taken on (old) laptops etc.

A lot of craft have been updated since these screenshots were posted.

Craft shown are just whatever the people taking high settings screenshots that ended up on the wiki were developing or flying regularly at the time, and show more of certain types of craft.

'''<big>[link to gallery here]</big>'''

== Screenshot of the month gallery ==
From a forum thread competition. This isn't a settings competition, and people post without modern renderers or using old FlightGear versions. Screenshots are often about new or work-in-progress aircraft, multiplayer events, or humour - not necessarily for showcasing or finished work.

'''<big>[link to gallery here]</big>'''

User:Vs/Gallery

2021-12-20T08:10:48Z

Vs: draft of text for gallery

== At least somewhat high-ish settings screenshot gallery (2018-2021) ==

''If you want to know what modern FlightGear looks like in parts of the world with well developed scenery, on GPUs and other hardware from the last 5-6 years.''

A flight simulator needs galleries for different categories of performance, settings and hardware - when it comes to visuals people want to know how a simulator looks on the hardware they '''actually''' have. FlightGear scales to run on a huge range of hardware - from reasonably fast integrated laptop GPUs, to needing mid or high end discrete GPUs at high settings. This means that a person with a faster CPU and slow GPU can still visualise a simulation with a flight-dynamics engine benchmark tested by NASA (JSBSim) on a flight-model with wind-tunnel data, and a weather simulation. Being a volunteer project, we don't have people to note performance, note download bandwidth at different flight speeds, and change settings to take multiple screenshots of the same view. On the other hand, FlightGear is freely available for you to see on your hardware! For a discussion on performance targets, settings, and hardware - as well as a high-ish settings hardware/performance profile for 2018.3 LTS - see the [[Hardware recommendations]] wiki page.

''Caveats:''

Screenshots are what ended up in the wiki for one reason or another - a quick collection from glancing through thumbnails of recent wiki uploads, and screenshot of the month entries.

Not all screenshots have all settings turned up significantly (e.g tree density, or Anti-Aliasing). Visuals depend completely on how well people have looked into configuring settings, and learned things like the Advanced Weather and Environment simulations at the time they took the screenshot. Some screenshots have been taken on (old) laptops etc.

A lot of craft have been updated since these screenshots were posted.

Craft shown are just whatever the people taking high settings screenshots that ended up on the wiki were developing or flying regularly at the time, and show more of certain types of craft.

'''<big>[link to gallery here]</big>'''

== Screenshot of the month gallery ==
From a forum thread competition. This isn't a settings competition, and people post without modern renderers or using old FlightGear versions. Screenshots are often about new or work-in-progress aircraft, multiplayer events, or humour - not necessarily for showcasing or finished work.

'''<big>[link to gallery here]</big>'''

File:Iceland in FlightGear 2020 01 Volcanic plume and snow (Aerospatiale Alouette III).jpg

2021-12-19T13:51:47Z

Vs:

=={{int:filedesc}}==
{{Information
|description={{en|1=Iceland in FlightGear 2020.x. Volcanic plume and snow (Aerospatiale Alouette III)}}
|date=2019-04-10
|source=Screenshots taken by Thorsten Renk. Permission given to use under CC-BY-SA-4.0.

|author=Thorsten Renk
|permission=
|other versions=
}}

=={{int:license-header}}==
{{subst:Custom license marker added by UW}}
Permission given to use under CC-BY-SA-4.0.
{{Cc-by-sa-4.0}}

[[Category:Screenshots at high settings]]
[[Category:Screenshots at high settings/non-sotm]]
[[Category:Screenshots at high settings/sotm]]
[[Category:Screenshots of scenery in Iceland]]
[[Category:Aérospatiale Alouette III screenshots]]
[[Category:Screenshots of snow]]

Howto:Make nice screenshots

2021-12-19T13:28:23Z

Vs: cleanup

{{mergefrom|Submitting Screenshots|Howto talk:Make nice screenshots#Merging Submitting Screenshots into this page|date=January 2014}}

This [[:Category:Howto|howto]] will explain '''how to make nice screenshots''' in [[FlightGear]].

== Basics ==
What separates good pictures from bad pictures?

Good pictures
* Appeal to us in some way, by telling a story, revealing something unexpected, or showing an interesting point of view.
* Encourage us to look at them for more than just a second, searching for more details. A good screen-shot can invite us to think about how it was made, maybe even inspire us to create images of our own.

The best screenshots are technically correct, the lighting and colors are right, and the composition is good.

Explaining how to compose a picture is difficult, so instead I suggest you to read tutorials and explanations given on many websites on the web like this one: {{wikipedia|Composition (visual arts)}}.

== Quality ==
From a broader perspective, it would be desirable if new screenshots could also showcase new FlightGear's capabilities using high quality settings. Say someone googles "VFR guide" because he wants to know something about VFR flying and comes across a bunch of screenshots of FlightGear - we'd really want to impress here so that user gets curious and tries FlightGear. Back when there were still manuals, almost all simulators (Falcon 4.0 for instance) had the highest detail level for all the internal screenshots, not the lowest. So that's something to keep in mind when showcasing FlightGear.

A good virtual picture needs a good quality. That means:
* [[Anti-aliasing|Enabling AntiAliasing]] (AA). Enabling some level of [[Anti-aliasing#Transparency_anti-aliasing|Transparency anti-aliasing]] if using [[Category:Screenshots of overlays]] terrain overlays at low altitude.
* Appealing/true colors
* Size of the picture- not too small, not too big
* No Gui/Menu/FPS counter etc. visible
* Full effects

This means you need a decent computer with middle - good specs. At a minimum, you should able to run Flightgear with smooth frame rate with high anti-aliasing settings.
Some people don't have this, so there is another solution proposed by Melchior Franz : [http://www.opensubscriber.com/message/flightgear-devel@lists.sourceforge.net/8196594.html]. Running at a lower resolution will often improve frame-rate when AA or high shader settings cause a frame-rate bottleneck. Windowed mode will let you experiment with different resolutions.

If the intention is to make a screenshot to showcase Flightgear, it's always possible to pause the sim and turn graphics settings up, and then turn settings down to resume flying.

== How to get some unusual/ interesting views ==
To get some ideas, it's a good idea to look for aircraft picture pages around the web like [http://www.airliners.net Airliners.net]. It will give you some ideas, and in addition, it is always a good idea to think about what you actually want to show case. While a snapshot of an airliner in mid flight is -for instance- a nice way of showing its latest features on the forum, it typically doesn't really last as an overall impressive screen shot. Placing the aircraft in a scene where some implied action is taking place will most of the time already make a huge difference. Capture the plane while it's banking, gear is retracting, etc. will imply some dynamic motion in your otherwise static image. In this respect, it may help to think of a little story, a scenario that you're re-enacting. Trying to capture a few key scenes from a flight may also help to make the difference between an average and an interesting screen shot.

=== Air to Air ===
* '''Helicopter View:''' This assumes that you are in a virtual, invisible helicopter besides the aircraft. You are always flying level. With the mouse you can choose the position of the "helicopter".
* '''Chase View:''' This assumes you are chasing the aircraft. It is very similar to the first one.
* '''Chase View with yaw:''' Also chasing the aircraft, but the virtual camera doesn't turn with the aircraft.
* '''I'm a missile view (on certain aircraft only):''' This view places itself near an AI air-to-air missile that has been fired, looking forwards. With the mouse you can choose the view direction. Only on the Mirage-2000-5 and Harrier development versions.
Try switching between them to see what you like more(I prefer Chase view). Playing around with position of the camera will help too. As an example if the aircraft is turning and banking, make a shot from the wing to the aircraft facing the ground. Or while approaching the runway, a shot from behind the aircraft would be good. For I'm a missile view, moving the camera forward and looking back at the missile and the aircraft can make compelling shots.

=== Ground to Air ===
[[File:Lugano-tower-on-mountain.jpg|thumb|270px|Setting the Tower on top of a mountain looking down to the airport with the [http://www.gidenstam.org/FlightGear/misc/place_tower.xml Place_Tower.xml]]]

For this we use the Tower view and Tower View look from. This assumes that the virtual camera is on the Airport Tower, ca. 30ft above the airport level. You can choose via the Menu which airport is used. That's nice, but limited.

Anders Gidenstam made a nice nasal script to move the tower whenever you control-click on the ground.
You can find it [http://www.gidenstam.org/FlightGear/misc/place_tower.xml here]. Copy the code between the <code><PropertyList></code>-tags and put in somewhere in your <code>preferences.xml</code> . Now, when you ''{{Key press|Ctrl}} + left click'' somewhere on the ground, you can set the position of the tower view. The view is still about 30 feet above ground level; assuming you want to stand at eye-level, you can change the line
<syntaxhighlight lang="nasal">
setprop(tower ~ "/altitude-ft", 30 + (click_pos.alt() * M2FT));
</syntaxhighlight>
to
<syntaxhighlight lang="nasal">
setprop(tower ~ "/altitude-ft", 6.5 + (click_pos.alt() * M2FT));
</syntaxhighlight>

=== Panorama ===
[[File:C172p-bodensee-panorama.jpg|thumb|600px|Panorama image stitched with 23 images inside the C172P cockpit while flying above Lake Constance (Bodensee)]]

A {{wikipedia|Panorama}} is a wide-angle view. With this, you can show large areas of the scenery or flightdecks.

For this, use the cockpit, passenger, or tower view, then position the virtual camera at the point you want. Pause the sim and pan the virtual camera all the way around, saving many screenshots so they cover the entire visible area.
Now use your favourite panorama software and stitch it!
No software yet? Use Google; there are several freeware programs outside. A common choice is [http://hugin.sourceforge.net/ Hugin]; it's free and open source, cross-platform and used by many professional photographers.
 
==== Panoramas with Hugin ====
There is a (WiP) nasal script in [https://forum.flightgear.org/viewtopic.php?t=36297 this forum thread] that takes a user configurable grid of overlapping screenshots. The script is based on the spherical panorama script. To take a line of screenshots means setting grid size to 1 by n.

A lot of lower FoV and closely overlapping screenshots can eliminate perspective distortion. FG is paused preventing cloud, tree and sun movement. The combination allows creating higher quality panoramas which aren't often practical with a physical camera.

Cylindrical and similar panoramas don't need a special viewer, unlike spherical panoramas. Hugin is pretty much automated and following a simple series of clicks will produce good results. The forum thread has details on using Hugin.

[[File:Austria in Autumn in FlightGear 2019 02.jpg|thumb|center|800x600px|Example panorama with wide view. This is made with the WiP script at Hugin at Innsbruck Airport (LOWI) from a line of just 10 screenshots. A lower FoV and more screenshots will reduce distortion. Click image to view full size. Another example panorama with smaller view made from 3 screenshots is [[:File:Austria_in_Autumn_in_FlightGear_2019_01.jpg|here]]. ]]

==== Spherical panoramas ====
If you want to make full spherical panorama take a look at this [[Howto: Make full spherical panorama|tutorial]].

== Field of View (FoV) ==
[[File:C172p-wide-narrow.jpg|thumb|270px|The difference of wide/narrow angle. See how the background changes using a zoom.]]

You can change this by pressing {{Key press|Shift|X}} or {{key press|X}} or using the Mouse-wheel in View-mode.
The field of view is by default set to 55 (degrees).

Increasing the field you get wide angle up to 120 degrees. That's interesting as it covers a whole part of the scenery but also seems to make objects appear far away. Use it for showing large parts of sceneries, or long aircraft, etc. Another interesting feature of using a wide angle is that it exaggerates perspective. One effective use of this consists of using a wide angle lens combined with placing the camera near the object. This will make the object in question appear larger, more impressive than it really is. For an higher, wider angle make a panorama.

Decreasing the field you get a narrow angle and a zoom-effect. This means you can take far away objects virtually close to you. An interesting effect is, that it also makes the background more "dense". Another interesting side effect is distance foreshortening, meaning that the distance between various object is becoming compressed, suggesting less space between objects than there really is.

== Lighting and Daytime ==
[[File:C172p-water-shader.jpg|thumb|270px|Showing the effect of the low sun and the water shaders]]

The most appealing photos in real life are made in the morning or evening. The light has a warm color and the shadows and ambient colors are soft and long which gives fantastic impressions. The noon gives hard shadows and strong contrasts, which are hard to deal with.

This applies to FlightGear as well. So play a bit with the time of day, especially Dawn/Morning/Afternoon and Dusk. Play with the seasons and locations as well. In the winter near the poles, the sun is low, while near the equator the sun is standing high in the sky. As an example, this gives nice effects with the water shaders.

== Weather ==
Our weather has improved much with the addition of [[advanced weather]] - see the [[Weather#Advanced Weather Gallery .282017.2B.29|gallery]]. To enable it, you must open the <tt>Environment > Weather</tt> dialog, then check "Detailed Weather" and click "OK". With advanced weather enabled, clouds are placed while taking the terrain and wind patterns into account, making for much more realistic cloud and weather patterns. Advanced weather works best with [[atmospheric light scattering]] enabled as well.

{| class="floatright"
|-
| [[File:Gazelle_over_Blue_Mountains_near_Katoomba_in_Australia_with_signature_blue_haze_(FlightGear_2020.x).jpg|thumb|150px|Blue organic smog in the Australian Blue Mountains from Eucalyptus oil released by trees]]
| [[File:SOTM_2018-03_Gazelle_at_Sunset._Near_Mt._St._Helens_by_StuartC.jpg|thumb|150px|Ground haze near Mount St. Helens]]
| [[File:Sunlight_streaming_through_clouds,_EC_135_over_Zurich_in_Switzerland_(Flightgear_2018.x).jpg|thumb|150px|Cloud shadows on ground and the lake, as sunlight streams through gaps in clouds]]
|-
| [[File:SOTM_2018-12_Stormy_Day_by_GinGin.jpg|thumb|150px|The convection slider affects the shape of clouds as well as physics]]
| [[File:Pterosaur,_Hawaii_(Flightgear_2019.x).jpg|thumb|150px|Smaller scales can make it easier to get contrasting weather in visible range]]
|
|}

This is an old [https://www.flightgear.org/tours/advanced-weather-v1-4-in-flightgear-2-6/ 2012 article] on how the advanced weather system works and is driven by terrain. It's definitely is worth reading.

The dialogue <tt>Environment > Weather > Detailed weather > Advanced settings</tt> has a lot of options that affect weather. The <code>cloud shadows</code> options is there. The <code>ground haze</code> and <code>haze structure</code> options simulate moisture. The <code>smog</code> slider should also be used for the organic smog of forests in areas such as the Blue Mountains of Australia, the Blue Ridge mountains of USA, and some forests in countries like France or Italy. Turning up <code>convective conditions</code> and <code>turbulence</code> will affect cloud shape as thermals get stronger and narrower.

The [[Weather#Weather_pattern_scales|scale sliders]] in the Advanced options dialogue affect how quickly the weather changes over space. For instance it's easier to get a single storm cell with skies mostly clear elsewhere by making the scales smaller.

Remember to use <tt>''Environment > Weather > Detailed weather > Advanced settings > Temperature offset''</tt> with scenarios to simulate higher or lower temperatures. This is the only way to simulate winter, for example. Rainy scenarios produce snow-fall as as the temperature changes.

Use ''[[Weather#Snow%20and%20rain%20on%20ground|Environment > Environment settings]]'' for rain on the ground, or adjusting snow deposits - these are not set from the weather dialog as they depend on ''history'' of weather, not weather at any instant.

The advanced weather simulation is very sophisticated. There are many properties of atmosphere state that are currently not exposed by the GUI, or are not practical to expose. These properties are randomised each time AW is initialised. Live METAR reports are a vague, limited, rounded off, variable quality, hint at atmospheric state very close to an airfield given at varying intervals intended for airfield operation. Therefore, when using METARs to drive weather there are a lot of properties that unavoidably need to by randomly guessed by Advanced Weather. Pressing "Apply" in the Weather dialog for a given weather condition or a METAR will create a new random set of properties.

== Environment ==

Nature is always changing, often in cycles. This [https://www.flightgear.org/tours/simulating-the-ever-changing-scenery/ article] from 2015 details some ways in which Flightgear simulates this constant change. Since that article has been written things like Auroras have been added. The settings are in <tt>Menu > Environment > Environment settings</tt>. To control volcanic activity (March 2020), fly near a [[Volcanoes|listed volcano]] and goto Environment > Volcanoes to see a list of volcanoes in the region.

The position of the sun, planets, and moon follow reality and are driven by Flightgear's accurate celestial simulation. The arc the sun describes will vary according to time of year and how far away from the equator you are. In winter the arc of the sun keeps lower the further you move towards the poles. Moon phases vary in a [https://en.wikipedia.org/wiki/Lunar_phase monthly cycle]. Remember the moon is visible during the day too, and can create some striking views, especially when zoomed in a bit.

[[Earthview]] displays the Earth from high altitudes or orbit with cloud shadows and cheangeable atmospheric properties. There are high resolution texture maps available [[Earthview#Customization|here]]. Try [[FlightGear space program|spacecraft]] like [[Vostok-1]] or [[Space Shuttle]], high altitude craft like the [[North American X-15|X-15]], or fictitious craft like the UFO or a [[FlightGear hangars|3rd party]] craft.

Flightgear supports small scale detail with ''3d structure'' (volumetric detail) on terrain with the use of [[:Category:Screenshots of overlays|overlays]]. Overlays can show detail down to individual grass blades on airport keep, and are therefore are GPU intensive. Try them out if you have a recent GPU with the [[Anti-aliasing#Transparency_anti-aliasing|Multi-sampling]] variety of transparency anti-aliasing enabled. Some regions will have performance to spare as they are less demanding on GPUs because they don't have trees or bushes like Iceland, which can help FPS on older GPUs while using overlays. Overlays are easy to toggle, and switching to a smaller resolution in windowed mode may help.

There is a 2nd type of grass that is currently [[FlightGear_Newsletter_February_2015#ALS_Volumetric_Grass|turned on through XML]] as it looks bad without ALS renderer (March 2020). It's used in some sceneries like the [[User:Wlbragg#Kansas_Custom_Scenery|Kansas/Midwest scenery]] to add smaller plant layers on top of grass. More examples and instructions in [https://forum.flightgear.org/viewtopic.php?f=19&t=34547 this] forum thread.

Remember to experiment with the snowline and snow thickness. The snowline is set by default to the METAR weather at the moment. Snow can stay around for weeks. The actual thickness of snow and the snowline depends on the history of snowfall and weather over a period. It's impossible to know that from the METAR. See Environment settings > 'Set maximum snow level from METAR', 'snowline', and 'snow thickness'. The right sun angle can bring out detail in snow.

<gallery mode="packed">
File:Seasons transition from summer to autumn at Innisbruck, Austria (Flightgear 2019.x).jpg|Transition of seasons from summer to autumn
File:Kilauea Lava Lake, Hawaii (Flightgear 2019.x).jpg|Lava lake showing 3d structure of cooled lava with overlays enabled at Kilauea, Hawaii
File:SOTM-Sept17.jpg|'Weeping wall' waterfalls at Mount Waialeale, Island of Kauai, Hawaii
File:BK 117 on the shore of lake Zurich, Switzerland (Flightgear 2018.x-19.x).jpg|The moon is visible at daytime. Changing date slightly changes phase
File:Aurora Borealis and Sun halo in Northern Norway in Autumn (Flightgear 2019.x).jpg|Aurora Borealis and Sun halo in northern Norway (sun below the horizon). The rays of the low sun are red, making the halo red
File:SOTM 2019-03 Look at those clouds by Thorsten.jpg|Earthview
File:Tidal flats at low tide in Morecambe Bay in England (Flightgear 2020.x) 01.jpg|Tidal flats at low tide. Tidal flats gradually transition from uncovered to fully covered by water. Tides change based on time of day.
File:Tidal flats at high tide in Morecambe Bay in England (Flightgear 2020.x) 02.jpg|Tidal flats at high tide
File:Iceland airport keep- thin snow, Keflavik International Airport (BIKF) in Flightgear 2020 LTS 06.jpg| Thin patchy snow
</gallery>
=== Notable optical and lighting effects ===

Flightgear has a very sophisticated light simulation. This [https://www.flightgear.org/tours/the-magic-of-light-and-haze/ 2014 article] describes just some of what was simulated at the time. Tip: Press 'Apply' in the weather dialog to get a new set of random values for unexposed atmosphere properties that create optical effects. Here are a few things to watch out for (March 2020):

* Ice halos from ice crystals (icy haze) in the atmosphere interacting with sunlight. Lower temperatures increase the chance. Use a negative [[Weather#General settings|temperature offset]] to lower temperatures.

* Sun halos: 22 degree ring around the sun. Halos occur frequently, upto a 100 days per year.
* Rainbows: in rain volumes forming a 40 degree ring around the point opposite the sun (anti-solar point). Heavier downpours with larger droplet sizes makes bows more intense.
* Aurora: A ring around both magnetic poles at all times of the year. Normally seen at latitudes above 60 degrees. Large disturbances in the magneto-sphere by solar activity can cause Auroras to be seen further towards the equator. Auroras have been seen as far away from poles as Austrian Alps/Germany(2015), Florida(1989), and even reportedly Honolulu (great solar storm of 1859).
* Clouds: Colour change of high (cirrus) clouds with angle because of the way ice crystals interact with light - try a low sun. The "silver lining" at edges of clouds.
* Water colour: the colour of water depends on the depth, suspended particles bouncing light back toward the camera, light from the overhead sky, and time of day. Suspended particles or depth changes the colour from region to region in Flight-gear. Green algae can make the water in the Colorado river different from the clear shallow blue-ish Caribbean sea, or the mouth of the Amazon river which is brownish from silt. An overcast sky will make the sea grey-ish.
* Ground and surfaces: Lighting of water, puddles, snow, and ice. Water includes rain splashes, fog, and ice on canopies. Snow can build up on flatter surfaces, including roofs. Experiment with the sun at low angles, snow thickness, and sunlight that is reddish or yellowish at sunrise/sunset. Experiment with wind-strength, direction to create waves.
* Earthview: Try increasing the dust levels. Try manipulating the clouds after temporarily un-ticking cloud shadows. Terrain relief is best seen with a low sun angle.

<gallery mode="packed">
File:SOTM 2020-01 The Goddness of Love & Beauty in iridescence by eatdirt.jpg|Colour change due to scattering by ice crystals
File:Eurocopter EC135 over wet volumetric grass in Innsbruck Airport (LOWI), Austria (Flightgear 2018.x).jpg|Reflection of light from the sun by puddles at lower sun angles
File:Bell 412 over a snowcapped Mount Etna in Sicily in winter (Flightgear 2019.x) 02.jpg|Thin clouds close to the sun show a peak in the intensity of light scattered in the forward direction. Snow is lit by the yellowish light from the low sun.
File:SOTM 2018-11 Windows 85 Simulator by GinGin.jpg|At low angles dust on glass surfaces can be seen on craft which support it like the Shuttle, A320, and EC145
File:C172p-frost.jpg|Frost on windows
File:SOTM 2019-06 Catching the rainbow by F5SLQ.png|Rainbow
File:Silver lining of clouds, EC135 over Zurich in Switzerland (Flightgear 2018.x).jpg|'Silver lining' in the fringes of clouds
File:SOTM 2019-12 Caribbean Island by Madbyte70.jpg|Shallow clear waters of the Caribbean under a clear noon sky
File:Sun dog and ice halo, from top of Mount Herdubreid volcano in Iceland (Flightgear 2020.x).jpg|Sun halo (22 degree ring), Sun pillar (vertical line through the sun), and Sun dogs (left and right of the sun).
</gallery>
 

== Locations ==
The choice of the location depends a bit what you want to show. So what want you to show? Do you have already a theme in mind?

As an example for showing an aircraft just for presentation, use an "empty" background like the sky, sea or desert. If you want to show the aircraft during operation you could choose some of FlightGear's better airports like [[EHAM]], [[LFPG]] as the background, or some of the more detailed custom sceneries.

== Picking the right livery and aircraft configuration ==
{| class="floatright"
|-
| [[File:C172p-preview5.jpg|thumb|150px|C172P, White and blue livery]]
| [[File:C172p-preview4.jpg|thumb|150px|C172P, green and grey livery]]
| [[File:SOTM-Mar19.jpg|thumb|150px|Low sun colouring the Gazelle over Madrid]]
| [[File:C172p-preview13.jpg|thumb|150px|Craft light & intensities can make a difference]]
|}
The right colour scheme for the scene can make a huge difference. Liveries in FlightGear can often be changed mid flight. The first two shots of the c172p show the difference it makes. If the liveries were swapped in the two screenshots, the result would be less pleasing to the eye. The light from a low sun is yellowish or reddish. This can add to the colour of shinier surfaces or glass depending on angle. Things like afterburners or spotlights affect colour too.

 
== Hoping to stumble upon the right shot versus changing what you can control to increase your chances of finding a good shot ==
Nature can create an almost infinite combinations of environment state, weather and lighting conditions. Flightgear's simulation follows nature. A particular combination can be rare indeed. A casual google will find many articles written about how long nature and landscape photographers using a physical camera have to wait! In a simulated environment like Flightgear there is a huge advantage when we can control the environment or even time itself.

[https://mymodernmet.com/professional-photography-tips-albert-dros/ This] article and its' [https://petapixel.com/2018/06/18/how-i-wait-years-to-get-my-photos/ reference] article are just the first search results, but they talk well about how people taking nature photos with a physical camera "brainstorm" about possible combinations of environment, weather, and lighting that go well together. People have to do all they can to try to increase their chances of being in right place at the right time to see something interesting. The article talks about waiting years to get foggy weather at a specific location or waiting 3 years to get a combination of ground haze/sunrise/tulips. One account is about returning year after year for the 1 week during which the sunsets exactly in the middle of the arch of a bridge while hoping for clouds that moved away from the camera. These photographers may never get the exact intensity or combination they seek, but they can hope for something interesting. Some events like unusual weather, huge geomagnetic storms, or volcanic eruptions may happen once or a few times in a lifetime. The chances of then finding a particular combination of weather or environment is almost zero.

Unlike taking photos with a physical camera, you don't have to hope you are in the right spot, looking in the right direction, with the right weather and lighting exactly right for that direction. We have god-like control over time, environment settings, weather, and lighting. The landscape is harder to control as relocating or approaching from another direction does take time.

If you are flying and find a particularly striking location or view suitable for a particularly good spot, it's always possible to imagine if it would be better with different approach direction, environment settings, weather and lighting. Experimenting with different settings can help. The previous weather can be restored when you resume your flight. The flight recorder lets you look through the historical flight path and change weather (some craft support this better than others).

[[File:Lightning_strike_showing_illumination_of_nearby_clouds_(Flightgear_2019.x)_01.jpg|thumb|150px|'Catching' lightning by slowing physics time and then pausing]]
The sim can be paused at any time. This lets you to easily switch view, tweak Field of View, change environment settings etc. There are two different clocks in Flightgear. The environmental clock controls things like the sun, moon and their lighting. The physics clock is used for the physics that can affect your craft. Weather is also part of physics. You can watch a sunrise while flying among mountains with 600x environmental time-acceleration without crashing. The sim must be unpaused for Advanced Weather to be re-initialised with new random properties and populate clouds. The sim must also be briefly unpaused to let change of environment time affect the scene lighting. Slowing physics time down can help you change weather without your craft going past the landscape. In fact if you slow down physics time, you can 'catch' lighting by pausing, and then take a screenshot.

Lighting in the atmosphere is all about angles. Time, sun position, moon phase, view direction relative to the sun. You can use this knowledge to make it more likely you see what you are looking for. For instance rainbows are light scattered back by a rain volume. Rainbows form a circle around the point opposite the sun. Using this, you can increases the odds of a good rainbow screenshot by flying when the sun is low, and approaching interesting scenery in a direction that places the scenery between the point opposite the sun and your camera. Of course, the point opposite the sun has to be in a rain volume too. Flying when the sun is low is simply a good way to spot rainbows. If you found an interesting scene you want to showcase like an airport, you can always try to put the sun in a good spot by changing time of day/year and re-initialise weather until you get a rain volume where you want!
== Colors and whitebalance ==
As in real life, in FGFS the pictures often have to be corrected in colors and white balance. This can be done with almost any image editor. In [http://www.gimp.org GIMP] this can be done through <tt>Layers > Colors > Brightness and contrast</tt>.

== Conclusion ==
When keeping this all in mind, you can make some stunning pictures. Try and play with as much you can, look at real images to get hints or try to copy a real life image in FlightGear. All this will help you to take good pictures!

(''Note: the screenshots used in the page aren't all examples of artistic shots (March 2020). A few of them illustrate a particular aspect of FG with haze/smog turned down, or were what was available at hand. See the screenshots of the month category for better examples'')

== User experiences ==
[[File:Shuttle launch at sunrise.jpg|thumb|250px|Space Shuttle launch]]
Thorsten Renk
{{FGCquote
|1= One of my favourite Shuttle shots: I took about an hour. I set up a good thirty different cloud configurations on the pad and then used the view offsets to anticipate how they'd look when I punch through the cloud deck. When I had one I liked, I played with time and environment settings to adjust the light. Then I launched and paused FG going through the cloud deck and used the view offsets for five minutes to find the one angle which I really liked. Then I repeated the whole exercise two more times and took the best shot out of those.
|2= {{cite web
| url = http://forum.flightgear.org/viewtopic.php?f=19&t=28162&start=225#p274091
| title = <nowiki>[FlightGear Forum] Re: FG Promotional Video</nowiki>
| author = <nowiki>Thorsten Renk</nowiki>
| date = Jan 26th, 2016
| added = Feb 14th, 2016
| script_version = 0.23
}}
}}

== Related content ==
=== Wiki ===
* [[Howto:Make full spherical panorama]]
* [[Submitting Screenshots]]
* [[:Category:Screenshot of the month]]

=== Forum ===
* {{forum link|f=19|title=Media}} - Subforum with many great screenshots.
* {{forum link|type=search|f=19|keywords=(screenshot+month{{!}}SOTM)|text=Search for Screenshot of the month (SOTM)}}

[[Category:Howto|Make nice screenshots]]

[[de:Howto:Gute Screenshots machen]]

File:Iceland in FlightGear 2019 05 Keflavik BIKF (Space Shuttle).jpg

2021-12-19T13:20:30Z

Vs: add category

=={{int:filedesc}}==
{{Information
|description={{en|1=Space shuttle landing at [[Keflavik Airport|Keflavik International Airport]] (BIKF) in FlightGear 2019, military side.}}
|date=2019-05-04
|source=Screenshots taken by Thorsten Renk. Permission given to use under CC-BY-SA-4.0.

|author=Thorsten Renk
|permission=
|other versions=
}}

=={{int:license-header}}==
{{subst:Custom license marker added by UW}}
Permission given to use under CC-BY-SA-4.0.
{{Cc-by-sa-4.0}}

[[Category:Screenshots at high settings]]
[[Category:Screenshots at high settings/non-sotm]]
[[Category:Screenshots at high settings/sotm]]
[[Category:Space Shuttle screenshots]]
[[Category:Keflavik Airport screenshots]]
[[Category:Screenshots of snow]]

File:Iceland airport keep- thin snow, Keflavik International Airport (BIKF) in Flightgear 2020 LTS 06.jpg

2021-12-19T13:19:16Z

Vs: add categories

=={{int:filedesc}}==
{{Information
|description={{en|1=Iceland airport keep, [[Keflavik Airport|Keflavik International Airport]] (BIKF) in FlightGear 2020 LTS

Thin snow, autumn grass.}}
|date=2020-10-29
|source={{own}}
|author=[[User:Vs|Vs]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Screenshots at high settings]]
[[Category:Screenshots at high settings/2020]]
[[Category:Screenshots at high settings/non-sotm]]
[[Category:Screenshots of scenery in Iceland]]
[[Category:Keflavik Airport screenshots]]
[[Category:Screenshots of ALS]]
[[Category:Screenshots of overlays]]
[[Category:Screenshots of snow]]

File:SOTM 2021-08 Unscheduled flight at Innsbruck (Space Shuttle) by GinGin.jpg

2021-12-19T13:15:58Z

Vs: add category

=={{int:filedesc}}==
{{Information
|description={{en|1=SOTM 2021-08 Unscheduled flight at Innsbruck (Space Shuttle) by GinGin}}
|date=2021-08-31
|source=FlightGear.org SOTM 2020-08, released under CC-BY-SA-4.0
|author=X - see filename.
|permission=
|other versions=
}}

=={{int:license-header}}==
{{cc-by-sa-4.0}}

[[Category:Screenshot of the month/2021-08]]
[[Category:Innsbruck Airport screenshots]]
[[Category:Screenshots at high settings]]
[[Category:Screenshots at high settings/2021]]
[[Category:Screenshots at high settings/sotm]]
[[Category:Screenshots of weather]]
[[Category:Space Shuttle screenshots]]
[[Category:Screenshots of snow]]

File:Winter on the Beagle Channel.jpg

2021-12-19T13:15:51Z

Vs: add category

=={{int:filedesc}}==
{{Information
|description={{en|1="Winter on the Beagle Channel", [[Airbus A320 Family|Airbus A320]].}}
|date=2020-07-12
|source={{forum url|p=371031}}
|author=Picun_1812
|permission=
|other versions=
}}

=={{int:license-header}}==
{{cc-by-sa-4.0}}

[[Category:Airbus A320 cockpit screenshots]]
[[Category:Screenshot of the month/2020-07]]
[[Category:Screenshots of snow]]

File:Bell 412 over a snowcapped Mount Etna in Sicily in winter (Flightgear 2019.x) 02.jpg

2021-12-19T13:15:43Z

Vs: add category

=={{int:filedesc}}==
{{Information
|description={{en|1=[[Bell 412]] over a snow capped Mount Etna in Sicily in winter (FlightGear 2019.x)

Note the lighting of snow in the reddish sunlight

Note the strong forward scattering in the clouds close to the sun that are thin enough for light to pass through}}
|date=2020-03-09
|source={{own}}
|author=[[User:Vs|Vs]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Screenshots_at_high_settings]]
[[Category:Screenshots_at_high_settings/2019]]
[[Category:Screenshots_at_high_settings/non-sotm]]
[[Category:Screenshots of scenery in Sicily]]
[[Category:Bell 412 screenshots]]
[[Category:Screenshots of snow]]

File:SOTM 2018-11 Morning Mountain flight by StuartC.jpg

2021-12-19T13:15:36Z

Vs: add category

=={{int:filedesc}}==
{{Information
|description={{en|1=SOTM 2018-11: Morning Mountain flight by StuartC}}
|date=2018-11-30
|source=SOTM 2018-11
|author=X
|permission=
|other versions=
}}

=={{int:license-header}}==
{{cc-by-sa-4.0}}

[[Category:Screenshot of the month/2018-11]]
[[Category:Screenshots_at_high_settings]]
[[Category:Screenshots_at_high_settings/2018]]
[[Category:Screenshots_at_high_settings/sotm]]
[[Category:Screenshots of snow]]

File:SOTM 2019-06 Ice and fire by vnts.jpg

2021-12-19T13:15:28Z

Vs: add category

=={{int:filedesc}}==
{{Information
|description={{en|1=SOTM 2019-06: Ice and fire by vnts}}
|date=2019-06-28
|source=SOTM June 2019
|author=vnts
|permission=
|other versions=
}}

=={{int:license-header}}==
{{cc-by-sa-4.0}}

[[Category:Screenshot of the month|2019 06]]
[[Category:Screenshot of the month/2019-06]]
[[Category:Screenshots of volcanoes]]
[[Category:Screenshots_at_high_settings]]
[[Category:Screenshots_at_high_settings/2019]]
[[Category:Screenshots of scenery in Sicily]]
[[Category:Bell 412 screenshots]]
[[Category:Screenshots_at_high_settings/sotm]]
[[Category:Screenshot_of_the_year/2019]]
[[Category:Screenshots of snow]]

File:Bell 412 over a snowcapped Mount Etna, Sicily - Flightgear 2019.x.jpg

2021-12-19T13:15:23Z

Vs: add category

=={{int:filedesc}}==
{{Information
|description={{en|1=Bell 412 over a snowcapped Mount Etna in Sicily in winter

Flightgear 2019.x

Note forward scattering of thin clouds close to the sun, and snow being lit by reddish sun light}}
|date=2020-04-20
|source={{own}}
|author=[[User:Vs|Vs]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Screenshots at high settings]]
[[Category:Screenshots at high settings/non-sotm]]
[[Category:Bell 412 screenshots]]
[[Category:Screenshots of ALS]]
[[Category:Screenshots of scenery in Sicily]]
[[Category:Screenshots of volcanoes]]
[[Category:Screenshots at high settings/2019]]
[[Category:Screenshots of snow]]

File:SOTM 2020-11 Dawn Of Winter (Piper PA-18 Super Cub Amphibian, Juneau, Alaska, USA) by Husky Dynamics.jpg

2021-12-19T13:07:06Z

Vs: add category

=={{int:filedesc}}==
{{Information
|description={{en|1=SOTM 2020-11 Dawn Of Winter (Piper PA-18 Super Cub Amphibian, Juneau, Alaska) by Husky Dynamics}}
|date=2020-11-30
|source=FlightGear.org SOTM 2020-11
|author=X - see filename.
|permission=
|other versions=
}}

=={{int:license-header}}==
{{cc-by-sa-4.0}}

[[Category:Screenshot of the month/2020-11]]
[[Category:Piper PA-18 Super Cub screenshots]]
[[Category:Screenshots of scenery in Alaska]]
[[Category:Screenshots at high settings]]
[[Category:Screenshots at high settings/2020]]
[[Category:Screenshots at high settings/sotm]]
[[Category:Screenshots of weather]]
[[Category:Screenshots of snow]]

World Scenery 3.0 roadmap

2021-12-19T08:17:48Z

Vs: cleanup

{{Scenery Core Development}}
{{See also|TerraGear roadmap}}
{{Project
|name = World Scenery 3.0
|description = New world-wide scenery
|start-date = 2019-Sep
|current-status = Active <ref>https://sourceforge.net/p/flightgear/mailman/message/37074319/</ref>
|developers = Scott Giese Richard Harrison Stuart Buchanan

|motivation-body =
{{Main article|Virtual Planet Builder}}
{{FGCquote
|Virtual Planet Builder (VPB) is OSG's terrain-database-building tool.
It loads GIS elevation data for a
region, combines it with imagery and produces a spatially-balanced
quadtree tiled database that can be navigated simply by loading the
top-level file. All of the LOD Ranges are pre-configured and the
DatabasePager automatically loads and unloads different segments of
terrain without any supporting userspace code required. VPB can build
terrain models ranging from a small area to the entire planet. These
databases can be fluidly navigated at 60fps from outer space down to
ground level with no interruptions. The terrain models are built of
regular grid arrays with optional edge-skirts to conceal any cracks
caused by adjacent LOD differences. 
|{{cite web |url=http://alphapixel.com/wp-content/uploads/2015/04/OpenSceneGraph-OSG-Virtual-Planet-Builder-VPB-OSGDEM.pdf
|title=<nowiki>OpenScenGraph's Virtual Planet Builder/OSGDEM</nowiki>
|publisher=<nowiki>AlphaPixel, LLC</nowiki>
}}
}}

|objective-body =

[[File:Edinburgh rendering using WS3.0.jpg|thumb|Initial rendering of Edinburgh scenery using a raster landclass and texture lookup for city, water and grass]]
[[File:WS3.0 terrain with WS2.0 EGPH.jpg|thumb|Screenshot showing a WS2.0 airport .btg file rendered with WS3.0 terrain]]
[[File:EGPH roads.jpg|thumb|WS3.0 Edinburgh airport with runtime-generated roads from OSM data]]
[[File:WS30 - West Lothian.png|thumb|WS30 view of West Lothian, with 25m resolution landclass data, vegetation, osm2city buildings, and OSM-based roads and rivers.]]
[[File:WS30 street lighting.jpg|thumb|Edinburgh at night, with osm2city buildings, OSM-base roads, including whether they are lit or not. Note the road in the foreground which is lit near the buildings and unlit in the countryside.]]

Produce high-quality scenery using the best-known practices.

TerraGear becomes obsolete in favor of VPB.

* '''OpenGL 3.3 Core Profile''': WS3.0 will require us to eliminate the usage of the fixed-function pipeline. 
* '''Shader-based Rendering''': All of the terrain renderings will be done via GLSL shaders. 
* '''OSG Core''': OpenSceneGraph will require targeting of the OpenGL Core Profile.

WS3.0 will continue to cooperate with osm2city.

Easy upgrade: Airport layouts will be generated in real-time. Apt.dat will continue to be the primary source for airport layouts.
Airports will be draped over the terrain. This eliminates the need to cut airport layouts into the underlying terrain.

|background-body =
=== Data Sources ===

:;SRTMGL3.003:: https://e4ftl01.cr.usgs.gov/MEASURES/SRTMGL3.003/
:;SRTMGL1.003:: https://e4ftl01.cr.usgs.gov/MEASURES/SRTMGL1.003/
:;Global Land Cover:: https://lcviewer.vito.be/
:;Natural Earth:: https://www.naturalearthdata.com/
:;OpenStreetMap :: https://www.openstreetmap.org (See https://sourceforge.net/p/flightgear/fgmeta/ci/next/tree/ws30/ genroads.py, gencoastline.py, genwater.py for details)

|status-body =

As of 11/2021, WS30 is available on "next", and on the [https://download.flightgear.org/builds/nightly/ nightly builds].

Scenery is available for Scotland, but must be downloaded directly (https://drive.google.com/file/d/1tGXSI8RwQxFL0_AFhXaFRVA6go-u7YBW/view?usp=sharing). You need to add the downloaded and then extracted folder as additional scenery folder.

WS30 can be enabled from the Rendering Options menu, with fine-tuning from the LoD menu. Alternatively you can set --prop:/scenery/use-vpb=true to enable it as command line option.

Airports are currently in the old WS2 format - including airport keep terrain. The WS30 terrain goes under the airport so it is not visible.

Roads are implemented. Lights on roads are implemented - to see, set time to night. WiP rendering.

Vegetation is available - initial version.

Water uses a different technology to WS30 terrain - it uses a precise vector format. OSM waterbodies and coastlines are utilised in WS30. Texture coordinates are used for smooth transitions and detail. Water rendering is separate to terrain, and very WiP currently.

Scenery generation workflow is at an advanced stage. It's fast to build. Scott was able to do UK in a matter of hours [https://sourceforge.net/p/flightgear/mailman/message/37259618/]. People interested in generating scenery for the World Build, or getting their landclass or elevation work on [[Suggested custom scenery|custom scenery]] in, should start learning the tools and process. The exact VPB settings and scenery file format may change several times before the final build. But the process of getting work in to shouldn't change much for scenery creators. See the [[Virtual Planet Builder]] page for instructions.

====Scenery generation tool availability ====
* [[VPB]]: '''Linux:''' build from source, docker image available. '''Windows and Mac:''' build from source, no binaries yet, needs NVTT binaries - see "[[Mailing lists|fg-devel]]" mailing list to assist.
* [[QGIS]]: Not needed when experimenting with terrain generation using lower res landclass rasters provided by CORINE. '''Linux:''' build from source, binary packages[https://qgis.org/en/site/forusers/download.html], official docker release available: https://hub.docker.com/r/qgis/qgis but Fahim was not sure easy the GUI is to use [https://sourceforge.net/p/flightgear/mailman/message/37381800/]. '''Windows, Mac:''' official QGIS binary releases [https://qgis.org/en/site/forusers/download.html].

===LoD settings===
Go to ''View > Adjust LoD > World Scenery 3.0 section'' (Nov 2021).
* 7 LoD levels - most detailed is 6, shown at closest range. Least detailed is 0, shown at long range. LoD 0 tiles with Scotland scenery are 1x1 degree, or approx 111 km x 111 km at the equator.
* Scenery is divided into chunks called tiles. As view distance increases, tiles with a LoD level are replaced by tiles with the next lowest LoD level. e.g. Four LoD 6 tiles are replaced by one LoD 5 tile. Four LoD 5 tiles are replaced by one LoD 4 tile. As view gets closer the reverse happens. One LoD 2 tile is replaced by four LoD 3 tiles.
* Detail range - The LoD level below which each type of feature is not visible. e.g. setting vegetation to LoD 3 means vegetation is shown for LoD 3/4/5/6 and not shown for tiles with LoD 0/1/2.
* Minimum line feature width (line features are things like roads or rivers) - for every LoD level, the width in meters below which a line feature is not shown. e.g. setting LoD level four to 30 meters means rivers or roads that are narrower than 30 meters are not shown for level four tiles. The minimum widths should stay the same or decrease when going down a LoD level.
* Minimum area feature width (area features are things like lakes) - similar to minimum line feature width, but for area in square meters. Setting LoD 3 to 100 square meters means lakes of size 99 square meters or 40 square meters will not show for LoD level 3 tiles.

Proof of Concept {{progressbar|100}}
* VPB {{done}}
* osgOcean {{done}}
* osgVegetation {{done}}
* Generate terrain for Hawaii {{done}}
* Hack Hawaii VPB into FG {{done}}
 

OSG {{progressbar|70}}
* Core Profile: {{done}}
* GLVND Support: {{done}}
* glTF Plugin Support: {{ongoing}}
 

{{gallery
| title = Standard-Fidelity
| align = right
| N00-N10-LC100m-SRTMGL3.png | N00-N60 lat
| Africa-LC100m-SRTMGL3.png | Africa Land Coverage
| Africa-Natural.png | Natural Earth
| Ocean-N00-N90.png | Ocean Fill
}}
=== Standard-Fidelity - 90m SRTMGL3 - 100m Global Land Cover ===

=== Northern Hemisphere: 152.3 GB ===
=== Southern Hemisphere: 57.4 GB ===

Virtual Planet Builder {{progressbar|70}}
* Procure Demographic Data: SRTMGL3.003 {{paused}}
** Northern: {{progressbar|70}}
** Southern: {{progressbar|70}}
* Process through VPB {{paused}}
** Northern: {{progressbar|70}}
** Southern: {{progressbar|70}}
* Ocean {{done}}
** Northern: {{progressbar|100}}
** Southern: {{progressbar|100}}
 

=== High-Fidelity - 30m SRTMGL1 - Best Available Land Cover ===

Virtual Planet Builder {{progressbar|30}}
* Procure Demographic Data: SRTMGL1.003 {{paused}}
** Northern: {{progressbar|70}}
** Southern: {{progressbar|0}}
* Process through VPB {{paused}}
** Northern: {{progressbar|70}}
** Southern: {{progressbar|0}}
 

|news-body=
The northern hemisphere, up to N60, has been completed. The southern hemisphere, above S56, has been completed.
SRTM data was not captured above N60 and below S56, so alternative data sources need to be procured.

Stuart has made good progress with the procedure needed to convert apt.dat into an airport object. Our goal is to utilize this to project/drape the airport layout over the terrain. This will enable localized edits of airports without requiring us to generate another world scenery build.

Oceans are complete.
}}

{{gallery
| title = Standard-Fidelity Gallery
| align = center
| Terrain-Mesh.jpg | WS3 Terrain Mesh
| S10-N60-LC100m-SRTMGL3.png | Asia/India
| N00-N10-LC100m-SRTMGL3.png | Europe
| N00-N40-LC100m-SRTMGL3.png | USA
| Africa-LC100m-SRTMGL3.png | Land Coverage
| Africa-Natural.png | Natural Earth
| Africa-Natural2.png | Natural Earth
}}

For the experimental runtime generated mesh/landclassing engine - which may become WS3.0 - see [[Experimental terrain engine]].

[[Category:Development projects‎]]
[[Category:Scenery]]

World Scenery 3.0 roadmap

2021-12-19T08:07:46Z

Vs: /* Status */ add section on scenery generation tool availability.

{{Scenery Core Development}}
{{See also|TerraGear roadmap}}
{{Project
|name = World Scenery 3.0
|description = New world-wide scenery
|start-date = 2019-Sep
|current-status = Active <ref>https://sourceforge.net/p/flightgear/mailman/message/37074319/</ref>
|developers = Scott Giese Richard Harrison Stuart Buchanan

|motivation-body =
{{Main article|Virtual Planet Builder}}
{{FGCquote
|Virtual Planet Builder (VPB) is OSG's terrain-database-building tool.
It loads GIS elevation data for a
region, combines it with imagery and produces a spatially-balanced
quadtree tiled database that can be navigated simply by loading the
top-level file. All of the LOD Ranges are pre-configured and the
DatabasePager automatically loads and unloads different segments of
terrain without any supporting userspace code required. VPB can build
terrain models ranging from a small area to the entire planet. These
databases can be fluidly navigated at 60fps from outer space down to
ground level with no interruptions. The terrain models are built of
regular grid arrays with optional edge-skirts to conceal any cracks
caused by adjacent LOD differences. 
|{{cite web |url=http://alphapixel.com/wp-content/uploads/2015/04/OpenSceneGraph-OSG-Virtual-Planet-Builder-VPB-OSGDEM.pdf
|title=<nowiki>OpenScenGraph's Virtual Planet Builder/OSGDEM</nowiki>
|publisher=<nowiki>AlphaPixel, LLC</nowiki>
}}
}}

|objective-body =

[[File:Edinburgh rendering using WS3.0.jpg|thumb|Initial rendering of Edinburgh scenery using a raster landclass and texture lookup for city, water and grass]]
[[File:WS3.0 terrain with WS2.0 EGPH.jpg|thumb|Screenshot showing a WS2.0 airport .btg file rendered with WS3.0 terrain]]
[[File:EGPH roads.jpg|thumb|WS3.0 Edinburgh airport with runtime-generated roads from OSM data]]
[[File:WS30 - West Lothian.png|thumb|WS30 view of West Lothian, with 25m resolution landclass data, vegetation, osm2city buildings, and OSM-based roads and rivers.]]
[[File:WS30 street lighting.jpg|thumb|Edinburgh at night, with osm2city buildings, OSM-base roads, including whether they are lit or not. Note the road in the foreground which is lit near the buildings and unlit in the countryside.]]

Produce high-quality scenery using the best-known practices.

TerraGear becomes obsolete in favor of VPB.

* '''OpenGL 3.3 Core Profile''': WS3.0 will require us to eliminate the usage of the fixed-function pipeline. 
* '''Shader-based Rendering''': All of the terrain renderings will be done via GLSL shaders. 
* '''OSG Core''': OpenSceneGraph will require targeting of the OpenGL Core Profile.

WS3.0 will continue to cooperate with osm2city.

Easy upgrade: Airport layouts will be generated in real-time. Apt.dat will continue to be the primary source for airport layouts.
Airports will be draped over the terrain. This eliminates the need to cut airport layouts into the underlying terrain.

|background-body =
=== Data Sources ===

:;SRTMGL3.003:: https://e4ftl01.cr.usgs.gov/MEASURES/SRTMGL3.003/
:;SRTMGL1.003:: https://e4ftl01.cr.usgs.gov/MEASURES/SRTMGL1.003/
:;Global Land Cover:: https://lcviewer.vito.be/
:;Natural Earth:: https://www.naturalearthdata.com/
:;OpenStreetMap :: https://www.openstreetmap.org (See https://sourceforge.net/p/flightgear/fgmeta/ci/next/tree/ws30/ genroads.py, gencoastline.py, genwater.py for details)

|status-body =

As of 11/2021, WS30 is available on "next", and on the [https://download.flightgear.org/builds/nightly/ nightly builds].

Scenery is available for Scotland, but must be downloaded directly (https://drive.google.com/file/d/1tGXSI8RwQxFL0_AFhXaFRVA6go-u7YBW/view?usp=sharing). You need to add the downloaded and then extracted folder as additional scenery folder.

WS30 can be enabled from the Rendering Options menu, with fine-tuning from the LoD menu. Alternatively you can set --prop:/scenery/use-vpb=true to enable it as command line option.

Airports are currently in the old WS2 format - including airport keep terrain. The WS30 terrain goes under the airport so it is not visible.

Roads are implemented. Lights on roads are implemented - to see, set time to night. WiP rendering.

Vegetation is available - initial version.

Water uses a different technology to WS30 terrain - it uses a precise vector format. OSM waterbodies and coastlines are utilised in WS30. Texture coordinates are used for smooth transitions and detail. Water rendering is separate to terrain, and very WiP currently.

Scenery generation workflow is at an advanced stage. It's fast to build. Scott was able to do UK in a matter of hours [https://sourceforge.net/p/flightgear/mailman/message/37259618/]. People interested in generating scenery for the World Build, or getting their landclass or elevation work on [[Suggested custom scenery|custom scenery]] in, should start learning the tools and process. The exact VPB settings and scenery file format may change several times before the final build. But the process of getting work in to shouldn't change much for scenery creators. See the [[Virtual Planet Builder]] page for instructions.

====Scenery generation tool availability ====
* [[VPB]]: '''Linux:''' build from source, docker image available. '''Windows and Mac:''' build from source, VPB has no binaries yet, needs NVTT binaries - see mailing list to assist.
* [[QGIS]]: Not needed when experimenting with terrain generation using lower res landclass rasters provided by CORINE. '''Linux:''' build from source, binary packages[https://qgis.org/en/site/forusers/download.html], official docker release available: https://hub.docker.com/r/qgis/qgis but Fahim was not sure how the GUI aspect worked [https://sourceforge.net/p/flightgear/mailman/message/37381800/]. '''Windows, Mac:''' official QGIS binary releases [https://qgis.org/en/site/forusers/download.html].

===LoD settings===
Go to ''View > Adjust LoD > World Scenery 3.0 section'' (Nov 2021).
* 7 LoD levels - most detailed is 6, shown at closest range. Least detailed is 0, shown at long range. LoD 0 tiles with Scotland scenery are 1x1 degree, or approx 111 km x 111 km at the equator.
* Scenery is divided into chunks called tiles. As view distance increases, tiles with a LoD level are replaced by tiles with the next lowest LoD level. e.g. Four LoD 6 tiles are replaced by one LoD 5 tile. Four LoD 5 tiles are replaced by one LoD 4 tile. As view gets closer the reverse happens. One LoD 2 tile is replaced by four LoD 3 tiles.
* Detail range - The LoD level below which each type of feature is not visible. e.g. setting vegetation to LoD 3 means vegetation is shown for LoD 3/4/5/6 and not shown for tiles with LoD 0/1/2.
* Minimum line feature width (line features are things like roads or rivers) - for every LoD level, the width in meters below which a line feature is not shown. e.g. setting LoD level four to 30 meters means rivers or roads that are narrower than 30 meters are not shown for level four tiles. The minimum widths should stay the same or decrease when going down a LoD level.
* Minimum area feature width (area features are things like lakes) - similar to minimum line feature width, but for area in square meters. Setting LoD 3 to 100 square meters means lakes of size 99 square meters or 40 square meters will not show for LoD level 3 tiles.

Proof of Concept {{progressbar|100}}
* VPB {{done}}
* osgOcean {{done}}
* osgVegetation {{done}}
* Generate terrain for Hawaii {{done}}
* Hack Hawaii VPB into FG {{done}}
 

OSG {{progressbar|70}}
* Core Profile: {{done}}
* GLVND Support: {{done}}
* glTF Plugin Support: {{ongoing}}
 

{{gallery
| title = Standard-Fidelity
| align = right
| N00-N10-LC100m-SRTMGL3.png | N00-N60 lat
| Africa-LC100m-SRTMGL3.png | Africa Land Coverage
| Africa-Natural.png | Natural Earth
| Ocean-N00-N90.png | Ocean Fill
}}
=== Standard-Fidelity - 90m SRTMGL3 - 100m Global Land Cover ===

=== Northern Hemisphere: 152.3 GB ===
=== Southern Hemisphere: 57.4 GB ===

Virtual Planet Builder {{progressbar|70}}
* Procure Demographic Data: SRTMGL3.003 {{paused}}
** Northern: {{progressbar|70}}
** Southern: {{progressbar|70}}
* Process through VPB {{paused}}
** Northern: {{progressbar|70}}
** Southern: {{progressbar|70}}
* Ocean {{done}}
** Northern: {{progressbar|100}}
** Southern: {{progressbar|100}}
 

=== High-Fidelity - 30m SRTMGL1 - Best Available Land Cover ===

Virtual Planet Builder {{progressbar|30}}
* Procure Demographic Data: SRTMGL1.003 {{paused}}
** Northern: {{progressbar|70}}
** Southern: {{progressbar|0}}
* Process through VPB {{paused}}
** Northern: {{progressbar|70}}
** Southern: {{progressbar|0}}
 

|news-body=
The northern hemisphere, up to N60, has been completed. The southern hemisphere, above S56, has been completed.
SRTM data was not captured above N60 and below S56, so alternative data sources need to be procured.

Stuart has made good progress with the procedure needed to convert apt.dat into an airport object. Our goal is to utilize this to project/drape the airport layout over the terrain. This will enable localized edits of airports without requiring us to generate another world scenery build.

Oceans are complete.
}}

{{gallery
| title = Standard-Fidelity Gallery
| align = center
| Terrain-Mesh.jpg | WS3 Terrain Mesh
| S10-N60-LC100m-SRTMGL3.png | Asia/India
| N00-N10-LC100m-SRTMGL3.png | Europe
| N00-N40-LC100m-SRTMGL3.png | USA
| Africa-LC100m-SRTMGL3.png | Land Coverage
| Africa-Natural.png | Natural Earth
| Africa-Natural2.png | Natural Earth
}}

For the experimental runtime generated mesh/landclassing engine - which may become WS3.0 - see [[Experimental terrain engine]].

[[Category:Development projects‎]]
[[Category:Scenery]]

VPB

2021-12-19T08:06:53Z

Vs: add redirect

#REDIRECT [[Virtual Planet Builder]]

Virtual Planet Builder

2021-12-19T08:06:29Z

Vs: cleanup

{{Scenery Core Development}}

VirtualPlanetBuilder (VPB) is an OSG tool that generates native OSG data to represent terrain, usually by draping a GEO-TIFF over an elevation model.

== Building VirtualPlanetBuilder ==

The VPB project and code can be found here: https://github.com/openscenegraph/VirtualPlanetBuilder

There is now[https://sourceforge.net/p/flightgear/mailman/message/37385201/] a VPB {{Wikipedia|Docker_(software)|docker}} container for Linux: https://hub.docker.com/r/flightgear/ws30-vbp-generator and https://github.com/fdalvi/flightgear-ws30-vbp-generator

If you've got an existing FlightGear build, there are some additional dependencies:
* OSG
** Including NVTT. ('sudo apt-get install libnvtt-dev' - oddly VPB builds without it but then checks for the shared library at runtime...)
* GDAL (https://gdal.org/), Note that this needs to 2.4.X
** ... which requires PROJ 6 or above (https://proj.org/)
*** ... which requires the sqlite3.11 or above development package (on linux - 'sudo apt-get install libsqlite3-dev')

Note that GDAL and PROJ do not use cmake, so it builds in the source directory as follows:
./configure -prefix=/path/to/install
make

VPB is built using cmake e.g.

cmake -DOSG_DIR=/path/to/OSG/install /path/to/VPB/src
make

== Getting Landcover Data ==

For CORINE data covering Europe, try here: https://land.copernicus.eu/pan-european/corine-land-cover/clc2018

For US National Landcover Database (NLCD) try here: https://www.mrlc.gov/viewer/

Choose RASTER data, which will download a geo-referenced TIF image.

Note that the mapping from landcover to materials is performed in Materials/base/landclass-mapping.xml, and currently only maps CORINE landclasses.

== Getting DEM data. ==

The most commonly used Digital Elevation Model used is SRTM.

SRTM with 90m resolution is available here: http://srtm.csi.cgiar.org/

SRTM with 30m resolution is available here: https://lpdaac.usgs.gov/products/nasadem_hgtv001/ ''([https://e4ftl01.cr.usgs.gov/MEASURES/NASADEM_HGT.001/ Directory] , [https://search.earthdata.nasa.gov/search Interactive search] by selecting areas or points: [https://search.earthdata.nasa.gov/search/granules?p=C1546314043-LPDAAC_ECS&pg[0][v]=f&pg[0][gsk]=-start_date&q=NASADEM%20HGT&tl=1633679290.379!3!! example] . To download you need a free account from [https://urs.earthdata.nasa.gov/users/new here]'')

VPB accepts both raster and HGT files.

== LoD, Mesh size and Framerate ==

Unlike WS2.0 which has a fixed terrain mesh, VPB uses different terrain meshes with different level of detail (LoD) depending on the distance of the viewer from the particular piece of terrain.
[[File:Virtual Planet Builder LoD.png|thumb|Simplified diagram of different LoD tiles being loaded as an aircraft gets closer.]]
[[File:VPB Lod Filename scheme.png|thumb|Diagram showing how the Virtual Planet Builder filenames are built for each LoD level. Note that this just shows 3 LoD Levels. Our scenery goes to "L5".]]

Virtual Planet Builder provides a variety of settings that have a big impact on the eventual terrain mesh. The two main settings (the number of LoD levels, and the ratio of the LoD radius and maximum visible range), have a huge impact on the number of vertices, how the terrain looks, LoD "popping", and framerate.

To attempt to understand the relationship, a test was performed. WS30 terrain was generated for a 2x2 degree section of the European Alps bounded by (7E, 45N), and (8E, 47N), with settings as listed below. FlightGear was then run on a desktop with an NVidia GeForce GTX 1660 with 6GB of VRAM. The system appeared I/O limited as GPU utilization was around 30% and on 2GB of VRAM was used.

The following commandline options were used to place the ufo just to the NE of the Matterhorn, facing SW.
--aircraft=ufo --timeofday=morning --disable-real-weather-fetch --disable-ai-traffic --disable-random-objects --disable-random-vegetation --altitude=15000 --prop:/scenery/use-vpb=true --disable-sound --disable-ai-models --prop:/sim/rendering/texture-cache/cache-enabled=false --lat=46.021023 --lon=7.728291 --altitude=12662.75 --heading=226.0
{| class="wikitable"
|+
Experimental results varying LoD Level and visibility distance ratios
!Dem Resolution
!LoD Levels
!Radius to max visible distance ratio
!Lowest LoD Radius (km)
!Highest LoD Range (km)
!Lowest LoD Range (km)
!Vertices in view
!Triangles in view (M)
!Framerate (M)
!Frame Latency (ms)
!Terrain Size (MB)
|-
|90
|8
|7
|0.6
|1099
|4.3
|15
|30
|28
|40
|128
|-
|30
|8
|7
|0.6
|1099
|4.3
|32
|61
|19
|59
|425
|-
|30
|7
|5
|1.2
|785
|6.1
|5.6
|11
|75
|17
|170
|-
|30
|7
|3
|1.2
|475
|3.7
|3
|6
|105
|14
|170
|-
|30
|6
|5
|2.5
|785
|12
|4
|7
|115
|13 (a)
|80
|-
|30
|4
|5
|9.8
|785
|49
|3
|6
|125
|12 (b)
|25
|}
Notes:

(a) - Using these settings there was a noticeable reduction in apparent heightmap resolution with a 30m DEM, probably because the resolution of the lowest LoD level was ~40m, compared with 20m for an 7 LoD level mesh.

(b) Using these settings, the terrain resolution was unacceptably poor.

These results suggest that using 7 LoD Levels and a radius of "3" will provide a good balance, with high terrain quality and good frame-rate.

== Running VPB ==

FlightGear expects scenery in 1x1 degree tiles in a slightly different format to WS2.0. The scenery needs to be in a "vpb" directory, followed by a directory structure similar to WS20 (10x10, then 1x1 degree directories), with the final file being a 1x1 degree section with a "ws_" prefix, and in the ".osgb" format. E.g. vpb/w010n50/w004n50/ws_w004n50.osgb

Here are the options I've used to generate some scenery of the UK:

./bin/osgdem --TERRAIN \
--compressor-nvtt \
--compression-quality-highest \
--no-interpolate-imagery \
--disable-error-diffusion \
--geocentric \
-t /home/stuart/FlightGear/VPB/data/CORINE/u2018_clc2018_v2020_20u1_raster100m/DATA/U2018_CLC2018_V2020_20u1.tif \
-d /home/stuart/FlightGear/VPB/data/SRTM90/srtm_34_02.tif \
-d /home/stuart/FlightGear/VPB/data/SRTM90/srtm_35_01.tif \
-d /home/stuart/FlightGear/VPB/data/SRTM90/srtm_35_02.tif \
-d /home/stuart/FlightGear/VPB/data/SRTM90/srtm_36_01.tif \
-d /home/stuart/FlightGear/VPB/data/SRTM90/srtm_36_02.tif \
-b -4 50 -3 51 \
--PagedLOD \
-l 7 \
--radius-to-max-visible-distance-ratio 3 \
-o vpb/w010n50/w004n50/ws_w004n50.osgb

* --TERRAIN to use osgTerrain::Terrain database
* --compressor-nvtt --compression-quality-highest to generate native DDS mipmaps
* --geocentric because that's what FG uses
* -t the texture to drape (in this case CORINE)
* -d the DEM to use (in this case pieces of SRTM90)
* -b is the extents in decimal degrees: LON1 LAT1 LON2 LAT2, in this case from (-4,50) to (-3,51)
* --PagedLOD to generate PagedLOD nodes
* -l 4 the number of LOD levels to generate. At the equator, a 1x1 degree tile has a 157km diagonal. The LoD follows a quad-tree like structure, with each LOD level having 4 sub-tiles in a 2x2 array. If we want our smallest tile to have a ~10km diagonal, we need 4 LoD levels
* --radius-to-max-visible-distance-ratio is self-explanatory. We want the lowest level of LoD to be visible 20km away, so a ratio of 5 is appropriate.
* -o is the output file, in this case native OSG binary format. FG expects WS3.0 data in a vpb subdirectory, with the structure shown.

[[Category:Scenery software]]

Virtual Planet Builder

2021-12-19T08:06:05Z

Vs: Add link to VPB docker.

{{Scenery Core Development}}

VirtualPlanetBuilder (VPB) is an OSG tool that generates native OSG data to represent terrain, usually by draping a GEO-TIFF over an elevation model.

== Building VirtualPlanetBuilder ==

The VPB project and code can be found here: https://github.com/openscenegraph/VirtualPlanetBuilder

There is now a VPB {{Wikipedia|Docker_(software)|docker}} container for Linux: https://hub.docker.com/r/flightgear/ws30-vbp-generator and https://github.com/fdalvi/flightgear-ws30-vbp-generator

If you've got an existing FlightGear build, there are some additional dependencies:
* OSG
** Including NVTT. ('sudo apt-get install libnvtt-dev' - oddly VPB builds without it but then checks for the shared library at runtime...)
* GDAL (https://gdal.org/), Note that this needs to 2.4.X
** ... which requires PROJ 6 or above (https://proj.org/)
*** ... which requires the sqlite3.11 or above development package (on linux - 'sudo apt-get install libsqlite3-dev')

Note that GDAL and PROJ do not use cmake, so it builds in the source directory as follows:
./configure -prefix=/path/to/install
make

VPB is built using cmake e.g.

cmake -DOSG_DIR=/path/to/OSG/install /path/to/VPB/src
make

== Getting Landcover Data ==

For CORINE data covering Europe, try here: https://land.copernicus.eu/pan-european/corine-land-cover/clc2018

For US National Landcover Database (NLCD) try here: https://www.mrlc.gov/viewer/

Choose RASTER data, which will download a geo-referenced TIF image.

Note that the mapping from landcover to materials is performed in Materials/base/landclass-mapping.xml, and currently only maps CORINE landclasses.

== Getting DEM data. ==

The most commonly used Digital Elevation Model used is SRTM.

SRTM with 90m resolution is available here: http://srtm.csi.cgiar.org/

SRTM with 30m resolution is available here: https://lpdaac.usgs.gov/products/nasadem_hgtv001/ ''([https://e4ftl01.cr.usgs.gov/MEASURES/NASADEM_HGT.001/ Directory] , [https://search.earthdata.nasa.gov/search Interactive search] by selecting areas or points: [https://search.earthdata.nasa.gov/search/granules?p=C1546314043-LPDAAC_ECS&pg[0][v]=f&pg[0][gsk]=-start_date&q=NASADEM%20HGT&tl=1633679290.379!3!! example] . To download you need a free account from [https://urs.earthdata.nasa.gov/users/new here]'')

VPB accepts both raster and HGT files.

== LoD, Mesh size and Framerate ==

Unlike WS2.0 which has a fixed terrain mesh, VPB uses different terrain meshes with different level of detail (LoD) depending on the distance of the viewer from the particular piece of terrain.
[[File:Virtual Planet Builder LoD.png|thumb|Simplified diagram of different LoD tiles being loaded as an aircraft gets closer.]]
[[File:VPB Lod Filename scheme.png|thumb|Diagram showing how the Virtual Planet Builder filenames are built for each LoD level. Note that this just shows 3 LoD Levels. Our scenery goes to "L5".]]

Virtual Planet Builder provides a variety of settings that have a big impact on the eventual terrain mesh. The two main settings (the number of LoD levels, and the ratio of the LoD radius and maximum visible range), have a huge impact on the number of vertices, how the terrain looks, LoD "popping", and framerate.

To attempt to understand the relationship, a test was performed. WS30 terrain was generated for a 2x2 degree section of the European Alps bounded by (7E, 45N), and (8E, 47N), with settings as listed below. FlightGear was then run on a desktop with an NVidia GeForce GTX 1660 with 6GB of VRAM. The system appeared I/O limited as GPU utilization was around 30% and on 2GB of VRAM was used.

The following commandline options were used to place the ufo just to the NE of the Matterhorn, facing SW.
--aircraft=ufo --timeofday=morning --disable-real-weather-fetch --disable-ai-traffic --disable-random-objects --disable-random-vegetation --altitude=15000 --prop:/scenery/use-vpb=true --disable-sound --disable-ai-models --prop:/sim/rendering/texture-cache/cache-enabled=false --lat=46.021023 --lon=7.728291 --altitude=12662.75 --heading=226.0
{| class="wikitable"
|+
Experimental results varying LoD Level and visibility distance ratios
!Dem Resolution
!LoD Levels
!Radius to max visible distance ratio
!Lowest LoD Radius (km)
!Highest LoD Range (km)
!Lowest LoD Range (km)
!Vertices in view
!Triangles in view (M)
!Framerate (M)
!Frame Latency (ms)
!Terrain Size (MB)
|-
|90
|8
|7
|0.6
|1099
|4.3
|15
|30
|28
|40
|128
|-
|30
|8
|7
|0.6
|1099
|4.3
|32
|61
|19
|59
|425
|-
|30
|7
|5
|1.2
|785
|6.1
|5.6
|11
|75
|17
|170
|-
|30
|7
|3
|1.2
|475
|3.7
|3
|6
|105
|14
|170
|-
|30
|6
|5
|2.5
|785
|12
|4
|7
|115
|13 (a)
|80
|-
|30
|4
|5
|9.8
|785
|49
|3
|6
|125
|12 (b)
|25
|}
Notes:

(a) - Using these settings there was a noticeable reduction in apparent heightmap resolution with a 30m DEM, probably because the resolution of the lowest LoD level was ~40m, compared with 20m for an 7 LoD level mesh.

(b) Using these settings, the terrain resolution was unacceptably poor.

These results suggest that using 7 LoD Levels and a radius of "3" will provide a good balance, with high terrain quality and good frame-rate.

== Running VPB ==

FlightGear expects scenery in 1x1 degree tiles in a slightly different format to WS2.0. The scenery needs to be in a "vpb" directory, followed by a directory structure similar to WS20 (10x10, then 1x1 degree directories), with the final file being a 1x1 degree section with a "ws_" prefix, and in the ".osgb" format. E.g. vpb/w010n50/w004n50/ws_w004n50.osgb

Here are the options I've used to generate some scenery of the UK:

./bin/osgdem --TERRAIN \
--compressor-nvtt \
--compression-quality-highest \
--no-interpolate-imagery \
--disable-error-diffusion \
--geocentric \
-t /home/stuart/FlightGear/VPB/data/CORINE/u2018_clc2018_v2020_20u1_raster100m/DATA/U2018_CLC2018_V2020_20u1.tif \
-d /home/stuart/FlightGear/VPB/data/SRTM90/srtm_34_02.tif \
-d /home/stuart/FlightGear/VPB/data/SRTM90/srtm_35_01.tif \
-d /home/stuart/FlightGear/VPB/data/SRTM90/srtm_35_02.tif \
-d /home/stuart/FlightGear/VPB/data/SRTM90/srtm_36_01.tif \
-d /home/stuart/FlightGear/VPB/data/SRTM90/srtm_36_02.tif \
-b -4 50 -3 51 \
--PagedLOD \
-l 7 \
--radius-to-max-visible-distance-ratio 3 \
-o vpb/w010n50/w004n50/ws_w004n50.osgb

* --TERRAIN to use osgTerrain::Terrain database
* --compressor-nvtt --compression-quality-highest to generate native DDS mipmaps
* --geocentric because that's what FG uses
* -t the texture to drape (in this case CORINE)
* -d the DEM to use (in this case pieces of SRTM90)
* -b is the extents in decimal degrees: LON1 LAT1 LON2 LAT2, in this case from (-4,50) to (-3,51)
* --PagedLOD to generate PagedLOD nodes
* -l 4 the number of LOD levels to generate. At the equator, a 1x1 degree tile has a 157km diagonal. The LoD follows a quad-tree like structure, with each LOD level having 4 sub-tiles in a 2x2 array. If we want our smallest tile to have a ~10km diagonal, we need 4 LoD levels
* --radius-to-max-visible-distance-ratio is self-explanatory. We want the lowest level of LoD to be visible 20km away, so a ratio of 5 is appropriate.
* -o is the output file, in this case native OSG binary format. FG expects WS3.0 data in a vpb subdirectory, with the structure shown.

[[Category:Scenery software]]

File:SOTM 2021-01 Noon at mid winter (Saab 37 Viggen near ESPA in Sweden) by Johan G in FlightGear 2020.jpg

2021-12-18T13:58:46Z

Vs: add categories

=={{int:filedesc}}==
{{Information
|description={{en|1=SOTM 2021-01 Noon at mid winter (Saab 37 Viggen near ESPA in Sweden) by Johan G. FlightGear 2020.3 LTS}}
|date=2021-01-31
|source=FlightGear.org SOTM 2021-01
|author=X - see filename.
|permission=
|other versions=
}}

=={{int:license-header}}==
{{cc-by-sa-4.0}}

[[Category:Screenshot of the month/2021-01]]
[[Category:Saab 37 Viggen screenshots]]
[[Category:Screenshots of snow]]
[[Category:Screenshots at high settings]]
[[Category:Screenshots at high settings/2021]]
[[Category:Screenshots at high settings/sotm]]

File:Aircrane Over the Mojave 2.jpg

2021-12-18T13:30:35Z

Vs: Add categories

=={{int:filedesc}}==
{{Information
|description={{en|1=Aircrane over the Mojave Desert in the Palmdale/Landcaster area. Compositor shadows, OSM2CITY models, ALS lighting and Orthographics texture.}}
|date=2020-12-09 12:25:15
|source={{own}}
|author=[[User:Wlbragg|Wlbragg]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Compositor]]
[[Category:Orthographics]]
[[Category:Screenshot of the month/2020-12]]
[[Category:Sikorsky S-64 Skycrane screenshots]]

File:C182S Alps Sunset.jpg

2021-12-18T13:30:29Z

Vs: Add categories

=={{int:filedesc}}==
{{Information
|description={{en|1=C182S: Sunset at the Alps above Schliersee}}
|date=2020-12-03 23:57:21
|source={{own}}
|author=[[User:Hbeni|Hbeni]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Cessna 182S screenshots]]
[[Category:Screenshot of the month/2020-12]]

File:Searching.jpg

2021-12-18T13:30:21Z

Vs: Add categories

=={{int:filedesc}}==
{{Information
|description={{en|1=AirCrane using cluster shader lighting}}
|date=2021-01-11 11:53:38
|source={{own}}
|author=[[User:Wlbragg|Wlbragg]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Compositor screenshots]]
[[Category:Sikorsky S-64 Skycrane screenshots]]
[[Category:Screenshot of the month/2021-01]]
[[Category:Screenshots at high settings]]
[[Category:Screenshots at high settings/2021]]
[[Category:Screenshots at high settings/sotm]]
[[Category:Screenshots of weather]]

File:Fokker50 KLM.jpg

2021-12-18T13:30:12Z

Vs: Add categories

== Summary ==
{{File information
|Description = [[Fokker 50]] in KLM Cityhopper livery.
|Source ={{own}}
|Date =
|Author =[[User:Erik|Erik]]
}}

[[Category:Screenshots of aircraft]]
[[Category:Screenshot of the month/2021-02]]
[[Category:Screenshots at high settings]]
[[Category:Screenshots at high settings/2021]]
[[Category:Screenshots at high settings/sotm]]
[[Category:Fokker 50 screenshots]]

File:Madrid OSM2City.jpg

2021-12-18T13:30:03Z

Vs: Add categories

=={{int:filedesc}}==
{{Information
|description={{en|1=First [[OSM2City]] world-build scenery of Madrid, Spain.}}
|date=2021-04-18
|source={{forum link|p=384759|title=Submit your screenshot for the SOTM of April 2021}}
|author=vnts
|permission=
|other versions=
}}

=={{int:license-header}}==
{{cc-by-sa-4.0}}

[[Category:Screenshots of scenery in Madrid]]
[[Category:Screenshots of scenery with OSM2City output]]
[[Category:Screenshot of the month/2021-04]]
[[Category:Screenshots at high settings]]
[[Category:Screenshots at high settings/2021]]
[[Category:Screenshots at high settings/sotm]]
[[Category:Screenshots of weather]]

File:Slope soaring at Rhossilli.jpg

2021-12-18T13:29:55Z

Vs: Add categories

=={{int:filedesc}}==
{{Information
|description={{en|1=Slope soaring with EasyStar RC glider at Rhossilli U.K.}}
|date=2021-06-18
|source={{own}}
|author=[[User:Kwikius|Kwikius]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}
[[Category:Screenshot of the month/2021-06]]

File:Lufthansa Cargo Boeing 777 over the sea of mountains.jpg

2021-12-18T13:29:46Z

Vs: Add categories

=={{int:filedesc}}==
{{Information
|description={{en|1=Lufthansa Cargo [[Boeing 777]] (D-ALFG) over the sea of mountains.}}
|date=2021-07-20
|source={{forum url|p=389148}}
|author=lomar
|permission=
|other versions=
}}

=={{int:license-header}}==
{{cc-by-sa-4.0}}

[[Category:Boeing 777 screenshots]]
[[Category:Screenshot of the month/2021-07]]
[[Category:Screenshots at high settings]]
[[Category:Screenshots at high settings/2021]]
[[Category:Screenshots at high settings/sotm]]

File:SOTM 2021-08 Downtown (Bombardier Q400) by Delta5142.jpg

2021-12-18T13:29:40Z

Vs: Add categories

=={{int:filedesc}}==
{{Information
|description={{en|1=SOTM 2021-08 Downtown (Bombardier Q400) by Delta5142

Bombardier Q400 aka Dash 8}}
|date=2021-08-31
|source=FlightGear.org SOTM 2020-08, released under CC-BY-SA-4.0
|author=X - see filename.
|permission=
|other versions=
}}

=={{int:license-header}}==
{{cc-by-sa-4.0}}

[[Category:Screenshot of the month/2021-08]]
[[Category:Bombardier Q400 screenshots]]

File:SOTM 2021-01 Trans Atlantic Abort over Pyrenees (Space Shuttle) by GinGin.jpg

2021-12-18T13:29:27Z

Vs: add categories

=={{int:filedesc}}==
{{Information
|description={{en|1=SOTM 2021-01 Trans Atlantic Abort over Pyrenees (Space Shuttle) by GinGin}}
|date=2021-01-31
|source=FlightGear.org SOTM 2021-01
|author=X - see filename.
|permission=
|other versions=
}}

=={{int:license-header}}==
{{cc-by-sa-4.0}}

[[Category:Screenshot of the month/2021-01]]
[[Category:Space Shuttle screenshots]]
[[Category:Screenshots at high settings]]
[[Category:Screenshots at high settings/2021]]
[[Category:Screenshots at high settings/sotm]]
[[Category:Screenshots of snow]]

Category:Tupolev Tu-144D screenshots

2021-12-18T13:29:06Z

Vs: Create category

[[Tupolev Tu-144D]] screenshots.
[[Category:Aircraft screenshots by model]]
[[Category:Screenshots of airliners]]
[[Category:Tupolev aircraft screenshots]]

Category:Rolladen-Schneider LS8 screenshots

2021-12-18T13:29:00Z

Vs: Create category

[[Rolladen-Schneider LS8]] screenshots.

[[Category:Rolladen-Schneider aircraft]]
[[Category:Aircraft screenshots by model]]
[[Category:Screenshots of civil aircraft]]

Category:Piper J3 Cub screenshots

2021-12-18T13:28:54Z

Vs: Create category

[[Piper J3 Cub]] screenshots.

[[Category:Aircraft screenshots by model]]
[[Category:Screenshots of civil aircraft]]
[[Category:Piper Aircraft screenshots]]

Category:Piper PA-24 Comanche screenshots

2021-12-18T13:28:47Z

Vs: Create category.

[[Category:Aircraft screenshots by model]]
[[Category:Screenshots of civil aircraft]]
[[Category:Piper Aircraft screenshots]]

Category:Piper Aerostar 700 screenshots

2021-12-18T13:28:42Z

Vs: Create category

[[Piper Aerostar|Piper Aerostar 700]] screenshots.
[[Category:Aircraft screenshots by model]]
[[Category:Screenshots of civil aircraft by type]]
[[Category:Piper Aircraft screenshots]]

Category:Screenshots of snow

2021-12-18T13:28:28Z

Vs: Create category

Screenshots containing scenery with [[snow]] in FlightGear. See [[Weather]] for more information on how to simulate cold weather and winter.
[[Category:Weather]]
[[Category:Screenshots of ALS]]

File:SOTM 2021-10 V2 by The epic chicken.jpg

2021-12-18T13:27:43Z