Thanks everyone! Very helpful, will report back. On Sat, Oct 3, 2015 at 10:13 AM, Jean-Francois Panisset <[email protected]> wrote:
> > On Windows you want to use the "Windows Process Monitor" utility: > > https://technet.microsoft.com/en-us/library/bb896645.aspx > > This will show you every system call made by Nuke (similar to strace on > Linux), and in particular which file paths it is trying to access. That > should allow you to discover if there are any weird paths to weird / slow / > retired servers being accessed. > > JF Panisset > > > >> We run Nuke from network location and this issue seems to be a hit and >> miss >> for us. Sometimes it's all fine and sometimes this starts happening. I >> haven't investigated as it's not a common issue. But when it happens I get >> to hear about it. For some reason it seems to plague some users more >> frequently than others. >> >> I recall that we used to have favorites set globally which pointed to old, >> non-existing paths. And when removing those the file dialog responded >> immediately. Not sure if this solved the issue completely for us as I've >> been on an extended parental leave. >> >> // Fredrik >> >> fre 2 okt 2015 kl. 21:49 skrev Erik Johansson <[email protected]>: >> >> > We had to setup a routine for syncing to local drive for all our >> scripts. >> > Keeping it on a network share made everything dread slow. Also in Maya >> but >> > no issues in either app on Linux. >> > On Oct 2, 2015 9:46 PM, "J Bills" <[email protected]> wrote: >> > >> >> Hi all - have a couple of machines now that seem to have a strange >> >> problem where opening Nuke, creating read nodes, write node file >> browsing, >> >> etc is taking a *really* long time. One of them takes 30 seconds, >> which >> >> you know... 30 seconds, meh, but it's not the snappy Nuke popping up >> that >> >> I know and love. And it's definitely annoying when you hit a read >> node and >> >> have to wait. Ok, and the other machine can take up to 10 minutes, but >> >> seems to be the same symptoms. So something is definitely wrong there. >> >> >> >> This is Nuke 9 on Windows 7. >> >> >> >> Doesn't seem to be when it hits our custom scripts - the delay seems to >> >> be with just plain starting up. Maybe something with the license >> server? >> >> >> >> Anyone run into this before? I don't notice anything in the shell. It >> >> might be some obscure network setting that's causing it, maybe some >> sort of >> >> windoze thing that I need to turn off. I might try turning off ipv6 >> on the >> >> machines... or something. Not sure. Will play with it soon and >> wondering >> >> if you all have any ideas. Thanks! >> >> >> > >> > > > _______________________________________________ > 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
