What version of Nuke 8 are you using, there was a bug in 8.0v6 and earlier that caused freezes like the one you are describing. (I think it was Bug 47008). Have you tried 8.0v7?
On Fri, Mar 4, 2016 at 8:00 AM, Daniel Hartlehnert <dah...@gmx.de> wrote: > Hi, > > sorry for cross-posting this from the forums, but i hardly got any > response there. > I tend to get this behavior in Nuke quite often with bigger scripts and it > just gets unusable. > The symptom is Nuke completely locking up when dbl-clicking a node to open > its properties. Usually it happens when dbl-clicking a roto or rotopaint > node. > Looking in the system monitor, i can see that 1 (out of 12) cpu’s is 100% > busy, and maybe, if you wait long enough, it will eventually be ok. > But i have waited for several minutes sometimes, still no go. > So the only option is to force quit out of Nuke. > The odd thing is, i can sometimes work in the same script for hours, then > suddenly the symptons start to show up. I even had it affect other nodes as > well. So dbl-clicking a merge node for example too ages. > I am on Nuke 8.0v6 on Linux. > > So my question is: are there any operations in Nuke that are single > threaded esp. regarding Rotos that could trigger this behavior? Have other > people seen this as well? > > Regards, > Daniel_______________________________________________ > Nuke-users mailing list > Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > -- Jose Fernandez de Castro
_______________________________________________ Nuke-users mailing list Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
