Re: [Nuke-users] Re: nuke script error
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 -- Peter Pearson, Software Engineer The Foundry, 6th Floor, The Communications Building, 48 Leicester Square, London, UK, WC2H 7LT Tel: +44 (0)20 7434 0449 Web: www.thefoundry.co.uk The Foundry Visionmongers Ltd. Registered in England and Wales No: 4642027 ___ 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
Re: [Nuke-users] Re: nuke script error
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
Re: [Nuke-users] Re: nuke script error
I use clones all the time and very rarely get bitten but 1) I know how to fix the script 2) I'm aware of the bug so I am careful about how I delete clones which I think is the heart of the problem I use the 'shakeClone' with a couple of modifications less often - mainly when I want to break a link. (I renamed it 'expressionClone' here as that is almost what it is, and not everyone these days has used shake, and added labelling so you knew which is the master/clone node(s) without having the expression links on) Obviously a fix is desirable but I certainly wouldn't want to lose 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 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 ___ 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
Re: [Nuke-users] Re: nuke script error
Well, it’s not so much a matter of getting ahold of scripts with corrupt clones... it’s a matter of being able to reproduce the clone corruption in the first place to track it down. Once the nodes have been written to the Nuke script, there isn’t a whole lot you can deduce, since the corruption 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 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 editor. Thanks, Richard ___ 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___ 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
Re: [Nuke-users] Re: nuke script error
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 for anything like that. Is this very common then when using cloned nodes? Should we avoid it? Thanks a lot. Best, Richard ___ 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 ___ 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
