Jim Wilson writes:
> Sigh.  This is confusing.  If I'm not mistaken, the axes as I described them 
> are the way plib does them.  So apparently what I've got now is something that
> works well for plib people.
> 
> At this point I'm thinking we should go with that.  The body-axis convention
> doesn't work well for external views.  I'm sure that anything would work, but
> I'm not too keen on reworking that pilot offset dial thing again :-).  
> Basically my decision was based on the fact that the "Chase view" had it
> different than the "Pilot view" and making the pilot view the same as the
> chase view (a necessity to standardize the properties) meant a whole lot less
> code editing.  I realize that I can lie to the interface and tell it that z is
> y and y is z.  Guess that would be my first choice if we want to go back to
> "screen orientation".  Note that the view code looks nice now with the Ys and
> the Zs all lined up :-) ...and I kind of like it that way.

>From my perspective, we could do worse than to adopt the plib standard
for heading/pitch/roll ... then we can take advantage of all the built
in plib routines that use this convention.

I think conversion to the system used by the visuals will always be a
problem.  As I understand it, FDM writers are all over the map as far
as conventions chosen ... Steve Baker once had a rant about
integrating visuals with FDM's in his military systems was always a
challenge because of the convention differences.

What he did was write a wrapper for the FDM that translated the
orientation into some 'standard' quaternian form.  Then that
'quaternian' form of the orientation was translated into whatever the
visual system needed.

I don't think we necessarily need to use quaternians, but whatever we
do, we'll have to do some sort of conversion from FDM -> Visuals
... especially since we can interface with a wide variety of FDM's.

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

Reply via email to