#R4
<< Puppeteer is a full motion capture interface and motion data path editor >>
<< You can build your own IK or use data capture from Flock of birds. >>
<< There are going to be reasons to have both, and they will compliment each
other. >>
Traditionally, you'd have to build the IK skeletonal links & hierarchy, define
joint constraints, friction, etc. *_anyway_* – then assign sensor data to
appropriate joints. I can see IK as necessary or desireable with a M/C system.
Other than M/C being your desired application, what reason would there be to
have both ? And how will they compliment each other ? Are you saying that the
data structures for both systems is the same ? That would be a huge coincidence
or either indicate they've worked together on this. And if that's the case,
then I back to being a little puzzled again. If the IK system in Puppeteer is a
superior implementation, then I question the choice of IK as a provided
plug-in. Hopefully, as a "pure" IK system, the YG's will be much more robust.
If not, then I'm still puzzled – and I don't see how they will be
complimentary products unless they were a cooperative development. A quality IK
system is still very rare and difficult to produce, so I am surprised that 2
appear at the same time.
BILL