[Flightgear-devel] DAFIFT progress

[James Turner]

Okay, so I have FG working with the DAFIFT NAV and WPT data (replaces default.fix and default.nav). Now, I need some advice:

- What things to test that may have broken. I've extended 'testnavs' quite a bit and everything in there works, but this is a minute sample compared to what's out there. So, any suggestions for things to try? Other than 'fly around a bit, tuning the radios lots'..

- I uncovered some API inconsistencies between the fixlist and the navlist (some routines taking degrees, others radians, for lat / lon) : which do we prefer? (I'll fix the offenders)

- I'm getting a bunch of odd records from the DAFIFT NAV file: they have no frequency defined (which renders them rather useless except as waypoints). They appear on my SimCharts from Jeppesen, along with frequencies. Examples:

In the UK:
SAT
ODH

In the US:
VBG
TOL
SSC
PAM

In the netherlands:
TWN
SSB

At least the UK ones all have the 'TAC' prefix on my SimCharts. So .... does anyone know what these things are? I'm guessing it's something military related. The have frequencies in the VOR range (eg 117.7 Mhz based on SimCharts). Now, I can happily ignore them, but I'd like to know what I'm looking at before I do that.

- The current code detects the datafile format dynamically, so with a trivial patch to fg_init, I can dynamically use FG_ROOT/DAFIFT instead of FG_ROOT/Navaids if the DAFIFT files are present ... assuming I do this, shall I go ahead and send my changes out for some wider testing? Curt / Dave, which of you is less busy?

- Next stop, airways .... and I almost have a 737 to fling about them, thanks to Dave Culp :-)

H&H
James

--
That which does not kill me has poor aim



_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel