Jim Wilson writes: > Norman Vine <[EMAIL PROTECTED]> said: > > > In your example you may not see the error but ..... > > What I meant was that offseting to the varible center of gravity wouldn't be > visible either outside or inside the aircraft. The FDM already provides the > attitude effects, it is the change in axes that wouldn't be noticable. > Actually you know if we did offset the camera and model to center of gravity > it could have a very minor negative effect. Assuming that some day we have a > dialog to configure payload, we'll see the 3D model shift back and forth on > the tarmac as we add fuel, passengers and luggage and the 3D origin changes :-)
OK but when in tet to be implemented external 'flier mode' similar to the existing static external view, which should be tied to the Model Origin, you should see the difference in the effects of a rotation of the plane when the plane's Center of Gravity moves > The question is this: If the FDM's agree to use the nose as the origin, > we'll have an offset to the 3D model's origin, right? Yes but we don't care where it is as long as Model explicitly states where it is in reference to the 'bounding sphere' or 'bounding box' of the model > Where would we put the > setting so that it was available to both the model and the viewer, defined > per aircraft type? in the Model-set.xml file, this way a FDM may be used by more then one model > IMHO it'd make the most sense to put the offset (from the nose or tail) to the > 3D model origin location into the FDM's aircraft config xml file. This > location should be on the leading edge of the wings and z axis centered on the > nose as described above. The 3D modeler's could refer to that data for > getting the model right, and the fdm should simply report lon/lat/alt at > *that* location. This is how the YASim 747 currently works and it seems fine. If we use a position relative to a 'bounding shape' then this can actually be determined at run time Norman _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
