Perhaps you have set one of your comps to raytrace 3D. Check that.
I wish. Just double checked and everything is Classic 3D... Thanks, though. -s
Have you tried converting the expressions that the scripts use? Knowing how they work and use a kind of hack to do their thing and how that involves sampleImage() I would predict they are terribly slow to begin with. Animation Assistant --> Expressions to Keyframes wil lbe your friend if the scripts don't have such functionality built-in.
Thanks M, I tried that last night and it didn't seem to help... I'm starting to think my expectations were just way too high.
I've boiled the comp down to nothing but a bunch of 3d animated text and a camera that flies around it (with the indespensible help of the Type Monkey and Layer Monkey scripts), and it still seems slow to me. At least, it doesn't seem significanlty faster than my 2008 MP and that's just heartbreaking. The GUI experience is extremely sluggish as well. The time indicator sometimes takes a couple seconds or more to catch up. The "fast previews" don't seem all that fast to me.
Does anybody out there have some good reviews for the MP in AE? Similarly bad? I feel so alone right now, lol. At least the nMP is better-shaped for hugs. -s
Most of the time MP slows things down. Feel free to give it a try.
There may be recursive expressions in your project that are slowing things down but I can't tell without a revealing screenshot.
Other things to try, do your motion previews and tests at 1/4 resolution. Turn off effects and lights until you need them for final tweaking. Only used ray-traced rendering if there is no other option.
> The GUI experience is extremely sluggish as well.
You mentioned dual 27" monitors. Try disconnecting one of them and just using After Effects on a single monitor. Does the UI respond faster?
Also, as a separate test, try turning off Show Cache Indicators in the Timeline panel menu. One the thing that is makes navigation slow is the calculation to determine whether or not each frame in the cache is still valid, which can be very slow for compositions with expressions and certain time-based features. (BTW, I'm testing a fix for this right now, which we hope to make available in a release this spring.)