This thread is great, I haven't seen this issue going around in a while! I was a compositor on Tron at DD, and that is exactly where this "channel virus" came from. The red guards were the armies of programs that CLU used as his muscle in the machine world of Tron. They can be seen in the background of many shots, and they wear helmets and carry spears which glow in some cases. The costume designers on that show did an amazing job. Those lines on the suits that glow were actually practical. However, there were some cases where they wanted the glow enhanced, or the electrical portions of the suits were malfunctioning, so we did this work digitally. Once a look was established, someone at DD made a gizmo for the glow enhancement, hence the redguard1.glow layer.
This thing is insidious. It quickly spread to pretty much every comp on Tron. Whenever you cut and paste a node from a script which has this layer, it would embed the layer creation code in the cut and paste stack, as someone on the list demonstrated. Every time a script was reused, a gizmo exported, or an artist shared some nodes with another artist, the channel virus was propagated. The redguard1.glow layer started showing up elsewhere in DD, it surfaced on Real Steel and Transformers 3. As mentioned previously in the thread, the only way to get rid of this is with a text editor, or if you're handy with sed or awk you can probably figure that out too. Every Nuke script in the entire facility must be checked, plus every single gizmo and Nuke script that is found in the NUKE_PATH environment. Don't forget user's home directories either. On Nov 19, 2011, at 12:07 PM, Dan Walker wrote: > I'm gonna try a show wide search for this in all our Nuke comps on Monday. > > Will let ya know what I find too. > > > > On Sat, Nov 19, 2011 at 10:38 AM, Diogo Girondi <[email protected]> > wrote: > I'll look for those in some scripts I have here. But I honestly don't > remember seeing any of those layers showing up in 6.3v2 and earlier versions. > > > On 19/11/2011, at 13:53, Ean Carr <[email protected]> wrote: > >> Well, what a coincidence. I just found a script at our facility with this: >> >> add_layer {rgba rgba.beta redguard1.glow} >> >> Fun times. >> >> -Ean >> >> On Sat, Nov 19, 2011 at 12:12 PM, Ean Carr <[email protected]> wrote: >> Our little "virus" layer is rgba.beta. Can't seem to get rid of the little >> rascal. -Ean >> >> >> On Sat, Nov 19, 2011 at 11:56 AM, Howard Jones <[email protected]> >> wrote: >> I've sent this to support - but it could be a legacy thing, I'm on 6.2v2 >> here so maybe 6.3 has the cure? >> >> Howard >> >> From: Dennis Steinschulte <[email protected]> >> To: Howard Jones <[email protected]>; Nuke user discussion >> <[email protected]> >> Sent: Saturday, 19 November 2011, 11:29 >> >> Subject: Re: [Nuke-users] ??? redguard1.glow ??? >> >> Fun, now that you mention it, I have had reguard and other written words in >> my nuke file as well as the RED GREEN BLUE thingie I posted a few days >> earlier. >> Reading through these posts i have seen some similarities here. >> I got an uncorrupted file for a show FileA_uncor with Nuke 6.0.1. There are >> python, tcl, expressions and all the "regular" stuff in it. Even with >> scripted import and whiteout footage nodes. >> Now I have got a new job where i need to get parts of the FileA_uncor. I >> copy/paste beaches of trees out of the old into the new Nuke 6.3.2 script. >> And after a short SAVE / CLOSE / RESTART NUKE, i have this strange behavior >> and i get FileB_cor with all the RED GREE … REGUARD, HORIZONT and other >> strange channel names i have never even created. >> Creating a fresh nuke 6.3.2 file, everything works as expected. >> This corruption even appears, when i copy these branches from 6.3.2 back >> into Nuke 6.0.1 . >> Ok my head feels dizzy now. >> I hope this report is kinda useful… >> Dennis >> >> >> >> >> On 19.11.2011, at 11:53, Howard Jones wrote: >> >>> Well I'm buggered - chasing up another issue and suddenly I see redguard!! >>> This script corrupted with {rgba.red, rgba.green..} appearing everywhere >>> which I fixed but every node has ( red green blue) in its label so below id >>> just from copying a grade node out and there it is! >>> No Tron Gizmo I'm aware of. >>> >>> Howard >>> >>> set cut_paste_input [stack 0] >>> version 6.2 v2 >>> push $cut_paste_input >>> add_layer {rgb rgb.red rgb.green rgb.blue} >>> add_layer {rgba rgba.beta redguard1.glow rgba.edgeblur} >>> add_layer {hilites hilites.red hilites.green hilites.blue hilites.alpha} >>> Grade { >>> white {1.933333278 1.684004068 1.478999972 1} >>> maskChannelInput hilites.green >>> name Grade145 >>> selected true >>> xpos -1158 >>> ypos -2623 >>> } >>> >>> >>> From: Howard Jones <[email protected]> >>> To: Nuke user discussion <[email protected]> >>> Sent: Saturday, 19 November 2011, 10:19 >>> Subject: Re: [Nuke-users] ??? redguard1.glow ??? >>> >>> Never seen it so I suspect it's not part of Nuke, >>> but now I've said that.... >>> >>> Howard >>> >>> From: Dan Walker <[email protected]> >>> To: Nuke user discussion <[email protected]> >>> Sent: Saturday, 19 November 2011, 4:47 >>> Subject: Re: [Nuke-users] ??? redguard1.glow ??? >>> >>> I've heard that this could have come from DD. If someone is reusing a >>> config/resource file home/.nuke and it's coming from another facility, >>> there is the possibility of contamination. >>> On Nov 18, 2011 7:56 PM, "Sam Cole" <[email protected]> wrote: >>> Could be totally off-base, but I recall that it's a glow gizmo/group >>> from Tron that people have kept using. >>> >>> ./sam >>> _______________________________________________ >>> Nuke-users mailing list >>> [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 >>> >>> >>> _______________________________________________ >>> Nuke-users mailing list >>> [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 >> >> >> >> >> _______________________________________________ >> Nuke-users mailing list >> [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 > > _______________________________________________ > Nuke-users mailing list > [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
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
