* Paul Furber -- Tuesday 03 May 2005 14:07:
> On Tue, 2005-05-03 at 13:26 +0200, Melchior FRANZ wrote:
> > No. If you had posted a command line that exposes the problem, *hundreds*
> > of fgfs developers would have tried to reproduce it, and maybe would have
> > been able to reproduce it and to find a solution. But so ...
>
> *Smacks forehead* - ask smart questions idiot! Sorry about that - I'll
> be more informative in future :)
Hehe ... no problem. (And I swear that this retarded sentence ("would have
tried to reproduce it, and maybe would have been able to reproduce it") was
an editing accident! Sheesh ... :-)
> > Try adding --log-level=info for a possible hint,
>
> ./fgfs --lat=87 --long=28 --altitude=30000 --log-level=info
That's an old, well known bug. If you position fgfs exactly on the tile
boundaries
(*integer* lon/lat), the intersection code somehow falls through between the
tiles. Try this:
$ ./fgfs --lat=87.001 --long=28.001 --altitude=30000
^^^^ ^^^^
I wouldn't be surprised if someone fixed that bug within ... the next twenty
years? ;-)
m.
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
