Hey, We have a setup where all read-nodes get their filepath from one Noop-node. Have been working great for updating all CG in a shot at one place instead of 50.. But now we have problems with a lot of lag in Nuke.. even if you're just looking at one node.. Feels like all the readnodes tries to read their path all the time, is there a way to halt expressionlinks to a noop-node from being active all the time? Or is it something else, someone recognize this problem?
So what the expression does is basicly reading filepaths from a Noop, nothing fancy. Just that there is like 50 reads or so. /Calle Calle Granström | Compositor V I S U A L A R T | www.visualart.se<http://www.visualart.se/> Email [email protected] | Phone + 46 (0) 73 5598477 | Office + 46 (0)8 15 32 00 Hälsingegatan 45| SE - 113 31 Stockholm Sweden
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
