On Thu, 27 Apr 2006 13:08:01 +0200 cyprien wrote: > > I wanted to go to LFRN runway 28R and i've selected it on th fgrun > interface... but this runway doesn't exist on Flightgear.
First of all, there is no 28R at LFRN in real life. There is a Rwy 28, but no Rwy 28R. See: http://www.sia.aviation-civile.gouv.fr/aip/enligne/UK/..%5CPDF_AIPparSSection%5CVAC%5CAD%5C2%5C0605_AD%202.LFRN.pdf for more information. If you're talking about the message that fgfs can give during startup that says something like "Failed to find runway 28R at airport LFRN", don't worry about that. That's not an error message -- it's just for information. FlightGear uses 28R as its default runway for initial placement because it has to use something -- KSFO is the default airport, and KSFO has a Rwy 28R, so why not use that? If you choose some other airport that doesn't have a Rwy 28R, and you don't specify a runway to use instead, FlightGear will: 1. try to place you on that airport's Rwy 28R; 2. fail to find a Rwy 28R to place you on; 3. send you a message saying so; 4. and then put you on whatever runway it finds that's closest to being in the same direction as 28R (actually, I can't remember, but I think it looks for the closest in the direction of increasing heading angle -- so it would pick a Rwy 35 over a Rwy 25 -- but I'm not positive of that. Maybe someone else here remembers). At LFRN, it tries to put you on Rwy 28R, fails (because there isn't one), and instead puts you on the closest runway to 28R, which is Rwy 28. -c -- Chris Metzler [EMAIL PROTECTED] (remove "snip-me." to email) "As a child I understood how to give; I have forgotten this grace since I have become civilized." - Chief Luther Standing Bear
signature.asc
Description: PGP signature
