Difference between revisions of "Howto:Install scenery"

From FlightGear wiki
Jump to: navigation, search
m (Airports directory is being used upon request)
(Add custom scenery entry for Earthview high res textures, Earthview screenshots, cleanup)
 
(48 intermediate revisions by 25 users not shown)
Line 1: Line 1:
 
{{installing}}
 
{{installing}}
==Obtaining scenery==
+
You can download the official [[World Scenery]] terrain from the [http://www.flightgear.org/Downloads/scenery-1.0.1.html FlightGear website]. Alternatively, custom scenery is available for certain specific areas. They are distributed separately due to 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.
+
[[File:SOTM-Sept17.jpg|thumb|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|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]]
  
There is also a 4 DVD set available for download via [http://www.torrentbox.com/download/59050/FlightGear_4_DVD_Disk-set.torrent BitTorent], 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].
+
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.
  
===TerraSync===
+
If you locate yourself at an airport and see nothing but water, you probably did not install that scenery area (correctly).
[[TerraSync]] is a very useful utility that automatically downloads and installs needed FlightGear scenery and keeps it up to date while the simulator is running.  
+
  
===Downloading from mirrors===
+
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
 +
: 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]].
 +
; Custom scenery
 +
: Non-official scenery covering all the way from small areas to very large areas, often with a high level of detail.
 +
 
 +
The default scenery is two 1 by 1 degree tiles surrounding the San Francisco Bay area from the World scenery.
 +
 
 +
 
 +
 
 +
 
 +
 
 +
{{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]]
 +
 
 +
You can download the official [[World Scenery]] terrain from the [http://www.flightgear.org/Download/scenery FlightGear website].
 +
 
 +
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].
 +
 
 +
==== Downloading from mirrors ====
 
A list of mirrors can be found [http://www.flightgear.org/mirrors.html#ftp here].
 
A list of mirrors can be found [http://www.flightgear.org/mirrors.html#ftp here].
  
On most of the mirrors, the latest scenery can be found under <tt>Scenery-2.0.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-1.0.0.html graphical interface] to find the appropriate chunk. Be careful about confusing N with S, and E with W!!
+
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!!
 
Here is how to find an airport's co-ordinates:
 
Here is how to find an airport's co-ordinates:
  
Line 18: Line 51:
 
#* 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.
 
#* 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.
  
==Installing scenery==
+
==== Downloading with BitTorrent ====
You can optionally use a GUI installer, called [[FlightGear Admin Wizard|FGAdmin]], to (un)install scenery.
+
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].
  
=== GNU/Linux ===
+
=== TerraSync scenery ===
 +
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 ====
 +
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
 +
* 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 ====
 +
[[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.
 +
 
 +
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 ===
 +
[[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.
 +
 
 +
See
 +
* [[Suggested Airports/Scenery]] for a list of custom scenery projects and an update on state of well developed areas.
 +
* [[Areas_populated_with_osm2city_scenery|Areas populated with OSM2City scenery]] for buildings, roads, power-lines, and objects for regions and entire countries based on Open Street Maps data. There is an [[Osm2city_worldbuild|OSM2City build for the entire world]] in progress with most areas already completed (July 2020).
 +
* [[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).
 +
 
 +
(August 2020)
 +
 
 +
== 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 ===
 +
# 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 ===
 
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.
  
  cd [[$FG_ROOT]]/Scenery
+
  cd SceneryDirectory
 
  tar -xvzf input_file.tgz
 
  tar -xvzf input_file.tgz
  
 
or
 
or
  
  tar -xvzf 'input_file.tgz' -C [[$FG_ROOT]]/Scenery
+
  tar -xvzf 'input_file.tgz' -C SceneryDirectory
  
In the above two examples it is supposed that the variable [[$FG_ROOT]] is set to the root of the data directory. If this is not set, you should substitute in the above examples the $FG_ROOT with the full pathname of this directory. In the above examples 'input_file.tgz' 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).
  
=== Windows ===
+
=== Alternate installation, Windows ===
Simply unpack the downloaded scenery into your <tt>[[$FG_ROOT]]/Scenery</tt> directory, using software like [http://www.winzip.com/ Winzip] or [http://www.7-zip.org 7-zip]. Do not forget to press the "Refresh" (German: "Neu Laden") button on the airport selection page, when using the [[FlightGear Wizard]].<br>
+
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.
'''!!! IMPORTANT !!!'''<br>
+
"Modern" Windows Versions (e.g. XP, Vista, Win7) tinkering a lot with user rights on access level. Therefore it's a bad idea to install and run FlightGear to and from "C:\Program Files" (German: C:\Programme). 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. Use something like "C:\FlightGear".
+
  
==Technical==
+
{{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.}}
Scenery for FlightGear is determined by looking at the environment variable [[$FG_SCENERY]]. Should the paths in $FG_SCENERY not be valid, FlightGear falls back to <tt>[[$FG_ROOT]]/scenery</tt>.
+
  
Mixing scenery types is almost universally a bad idea, and is unsupported. In this connection you should note that the scenery packaged with the base package/windows installer may not be the latest scenery.
+
=== Alternate installation, Macintosh ===
 +
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:
  
For this reason it's probably better to extract scenery files you've downloaded into a new folder, which we'll call, for the sake of this exercise, <tt>$FOOBAR/Scenery</tt>.
+
tar -xvzf 'input_file.tgz' -C /Applications/FlightGear.app/Contents/Resources/data/Scenery
In this directory, create two subdirectories: /Objects and /Terrain. You should untar individual files into the /Terrain folder.
+
 
 +
== Technical details ==
 +
=== Scenery lookup and $FG_SCENERY ===
 +
FlightGear determines what scenery to use by looking at the environment variable <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>.
 +
 
 +
=== 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>.
 +
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<br>set FG_SCENERY="$FOOBAR/Scenery" + FG_SCENERY
+
* On POSIX Clients
*On Windows (FGRun)<br>Go back to the first page of fgrun, and add the $FOOBAR/Scenery folder to the list.
+
*: <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>
  
=== Terrain ===
+
=== 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):
  
<tt>
+
* Scenery/
*Scenery/
+
** Terrain/
**Terrain/
+
*** w130n30/
***w130n30/
+
** Objects/
**Objects/
+
*** w130n30/
***w130n30/
+
</tt>
+
  
If you download a scenery module called w90n40.tgz from [http://flightgear.org/Downloads/scenery-1.0.1.html flightgear.org] and extract it in Scenery, the result will resemble something like the following:
+
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:
  
<tt>
+
* Scenery/
*Scenery/
+
** Terrain/
**Terrain/
+
*** w09n40/
***w09n40/
+
*** w130n30/
***w130n30/
+
** Objects/
**Objects/
+
*** w09n40/
***w09n40/
+
*** w130n30/
***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 FG_ROOT 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 [http://scenemodels.flightgear.org/ FlightGear Scenery Objects Database].
+
Objects and models can be found at the [[FlightGear Scenery Object Database]].
  
These objects are included in each scenery release, but as the object database is more frequently updated than the terrain, one may want to occasionally update the Object subdirectory from the FlightGear Scenery Objects Database between scenery releases.
+
These objects are included in each scenery release, but as the object database is more frequently updated than the terrain, one may want to occasionally update the <code>Object</code> subdirectory from the scenery objects database between scenery releases.
Another option is to download or update the scenery on-demand by using the terrasync program described below.
+
  
Objects are really part of the scenery and can be found in the Scenery directory under [[$FG_ROOT]].
+
Another option is to download or update the scenery on-demand by using the built in TerraSync utility described above.
  
<tt>
+
Objects are really part of the scenery and can be found in the <code>Scenery</code> directory under <code>$FG ROOT</code>.
*Scenery/
+
**Objects/
+
***w130n30/
+
</tt>
+
  
Any objects should be installed under the <tt>Scenery/Objects</tt> directory.
+
* Scenery/
 +
** Objects/
 +
*** w130n30/
  
=== Airports ===
+
Any objects should be installed under the <code>Scenery/Objects</code> directory.
<s>Currently FlightGear does not use</s> this directory<s>. However, in upcoming releases, it will be</s> is being used to extract airport data (like runway usage and parking spots) from.
+
  
: See also: [[Howto:_Animated_jetways#Usage]]
+
==== Models ====
 +
Replaces the former <code>$FG_ROOT/Models</code>; stores all the shared objects.
  
The directory tree might look somewhat overwhelming, it simply follows the <tt>Aiports/[I]/[C]/[A]/</tt> code (see [[ICAO-code]]).
+
* Scenery/
 +
** Models/
 +
*** Airport/
  
<tt>
+
==== Airports ====
*Scenery/
+
{{Main article|About Scenery/Airports}}
**Airports/
+
As of FlightGear 2.4.0, this directory is used to extract airport data (like runway usage and parking spots) from.
***K/
+
****S/
+
*****F/
+
</tt>
+
  
==Related content==
+
The directory tree might look somewhat overwhelming, but it simply follows the <code>Airports/[I]/[C]/[A]/</code> style.
* [[FlightGear Admin Wizard|FGAdmin]]
+
* Scenery/
* [[Installing Aircraft]]
+
** Airports/
 +
*** K/
 +
**** S/
 +
***** F/
 +
==Video tutorials on youtube (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|YxWV4wk_dHw|480px||Terramaster tutorial for Flightgear by FGUK - 2017 but still valid in 2020.}}
 +
== Related content ==
 
* [[Scenery FAQ]]
 
* [[Scenery FAQ]]
  
 
[[Category:Scenery]]
 
[[Category:Scenery]]
[[pt:Pt/Instalando Cenário]]
+
 
 +
[[ar:Howto:Install_scenery]]
 +
[[de:Howto:Install_scenery]]
 +
[[es:Instalación de escenarios]]
 +
[[fr:Installer une scène]]
 +
[[it:Come fare:Installare scenari]]
 +
[[nl:Scenery installeren]]
 +
[[PL:Instalowanie scenerii]]
 +
[[pt:Instalando Cenário]]

Latest revision as of 02:03, 29 August 2020

Hawaii scenery - "weeping wall" waterfalls at Mount Waialeale on the island of Kauai, near PHLI
Sicily scenery - the volcano Etna snowcapped in winter with a low level eruption, near LICC
Iceland scenery - having overlays enabled shows extremely high 3d detail like small rocks, plants, or individual grass blades
Madrid scenery with OSM2City output for Spain

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.

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 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 article on screenshots also covers turning on various settings.

Panorama of Innisbruck airport (LOWI) in Autumn with a 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
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.
Custom scenery
Non-official scenery covering all the way from small areas to very large areas, often with a high level of detail.

The default scenery is two 1 by 1 degree tiles surrounding the San Francisco Bay area from the World scenery.



CautionDo 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

World scenery tiles

You can download the official World Scenery terrain from the FlightGear website.

There is also a 4 DVD set available for download via 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 official FlightGear website.

Downloading from mirrors

A list of mirrors can be found here.

On most of the mirrors, the latest scenery can be found under Scenery-2.12.0/. Downloading from mirrors is often better than the official site, because mirrors are sometimes faster and have more user capacity. Use the graphical interface to find the appropriate chunk. Be careful about confusing N with S, and E with W!! Here is how to find an airport's co-ordinates:

  1. Go to the Wikipedia page for the airport in question (for example, PHNL for Honolulu)
  2. 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

There is a torrent file hosted on http://www.terasaur.org which you can find here. There is also an alternative torrent (only added a new announcement URL) with a strong seed available.

TerraSync scenery

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

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
  • 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

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.

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

Earthview orbital renderer at high sun - with high resolution texture packs installed.
Earthview orbital renderer at low sun showing light from cities. The 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.

See

  • Suggested Airports/Scenery for a list of custom scenery projects and an update on state of well developed areas.
  • Areas populated with OSM2City scenery for buildings, roads, power-lines, and objects for regions and entire countries based on Open Street Maps data. There is an OSM2City build for the entire world in progress with most areas already completed (July 2020).
  • Project 3000 for buildings and objects for 4000+ airports.
  • 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 - depends mainly on GPU memory (VRAM).

(August 2020)

Installing World and custom scenery

Install scenery outside the $FG_ROOT directory. See #Technical details below for an explanation.

Installing via a graphical interface

  1. Open the FlightGear Admin Wizard. On Windows, you can start it by clicking on Start -> All Programs -> FlightGear -> Tools -> FlightGear Admin Wizard.
  2. Click on Select Scenery Source... to select the directory containing the scenery .tgz files.
  3. 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 (C:\Users\your user name\Documents\FlightGear\Custom Scenery) is perfectly fine.
    • On Macintosh systems, the path should be /Applications/FlightGear.app/Contents/Resources/data/Scenery.
  4. 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

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.

cd SceneryDirectory
tar -xvzf input_file.tgz

or

tar -xvzf 'input_file.tgz' -C SceneryDirectory

input_file.tgz 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

Simply unpack the downloaded scenery into a directory of choice, using software like Winzip or 7-zip. Once done, append this directory to $FG_SCENERY. 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 C:\Program Files. 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 C:\FlightGear is a nice option.

Alternate installation, Macintosh

Unpack the .tgz file either by double-clicking it and moving the resulting wXXXnXXX folder to the Scenery folder described in the next line, or on the command line:

tar -xvzf 'input_file.tgz' -C /Applications/FlightGear.app/Contents/Resources/data/Scenery

Technical details

Scenery lookup and $FG_SCENERY

FlightGear determines what scenery to use by looking at the environment variable $FG SCENERY. 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 $FG SCENERY from which it is available.

Should the paths in $FG_SCENERY not be valid, FlightGear falls back to $FG ROOT/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 $FOOBAR/Scenery. In this directory, create two subdirectories: /Objects and /Terrain. You should untar individual files into the /Terrain folder.

Then you should set up $FG_SCENERY to use the new path:

  • On POSIX Clients
    set FG_SCENERY="$FOOBAR/Scenery" + FG_SCENERY
  • On Windows (FGRun)
    Go back to the first page of fgrun, and add the $FOOBAR/Scenery folder to the list.
  • Via a command line option
    --fg-scenery="$FOOBAR/Scenery"

Directory structure

Terrain

The Scenery directory will show the following (scenery is shown for completeness and for easy reference to above):

  • Scenery/
    • Terrain/
      • w130n30/
    • Objects/
      • w130n30/

If you download a scenery module called w90n40.tgz from flightgear.org and extract it in Scenery, the result will resemble something like the following:

  • Scenery/
    • Terrain/
      • w09n40/
      • w130n30/
    • Objects/
      • w09n40/
      • w130n30/

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 $FG_ROOT directory, because the Scenery directory is not present in the archive.

Objects

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

These objects are included in each scenery release, but as the object database is more frequently updated than the terrain, one may want to occasionally update the Object subdirectory from the scenery objects database between scenery releases.

Another option is to download or update the scenery on-demand by using the built in TerraSync utility described above.

Objects are really part of the scenery and can be found in the Scenery directory under $FG ROOT.

  • Scenery/
    • Objects/
      • w130n30/

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

Models

Replaces the former $FG_ROOT/Models; stores all the shared objects.

  • Scenery/
    • Models/
      • Airport/

Airports

1rightarrow.png See About Scenery/Airports for the main article about this subject.

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 Airports/[I]/[C]/[A]/ style.

  • Scenery/
    • Airports/
      • K/
        • S/
          • F/

Video tutorials on youtube (2020.x)

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.
Terramaster tutorial for Flightgear by FGUK - 2017 but still valid in 2020.

Related content