I have a bug for this problem, bug 33643, but please log it yourself so that there is more priority to it. The problem comes when having expressions downstream of the node, for some reason this causes everything to evaluate on each stroke. The workaround is to do a copy of the roto that is not connected to the downstream nodes, work there and then reconnect. Check your tree, and let us know if there are any expression in (even in a gizmo) that might be causing this.
On Wed, Mar 20, 2013 at 12:22 PM, travisb <[email protected]> wrote: > Hey All, > > If I'm not mistaken, isn't the processing in your DAG and comp only supposed > to happen on what you are actively viewing? > > Because for quite sometime now I've noticed that while only viewing a single > read node and trying to do some quick roto or paint work efficiently only to > notice the rest of the comp is just processing away, making everything slow > as hell! > > I always thought this was sort of an important efficiency feature of Nuke > and I feel like it was working at some point or another but no longer does. > > **If I click off "highlight running operators" it seems to speed things up. > Although, shouldn't these operators not be running in the first place if I'm > not viewing them? I personally like to have this visual reference to > pinpoint bottlenecks in a comp, etc. > > Doesn't really seem to work as one would expect. Anyone view this as a > problem? > > Nuke7v04 Win7. > > Best, > Travis > > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users -- Jose Fernandez de Castro _______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
