[Closed] Noticed ORT Script not remembered on reload
Here is the simple script to use with the supplied test file
FOO=$dummy* AS ARRAY
FOR X=1 TO FOO.COUNT DO
(
doo=foo[x]
setBeforeORT doo.rotation.controller #relativerepeat
setAfterORT doo.rotation.controller #relativerepeat
)
Load the file dummy test
Run this script, it works as expected, using relative repeat after frame 100.
Save the file
Load the file
All of a sudden all the ORT had gone back to CONSTANT!
This works for me using Max 2011.
How did you get the noise controller to start and stop? When I apply a noise rotation controller it’s always on, and I don’t see any options to start and stop it. Maybe however you got it to start/stop is causing it to not be saved for you.
If I apply a noise controller to one of your dummies and type in the same properties it loops forever. I understand loop is not relative repeating, but in your example they are effectively the same.
The noise controller was set on a 100 frame animation, and rest assured, when the scene is
extended to 300 frames, it will stop on frame 101 unless the script is ran each time on reload.
My Max is older than yours, and maybe this is the problem, or maybe my 3dsmax.ini needs
to be deleted.
So when you load the file, without running the script, it loops for you?
This is totally different from what I get, the loop stops at frame 100, and all the
dummies reset to “constant” ORT on the noise controller.
No, when I load the file they are on constant and the noise controller is active between 0-100.
If I follow your steps in the first post, when I load the max file they load as Relative Repeat. That what I meant by “It works for me.” I am using Max 2011.
My comment about getting the noise controller to start/stop is because if I apply a noise controller it plays forever. There is no need for me to turn on Relative Repeat. But in your file they are only active between frame 0-100.
I personally don’t know any way to make the noise controller start and stop at particular frame. It’s just always active.