Andrew, I apologize for the confusion; it's probably a result of my ignorance about the different kinds of controllers one might need. I should clarify what I meant by target controller (or what I thought you meant by it). Our desired use of SmartBody involves having characters point at and manipulate objects in the virtual world (i.e. like Stefan Kopp's ACE). This means that some sort of procedural joint control (like the gaze controller) for the arm joints is required. In contrast to the example you gave, we are interested in moving the character joints to match the world coordinates of a static or moving pawn. Perhaps you can point your comments along the lines of helping me understand the relationship between a tethering controller and the type of procedural controller I am describing? Can you also give me an example of when you would want to implement a tethering controller?
Alex On 8/20/08 1:58 PM, "Andrew n marshall" <[EMAIL PROTECTED]> wrote: > > Alex, > > I think we probably need to start with a shared vocabulary. Just to > clarify, what I previously called the target controller in the Roadmap > documentation is better described as a "tethering controller". That is, > it moves SbmPawn's world_offset joint (in world coordinates) to match a > position in the coordinate system of another joint. Hence, the pawn > appears tethered to the other coordinate system, as if it were another bone. > > I have a feeling you understood "target controller" to mean something > else, since you described walking and gaze as types of target > controllers (which they aren't, by the prior definition). > > I believe the confusion may come from the fact that gaze and walking are > behaviors that track targets. Our goal, and the reason for the original > terminology, is to abstract that target tracking behavior and associated > configuration into a new controller. Thus, as the tethering controller > and the configuration notations improve, all tracking behaviors share > those improvements. For instance, we could extend the behavior to > support the notion of "between" two reference points. > > We believe the tethering controller is a simple procedural controller to > start with, while still being useful for our goals. If this is still > the direction you want to pursue, I'll try to clarify my other > comments. Otherwise, please suggest an alternative direction, and I'll > try to help you along. > > > Anm > > PS - I'm finally updating the docs on building controllers. > Alex Hill Ph.D. Research Scientist Center for Technology and Social Behavior Northwestern University <http://www.alexshill.com> ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Smartbody-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/smartbody-developer
