bb4c4f6b13
position. Terrasync runs as a separate process and accepts the --atlas=port format. The fgfs output tells the terrasync util where FlightGear is currently flying. Terrasync will then issue the appropriate commands to rsync the surrounding areas to your local scenery directory. As you fly, terrasync will periodically refresh and pull any new scenery tiles in the vicinity. This also works if the scenery on the scenery server is update. Rsync will pull any missing files, or any 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 hasn't 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 user has the necessary bandwidth to keep up with flight speeds. Final notes: At the moment Alex Perry has a partial rsync server, but I don't know it's status. I hope to have a full server up and running at some point soon. Currently the terragear utility just echos the commands it would run to rsync the data, it doesn't actually run the commands. This is a work in progress. |
||
|---|---|---|
| .. | ||
| Airports | ||
| BuildTiles | ||
| Include | ||
| Lib | ||
| Prep | ||
| Utils | ||
| .cvsignore | ||
| Makefile.am | ||