Yes. Many, many times I have seen that Nuke loads nodes that are not required by the rendering Write node. This is especially frustrating with Read nodes and the "Too many open files" issue. To get around this issue, I have written scripts that disable all Read nodes that are not upstream of an active Write node.
On Wed, May 18, 2011 at 5:06 AM, Gerard Keating <[email protected]> wrote: > This was in Nuke6.2v3 64 bit linux > > On 18 May 2011 13:05, Gerard Keating <[email protected]> wrote: > > Hi, > > I recently had a nuke render taking more then an hour. I opened the > > script and deleted the nodes that were not being used ie the ones that > > were not connected in anyway to the write node via expressions or > > clones or any way. I re-rendered and the script went through in > > seconds. > > I always thought that if a node is not in use it would not affect the > > render time. Was this assumption wrong? Has anyone else noticed this > > behaviour? > > Regards, > > Gerard Keating > > > _______________________________________________ > 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
