Clone corruptions tend to create errors like "Missing N6A46$98" or something associated with a crazy combination of numbers/letters like that. If you get this it's easy to open the script in a text editor, search for the number/letter and change that operator to a "NoOp", save, and re-open in Nuke. Key note is that when you open the script in Nuke, write down the error number and close Nuke but DO NOT SAVE or you will save the corrupted script and lose it.
As for the "Missing Close-Brace" that I started getting yesterday. I realized it had to do with larger scripts and finally narrowed it down to ones that had CameraTracker with multiple projections/3d/etc. These scipts can get larger and up to 5-10mb depending on what you have. After opening the corrupted script in a text editor and comparing the data to an un-corrupted one. You see that in the middle of the 30,000+ lines of numbers from the CameraTracker, that it just ends. No "close-brace", nothing from the script after the CameraTracker. Although via the GUI in Nuke, the [modified] in the script header had disappeared after saving. It actually takes it another second or two to finish writing to disk/server, especially if you're working over a network. So after saving, wait a minute or two before actually exiting the script/Nuke and this should prevent issues like this. I usually just type "exit()" in my script editor to make it instantaneous and this isn't a good habit and most likely caused this to happen. It all depends on your network speed too, so everyone's case will be different. Hope this helps, and if you got "Missing Close-Brace"....... Better start on your last version or re-making the comp because you won't be getting that script back unfortunately.
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
