This gear collision stuff is going in horrific circles, and I've clearly done a piss poor job of explaining it. Here is what I want, from the top:
I want a gear interface where I specify the following two (2) points in 3D space: One is the point of gear minimum compression, the other is the point of full extension. I want the scenery code to compute an intersection between the gear and the ground that lies between these two points, based on the scene geometry. I want the returned intersection point to disambiguate the following two edge cases: one where the gear minimum compression point is under ground, and one where the maximum compression point is above ground. If there are more than two geometry intersections along that line, I want the one closes to the minimum compression point. Forget anything else you might think I want. I don't want that. I want the above interface. That is all I want. I no longer claim (publically) that this interface is better. I no longer claim that any other interfaces are wrong. I just want them, OK? Does anyone have a reason why such interface should not be duly granted to the poor YASim developer? Speak now, or forever hold your, ... whatever. Did I mention that it's really a very simple interface? Andy -- Andrew J. Ross NextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com "Men go crazy in conflagrations. They only get better one by one." - Sting (misquoted) _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
