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.
Right, but plib (and OpenGL) coders will not be a big part of our target audience. You are right that the aircraft body-axis convention has no special significance in external views, but then, neither does the plib/OpenGL convention. I think it would be best to be consistent within FlightGear, rather than consistent with external libraries. This might matter a lot because very soon we'll be adding user-defined payload weights for the FDMs (right now you have to edit the JSBSim or YASim config files to add them). We'll almost certainly have properties using the aircraft body axes for specifying the position and weight of each passenger, luggage pile, etc., and it might cause unnecessary confusion if the conventions for the view position have x=left/right rather than x=front/back. In many cases, we'll want to use the same coordinates for view and payload positions. > I'm not too keen on reworking that pilot offset dial thing again > :-). Fair enough. You've done your share on that, and until we get to a proper GUI overhaul, I can try to fix it for whatever we end up using. > Basically my decision was based on the fact that the "Chase view" > had it different than the "Pilot view" Yes, that's a bit of a nasty problem any way we do it. All the best, David -- David Megginson [EMAIL PROTECTED] _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
