Flightgear install scenery linux how to#
Flightgear install scenery linux update#
Flightgear install scenery linux download#

There is also a 4 DVD set available for download via BitTorent, which can be a higher performance option for those wanting to download the entire world. See Suggested Airports/Scenery for a list of custom scenery projects. They are distributed separately due to their license, or because their level of detail is not suitable for low-end machines. Alternatively, custom scenery is available for certain specific areas. once you've set up FG_ROOT properly, that is.You can download the official World Scenery terrain from the FlightGear website. (*) In which case it is in $FG_ROOT/Scenery. If you want more help, tell us how you start FG and please try to be more specific. foobar stands for aircraft or scenery, of course on Windows, the path separator is a semicolon instead of a colon) (I think you can mix both, but that's weird. -fg- foobar=/path1 -fg- foobar=/path2.For -fg-aircraft and -fg-scenery, two syntaxes are possible: Just use the options mentioned above so that FG can find them. There is no standard place where to install additional aircraft or scenery. If you divert from the default values, you need to reflect it on -fg-aircraft and -fg-scenery, otherwise FG won't find what you've downloaded (or use equivalent GUI settings in a launcher, since I don't know how you start FG.).

There is also -terrasync-dir to specifically choose the TerraSync dir, but -download-dir is more useful in general. You may choose a different one with -download-dir. On Linux, this is by default $FG_HOME, i.e. When you download aircraft from the built-in launcher, or scenery from TerraSync (the wiki page is outdated, it is integrated in FG nowadays and already based on HTTP), the data goes inside the download directory. So, unless you get scenery from the base package(*), or from TerraSync, or install some manually, you get to start in water (frequent question here.). Contrary to aircraft, there is no default scenery in FGData, because updating it regularly would make FGData absolutely huge since it is a Git repository. At a high-level, the situation is similar to aircraft: FG looks for scenery in folders specified with -fg-scenery options, in the TerraSync directory as well as in $FG_ROOT/Scenery (collectively and slightly informally referred to as $FG_SCENERY). There is also an FG_AIRCRAFT environment variable that does the same thing, and often we use the $FG_AIRCRAFT notation to informally represent your setting, regardless of how you've specified it (be it with -fg-aircraft or with the environment variable).įinally, there is scenery. fgfs supports a -fg-aircraft option (that can be passed several times) that you can use to tell him where you have additional aircraft (i.e., the ones in places different from $FG_ROOT/Aircraft). With and without the built-in launcher, you can also use aircraft downloaded from FGAddon.

Flightgear install scenery linux update#

With the built-in launcher (fgfs -launcher), there is a sort of package manager for aircraft, allowing to install and update aircraft by clicking on obvious buttons.

Flightgear install scenery linux how to#

How to do so and tell FG where they are depends on how you start FG, so we would need to know that. If you want more, you have to install them. There are always a few default aircraft in FGData (c172p and ufo + variants). But generally, you also want aircraft and scenery. Just rely on the platform default for your OS. In fact, it is discouraged unless you really need to change it. But there are other ways to avoid tedious typing of the same options: launchers, $FG_HOME/fgfsrc, and home-made scripts.įG_HOME doesn't have to be set. If you compile FG yourself, it can remember a value passed at compile-time so that you don't have to pass -fg-root, unless you want to use another location. If you use a launcher, there is certainly a setting to tell FG the corresponding path otherwise, you can use -fg-root=/path/to/FGData, or set the FG_ROOT environment variable. You must, one way or another, tell FG where you have FGData (or the base package, which AFAIK is the contents of the FGData Git repository, without history information, but with a few more things suitable for a default installation such as a small scenery chunk around the default airport, for people who just installed FG and want to start flying without downloading anything). There is nothing really Linux-specific in that, except the default value for some paths like FG_HOME depends on the OS.