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 possible workaround is to
use the shakestyleclone script instead.. on nukepedia:
http://www.nukepedia.com/python-scripts/nodegraph/nshakeclone/
i tried to assemble all of the latest sugestions in the comments
into a new version without messing things up.. still seems to
work ;)
http://pastebin.com/JFaVgyX8
how about adding something like this to the default install of
nuke instead of the old clones?
actually i even it to true clones in some ways (for example you
can choose to keep certain parameters unlinked).
++ chris
On 3/30/12 at 10:40 AM, pe...@thefoundry.co.uk (Peter Pearson) wrote:
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 got a script where it's consistent to reproduce
(I'm assuming it's temperamental and random though, so
probably not that easy), please send it in to support.
Thanks,
Peter
_______________________________________________
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
