David Megginson writes: > Since we threw out Metakit (another loud hurray!) I've noticed that > FlightGear doesn't always place the runway correctly on the runway > threshold any more. Try this with the current base package, for > example: > > fgfs --airport=KHAF > > On the other hand, starting at KSFO is fine. At first, I suspected > that it was a matter of newer, more accurate runway data in the base > package, but I rebuilt w080n40 using the new runways.dat.gz, and I > still got the same problem at some of the new airports (exactly the > same with the old scenery and with the new scenery I just built).
This must be a data mismatch problem. I just checked KHAF with scenery I built over the weekend and it matched perfectly. Regards, Curt. -- Curtis Olson HumanFIRST Program FlightGear Project Twin Cities curt 'at' me.umn.edu curt 'at' flightgear.org Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
