Concerning scenery paths and their precedence, you list them in Additional scenery locations in the Add-ons tab. If you put download_dir/TerraSync (which is $FG_HOME/TerraSync unless you changed the download location) in this list, this will determine the precedence of your TerraSync folder relatively to other scenery paths in this list, otherwise it will come after all scenery paths you have explicitely defined and before the last default, $FG_ROOT/Scenery:
- Code: Select all
void QtLauncher::setSceneryPaths() // static method
{
globals->clear_fg_scenery();
// mimic what optionss.cxx does, so we can find airport data for parking
// positions
QSettings settings;
// append explicit scenery paths
Q_FOREACH(QString path, settings.value("scenery-paths").toStringList()) {
globals->append_fg_scenery(path.toStdString());
}
// append the TerraSync path
QString downloadDir = settings.value("download-dir").toString();
if (downloadDir.isEmpty()) {
downloadDir = QString::fromStdString(flightgear::defaultDownloadDir().utf8Str());
}
SGPath terraSyncDir(downloadDir.toStdString());
terraSyncDir.append("TerraSync");
if (terraSyncDir.exists()) {
globals->append_fg_scenery(terraSyncDir);
}
// add the installation path since it contains default airport data,
// if terrasync is disabled or on first-launch
globals->append_fg_scenery(globals->get_fg_root() / "Scenery");
}
(this is the corresponding code in the built-in launcher, it is almost the same but not quite once "normal FG" has started, see https://sourceforge.net/p/flightgear/fl ... .cxx#l2320 [OptionResult Options::processOptions()] for those who can read C++).
As for how the "mix" between several scenery paths is done, this is explained here:
FlightGear searches these scenery paths sequentially. The first terrain found for each tile is loaded. Objects for a tile are loaded from all directories visited before (and including the one where) the terrain was found.
as well as in $FG_ROOT/Docs/README.scenery.