Hi. It appears that in initialization, if an airport and heading are specified on the command line, a runway is immediately chosen based upon the heading, and latitude/longitude is set to that runway's threshhold. This is sensible if the user is starting *at* the airport; but if the user is starting somewhere else, and using the airport as a reference point via --offset-azimuth and --offset-distance, the result is that starting position can jump by a large amount simply by changing the starting heading. Changing the heading changes the runway fg_init thinks is relevant, and the offset is taken from the position that's been set to an irrelevant runway threshold location.
Not very important at all -- it probably takes a fairly contrived situation (like mine) to get bit by this -- but figured I'd mention it.
I think the options you mention are explicitly to align to the airport. A better approach would probably be to specify --lat and --lon instead.
Erik
_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
