You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following parameters used in the script were NOT found on the JSON "parameters" object of your script asset file:///c:/hello.jsx
t, t
Please set defaults in your JSX script (see documentation) or copy the following placeholder JSON code snippet and replace the values with your own:
"parameters" : [
{
"key" : "t",
"value" : null
}
{
"key" : "t",
"value" : null
}
]
Remember to always use a fallback default value for any use of the NX object to have the ability to run this script on After Effects directly. Example: const dogName = NX && NX.get("doggo") || "Doggo";
I know that this is not the best example, but what i really don't understand is,
that no matter what key i wanted to get. It always tells me that i should insert 't'.
And if i really add 't' as a key to my json, the error-message is gone.
So for some reason the parser is always looking for a 't'.
Tested with the latest version of nexrender-cli.
The text was updated successfully, but these errors were encountered:
Yes, I second that! It drives me nuts as well! Until finding time to fix it, our scripts do also have parameter "t" everywhere...
Might be your step into contributing, @jbojbo, what do you think? :o)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I always get the following error-message:
my json:
my jsx:
I know that this is not the best example, but what i really don't understand is,
that no matter what key i wanted to get. It always tells me that i should insert 't'.
And if i really add 't' as a key to my json, the error-message is gone.
So for some reason the parser is always looking for a 't'.
Tested with the latest version of nexrender-cli.
The text was updated successfully, but these errors were encountered: