David Megginson <[EMAIL PROTECTED]> said: > Jon Berndt wrote: > > >>No, let's not do that -- instead, let FlightGear pass the VRP through the > >>JSBSim API. That way, we can use different 3D models with the > >>same flight model. > > > > That _absolutely_ defeats the whole purpose. > > I don't see that. What is the benefit of a configurable VRP at all, if the > 3D modeller cannot set it in the XML config file for the model? In that > case, you might as well just report the 0,0,0 point, as Jim suggests. > > On that point, though, I'm still not sure that the nose is a good, standard > reference point -- I think that the leading edge of the wing at the wing > root might be better for fixed-wing aircraft, though I don't know what to > suggest for helicopters. > > For example, the propeller spinner is required on the Cherokee, so it counts > as part of the nose proper; on other aircraft, the spinner is optional, so > it does not count as part of the nose. Ditto for sensing booms projecting > forward from the nose. > > It is also possible that there are aircraft where the nacelles project > further forward than the nose, though I cannot think of one offhand. >
Actually when I say 0,0,0 I meant the same thing as the VRP. The VRP performs the same function as 0,0,0 in YASim coordinates (defines specific locaton of lon/lat/alt). VRP is only used by JSBsim to identify where the nose is. The issue of booms, etc was discussed here about two or three weeks ago. Best, Jim _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
