|
|
|
|
|
[
Permlink
| « Hide
]
Lex Neva - 12/Dec/07 09:50 AM
Now that I read your succinct description of this problem, I know I've seen it before. I think it also throws off calculations of percentages for loop in/out values.
To demonstrate this bug I have produced a short movie clip showing how it makes it impossible to make a low fps walk animation loop smoothly - this bug actually forces animators to use the highest fps possible to reduce it's effect! For these reasons I believe the bug's priority should be increased from 'Normal'.
The movie is available here: http://www.davedub.co.uk/downloads/too_many_frames.avi The bvh file is also available here: http://www.davedub.co.uk/downloads/female_poser_walk_8fps.bvh The attached bvh file is a loop of exactly one second without it's reference (t-stance) frame. When the first frame (t-stance) is added, the length becomes 1.125 seconds. I would expect the SL animation uploader to ignore the first frame when calculating the length of the animation. However, on upload we see that the uploader reports the animation length to be 1.13 seconds long instead of the expected 1.0 seconds. When the animation is played in SL, the first (or maybe last?) frame appears to be played twice, producing a break in the otherwise smooth animation. Steps to reproduce using the attached animation (female_poser_walk_8fps.bvh): Verify the animation length is exactly one second long + one frame (125mS for the t-stance) using any bvh file editor. Upload into SL - note the reported animation length at the top of the uploader Play the animation - note the complete loss of fluidity! Dave's video made me realize something else: When I've made looping animations in the past, I've chosen a total number of frames that led to an even whole-number percentage for each frame. For example, I'd choose 20 total frames (including the magic first frame), and then when looping, I'd set the "in%" to 5%. Without skipping that first frame, I'd see exactly what dave has shown.
Update: After reading Lex's comment, I tried uploading the same file using various In(%) and Out(%) values.
I tried: In(12.5%) (i.e. skip first frame, 100/8), Out(87.5%) (i.e. skip last frame 100-100/8), In(14.286%) (i.e. skip first frame, 100/7), Out(85.714%) (i.e. skip last frame 100-100/7), In(11.111%) (i.e. skip first frame, 100/9), etc etc None of these values did anything more than reduce the problem slightly. None of them actually made the problem go away. yep, i agree. Its getting worse as the viewers advance.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||