On Tuesday 15 November 2005 00:24, Innis Cunningham wrote: > Well as far as the fixes go no I think the fixes are valid,see Paul's > comments, OK, I don't really make use of the fixes so I've not investigated them much yet.
>If that airfield is named correctly then the problem comes > back to FG if not then yes it needs to be corrected in the data base. Yes, every respectable source I can find online agrees that EG73 is Fearn - the imposter (Nayland) must be a really tiny strip which I can't find any reference to in aviation databases. Which makes it all the more annoying that if you try placing an aircraft at EG73 from within FG, you always end up at Nayland (which looks more like a ditch than an airfield!). Starting with --airport=EG73 places the plane correctly at Fearn. I'll see what Robin Peel has to say about it, hopefully we can fix this one at the source. Any other instances of incorrectly named fields that are annoying folk? AJ _______________________________________________ Flightgear-users mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
