I mildly disagree. I think the FGFS should require that the FDMs _and_ the aircraft models all have the reference point at the original manufacturer's defined reference point (so they all match nicely) even if this is done by a parametric offset that the FDM's configuration file has somewhere.
The Aircraft's model file should contain an empty piece of movable airframe that is named "PILOT" and has the origin at the location of the obvious point of symmetry underneath a sitting person (grin) and has the up vector aligned with the slope of the seat back. This would allow the viewpoint stuff to specify pilot-centric viewpoints in terms of the PILOT location plus a specified distance that corresponds to the notional torso height of the simulated pilot to get the matrix. > Here's what make sense to me. > > The FDM defines some aribitrary reference point (i.e. on the firewall) > and provides the lon/lat/elev of that point. > > The FDM really doesn't care about the actual FlightGear view point. > It won't know if the user is flying from the left seat, the right > seat, or seat 5A in the DC-3. > > It seems like it would make much more sense for the flightgear side > (maybe the aircraft-set.xml file?) to provide the actual view offset > point relative to the FDM reference point. > > Curt. > > > David Megginson writes: > > Andy Ross writes: > > > > > We're evidently talking past each other. What you say is true. It is > > > *also* true that, under YASim, you have non-zero pilot offset numbers. > > > These are (1) defined by the FDM, in conflict with similar definitions > > > in the model, and (2) in an apparently different coordinate space from > > > the one the viewer is expecting. > > > > > > The viewer must be using those properties > > > (/sim/view/pilot/x-offset-m), no? How else would the settings by > > > YASim be affecting the view location? > > > > OK, here's how I had understood things: > > > > 1. The FDM sets the plane's lat/lon/alt to the ideal pilot viewpoint. > > > > 2. /sim/view/pilot/*-offset-m are properties controlled by the user > > and/or the view manager, and are added to the lat/lon/alt supplied > > by the FDM. > > > > Here's how Andy understands things: > > > > 1. The FDM sets the plane's lat/lon/alt to the origin, which is any > > arbitrary point on the plane's body. > > > > 2. /sim/view/pilot/*-offset-m are properties controlled by the FDM to > > give the offsets from the origin to the ideal pilot viewpoint. > > > > I'd like to reserve the /sim/view properties literally for allowing > > the user to move around inside (or outside) the plane. If my #1 is > > not correct, perhaps we should all the FDMs to put offsets somewhere > > under the FDM hierarchy. > > > > > > All the best, > > > > > > David > > > > -- > > David Megginson > > [EMAIL PROTECTED] > > > > > > _______________________________________________ > > Flightgear-devel mailing list > > [EMAIL PROTECTED] > > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > > -- > 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 > > _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
