![]() ![]() 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.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.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. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |