|
|
Same here – cache problems constantly and not real patterns or easy to reproduce. Mostly on 2014/15 so don’t even both to file bug reports. Just got to power through until film is done.
Best,
stephen van vuuren
336.202.4777
http://www.insaturnsrings.com/
A film is – or should be – more like music than like fiction. It should be a progression of moods and feelings. The theme, what’s behind the emotion, the meaning, all that comes later.
–Stanley Kubrick
From: After Effects Mail List [mailto:AE-List@media-motion.tv]
Sent: Thursday, December 14, 2017 9:52 PM
To: After Effects Mail List <AE-List@media-motion.tv>
Subject: Re: [AE] Cache bugs with expressions
I've had numerous cache issues with 2014, 2015, 2017 (haven't pushed 2018 yet). Not just with expressions either, it happens with plain timelines, convoluted timelines. No rhyme or reason. It just loves to hold onto old cache data. I can't
replicate it, it just does it when it wants to. I just learned to keep the Purge All Cache shortcut handy. "Ctrl + Alt + /" on PC.
David Torno
"The most useless day is that in which we do not laugh"
I’m playing round with a project that is based on an expression and I’m running into lots of cache bugs. I’m currently using CC 2017.
I’m just wondering if others have come across similar problems and if there are any workarounds.
The project I have uses a fairly lengthy expression which is applied to a text layer. The expression is also reading values from a slider. Other layers are then reading the output text of the text layer (ie the expression results) which controls their time-remapping
values.
It doesn’t take much for AE to stop working properly. I can move sliders around and nothing changes. I can completely change values and yet the RAM preview will play the same thing over and over. I can delete all keyframes, so in theory nothing should be
moving at all, yet scrubbing in the timeline still shows things moving around.
Basically, what I am trying to do is totally breaking AE’s cache system.
While I will report my problems to Adobe and will send them a project, I am wondering if there are some simple steps to avoid these issues.
Does anyone know if making layers shy, or setting them to guide layers, effects the way the preview system works? In previous versions, enabling motion blur has fixed cache bugs but this doesn’t seem to be the case here. I can RAM preview something and set
the same thing off as a BG render and get two different results…
Any suggestions?
-Chris
+---End of message---+
To unsubscribe send any message to <ae-list-off@media-motion.tv>
|
|
