> Jim Wilson > Sent: 13 February 2004 15:31 > > David Megginson <[EMAIL PROTECTED]> said: > > > Jim Wilson wrote: > > > > > Yes it is. I'm probably being really dense, but I can't > think of a > > > reason why it would be important to know what the origin > is in fdm > > > coordinates. So long as position is reported to fgfs at > the nose, > > > we should be fine. > > > > Assuming that the model also has its origin at the nose. If we can > > tell the > > FDM to report a different point, then the model can have > its origin anywhere. > > > > The *.ac file doesn't actually need to be changed in any > case. You can always use the offsets to move the 3D model > origin to the nose. IIRC these are the offset properties > that were originally used to place MSFS models that we > couldn't edit. That dimmension would be easy to figure out > because it would be the distance from the 3D model's origin > to the location of the nose. > > For those who don't know what I'm refering to see: http://www.flightgear.org/Docs/fgfs-model-howto.html#repositioning
> In a sense what I've described here is analogous what you suggest, it's just the FDM doesn't actually need to > know it (besides what ever you report would have to refer to some sort of static location). If we stick to > having the only thing connecting the 3D to the FDM those /orientation and /position properties, then we'll be in > better shape for multi-instance FDMs. That makes sense. So, I apply an offset to the 3d model, then an appropriate one to the views to bring those to the CofG (dry, I suppose). Then we can dynamically adjust the view offset to account for variations in the CofG with time so that the 3d model appears to rotate around the correct point at all times. Or will the views be offset some other way? Vivian _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
