* Mathias Fröhlich -- Thursday 26 May 2005 12:01:
> On Dienstag 03 Mai 2005 14:17, Melchior FRANZ wrote:
> > > > 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? ;-)
> Is fixed now in current cvs ...
Unfortunately, a similar bug showed up recently for *bucket* boundaries.
If you set /position/{latitude,longitude}-deg to a bucket boundary, fgfs
refuses to set /position/elevation-m accordingly. It simply lets the old
elevation in the property system. Annoying for scripts that read out
elevation. (I work around that by adding 0.0001 now in [1]). :-(
m.
[1] http://members.aon.at/mfranz/flightgear/getelev
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
