Hello -
We're occasionally getting a very hard to understand error message:
'Nothing is named
"/path/to/my/script"'
however, the path does NOT include the .nk extension.
I've managed to fix scripts by
deleting {}
removing "version ..." in the script header (we rolled back to 6.2v1
from 6.2v3 - v3 scripts in v1 would error)
finding some enumeration knobs that had integers for values instead
of text
but a lot of times it's just weird and a mystery (as if the above
aren't). Some cases half the script is missing - the {} cleanup and enum
fixes allowed the script to open completely (without the error message).
Other times it's ignorable (the version). In one case, turning off
postage stamps fixed it (too many open files?).
I've grepped through the scripts, but can't find what tosses up the
error (part of the Nuke binary?) so I can't pinpoint where it's being
triggered. Any ideas? A little more information in the message would be
nice.
Thanks
JRAB
_______________________________________________
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
