[EMAIL PROTECTED] writes: > > Question: Who's responsibility is it (or should it be) to set the > > runway elevation inside of FGInterface? > > JSBSIm does fine on its own by using a runway elevation (or scenery > elevation, or whatever) of zero - assuming sea level operations > only, for now. JSBSim defaults to sea level in standalone mode. We > have to default somewhere. If FlightGear wants us to follow them to > somewhere and fly from there, how else can we get the runway/scenery > elevation except from FlightGear?? It's a two-way street; FlightGear > has to tell us about the world it is simulating (the scene it is > showing and where in the world it is). We can do the rest. Maybe I > am unclear on what you are saying that FlightGear does and doesn't > do. Am I missing the point (I haven't had my morning coffee, yet, > so maybe I am)?
Jon, I didn't mean to evoke a defensive response. FlightGear does provide the ground elevation (continuously updating) via: scenery.get_cur_elev() The question is, who should be updating the values inside of FGInterface (which are really inside the JSBSim class since JSBSim inherits from FGInterface.) This is what JSBSim is using for runway elevation and is what is not getting updated when starting at KMYF. The answer probably looks different depending on which side of the fence you are sitting. I'm on the FlightGear side of the fence, not the FDM side, so bear that in mind. :-) The point I was trying to make is that there is some confusion here that we are trying to investigate and sort out. JSBSim properly handles updating the runway/ground elevation most of the time, but here is at least one situation where it doesn't. YASim doesn't handle this at all (but Andy's the new kid so we can cut him some slack.) :-) Once we make FlightGear interface with the FDM's completely via the property manager, then this confusion will go away entirely. FlightGear will provide the local ground elevation (or elevations of several wheel points, or a plane and a normal, or whatever) via the property manager. It will be up to the individual FDM's to make use of that information however they see fit. Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities [EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
