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], 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
