* darko -- Thursday 07 April 2005 16:23:
> I'm getting some trouble with Atlas. It correctly connets to FlightGear
> via NMEA through udp protocol and I can see my plane moving on the map,
> but I can't see the bitmap, there's only the name of the airports and
> other stuff, but the screen is just grey.
You have to generate the tile images. This is done with the "Map" program
that comes with Atlas. See "Map --help", especially:
--atlas=path Create maps of all scenery, and store them in path
> When I launch Atlas, also, it says that it can't find default.nav.gz.
Hmm ... wasn't the very last Atlas version changed to use the new files?
A link from default.nav.gz to nav.dat.gz in the Navaids/ dir should work.
FWIW: I'm not using "Map" with the --atlas option, but built my own script.
It allows some more control over the process, such as only generating
missing or outdated scenery (interesting after having downloaded only a
few buckets/tiles via terrasync), using higher resolution for some areas,
or building some areas before the rest etc. It wasn't meant for publication,
but anyway: http://members.aon.at/mfranz/flightgear/mapsync
There is only one option "-v" (verbose), the rest is determined automatically.
(it uses and creats $FG_ROOT/Atlas and uses the last path from FG_SCENERY)
Just running "mapsync" should be enough. If not: bad luck. :-)
m.
_______________________________________________
Flightgear-users mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d
