"Curtis L. Olson" <[EMAIL PROTECTED]> said: > Jim Wilson writes: > > > If you set --altitude=1933 when starting at CL77 the mishap does not > > occur. > > JSBSim is getting fed a consistant starting ground elevation now with > the latest CVS changes.
Yes I updated before replying, this works with the latest changes. Try setting --altitude=1933 (probably doesn't prove anything). I noticed that we're passing it 1924 (or at least thats what JSBsim is initializing at first pass). > > And I guess I'm wondering still if it is possible to set the plane > > on that tile before reporting position to FDM's so that it still > > works even if there is a data problem. > > This is what we do. The tile is loaded and a valid ground elevation > is determined before the FDM init() routine is called. > Ok sorry for the stupid q's :-) > > This may or may not be related but when I start up at an airport for > > which i have no scenery, the elevation is below 0. At EHAM it is > > -17 ft as shown in /position/altitude-ft. > > Actually, when an ocean tile is automatically generated, we use really > big triangles (i.e. two triangle to cover the whole tile.) If the > elevation is 0 at the corners, the surface of the tile forms a sort of > 3d square 'secant' so the elevation within the ocean tile will be < > 0. -17 sounds reasonable for an interior position. > Ah, ok ...makes sense. Thanks for the explanation. Best, Jim _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
