Ok, I run fgfs with the following arguments: --fg-root=/home/matevz/fgfs/data --atlas=socket,out,1,localhost,5500,udp --fg-scenery=/home/matevz/fgfs/data/Scenery --airport=LJLJ
and I run nice terrasync -p 5500 -d /home/matevz/fgfs/data/Scenery
And I found myself in the ocean.
Terrasync outputs:
pos = 0,0
lat = 0 lon = 0
lat_dir = 0 lon_dir = 0
mkdir -p /home/matevz/fgfs/data/Scenery/e000n00
rsync --verbose --archive --delete --perms --owner --group scenery.flightgear.org::scenery-0.9.2/e000n00/e000n00/ /home/matevz/fgfs/data/Scenery/e000n00/e000n00
And that's it.
Emm... advice? Looks like fgfs isn't reporting to terrasync the right coordinates to download? (LJLJ is in e010n040 world chunk)
- Matevz
_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
