someone else might have a better answer, but off the top of my head, if you put "hasError" in the disable knob of the offending node, I believe that will fix it.
On Wed, Oct 12, 2011 at 4:53 AM, Dorian Fevrier <[email protected]> wrote: > Hi Nuke users, > > I'm searching something that appear to be simple but I don't find any way to > do this. > > I have a Gizmo node with some switch and read nodes inside. > > Following the case, the read node can have a bad file value (generated by an > expression) and be in "ERROR" and "ERROR" is wrote on the Gizmo. > > Is there a simple way to avoid this node to return his "ERROR" state on the > Gizmo? > > Actually, the error message is write on it but, because I use switch, the > gizmo work perfectly... > > I hope someone already encountered this before. > > Thanks in advance, > > Dorian > _______________________________________________ > 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
