The two interesting commands were:

add_layer {rgba rgba.UVdistort rgba.beta redguard1.glow rgba.warper}

add_layer {partial}

Also a bunch of legitimate layers from 3D renders, e.g:

add_layer {outDiffuse outDiffuse.red outDiffuse.green outDiffuse.blue}

However, adding those with nuke.tcl('add_layer ....') doesn't retrigger
the error, will need to narrow down what node(s) are causing the problem

On 25/11/11 20:39, Howard Jones wrote:
> Yes its getting to the bottom of that issue is what I'm interested in.
> Nuke shouldn't add these layers when not relevant, so these things cant
> propagate but is it what causes this...
> 
> Shuffle49.out: Can't select rgba.alpha; it conflicts with other selected
> channels
> 
> If this is from spurious layers being copied then there is an issue in
> Nuke, covered by that bug number which needs to be taken seriously.
> 
> Out of interest what was in the add_layer, as the fix I have used so far
> is probably a bandage.
>  
> Howard
> 
>     ------------------------------------------------------------------------
>     *From:* Ben Dickson <[email protected]>
>     *To:* Nuke user discussion <[email protected]>
>     *Sent:* Friday, 25 November 2011, 8:55
>     *Subject:* Re: [Nuke-users] ??? redguard1.glow ???
> 
>     Heh, this issue has got a bit out of hand..
> 
>     It's a bit untidy, but most of these layers shouldn't cause any problems
> 
>     ...however, adding channels to default layers like "rgba" can cause
>     problems under certain circumstances. For examples, we had a few renders
>     die with:
> 
>     Shuffle49.out: Can't select rgba.alpha; it conflicts with other selected
>     channels
> 
>     ..and that script had an add_layer that added a bunch of nonsense
>     channels to rgba. The extra channels also caused the Shuffle's "in2" to
>     default to a strange channel, and a few other odd things
> 
>     A quick way of checking the gizmos for stray layer names is:
> 
>     for x in nuke.plugins(nuke.ALL, "*.gizmo"):
>         f = open(x).read()
>         if "add_layer" in f:
>             print x
>             print "\n".join(
>                 ["    %s" % line
>                 for line in f.split("\n")
>                 if "add_layer" in line])
>             print
> 
>     ..although you also need to check regular .nk scripts, ToolSet folders
>     and such
> 
>     On 25/11/11 18:42, Dennis Steinschulte wrote:
>     > Hi Group,
>     > As promised yesterday, here comes the answer from the support.
>     > If you have additional infos or things not mentioned here, just write
>     > the support team with the BUG ID 23221.
>     > (Darn, I missed the bug 22222 ;) )
>     >
>     >>>>>>
>     >
>     > Hi Dennis
>     >
>     > 
>     >
>     > Unfortunately this appears to be a corruption from a third party gizmo
>     > and we would not be able to say how this could have been passed
>     from one
>     > party to another.
>     >
>     > 
>     >
>     > We have searched many machines here, and from our basic Nuke
>     install we
>     > don't see any references to redguard1.glow.  Also we don't have the
>     > following that are mentioned on the user group :
>     >
>     > 
>     >
>     > bokeh_blur_jb_v03_1.gizmo
>     >
>     > Bokeh_Blur.gizmo
>     >
>     > Keyer_CB.gizmo
>     >
>     > 
>     >
>     > or any references to :
>     >
>     > 
>     >
>     > rgba.beta
>     >
>     > alpha.G_matte
>     >
>     > rga.alpha
>     >
>     > horizon.matte
>     >
>     > 
>     >
>     > Our engineers have also made sure of this and this does not originate
>     > from the
>     >
>     > 
>     >
>     > standard Nuke install.
>     >
>     > 
>     >
>     > As this is something that has been propagated from an external source,
>     > there isn't really anything we can suggest apart from removing all
>     Nuke
>     > installs, all third party gizmos and clean through old scripts,
>     install
>     > a standard Nuke and see if that resolves the issue.  You may also want
>     > to check any init.py or menu.py references in your .nuke directory to
>     > ensure that a python script isn't being run somewhere that causes the
>     > issue.
>     >
>     > 
>     >
>     > I have written up a bug to see if we can restrict what can create new
>     > channels and this is logged as Bug 23221.
>     >
>     > 
>     >
>     > 
>     >
>     > Kind Regards
>     >
>     > 
>     >
>     > Jason
>     >
>     >
>     >
>     > _______________________________________________
>     > Nuke-users mailing list
>     > [email protected]
>     <mailto:[email protected]>,
>     http://forums.thefoundry.co.uk/
>     > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
> 
>     -- 
>     ben dickson
>     2D TD | [email protected] <mailto:[email protected]>
>     rising sun pictures | www.rsp.com.au
>     _______________________________________________
>     Nuke-users mailing list
>     [email protected]
>     <mailto:[email protected]>,
>     http://forums.thefoundry.co.uk/
>     http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
> 
> 
> 
> 
> _______________________________________________
> Nuke-users mailing list
> [email protected], http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

-- 
ben dickson
2D TD | [email protected]
rising sun pictures | www.rsp.com.au
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Reply via email to