Howto:Install scenery: Difference between revisions

Jump to navigation Jump to search
Update link to mirrors
(Update link to mirrors)
Line 42: Line 42:


==== Downloading from mirrors ====
==== 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 [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!!
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:


# Go to the Wikipedia page for the airport in question (for example, PHNL for Honolulu)
#Go to the Wikipedia page for the airport in question (for example, PHNL for Honolulu)
# Find the co-ordinates (often at the top or right and side, marked with a small globe)
#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.
#*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 BitTorrent====
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].
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 ===
===TerraSync scenery===
The [[TerraSync]] scenery is automatically downloaded and synchronized as needed while FlightGear is running when the built in TerraSync utility is enabled.
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 ====
====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:
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
*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
*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
*Use TerraMaster to download and synchronize the scenery


==== Downloading with TerraMaster ====
====Downloading with TerraMaster====
[[File:TerraMaster r32 - Global view.png|thumb|TerraSync scenery in TerraMaster]]
[[File:TerraMaster r32 - Global view.png|thumb|TerraSync scenery in TerraMaster]]


Line 71: Line 71:
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.
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: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.]]
[[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.]]
Line 77: Line 77:


See  
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.
* [[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).
*[[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.
*[[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).


(August 2020)
(August 2020)


== 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.
Install scenery outside the <code>[[$FG_ROOT]]</code> directory.  See [[#Technical details]] below for an explanation.


=== Installing via a graphical interface ===
===Installing via a graphical interface===
{{Obsolete}}{{Incomplete|section}}
{{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.
#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 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.
#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 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>.
#*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.
#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 ===
===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.


Line 108: Line 108:
<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 ===
===Alternate installation, 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.
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.}}
{{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.}}


=== Alternate installation, Macintosh ===
===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:
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:


  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


== 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 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.
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>.
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.
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.


Line 131: Line 131:


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
*On POSIX Clients
*: <code>set FG_SCENERY="$FOOBAR/Scenery" + FG_SCENERY</code>
*:<code>set FG_SCENERY="$FOOBAR/Scenery" + FG_SCENERY</code>
* On Windows ([[FGRun]])
*On Windows ([[FGRun]])
*: Go back to the first page of fgrun, and add the <code>$FOOBAR/Scenery</code> folder to the list.
*:Go back to the first page of fgrun, and add the <code>$FOOBAR/Scenery</code> folder to the list.
* Via a command line option
*Via a command line option
*: <code>--fg-scenery="$FOOBAR/Scenery"</code>
*:<code>--fg-scenery="$FOOBAR/Scenery"</code>


=== Directory structure ===
===Directory structure===
==== Terrain ====
====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/
*Scenery/
** Terrain/
**Terrain/
*** w130n30/
***w130n30/
** Objects/
**Objects/
*** w130n30/
***w130n30/


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


* Scenery/
*Scenery/
** Terrain/
**Terrain/
*** w09n40/
***w09n40/
*** w130n30/
***w130n30/
** Objects/
**Objects/
*** w09n40/
***w09n40/
*** w130n30/
***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 <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 169: Line 169:
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/
*Scenery/
** Objects/
**Objects/
*** w130n30/
***w130n30/


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/
*Scenery/
** Models/
**Models/
*** Airport/
***Airport/


==== 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/
*Scenery/
** Airports/
**Airports/
*** K/
***K/
**** S/
****S/
***** F/
*****F/
==Video tutorials on youtube (2020.x)==
==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|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 ==
==Related content==
* [[Scenery FAQ]]
*[[Scenery FAQ]]


[[Category:Scenery]]
[[Category:Scenery]]
1,089

edits

Navigation menu