I can confirm that on W7, Nuke 7.0v5 we're getting copy errors a lot. It's completely random though, and can work hours before it happens. Right after you get a copy error, it continues to happen more often, strangely enough.
2013/3/31 J Bills <[email protected]> > I was getting this on 7.0v2 but it went away when upgrading to v5 for me. > But apparently it's still crashing for others on v5? > > btw - when I was stuck on 7.0v2 for a couple of days, I was able to work > around it by first pasting the node stack into Vim, and then recopying and > pasting into Nuke. strange one, for sure. > > > > On Sun, Mar 31, 2013 at 9:39 AM, Remco Consten <[email protected]> wrote: > >> >> Same problems here on nuke 7.0v5! Very frustrating. >> >> >> >> Op donderdag 7 maart 2013 schreef Michael ( >> [email protected]) het volgende: >> >> > I am still getting this in 7.0v5 and its on Ctrl-C (Windows 7) >> > >> > Noggy wrote: >> > It usually happens on the Paste (Ctrl+V). It also is as simple as a few >> grades/cc nodes and it still freezes. >> >> _______________________________________________ >> 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 > -- Cheers / Torbjorn
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
