Ok, I really hope this isn’t a bug, but I have a rig that is linked to my Camera’s Target Distance value. For some reason, my rig works fine when I animate the Target Distance but it completely stops responding after frame 83. Meaning, whatever position the rig is in at frame 83 is the position it stays in for the remainder of the animation. Anyone have ANY idea why this would happen? I am not using any “at time” commands in my Script Controllers. Target Distance is being called with $Camera.Target_Distance and the controller assigned to it is Bezier Float.
Thanks!
Sean
A bit more information: I am merging this rig into a scene that is 900 frames. The original max file that contains the rig has 80 frames, which coincidentally is the number of frames that actually work. I’m wondering if there is some sort of parameter for controller length that is preventing my merged script controllers from evaluating past frame 80?? Maybe this will help to shed some light on this problem…
Sean
I went into the Dope Sheet and noticed that some of my Script Controllers only had their ranges set from 0-80. Obviously, this is the problem. Is there a quick way to run a script that extends all the controller ranges to a set value? Jut curious. The problem is basically solved, but a script access to the Controller ranges would be nice.
Sean
Originally posted by slooper
[B]I went into the Dope Sheet and noticed that some of my Script Controllers only had their ranges set from 0-80. Obviously, this is the problem. Is there a quick way to run a script that extends all the controller ranges to a set value? Jut curious. The problem is basically solved, but a script access to the Controller ranges would be nice.Sean [/B]
Yes, this is a typical problem with controller ranges (with wire, expression, script and other non-keyframe controllers)
There are lots of scripts dealing with it, too.
Go to http://www.scriptspot.com and get one.