ok well i have seen enough from people to say that clone nodes are not
particularly stable without some sort of workaround.
thankfully we managed to get enough out of the corrupt script for it not to
have been a major problem.
cheers,
richard
___
On 30/03/12 00:50, Frank Rueter wrote:
yes, unfortunately this is very common and I stopped using clones for
this very reason years ago.
It's a shame it hasn't been fixed.
We can't reproduce this one - we know about it, but until we can
reproduce it, it's very difficult to fix.
If you've
i can see that it's very difficult to fix something if you can't
track down how it happens, but... doesn't the bug render the
current implementation pretty useless? i mean, is anybody still
using clones in real production and risks getting bitten by this?
for those who are not aware of it, a
the current
not quite perfect clone function
Howard
From: chris ze.m...@gmx.net
To: Nuke user discussion nuke-users@support.thefoundry.co.uk
Sent: Friday, 30 March 2012, 12:33
Subject: Re: [Nuke-users] Re: nuke script error
i can see that it's very difficult
Hi Peter,
We have a script that crashes every time we try to open it so can send you
that.
I think what might have made it go crazy was because we had clones of clones.
We have been able to salvage a lot of the work though thanks to Nathan's
suggestion of editing the script in a text
seems to
stem from an issue in the writing process itself (albeit not a particularly
consistent one).
-Nathan
From: chuckie7413
Sent: Friday, March 30, 2012 2:29 PM
To: nuke-users@support.thefoundry.co.uk
Subject: [Nuke-users] Re: nuke script error
Hi Peter,
We have a script that crashes
yes, unfortunately this is very common and I stopped using clones for
this very reason years ago.
It's a shame it hasn't been fixed.
On 3/30/12 12:15 PM, chuckie7413 wrote:
Hi Nathan,
Yeah there are a few cloned nodes in the script. Will take a look at
the script in a text editor and look
