Howto:Install scenery: Difference between revisions

Jump to navigation Jump to search

Howto:Install scenery (view source)

Revision as of 10:41, 11 July 2025

4,473 bytes removed ,  11 July
Major revision, update, cleanup
m (Add link for environment variable)
(Major revision, update, cleanup)
 
Line 1: Line 1:
{{installing}}
{{installing}}
   
   
[[File:SOTM-Sept17.jpg|thumb|Hawaii scenery - "weeping wall" waterfalls at Mount Waialeale on the island of Kauai, near PHLI]]
A default installation of [[FlightGear]] comes with a limited set of [[scenery]] to keep initial download sizes small. It includes the region around the featured airport for each release (Iceland since FlightGear 2020.1), and the area containing the airport used by the [[Cessna 172P]] tutorials (Hawaii, including PHTO). When [[TerraSync]] is enabled (by default as of FlightGear 2024.1.2), additional scenery is automatically downloaded, installed and updated for whichever location around the globe a user visits.  
[[File:SOTM_2019-06_Ice_and_fire_by_vnts.jpg|thumb|Sicily scenery - the [[volcanos|volcano]] Etna snowcapped in winter with a low level eruption, near LICC]]
[[File:Bell_412_in_Iceland_(Flightgear_2019.x).jpg|thumb|Iceland scenery - having [[:Category:Screenshots_of_overlays|overlays]] enabled shows extremely high 3d detail like small rocks, plants, or individual grass blades]]
[[File:SOTM-Mar19.jpg|thumb|Madrid scenery with [[Areas_populated_with_osm2city_scenery|OSM2City output]] for Spain]]


The normal way scenery is installed is that FlightGear will ''automatically'' download scenery as you fly. [[TerraSync]] has to be enabled first - [https://www.youtube.com/watch?v=GbiHMxXr_Mk video tutorial]. You don't have to do anything else.
This article explains '''how to manually install scenery''' for people with limited internet access, and how to install [[Howto:Install scenery#Custom scenery|custom sceneries]] that are not available through TerraSync. If you locate yourself at an airport and see nothing but water, you probably did not install that scenery area (correctly).


This article explains how to manually install scenery for people with limited internet access, and how to install [[Howto:Install scenery#Custom scenery|custom sceneries]] for improvements which have not been added to TerraSync yet.
== Scenery types ==
There are four scenery types, in increasing level of detail:


FlightGear comes with a limited set of [[scenery]] in the base package. This is to keep initial download sizes small. The base package includes the region around the featured airport for each release (which is Iceland for Flightgear 2020.x), and the area containing the airport used by the C172p tutorials (PHTO and Hawaii islands). Additional scenery can be installed by the user - this includes scenery automatically downloaded as you fly from Terrasync servers.
; World scenery 2
 
: Reasonable level of detail global scenery, with objects such as landmarks and airport buildings. Has not been updated since 2013.
If you locate yourself at an airport and see nothing but water, you probably did not install that scenery area (correctly).
 
For examples of what scenery looks like at high-ish settings in developed regions see the [[:Category:Screenshots_at_high_settings|high settings screenshots]] category. This is a useful way to check you have enabled or turned up all the scenery features, and a useful a way to check you are using the all the features of the weather & environment simulation - the [[Howto:Make_nice_screenshots|article on screenshots]] also covers turning on various settings.
{{TOC limit|3}}
{|
|[[File:Austria_in_Autumn_in_FlightGear_2019_01.jpg|thumb|800px|left|Panorama of Innisbruck airport (LOWI) in Autumn with a [[FlightGear_Newsletter_February_2015#ALS_Volumetric_Grass|2nd]] type of grass enabled. Click to view full size.]]
|}
== Types of scenery ==
There are basically three types of scenery (in order of detail):
 
; World scenery 2.1
: Reasonable level of detail scenery spanning the world and scenery objects, such as for example landmarks and airport buildings.
; TerraSync scenery
; TerraSync scenery
: Basically the same as the world scenery 2.1. In addition it also contains the latest scenery objects added by fellow FlightGear users to the [[Scenery Objects Database|scenery objects database]].
: World scenery 2 terrain with constantly updated scenery objects added by fellow FlightGear users to the [[Scenery Objects Database|scenery objects database]], and worldwide [[OSM2City 1st Worldbuild|OpenStreetMap-based buildings]]. Most of the terrain and airport layouts have not been updated since 2013.
; [[World Scenery 3.0|World scenery 3]]
: Experimental scenery with updated terrain, airports and objects.
; Custom scenery
; Custom scenery
: Non-official scenery covering all the way from small areas to very large areas, often with a high level of detail.
: Non-official scenery covering all the way from small areas to very large areas, often with a high level of detail and up-to-date terrain and airports.


The default scenery is two 1 by 1 degree tiles surrounding the San Francisco Bay area from the World scenery.
<gallery  mode="packed">
File:SOTM-Sept17.jpg|Hawaii scenery - "weeping wall" waterfalls at Mount Waialeale on the island of Kauai, near PHLI
File:SOTM_2019-06_Ice_and_fire_by_vnts.jpg|Sicily scenery - the [[volcanos|volcano]] Etna snowcapped in winter with a low level eruption, near LICC
File:Bell_412_in_Iceland_(Flightgear_2019.x).jpg|Iceland scenery - having [[:Category:Screenshots_of_overlays|overlays]] enabled shows extremely high 3d detail like small rocks, plants, or individual grass blades
File:SOTM-Mar19.jpg|Madrid scenery with [[Areas_populated_with_osm2city_scenery|OSM2City output]] for Spain
</gallery>


== Obtaining scenery ==
=== World scenery 2 ===


{{caution|'''Do not mix scenery''' types in the '''same directory'''.  It may cause problems like custom scenery being overwritten by the TerraSync or TerraMaster utilities, TerraMaster getting locked etc.}}
== Obtaining scenery ==
=== World scenery ===
[[File:Worldscenery-text.jpg|thumb|World scenery tiles]]
[[File:Worldscenery-text.jpg|thumb|World scenery tiles]]


You can download the official [[World Scenery]] terrain from the [http://www.flightgear.org/Download/scenery FlightGear website].
World scenery 2 is available in tiles of 1 by 1 degree. To find an airport's coordinates and corresponding tile:


There is also a 4 DVD set available for download via [http://www.torrentbox.com/download/59050/FlightGear_4_DVD_Disk-set.torrent BitTorrent] - NOTE THIS LINK IS BAD, which can be a higher performance option for those wanting to download the entire world. And, last but not least, it can be purchased as 3 DVD set from the [http://www.flightgear.org/dvd/ official FlightGear website].
# Go to the Wikipedia page for the airport in question (e.g., {{wikipedia|Honolulu International Airport}}, PHNL).
# Find the co-ordinates (often at the top or right and side, marked with a small globe). For PHNL these are 21 N 157 W.
# Round the coordinates to their nearest multiple of 10. Round up for Southern and Western hemisphere coordinates, and round down for Northern and Eastern coordinates, as illustrated by the image. PHNL yields w160n20, while 21 N 157 E would yield e150n20. clarifies this rule.


==== Downloading from mirrors ====
Scenery tiles can be downloaded from [https://www.flightgear.org/download/mirror/ these mirrors]. On most of them the latest scenery can be found under <tt>/Scenery-v2.12</tt>.
A list of mirrors can be found [https://www.flightgear.org/download/mirror/ here].


On most of the mirrors, the latest scenery can be found under <tt>Scenery-2.12.0/</tt>. Downloading from mirrors is often better than the official site, because mirrors are sometimes faster and have more user capacity. Use the [http://www.flightgear.org/Downloads/scenery graphical interface] to find the appropriate chunk. Be careful about confusing N with S, and E with W!!
=== TerraSync scenery ===
Here is how to find an airport's co-ordinates:
{{Main article|TerraSync}}


#Go to the Wikipedia page for the airport in question (for example, PHNL for Honolulu)
The [[TerraSync]] scenery is automatically downloaded and synchronized as needed while FlightGear is running when the built in TerraSync utility is enabled. As an alternative, especially suited for users with limited internet speeds, scenery can be prefetched before starting a flight via the [[TerraMaster]] tool.
#Find the co-ordinates (often at the top or right and side, marked with a small globe)
#*e.g. PHNL is in 21 N 157 W. If it's in the western hemisphere, you should round it up... so you should find the block with W160N20 If the co-ords were 21 N 157 E, you would round it '''down'''.. meaning that this location would be E150N20.


====Downloading with BitTorrent====
==== Downloading with TerraMaster ====
There is a torrent file hosted on http://www.terasaur.org which you can [http://terasaur.org/torrent/download/ae22ec86209fb14cb143a968be5ba8d3bebd7d6f/Scenery-v2.10.torrent find here]. There is also an alternative torrent (only added a new announcement URL) with a strong seed [http://flightgear.mxchange.org:23456/file?info_hash=%AE%22%EC%86%20%9F%B1L%B1C%A9h%BE%5B%A8%D3%BE%BD%7Do available].


===TerraSync scenery===
{{Main article|TerraMaster}}
The [[TerraSync]] scenery is automatically downloaded and synchronized as needed while FlightGear is running when the built in TerraSync utility is enabled.


====TerraSync on low end machines====
[[File:TerraMaster r32 - Global view.png|thumb|TerraSync scenery in TerraMaster]]
When downloading and synchronizing tiles on lower end machines or when having an unstable or slow Internet connection, TerraSync might cause stuttering and/or slow down FlightGear.  If you encounter that there are a few ways around it:


*Simply disable TerraSync and use the World scenery instead
TerraMaster is a stand alone scenery manager that can download and synchronize TerraSync scenery.  It also makes it easier to maintain and get a good overview of downloaded TerraSync scenery. It is a cross platform graphical application written in Java.
*Start FlightGear and sit around "in the sea" while TerraSync downloads or synchronizes scenery and then disable it and restart FlightGear
*Use TerraMaster to download and synchronize the scenery


====Downloading with TerraMaster====
TerraMaster allows the FlightGear user to manage scenery tiles easily, selecting which tiles to download, synchronize or delete, and viewing the downloaded/not yet downloaded tiles at a glance. TerraMaster is highly recommended not only for managing scenery tiles easily especially if you are downloading and managing scenery from a computer that does not have FlightGear installed. The downloaded tiles are put into a folder which can then be loaded by FlightGear.
[[File:TerraMaster r32 - Global view.png|thumb|TerraSync scenery in TerraMaster]]


[[TerraMaster]] is a stand alone scenery manager that can download and synchronize TerraSync scenery.  It also makes it easier to maintain and get a good overview of downloaded TerraSync scenery. It is a cross platform graphical application written in Java.
=== World scenery 3 ===
{{Main article|World Scenery 3.0}}


TerraMaster allows the FlightGear user to manage scenery tiles easily, selecting which tiles to download, synchronize or delete, and viewing the downloaded/not yet downloaded tiles at a glance. TerraMaster is highly recommended not only for managing scenery tiles easily especially if you are downloading and managing scenery from a computer that does not have FlightGear installed. The downloaded tiles are put into a folder which can then be copied into the FlightGear directory later on to complete the scenery.  It can also download tiles directly into the TerraSync directory.
=== Custom scenery ===


===Custom scenery===
[[File:Asia.jpg|thumb|[[Earthview]] orbital renderer at high sun - with high resolution texture packs installed.]]
[[File:SOTM_2019-04_Space_Sauna_by_GinGin.jpg|thumb|[[Earthview]] orbital renderer at low sun showing light from cities. The [[Space_Shuttle|Space Shuttle]] shows the glow from the heat of hypersonic re-entry.]]
Custom scenery is available for certain specific areas. They are distributed separately either due to being only part of a single landmass that has not been re-built completely, being work-in-progress, waiting to be integrated to Terrasync, their license, or because their level of detail is not suitable for low-end machines.
Custom scenery is available for certain specific areas. They are distributed separately either due to being only part of a single landmass that has not been re-built completely, being work-in-progress, waiting to be integrated to Terrasync, their license, or because their level of detail is not suitable for low-end machines.


See
* [[Suggested Airports/Scenery]] for a list of custom scenery projects and an update on state of well developed areas.
*[[Suggested Airports/Scenery]] for a list of custom scenery projects and an update on state of well developed areas.
* [[Project3000#Download_the_software_and_shared_models|Project 3000]] for buildings and objects for 4000+ airports.
*[[Project3000#Download_the_software_and_shared_models|Project 3000]] for buildings and objects for 4000+ airports.
* [[Earthview#Installing_and_using_customized_textures|Earthview high resolution]] texture packs. Earthview is Flightgear's orbital renderer capable of handling large view distances without numerical problems. People using high altitude and space craft should select the texture pack that their GPU can handle - [[Earthview#Requirements|depends]] mainly on GPU memory (VRAM).
*[[Earthview#Installing_and_using_customized_textures|Earthview high resolution]] texture packs. Earthview is Flightgear's orbital renderer capable of handling large view distances without numerical problems. People using high altitude and space craft should select the texture pack that their GPU can handle - [[Earthview#Requirements|depends]] mainly on GPU memory (VRAM).
*[[Areas_populated_with_osm2city_scenery|Areas with OSM2City scenery]] for buildings, roads, power-lines, and objects for regions and entire countries based on Open Street Maps data. ''Note: As of FlightGear 2020.3.7 LTS and later OSM2City objects for the [[OSM2City 1st Worldbuild|entire world]] are automatically downloaded through TarraSync.'' ''OSM2City objects in old custom sceneries are very likely obsolete - see [[OSM2City 1st Worldbuild#Troubleshooting|troubleshooting]] OSM2City on how to deal with this. You should only download OSM2City custom sceneries if they have some options not enabled in the current rollout of TerraSync OSM2City scenery - like auto-generation of areas without Open Street Map coverage.'' (April 2021).


(August 2020)
<gallery  mode="packed">
File:Asia.jpg|[[Earthview]] orbital renderer at high sun - with high resolution texture packs installed.
File:SOTM_2019-04_Space_Sauna_by_GinGin.jpg|Earthview orbital renderer at low sun showing light from cities. The [[Space_Shuttle|Space Shuttle]] shows the glow from the heat of hypersonic re-entry.
</gallery>


==Installing World and custom scenery==
== Installing world and custom scenery ==
Install scenery outside the <code>[[$FG_ROOT]]</code> directory.  See [[#Technical details]] below for an explanation.


===Installing via a graphical interface===
Always install scenery outside the <code>[[$FG_ROOT]]</code> directory. See [[#Technical details]] below for an explanation.
{{Obsolete}}{{Incomplete|section}}
#Open the [[FlightGear Admin Wizard]]. On Windows, you can start it by clicking on Start -> All Programs -> FlightGear -> Tools -> FlightGear Admin Wizard.
#Click on ''Select Scenery Source...'' to select the directory containing the scenery .tgz files.
#Click on ''Select Install Destination...'' to select the directory where you want to install the scenery.
#*On Windows, it should be a directory you can read from/write to. If you use FlightGear 3.2 and above, the default path (<code>C:\Users\''your user name''\Documents\FlightGear\Custom Scenery</code>) is perfectly fine.
#*On Macintosh systems, the path should be <code>/Applications/FlightGear.app/Contents/Resources/data/Scenery</code>.
#In the left pane, check the scenery tiles you want to install and click on ''Install Selected Files'' to install the scenery.


===Alternate installation, GNU/Linux===
{{caution|'''Do not mix scenery''' types in the '''same directory'''. It may cause problems like custom scenery being overwritten by the TerraSync or TerraMaster utilities, TerraMaster getting locked etc.}}
 
=== GNU/Linux ===
If you are under a Linux operation system and you are not using a graphical interface to extract the tar archive, you can use one of the two following set of commands in a shell terminal.
If you are under a Linux operation system and you are not using a graphical interface to extract the tar archive, you can use one of the two following set of commands in a shell terminal.


<syntaxhighlight lang="shell">
  cd SceneryDirectory
  cd SceneryDirectory
  tar -xvzf input_file.tgz
  tar -xvzf input_file.tgz
</syntaxhighlight>


or
or


<syntaxhighlight lang="shell">
  tar -xvzf 'input_file.tgz' -C SceneryDirectory
  tar -xvzf 'input_file.tgz' -C SceneryDirectory
</syntaxhighlight>


<code>input_file.tgz</code> should be substituted with the filename of the archive to be extracted (the filename should be completed with the full pathname or any other valid method so that the shell could find the correct archive).
<code>input_file.tgz</code> should be substituted with the filename of the archive to be extracted (the filename should be completed with the full pathname or any other valid method so that the shell could find the correct archive).


===Alternate installation, Windows===
=== Windows ===
Simply unpack the downloaded scenery into a directory of choice, using software like [http://www.winzip.com/ Winzip] or [http://www.7-zip.org 7-zip]. Once done, append this directory to <code>[[$FG_SCENERY]]</code>. When using the [[FlightGear Wizard]], you can do so on the first page (previous from aircraft selection). Do not forget to press the "Refresh" button on the airport selection page, when using the wizard.


{{note|More recent Windows versions (e.g. XP, Vista, Win7) tinkering a lot with user rights on access level. Therefore it is a bad idea to install and run FlightGear (scenery) to and from <code>C:\Program Files</code>. Find another drive/folder where you, as logged in user, have all neccesary right to read, write and execute the files you installed. Additionally there's a space / blank in folder's name which could cause weird behaviour. Using <code>C:\FlightGear</code> is a nice option.}}
Simply unpack the downloaded scenery into a directory of choice, using software like [http://www.winzip.com/ Winzip] or [http://www.7-zip.org 7-zip]. Once done, append this directory to <code>[[$FG_SCENERY]]</code> (in the launcher, this can be done under Add-ons > Additional scenery folders).


===Alternate installation, Macintosh===
=== macOS ===
Unpack the .tgz file either by double-clicking it and moving the resulting <code>wXXXnXXX</code> folder to the Scenery folder described in the next line, or on the command line:


Unpack the .tgz file either by double-clicking it and moving the resulting <code>wXXXnXX</code> folder to the Scenery folder described in the next line, or on the command line:
<syntaxhighlight lang="shell">
  tar -xvzf 'input_file.tgz' -C /Applications/FlightGear.app/Contents/Resources/data/Scenery
  tar -xvzf 'input_file.tgz' -C /Applications/FlightGear.app/Contents/Resources/data/Scenery
</syntaxhighlight>


==Technical details==
== Technical details ==
===Scenery lookup and $FG_SCENERY===
=== Scenery lookup and $FG_SCENERY ===
FlightGear determines what scenery to use by looking at the [[Environment variables|environment variable]] (setting)<code>[[$FG SCENERY]]</code>. There can be more than one scenery path in the variable, for example one path to to TerraSync scenery and one path to custom scenery. Scenery can be overlapping and a tile will be loaded from the first path in <code>$FG SCENERY</code> from which it is available.
 
FlightGear determines what scenery to use by looking at the [[Environment variables|environment variable]] (setting) <code>[[$FG SCENERY]]</code>. There can be more than one scenery path in the variable, for example one path to to TerraSync scenery and one path to custom scenery. Scenery can be overlapping and a tile will be loaded from the first path in <code>$FG SCENERY</code> from which it is available.


Should the paths in <code>$FG_SCENERY</code> not be valid, FlightGear falls back to <code>[[$FG ROOT]]/Scenery</code>.
Should the paths in <code>$FG_SCENERY</code> not be valid, FlightGear falls back to <code>[[$FG ROOT]]/Scenery</code>.


===Directories and configuring $FG_SCENERY===
=== Directories and configuring $FG_SCENERY ===
Mixing scenery types is almost universally a bad idea, and is unsupported. You should also note that the scenery packaged with the base package/windows installer may not be the latest scenery.


For this reason it is probably better to extract scenery files you have downloaded into a new folder, which we for the sake of this exercise will call <code>$FOOBAR/Scenery</code>.
Mixing scenery types is almost universally a bad idea, and is unsupported. Also note that the scenery packaged with the base package/windows installer may not be the latest scenery.
 
For this reason it is better to extract downloaded scenery files into a new folder, which we for the sake of this exercise will call <code>$FOOBAR/Scenery</code>.
In this directory, create two subdirectories: <code>/Objects</code> and <code>/Terrain</code>. You should untar individual files into the <code>/Terrain</code> folder.
In this directory, create two subdirectories: <code>/Objects</code> and <code>/Terrain</code>. You should untar individual files into the <code>/Terrain</code> folder.


Then you should set up $FG_SCENERY to use the new path:
Then you should set up $FG_SCENERY to use the new path:
*On POSIX Clients
*:<code>set FG_SCENERY="$FOOBAR/Scenery" + FG_SCENERY</code>
*On Windows ([[FGRun]])
*:Go back to the first page of fgrun, and add the <code>$FOOBAR/Scenery</code> folder to the list.
*Via a command line option
*:<code>--fg-scenery="$FOOBAR/Scenery"</code>


===Directory structure===
* In the [[Qt launcher]]:
====Terrain====
*: Add the $FOOBAR/Scenery folder to Add-ons > Additional scenery folders.
* On POSIX Clients
*: <code>set FG_SCENERY="$FOOBAR/Scenery" + FG_SCENERY</code>
* Via a command line option
*: <code>--fg-scenery="$FOOBAR/Scenery"</code>
 
=== Directory structure ===
==== Terrain ====
 
The Scenery directory will show the following (scenery is shown for completeness and for easy reference to above):
The Scenery directory will show the following (scenery is shown for completeness and for easy reference to above):


*Scenery/
<tt>
**Terrain/
* Scenery/
***w130n30/
** Terrain/
**Objects/
*** w130n30/
***w130n30/
** Objects/
*** w130n30/</tt>


If you download a scenery module called <code>w90n40.tgz</code> from [http://flightgear.org/Downloads/scenery-1.0.1.html flightgear.org] and extract it in <code>Scenery</code>, the result will resemble something like the following:
If you download a scenery module called <code>w90n40.tgz</code> and extract it in <code>Scenery</code>, the result will resemble something like the following:


*Scenery/
<tt>
**Terrain/
* Scenery/
***w09n40/
** Terrain/
***w130n30/
*** w09n40/
**Objects/
*** w130n30/
***w09n40/
** Objects/
***w130n30/
*** w09n40/
*** w130n30/</tt>


Note that the directory structure is already present in the tar archive, starting from the Scenery directory. Note that you have to extract the tar archive in the Scenery directory, not in the <code>$FG_ROOT</code> directory, because the Scenery directory is not present in the archive.
Note that the directory structure is already present in the tar archive, starting from the Scenery directory. Note that you have to extract the tar archive in the Scenery directory, not in the <code>$FG_ROOT</code> directory, because the Scenery directory is not present in the archive.


====Objects====
==== Objects ====
 
Objects and models can be found at the [[FlightGear Scenery Object Database]].
Objects and models can be found at the [[FlightGear Scenery Object Database]].


Line 173: Line 160:
Objects are really part of the scenery and can be found in the <code>Scenery</code> directory under <code>$FG ROOT</code>.
Objects are really part of the scenery and can be found in the <code>Scenery</code> directory under <code>$FG ROOT</code>.


*Scenery/
<tt>
**Objects/
* Scenery/
***w130n30/
** Objects/
*** w130n30/</tt>


Any objects should be installed under the <code>Scenery/Objects</code> directory.
Any objects should be installed under the <code>Scenery/Objects</code> directory.


====Models====
==== Models ====
 
Replaces the former <code>$FG_ROOT/Models</code>; stores all the shared objects.
Replaces the former <code>$FG_ROOT/Models</code>; stores all the shared objects.


*Scenery/
<tt>
**Models/
* Scenery/
***Airport/
** Models/
*** Airport/</tt>
 
==== Airports ====


====Airports====
{{Main article|About Scenery/Airports}}
{{Main article|About Scenery/Airports}}
As of FlightGear 2.4.0, this directory is used to extract airport data (like runway usage and parking spots) from.
As of FlightGear 2.4.0, this directory is used to extract airport data (like runway usage and parking spots) from.


The directory tree might look somewhat overwhelming, but it simply follows the <code>Airports/[I]/[C]/[A]/</code> style.
The directory tree might look somewhat overwhelming, but it simply follows the <code>Airports/[I]/[C]/[A]/</code> style.
*Scenery/
<tt>
**Airports/
* Scenery/
***K/
** Airports/
****S/
*** K/
*****F/
**** S/
==Video tutorials on youtube (2020.x)==
***** F/
</tt>
 
== Video tutorials (2020.x) ==
 
{{#ev:youtube|TNN_AZhaHPU|480px||Scenery installation for Flightgear 2020.x by Parnikkapore. Note this is recorded on a non-gaming laptop, and certain settings are not turned up very high.}}
{{#ev:youtube|TNN_AZhaHPU|480px||Scenery installation for Flightgear 2020.x by Parnikkapore. Note this is recorded on a non-gaming laptop, and certain settings are not turned up very high.}}
{{#ev:youtube|YxWV4wk_dHw|480px||Terramaster tutorial for Flightgear by FGUK - 2017 but still valid in 2020.}}  
{{#ev:youtube|YxWV4wk_dHw|480px||Terramaster tutorial for Flightgear by FGUK - 2017 but still valid in 2020.}}  
==Related content==
 
*[[Scenery FAQ]]
== Related content ==
 
* [[Scenery FAQ]]


[[Category:Scenery]]
[[Category:Scenery]]
Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/142089"

Navigation menu