Keyframe update delay and dopemaster

[lmilton]

Not sure. Does this happen only on complex scenes? Approximately how many channels are you dealing with in your tests?

Also, has anyone else out there encountered this?

-lyle

[WesComan]

Could this be the lag caused by the autosave backup file being written?


Whilst we're on the subject Lyle, could we have the progress bar show that the backup file is being written? I get a few comments from people new to messiah saying that it 'lags' quite a bit and I think that this is mostly as the autosave kicks in and writes the backup file (in large scenes it can feel that messiah freezes for a few seconds). If we can see that something is happening it would help folks understand what's going on.

[SpikeWorx]

I have always deactivated the autosave function.

Not sure. Does this happen only on complex scenes? Approximately how many channels are you dealing with in your tests?

Also, has anyone else out there encountered this?

-lyle
No, not on every scenes. Just some, e.g. the Hulk Rig of zoogono, or Monte1.
Shifitng in all items mode works for a while, shifting keys aroound. After a while the keyframe update slows down. I´ve tested my ram with different software. It´s ok .
I´ve tested the memory usage level. The memory usage monitor history normally increases a little when shifting a bunch of keys. That´s ok. And back again after a while.
But in these complex scenes and all items mode after shifting a while, it doesn´t!
First it works a while, but then it slows down.
The memory usage keeps on an high level, without decreasing back to a normal level as it should and does normally.
Yes, I know that it often takes a while for Win, especially 2000 to free the memory. But in this case, it doesn´t comes to a normal level again after the slowdown.
No matter how long I wait. Just a clear scene in Messiah sets the memory usage to the normal level again.
I haven´t these problems with other programms.

[Freebooter]

Hi, hope no-one minds me jumping in here...

Well, having built that "hulk" rig, I can tell you now that it isn't really much good for animating with unless you turn the bulge effects off. I found that because of the way I implimented it, the bulges slow the feedback down quite a bit. You can just turn the bulges back on once you've done the animation. Also, if you're using the key all setting, you're probably making a lot more keys than you actually need to animate with.

Hope it helps,

Nic

[SpikeWorx]

Hi, hope no-one minds me jumping in here...

Well, having built that "hulk" rig, I can tell you now that it isn't really much good for animating with unless you turn the bulge effects off. I found that because of the way I implimented it, the bulges slow the feedback down quite a bit. You can just turn the bulges back on once you've done the animation. Also, if you're using the key all setting, you're probably making a lot more keys than you actually need to animate with.

Hope it helps,

Nic
Yes, thank you :) But it´s not a scene specific issue.
The problem is that at a specific level of complexity the memory consumption doesn´t go back to a normal level. Normally it does in Messiah.
Just not in this specific situation with dopemaster on complex scenes with lots of items where it seems you need a lot of ram to shift the keys around.
It´s like that.
First I shift keys around, the memory usage goes up. Wait a minute or two, it doesn´t goes back after the shift. It´s fine at this point though.
No slowdown because the level still is relatively low. Shift again and the memory usage goes up more. Every shift adds more to the usage. It doesn´t decline and at a specific consumption level, the slowdown occurs.
It does if I use the clear scene funtion, but not automatically after the shifting slowdown.

Maybe it´s important or not. I have deleted the Python and autorig plugins from the plugin directory.

[SpikeWorx]

*bump*********

[SpikeWorx]

Bump again.
Hey Lyle or any other from pmg. Any input on this? :)

[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.