googlo
06-29-2002, 11:22 PM
Hey everyone,
I was starting to set up an animation today using a set of slider manipulators and I found something really unusual. I don't know if this is a bug or not, but it sure seems like it.
Ok. I've found that when you set up slider manipulator, it's range of values only work over the number of frames in the animation at the moment of it's creation.
Example.
Lets say you start off with an animation default of 100 frames. Then you make a slider and set its min/ max values 0/500 respectively. Make a cube, and for it's rotation parameter in track view give it the EulerXYZ controller. Now wire the sliders value to the cube's z-rotation component, and set the flow to <-> (both ways) so that the slider controls the cube rotation, and if you rotate the cube manually, it shows up on the slider.
Now before you close the wire parameters dialogue box, make sure the 'value' variable in it's corresponding Expression box has this expression mulitplied to it (pi/180):
in the end it should read like this: value*(pi/180). this is just so that the the slider values are converted to radians for use in the EulerXYZ controller.
Ok, now that it's all set up, change the animations length to something like 200 total frames.
Here's where the glitch shows up.
Try keyframing from frame 0 to frame 200 the entire range of the slider. It won't let you do it, or more I mean, it won't capture the entire range of the slider. It's like the slider gets stuck on operating or 'seeing' only the animation frame range that existed at the moment of its creation!
Anyone else see this happening?!
I was starting to set up an animation today using a set of slider manipulators and I found something really unusual. I don't know if this is a bug or not, but it sure seems like it.
Ok. I've found that when you set up slider manipulator, it's range of values only work over the number of frames in the animation at the moment of it's creation.
Example.
Lets say you start off with an animation default of 100 frames. Then you make a slider and set its min/ max values 0/500 respectively. Make a cube, and for it's rotation parameter in track view give it the EulerXYZ controller. Now wire the sliders value to the cube's z-rotation component, and set the flow to <-> (both ways) so that the slider controls the cube rotation, and if you rotate the cube manually, it shows up on the slider.
Now before you close the wire parameters dialogue box, make sure the 'value' variable in it's corresponding Expression box has this expression mulitplied to it (pi/180):
in the end it should read like this: value*(pi/180). this is just so that the the slider values are converted to radians for use in the EulerXYZ controller.
Ok, now that it's all set up, change the animations length to something like 200 total frames.
Here's where the glitch shows up.
Try keyframing from frame 0 to frame 200 the entire range of the slider. It won't let you do it, or more I mean, it won't capture the entire range of the slider. It's like the slider gets stuck on operating or 'seeing' only the animation frame range that existed at the moment of its creation!
Anyone else see this happening?!