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
