I'm only getting this with JSBsim right now. Maybe I've got something
screwed
up here anyone else seeing this? The symptom is that if I specify an
airport
that is not in scenery the simulation comes up correctly momentarily and
then
tries to load a tile and does the fatal bogus long/lat error.
This is the output using --airport-id=EHAM:
http://www.spiderbark.com/fgfs/scenerynotfound.txt
Note that this problem does go away if I set --altitude=0 or some other
small
number before starting.
The problem may be stemming from an improper altitude sent to the
FGInterface bus or something ... I don't know. Tony: if we are given an
incorrect unsynchronized altitude data what does the trim routine do? I am
thinking this is due to differences in the way JSBSim is started up but not
explicitly in the JSBSim code. Could be a bug in the way altitude is figured
for some airports?
Jon
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
