Expression errors in template

[Stefan Cargoski]

Hi community

I downloaded a free template and getting the following warning about expressions. Does it mean it will not render? Is it safe to keep on modifying this template, or should I get another one?

Thank you.

[Mylenium]

Without any info where you got this project from and what it's supposed to do, nobody can even guess if it will actualyl render without flaws. Start by actually expanding the expression warning pane with the rightmost arrow in the orange area and see what it says. You may also want to read the online help on expression basics. Since there are overall 97 errors it stands to reason that these are references to all the same global control e.g. for color or fade durations and when defunct of course this may pose issues. anyway, we realyl can't know with so little info at hand.

Mylenium

[Stefan Cargoski]

I wanted to practice with a free AE template to see how it is to swap images and text around, so I found this website here, which I got the AE template from.

https://mixkit.co/free-after-effects-templates/animated-3d-reveal-561/

[David Arbor · Accepted solution]

It's possible that the expressions in this template use old and incorrect syntax that's not compatible with the new, modern JavaScript expression engine. If this is the case, you have two options:

1) First, confirm that switching to the old engine makes all the errors go away by going to File > Project Settings > Expressions and changing the engine from "JavaScript" to "Legacy ExtendScript."

2) If doing that makes the errors go away, then you can keep working, but it would be ideal to stick with the modern engine. There is a script included with After Effects to update legacy expressions. To use this, you should switch back to the JavaScript engine by undoing step one then...

3) Go to File > Scripts > "Upgrade Legacy Expressions.jsx"

The default option is to update all expressions in all compositions. Choosing this option will give you a warning saying that your project will be backed up. If anything goes wrong you can always go back to the backup version.

If switching to the Legacy ExtendScript engine in step one doesn't make all (or most of the errors) go away, then Mylenium's suggestion is likely correct.

[Stefan Cargoski]

I tried the first method to change the engine, so from 90 errors, I only got 9, which was a massive improvment, and then I tried to Script to Upgrade Legacy Expressions, and the errors went away like magic. Thank you for the input, was helpful.

Kind regards.

[David Arbor]

Glad to hear it worked. You should try switching back to the JavaScript engine now because that can provide better performance. If you don't get any errors you can leave it, but if you do, you can switch back to the Legacy ExtendScript engine. 

[Stefan Cargoski]

I made the switch, and all the errors appeared again, so I just left it as it was for the current template.

Kind regards,