#Flightgear download complete scenery how to#
#Flightgear download complete scenery install#
#Flightgear download complete scenery code#
#Flightgear download complete scenery simulator#

(There’s advantages and disadvantages to both). I expect the pure HTTP solution will need some very similar files to record the HTTP cache stamps of files it downloads - either one file at the root of the tree, or per-directory. The cache files are tiny and reflect the current revision of each file in the local copy they’re analogous to the data a real SVN client stores in its ‘.svn’ directory in the root of the checkout. The intention is to migrate to a pure HTTP solution for TerraSync (instead of SVN) after 2016.1 is released, since this will give us many more mirroring and hosting options.

#Flightgear download complete scenery code#

This should make it much easier for hosts to set up a mirror, probably enables us to use a CDN for load balancing and also makes the client code slim. The idea is to use plain HTTP as the access method for files required by terrasync. The main intention is to get rid of the SVN protocol to distribute scenery but use easier to implement protocols. We wanted to embed terrasync right into the core code so we could better coordinate downloading tiles and then loading them immediately into the sim (versus sometimes running into no tiles or partial tiles if an external tool was running rsync.) Īs some of you have probably noticed, some coding is currently happening in the terrasync corner, mostly by James and some parts by Torsten. However, there doesn't appear to be any good/robust multi-platform librsync available for our use. Terrasync started out as a standalone rsync-based utility. We probably throw away some or all files in that directory without prior notice, so please don't rely on them or make backup copies.

When using terrasync.py you should notice download of files in those folders, however they do not (yet) show up in the scenery. People using the fgfs integrated terrasync should not (yet) notice any difference. As a first step I have just added a folder called Objects_1 containing the osm2city buildings for e005n46 up to e010n48.

#Flightgear download complete scenery how to#

5.1 Corrupted and unreadable files or directoriesĪlso as a result from FSweekend, we are going to test some ideas how to distribute osm2city generated scenery with terrasync.4.2 FlightGear 2.4 up to and including 2.12.(Generic models used more than once in different places, each can represent many different objects, like generic houses or ships) (Static models define unique objects that exist in one place only, such as famous buildings or landmarks.) stg-files, which tell FlightGear where to place an object So when using TerraSync, you will always have the online resource from which TerraSync downloads its files, is synchronized with the FlightGear Scenery Database once a day. The master repository for TerraSync, i.e. TerraSync runs in the background (optionally as a separate process), monitors your position, and downloads (or updates) the latest scenery from the master scenery server 'just in time'.įor some time now TerraSync has been integrated into the core FlightGear process, so there is no need to deal with TerraSync for the typical user.

#Flightgear download complete scenery simulator#

It is a utility that automatically downloads the newest version of the needed FlightGear scenery while the simulator is running. This can happen by downloading certain bits of scenery before flying as described in the article installing scenery.Īlternatively, if you have a steady and reasonably fast internet connection, you can use TerraSync.

#Flightgear download complete scenery install#

To see the terrain below your aircraft, you have to install the respective scenery. Not to be confused with TerraGear, a toolset to generate scenery.