max slow down after frame 800

[LFShade]

Try this first: type gc() into the MAXScript listener, and see if that gets your speed back up. If not, then just try saving, resetting, and reloading your scene. If all else fails, you can try the following:

Save a copy of your scene (use save as and give it a different name). Go to a point a hundred frames or so before the slowdown, let's say frame 700 (since you'll need a couple of seconds of action for reference) and lay down a keyframe on all your animated objects. Now go back and delete all keys before that frame. Re-save this copy of the scene, do a reset, then reload it. You can now finish animating, and the speed should be back up to normal. When it comes time to render, just render the original file to frame 699, then load and render the copy from frame 700 on. I recommend rendering to still frames, but if you choose to render to video you can stitch the two output files together in your video editing app of choice (you might be able to do it in video post?).

I hope you don't have to go this last route, since it's the least fun ;)

[CiF]

LFShade thanks for relpying !!!

your last solution was exactly what I want to avoid, I you can imagine ;)

I saveing and reloading doesn't change anything :(

So I will try the cg() in script listener ...

thanks ..

[CiF]

and by the way ... can you explain me that is gc() ????

it display 5336460 and its still damn slow :(-


so if you have time ... I would like to know about this command.

thanks again.

[LFShade]

gc() stands for 'garbage collect'. It basically attempts to clear out any dead objects (in the programming sense), variables, and other unwanted remainders left behind as Max goes about its business. It pertains to MAXScript, but since the script language is so closely tied in with much of the Max interface, you can end up with 'garbage' even if you don't do any scripting yourself. The number that it reports is the number of available bytes in the MAXScript heap after the garbage collection is done. Sometimes, particularly after long sessions in Max, gc() can speed things up a click or two.

I'm afraid that since I don't know exactly what's causing your slowdown, I don't have any more suggestions as to what you might do about it :hmm:

[CiF]

LFShade : great thanks for the info.

For my pb, I discover that if I delete one particular object, everything goe back to normal speed !!!!!

OUF !!!!

But I really don't understand !!!

I have one character, pretty light char, and he's holding an object, but not all the time so I use the link constraint which allow me to bind and unbind the object to the hand.

with this object ... slow, and more slower with more targets !!!
without this object, perfectly fast !!!!

Do you understand something at that ????????

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.