"Curtis L. Olson" <[EMAIL PROTECTED]> writes:
> David Luff wrote:
>
> >I've been keeping the Atlas CVS up-to-date with FlightGear's changes, since
> >Per Liedman (the author) no longer has regular net access. I'll do the
> >latest airport change, and see if I can make a release. It probably w
David Luff wrote:
I've been keeping the Atlas CVS up-to-date with FlightGear's changes, since Per Liedman (the author) no longer has regular net access. I'll do the latest airport change, and see if I can make a release. It probably won't be until after Christmas now though.
Some sample code f
"Curtis L. Olson" writes:
> Innis Cunningham wrote:
>
> > Does this work with Atlas now?.The last time I went to build the maps
> > using Atlas I had to get the old default.nav files to get Atlas to work.
>
Hmm - I fixed this for Atlas itself (in CVS), but since I don't build the
symbols on th
On Thursday 23 December 2004 02:48, Innis Cunningham wrote:
> Does this work with Atlas now?.The last time I went to build the maps
> using Atlas I had to get the old default.nav files to get Atlas to work.
The navaids parsing in Atlas was fixed (CVS) very recently. I guess that now
the airport p
Innis Cunningham wrote:
Does this work with Atlas now?.The last time I went to build the maps
using Atlas I had to get the old default.nav files to get Atlas to work.
I think Atlas is about 2-3 generations behind here. Someone should look
at updating the airport loading code, and if no one is av
Hi Curt
"Curtis L. Olson" writes
I just commited a change to cvs that replaces the old basic.dat.gz and
runways.dat.gz files (which were in an old depricated/unsupported format)
with apt.dat.gz which is in the X-Plane format. This is the format we now
officially support. Having one single for
