Hello everyone,
I believe my problem is a case of me misunderstanding everything about rotation
I have a text file with a series of time and rotation values, in degrees : for exemple
0 : 91.0708
1 : 90.4475
2 : 90.467
3 : 91.077
4 : 92.4844
5 : 93.4939
6 : 99.1038
…
I read these values and assign them , frame after frame to the Y rotation of an object
at time t $Point01.rotation.y_rotation = val1
But the final rotation values received by the object are different
0 : 91.0708 => 91,071 – correct
1 : 90.4475 =>89,552 – wrong (is equal to 180-correct value)
2 : 90.467 =>90,466 – correct
3 : 91.077 =>88,923 – wrong (is equal to 180-correct value)
4 : 92.4844 =>92,484 – correct
5 : 93.4939 =>86,506 – wrong (is equal to 180-correct value)
6 : 99.1038 =>99,104 – correct
which makes the object flipping.
I really don’t understand what his happening. Why some values are passed correctly , while every others values are translated to (180- value) ? I guess this a subject of degrees and radians… but using degToRad made the whole thing completly erratic.
any help, explanations and pointers to the relevant pages of the help file pages will be greatly appreciated.
try this:
at time t $Point01.rotation.controller.y_rotation = val1
Rotation controllers are a little fuzzy to understand, at least for me. It seems like Max tries to interpret the rotation value, unless you put the value directly on the controller, as if you were putting the absolute value in the track view.
Accessing the $.rotation.controller.y_rotation instead of $.rotation.y_rotation, worked fine for me in the same situation.
I hope it helps,
cheers
M
It worked perfectly ! Thank you very much !