Durk Talsma:

[flightgear.git] / utils / TerraSync / README.txt

diff --git a/utils/TerraSync/README.txt b/utils/TerraSync/README.txt
index c71b48b2d05d32365d0ee3f5696a0944faf714ca..8f88be6a79dc96962af31ab4f904ba3981b548ec 100644 (file)
--- a/utils/TerraSync/README.txt
+++ b/utils/TerraSync/README.txt
@@ -7,14 +7,19 @@ Usage:
 
 Example:
 
-    $ fgfs --atlas=socket,out,1,localhost,5500,udp --fg-scenery=/data1/Scenery-0.7.9
-    $ nice terrasync -p 5500 -d /data1/Scenery-0.7.9
+    $ fgfs --atlas=socket,out,1,localhost,5500,udp --fg-scenery=/usr/local/FlightGear/data/scenery:/data1/Scenery-0.9.2
+    $ nice terrasync -p 5500 -d /data1/Scenery-0.9.2
 
 Requirements:
 
     - rsync util installed in your path.
     - mkdir util installed in your path.
 
+NOTE!!!!  Do not run terrasync against the default
+$FG_ROOT/data/Scenery/ directory.  I recommend creating a separate
+scenery directory and specifying both in your ~/.fgfsrc file or via
+the command line.
+
 TerraSync is a utility that is intended to run as a light weight
 background process.  It's purpose is to monitor the position of a
 FlightGear flight and pre-fetch scenery tiles from a remote server
@@ -38,25 +43,22 @@ As you fly, terrasync will periodically refresh and pull any new
 scenery tiles that you need for your position from the server.
 
 This also works if the scenery on the scenery server is updated.
-Rsync will pull any missing files, or any updated files.
+Rsync will pull any missing files, or any newly updated files.
 
 There is a chicken/egg problem when you first start up in a brand new
 area.  FlightGear is expecting the scenery to be there *now* but it
 may not have been fetched yet.  I suppose without making a more
-complex protocol, the user will need to be aware of this.  The user
-could restart flightgear after the initial rsync completes, and then
-after that everything should be good, assuming the flight track is
-"continuous" and the user has the necessary bandwidth to keep up with
-flight speeds.
+complex protocol, the user will need to be aware of this.  For now I
+suggest exiting FlightGear after terrasync gets caught up, and
+restarting FlightGear.  The second time FlightGear starts up
+everything should be good.
 
 Final notes:
 
-I have set up an initial scenery server at
-baron.flightgear.org::Scenery-0.7.9.  This is the 0.7.9 vintage
-scenery with airports rebuilt to include lighting.  Alex Perry also
-has a partial rsync server, but I don't know it's current status.
-William Riley has rebuilt the entire world, but the tiles are zipped
-in 10x10 degree chunks on on a relatively low bandwidth connection.
-There are aspects of the 0.7.9 scenery I like including the quality of
-the terrain, but William scenery has roads and streams which is also
-nice.
+I have set up the scenery server at
+scenery.flightgear.org::Scenery-0.9.2.  This is the latest 0.9.2 build
+of the world.
+
+Note to self:
+
+nice ./terrasync -p 5500 -s baron.flightgear.org:/stage/fgfs05/curt/Scenery-1.0 -d /stage/catalina3/Scenery-1.0/