> Alain <kua### [at] videotronca> wrote:
>
>> Would it be that your first frame had 2 object or less? Then, you add
>> some objects each frame.
>> In this case, the bounding don't kick in in for the first frame, and
>> stay disabled for the rest of the animation.
>
> In looking back over my notes about my own problem scene, you're indeed correct:
> I started off with only 1 object in the first frame of my animation, and added
> an extra object for each new frame. (The Bounding_Threshold was as its default
> of 3.) That caused a tremendous slow-down in the render, as the frame count went
> up. Turning Bounding_Threshold to 1 (or even zero) does eliminate the problem,
> as you suggested.
>
> The Subset_Start_Frame=2 trick also works--for reasons unknown! I was aware,
> from a long-ago newsgroup post, that whatever number of objects that are in a
> scene at frame 1 sets the Bounding_Threshold for an entire animation (or
> something like that.) So starting the animation at frame 2 seems to bypass that
> 'initial setting' in some way(?)
>
> Ken
>
>
>
>
It's probably that, at frame 2, you allready have at least 3 objects, 
triggering the bounding for all subbsequent frames.
That's why it's suggested to add some invisible object in an animation 
that start with less than 3 objects in the first frame, but get more 
objects as it progress. That way, you force the bounding for the first 
frame.

Post a reply to this message