Wait - are you referring to clone brushes or cloned nodes? We have the former but not the latter.
I was the artist on the Mavericks workstation and used clones a fair amount through the project, without problems... On Nov 27, 2013, at 8:54 AM, Richard Bobo <[email protected]> wrote: > I have gotten into the habit of making sure to, first, De-Clone any nodes > that I am copying and pasting from one script into another. Otherwise, it’s a > sure way to screw things up.. > > Rich > > > On Nov 27, 2013, at 11:38 AM, RsLittle <[email protected]> wrote: > >> Its the clones. Ones that did corrupt WILL at the worst possible time. >> Clones are russian roulette. >> >> >> From my Android phone on T-Mobile. The first nationwide 4G network. >> >> >> >> -------- Original message -------- >> From: Craig Tozzi <[email protected]> >> Date: 11/27/2013 11:28 AM (GMT-05:00) >> To: Nuke user discussion <[email protected]> >> Subject: Re: [Nuke-users] Mocha rotospline imports corrupt scripts on >> Mavericks >> >> >> He did, but there were other rotopaint nodes in the scripts from this >> project that didn’t come from Mocha (also using clones) that didn’t cause >> any problems. >> >> >> >> >> On Nov 27, 2013, at 8:22 AM, Randy Little <[email protected]> wrote: >> >>> are you sure thats not the "CLONE Bug" Sure sounds like it. did the >>> artist on Mavericks CLONE something. (anything) >>> >>> >>> >>> >>> On Wed, Nov 27, 2013 at 11:17 AM, Craig Tozzi <[email protected]> wrote: >>> Discovered a weird bug on this project we’re wrapping up: >>> >>> An artist using a Mac workstation running Snow Leopard had used Mocha Pro >>> and imported a rotospline into Nuke (7.09). He continued to work on the >>> shot with no issues. >>> >>> That Nuke script was later loaded onto another workstation that was running >>> Mavericks and Nuke 7.09. The shot was worked on further for about a half a >>> day, with multiple versions being saved. >>> >>> The problem: once the script was closed, it was found corrupt upon >>> reopening, with <missing close brace> and EOF errors. This ONLY occurred >>> if the script was opened and saved under Mavericks. Earlier versions of >>> the script that had only been used under Snow Leopard would open and close >>> without problem. >>> >>> It’s an ugly thing to find out, as you can go for a time before discovering >>> that your script has blown up. >>> >> >> _______________________________________________ >> Nuke-users mailing list >> [email protected], http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > > > > Rich Bobo > Senior VFX Compositor > Armstrong-White > http://armstrong-white.com/ > > Email: [email protected] > Mobile: (248) 840-2665 > Web: http://richbobo.com/ > > "The greatest achievement of the human spirit is to live up to one's > opportunities, and to make the most of one's resources." > - Vauvenargues > > _______________________________________________ > 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
