We've experienced something a bit similar when decloning nodes (no facility code involved, just plain vanilla Nuke). We first noticed that back on 6.3 and it still seems to be an issue on 9.x.
On Mon, Jul 13, 2015 at 4:57 PM, niki <[email protected]> wrote: > Hello > > > long time since I used this list so please excuse me if I am repeating a > bug that may be already known. > > I'm currently working at Cutting Edge in Sydney and we have noticed a > pretty bad bug in both v08 and v9.0v5. > At some point after working on a shot for some time our scripts become > corrupted and on Save the merge inputs swap randomly between the matte and > a side or jump to different nodes all together. > > So far we have noted that it seems to be only the A stream and the Matte > that is affected. The B stream seems to remain correct. > > The only solve we have found is to remove all merge nodes. > Save file > Replace all merge nodes. > > Has anyone else seems this ? > > Many Thanks > > Niki > > > > > [email protected] > www.nikibern.com > > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > -- "Attention, attention. Here and now, boys," the mynah repeated. "Here and now, boys."
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
