This finally explains the animation issues I noticed in https://github.com/rdeits/meshcat/pull/97 . It looks like the AnimationMixer internally uses the UUIDs of its clips to store or cache some information, but by default the clip parser doesn't actually assign a UUID. Without a unique ID, the clips seem to get their properties mixed up inside the mixer, resulting in one clip binding to the property of another. By setting a UUID at parse time, we can avoid the issue.
RussTedrake
commented
3 years ago
Fixes #105
This finally explains the animation issues I noticed in https://github.com/rdeits/meshcat/pull/97 . It looks like the
AnimationMixerinternally uses the UUIDs of its clips to store or cache some information, but by default the clip parser doesn't actually assign a UUID. Without a unique ID, the clips seem to get their properties mixed up inside the mixer, resulting in one clip binding to the property of another. By setting a UUID at parse time, we can avoid the issue.