Re: [Flightgear-devel] Bug in starting runway selection @ KCGS.

2006-03-12 Thread David Megginson
On 12/03/06, David Luff <[EMAIL PROTECTED]> wrote: > OK, this is partially fixed in CVS now. fgfs --airport=KCGS will now put you > on the helipad (at KCGS), since that is the closest to the default heading of > 270. The J3 Cub could *almost* manage that. Maybe we need a Super Cub option. A

Re: [Flightgear-devel] Bug in starting runway selection @ KCGS.

2006-03-12 Thread David Luff
Chris Metzler writes: > > KCGS has a single runway, 15/33. > > Starting FG with --runway=15 or with --runway=33 works just fine. > > Starting FG with no runway specified at all, OTOH, produces a message > of "Failed to find a good runway for KCGS", after which the plane is > placed at KSFO. >

Re: [Flightgear-devel] Bug in starting runway selection @ KCGS.

2006-03-11 Thread Innis Cunningham
Chris Metzler writes It's not universal to that situation -- I just started going through apt.dat airports with both a normal (non-water) runway and a helipad, and (in order in apt.dat) 8L3, LA77, 97WA, and 1LA4 all loaded OK; but then 7X8 produced exactly the same behavior as KCGS. ID19, KCCA

Re: [Flightgear-devel] Bug in starting runway selection @ KCGS.

2006-03-11 Thread Chris Metzler
On Sun, 12 Mar 2006 00:02:52 + David Luff wrote: >David Luff writes: >> Chris Metzler writes: >>> >>> KCGS has a single runway, 15/33. >>> >>> Starting FG with --runway=15 or with --runway=33 works just fine. >>> >>> Starting FG with no runway specified at all, OTOH, produces a >>> message o

Re: [Flightgear-devel] Bug in starting runway selection @ KCGS.

2006-03-11 Thread David Luff
David Luff writes: > Chris Metzler writes: > > > > > KCGS has a single runway, 15/33. > > > > Starting FG with --runway=15 or with --runway=33 works just fine. > > > > Starting FG with no runway specified at all, OTOH, produces a message > > of "Failed to find a good runway for KCGS", after wh

Re: [Flightgear-devel] Bug in starting runway selection @ KCGS.

2006-03-11 Thread David Luff
Chris Metzler writes: > > KCGS has a single runway, 15/33. > > Starting FG with --runway=15 or with --runway=33 works just fine. > > Starting FG with no runway specified at all, OTOH, produces a message > of "Failed to find a good runway for KCGS", after which the plane is > placed at KSFO. >

[Flightgear-devel] Bug in starting runway selection @ KCGS.

2006-03-11 Thread Chris Metzler
KCGS has a single runway, 15/33. Starting FG with --runway=15 or with --runway=33 works just fine. Starting FG with no runway specified at all, OTOH, produces a message of "Failed to find a good runway for KCGS", after which the plane is placed at KSFO. -c -- Chris Metzler [