It sounds like you're hitting a couple corner cases where the global performance cache doesn't work as it should. It's a pretty new feature, but it's also quite complex, and there are still a few bugs like yours that need to be worked out.
In most cases, the global performance cache provides a big performance boost for users -- but when it doesn't, it is a bit painful to work around.
I'd suggest filing separate
bug reports [link] for your issues so that they can be fixed in future releases.
[stephane audrier] "I forgot to mention in my last message that the main comp is time remapped (twixtored, Cache Last Mention unchecked)."
Is that the latest version of Twixtor?
[stephane audrier] "By the way, i've got the same problem (persistent cache) in another comp with a different setup... In that comp i've a light animated with few bezier keys, it's set to be Emitter for Particular. And when i tweak a key of the light trajectory into that comp viewer (not main comp viewer), sometimes i've a "jump" of the trajectory (until i clear the cache of course) because all the last ram preview is still loaded except the frame where i was tweaking the key (where it's well updated)."
I can explain why it's happening: because there are no changes to the Particular layer itself, AE is not invalidating the cache for that specific layer when you move the light. AE does not see the relationship between the Particular layer and the emitter light layer, so it doesn't correctly clear the cache for the Particular layer when the light layer moves.
Again, sounds like a bug to me, and I'd report it.
Walter Soyka
Principal & Designer at
Keen Live
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
RenderBreak Blog - What I'm thinking when my workstation's thinking
Creative Cow Forum Host: Live & Stage Events