[Flightgear-devel] Terrasync not working correctly?
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
Re: [Flightgear-devel] Terrasync not working correctly?
Matevz Jekovec writes: > 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) It might be possible that FlightGear is sending data out port 5500 before the FDM is fully initialized. I'd suggest letting it run until it looks like it has stopped rsyncing. And don't forget there is a chicken and egg problem where if you start up in a brand new area, FlightGear will initialize, not find scenery, and generate ocean tiles before terrasync has a chance to download the tiles. For now I suggest starting up flightgear, letting terrasync kick off it's downloading, then quite and restart FlightGear adn you should now pick up the newly downloaded tiles. We used to have a way to flush the tile cache, and reload it from scratch, but I think that got lost along the way during a code refactoring. Regards, Curt. -- Curtis Olson HumanFIRST Program FlightGear Project Twin Citiescurt 'at' me.umn.edu curt 'at' flightgear.org Minnesota http://www.flightgear.org/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Terrasync not working correctly?
Curtis L. Olson wrote: Matevz Jekovec writes: 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) It might be possible that FlightGear is sending data out port 5500 before the FDM is fully initialized. I'd suggest letting it run until it looks like it has stopped rsyncing. And don't forget there is a chicken and egg problem where if you start up in a brand new area, FlightGear will initialize, not find scenery, and generate ocean tiles before terrasync has a chance to download the tiles. For now I suggest starting up flightgear, letting terrasync kick off it's downloading, then quite and restart FlightGear adn you should now pick up the newly downloaded tiles. We used to have a way to flush the tile cache, and reload it from scratch, but I think that got lost along the way during a code refactoring. Ok, I let it wait this time and terrasync returned a weird error: 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 rsync: failed to connect to scenery.flightgear.org: Connection timed out rsync error: error in socket IO (code 10) at clientserver.c(83) mkdir -p /home/matevz/fgfs/data/Scenery/w010s10 rsync --verbose --archive --delete --perms --owner --group scenery.flightgear.org::scenery-0.9.2/w010s10/w001s01/ /home/matevz/fgfs/data/Scenery/w010s10/w001s01 rsync: failed to connect to scenery.flightgear.org: Connection timed out rsync error: error in socket IO (code 10) at clientserver.c(83) mkdir -p /home/matevz/fgfs/data/Scenery/e000s10 rsync --verbose --archive --delete --perms --owner --group scenery.flightgear.org::scenery-0.9.2/e000s10/e000s01/ /home/matevz/fgfs/data/Scenery/e000s10/e000s01 Now maybe there's a problem on my side because of the router, but I doubt it. I'll take a look later today. Is rsync server running fine on scenery.flightgear.org? - Matevz ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Terrasync not working correctly?
Hi Matevz, I was able to run rsync fine last night after my first reply to your problem so I believe the rsync server should be working just fine. Curt. Matevz Jekovec writes: > Curtis L. Olson wrote: > > >Matevz Jekovec writes: > > > > > >>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) > >> > >> > > > >It might be possible that FlightGear is sending data out port 5500 > >before the FDM is fully initialized. I'd suggest letting it run until > >it looks like it has stopped rsyncing. And don't forget there is a > >chicken and egg problem where if you start up in a brand new area, > >FlightGear will initialize, not find scenery, and generate ocean tiles > >before terrasync has a chance to download the tiles. For now I > >suggest starting up flightgear, letting terrasync kick off it's > >downloading, then quite and restart FlightGear adn you should now pick > >up the newly downloaded tiles. We used to have a way to flush the > >tile cache, and reload it from scratch, but I think that got lost > >along the way during a code refactoring. > > > > > Ok, I let it wait this time and terrasync returned a weird error: > 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 > rsync: failed to connect to scenery.flightgear.org: Connection timed out > rsync error: error in socket IO (code 10) at clientserver.c(83) > mkdir -p /home/matevz/fgfs/data/Scenery/w010s10 > rsync --verbose --archive --delete --perms --owner --group > scenery.flightgear.org::scenery-0.9.2/w010s10/w001s01/ > /home/matevz/fgfs/data/Scenery/w010s10/w001s01 > rsync: failed to connect to scenery.flightgear.org: Connection timed out > rsync error: error in socket IO (code 10) at clientserver.c(83) > mkdir -p /home/matevz/fgfs/data/Scenery/e000s10 > rsync --verbose --archive --delete --perms --owner --group > scenery.flightgear.org::scenery-0.9.2/e000s10/e000s01/ > /home/matevz/fgfs/data/Scenery/e000s10/e000s01 > > > Now maybe there's a problem on my side because of the router, but I > doubt it. I'll take a look later today. Is rsync server running fine on > scenery.flightgear.org? > > > - Matevz > > > > > > > > Curtis L. Olson wrote: > cite="[EMAIL PROTECTED]"> > Matevz Jekovec writes: > > > 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) > > > > It might be possible that FlightGear is sending data out port 5500 > before the FDM is fully initialized. I'd suggest letting it run until > it looks like it has stopped rsyncing. And don't forget there is a > chicken and egg problem where if you start up in a brand new area, > FlightGear will initialize, not find scenery, and generate ocean tiles > before terrasync has a chance to download the tiles. For now I > suggest starting up flightgear, letting terrasync kick off it's > downloading, then quite and restart FlightGear adn you should now pick > up the newly downloaded tiles. We used to have a way to flush the > tile cache, and reload it from scratch, but I think that got lost > along the way during a code refactoring. > > > Ok, I let it wait this time and terrasync returned a weird error: > 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/e0
