 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
||||||||||
 |
 |
 |
||||||||||||||||||
 |
||||||||||||||||||||
 |
||||||||||||||||||||
 |
||||||||||||||||||||
 |
||||||||||||||||||||
 |
||||||||||||||||||||
 |
||||||||||||||||||||
 |
 |
 |
 |
|||||||||||||||||
 |
23.03.03 We begin new project on the ocean coast. We begin new project on the ocean coast. We begin new project on the ocean coast. want more details... 23.03.03 We begin new project on the ocean coast. We begin new project on the ocean coast. We begin new project on the ocean coast. want more details... |
|
 |
|
Contains a modification to the way BVH file data is converted to Poser(r) rotations. In general, the creation of rotation values should be much better, and there should be many fewer frames which show bizarre bending problems and grossly exaggerated rotations (more than 360 degrees). There will always be some positions that will need to be custom finessed for best appearance. But, there is a cost to this improvement. The values will not be as continuous over time as they were before. The animation will be smooth, but the curves may seem to show discontinuities (similar to using Quaternion interpolation). So, attempting to resample the keyframes so that there are fewer keys will probably produce some bizarre interpolations in between keyframes. But most users of motion capture data don't seem to need to do this keyframe reduction, so the new computations should be better for most people.So, attempting to resample the keyframes so that there are fewer keys will probably produce some bizarre interpolations in between keyframes. But most users of motion capture data don't seem to need to do this keyframe reduction, so the new computations should be better for most people. |
|
||||||||||||||
|
|
||||||||||||||||||||
 |
||||||||||||||||||||
 |
 |
 |
 |
|
||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|