AWS Thinkbox Discussion Forums

bug: realflow version not sticky + AE submit error

When submitting realflow from the deadline Launcher I notice that the realflow version & build aren’t “sticky”
Every time when the window is opened I have to select the right version (2013 instead of 2012) and the build (64bits instead of “none”)
I noticed for example that with after effects the version does stay “sticked” having altered it’s version

This brings me to a second point, I’ve copied the SubmitAETodeadline into the scripts section of AE CC.
And when I want to submit a job from AE CC I get the following error:
“Unable to execute script at line 290. root is undefined”

Could this have something to do with the fact that I haven’t installed AE CC in it’s factory default location?
This also applied to AE CS 5.5, but there it opens the script window at the following line:
sanityScriptPath = root + “\submission\AfterEffects\Main\CustomSanityChecks.jsx”;

Being highlighted in orange.

my custom paths are the following:
C:\Software\Adobe\Adobe After Effects CC
C:\Software\Adobe\Adobe After Effects CS5.5\

tnx!

Thanks! We’ve logged the realflow issue as a bug, which we should be able to fix before 6.1 is released.

For the AE submission problem, it sounds like you grabbed the SubmitAETodeadline.jsx file from the Main folder instead of the DeadlineAfterEffectsClient.jsx file from the Client folder. The DeadlineAfterEffectsClient.jsx file from the Client folder is the one you need to install on your workstation. It defines the “root” variable that the error message is complaining about.

Cheers,
Ryan

aah, yes… that solves it :slight_smile:

with DL 5 it was the submitAEtodeadline script if I recall correctly… hence the confusion.

Privacy | Site terms | Cookie preferences