Re: [Nuke-users] Re: ??? redguard1.glow ???

[John RA Benson]

missing brace? If the script doesn't load and it's due to a variable that has something like myKnob {} and it should be myKnob {0 0} (or whatever), then yes. If it's a case where the writing of the script doesn't complete and the end brace is missing, sadly, that's always a dead end. also finds bad clones and helps out there too. I included a broken script at the end of the cookbook to show what it's fixing. Basically, if you launch a script and you get the "nothing is named /path/to/my/script.nk", chances are that this will recover it. No guarantees of course - there's a lot of mysterious stuff that kills scripts - but it's helped out loads here and is a good starting point for adding other fixit loops as a general purpose cleaning tool. jrab John Vanderbeck wrote: Very cool.   Does this have any hope of fixing missing brace errors, or are those scripts really just toast? We have been running into it more and more and more lately :(     From: nuke-users-boun...@support.thefoundry.co.uk [mailto:nuke-users-boun...@support.thefoundry.co.uk] On Behalf Of John RA Benson Sent: Thursday, April 12, 2012 7:49 AM To: Nuke user discussion; Nuke Python discussion Subject: Re: [Nuke-users] Re: ??? redguard1.glow ???   This thread finally prompted me to do some sharing - I've fixed a lot of bad layers in scripts with some simple python (well, with regular expressions, which are simple but can be confusing). Some of these scripts were recovered from dead because of broken clones or empty {}. The usual... http://www.nukepedia.com/python/regular-expressions-re-module-to-fix-broken-scripts/ The tips not only clean up dummy layers like redguard - whatever you need to clean up - but also address some of the other issues that bugger scripts, like bad clones and the weird {} issue. Since it's just working on text, the script works on gizmos (often the source of mystery layers) that might have junk in them as well as nuke scripts that have been infected. Flavor to taste and enjoy - jrab Frank Rueter wrote: Yeah, this is the single most annoying/dangerous bug in Nuke. I've encountered this numerous times over the years (since D2Software days actually). It would be really nice to have some sort of collision handling if anything threatens to interfere with the default channel sets. Have you done a text search for the fully qualified channel names ("redguard.whatever") in all of the files in Nuke's plugin path? On 4/10/12 7:47 AM, thoma wrote: thanks frank - i did just that and it has worked so far. The strange thing is I did find one gizmo that had a redguard layer in there but not with all of the channels that were showing up in my script - also no hint of why they would start replacing rgba. Anyway thanks Thomas _______________________________________________ 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   _______________________________________________ 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   _______________________________________________ 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

_______________________________________________
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