Changes

Jump to navigation Jump to search
m
Robot: Cosmetic changes
Line 1: Line 1:  
{{installing}}
 
{{installing}}
==Obtaining scenery==
+
== 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.
 
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.
    
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].
 
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].
   −
===TerraSync===
+
=== TerraSync ===
 
[[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.  
 
[[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===
+
=== 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].
   Line 18: Line 18:  
#* 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==
+
== Installing scenery ==
 
You can optionally use a GUI installer, called [[FlightGear Admin Wizard|FGAdmin]], to (un)install scenery.
 
You can optionally use a GUI installer, called [[FlightGear Admin Wizard|FGAdmin]], to (un)install scenery.
   Line 31: Line 31:  
  tar -xvzf 'input_file.tgz' -C [[$FG_ROOT]]/Scenery
 
  tar -xvzf 'input_file.tgz' -C [[$FG_ROOT]]/Scenery
   −
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).
+
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).
    
=== Windows ===
 
=== 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 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 />
'''!!! IMPORTANT !!!'''<br>
+
'''!!! 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".
 
"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==
+
== Technical ==
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>.
+
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.
 
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.
Line 47: Line 47:     
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<br />set FG_SCENERY="$FOOBAR/Scenery" + FG_SCENERY
*On Windows (FGRun)<br>Go back to the first page of fgrun, and add the $FOOBAR/Scenery folder to the list.
+
* On Windows (FGRun)<br />Go back to the first page of fgrun, and add the $FOOBAR/Scenery folder to the list.
    
=== Terrain ===
 
=== Terrain ===
Line 54: Line 54:     
<tt>
 
<tt>
*Scenery/
+
* Scenery/
**Terrain/
+
** Terrain/
***w130n30/
+
*** w130n30/
**Objects/
+
** Objects/
***w130n30/
+
*** w130n30/
 
</tt>
 
</tt>
   Line 64: Line 64:     
<tt>
 
<tt>
*Scenery/
+
* Scenery/
**Terrain/
+
** Terrain/
***w09n40/
+
*** w09n40/
***w130n30/
+
*** w130n30/
**Objects/
+
** Objects/
***w09n40/
+
*** w09n40/
***w130n30/
+
*** w130n30/
 
</tt>
 
</tt>
   Line 81: Line 81:  
Another option is to download or update the scenery on-demand by using the terrasync program described below.
 
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]].
+
Objects are really part of the scenery and can be found in the Scenery directory under [[$FG ROOT]].
    
<tt>
 
<tt>
*Scenery/
+
* Scenery/
**Objects/
+
** Objects/
***w130n30/
+
*** w130n30/
 
</tt>
 
</tt>
   Line 94: Line 94:  
<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.
 
<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]]
+
: See also: [[Howto: Animated jetways#Usage]]
    
The directory tree might look somewhat overwhelming, it simply follows the <tt>Airports/[I]/[C]/[A]/</tt> code (see [[ICAO-code]]).
 
The directory tree might look somewhat overwhelming, it simply follows the <tt>Airports/[I]/[C]/[A]/</tt> code (see [[ICAO-code]]).
    
<tt>
 
<tt>
*Scenery/
+
* Scenery/
**Airports/
+
** Airports/
***K/
+
*** K/
****S/
+
**** S/
*****F/
+
***** F/
 
</tt>
 
</tt>
   −
==Related content==
+
== Related content ==
 
* [[FlightGear Admin Wizard|FGAdmin]]
 
* [[FlightGear Admin Wizard|FGAdmin]]
 
* [[Installing Aircraft]]
 
* [[Installing Aircraft]]
 
* [[Scenery FAQ]]
 
* [[Scenery FAQ]]
 +
[[pt:Pt/Instalando Cenário]]
    
[[Category:Scenery]]
 
[[Category:Scenery]]
[[pt:Pt/Instalando Cenário]]
 

Navigation menu