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