You can get round the auto save easily. I set auto saves to a local drive on all machines before, and we still had it recognise there was a new version available.
Just As deke mentioned but I never had any issues of it not noticing the latest auto save. Though to mention it was an issue on Linux too. Or to be precise, nuke was attempting to save 20mB files to a stressed network every 30 secs across 50+ compers. Once it was set to save locally and proxies used as a local copy (pre localise) most stress on the network was removed. Not sure about the prerender. Can you keep and split out what you're using and prerender the rest? Howard On 19 Apr 2013, at 21:56, Michael Garrett <[email protected]> wrote: > Also, I can't really precomp the roto because I'm using bits and pieces all > over the place but it's a good idea to keep in mind to prevent the autosave > activity. > > On 19 April 2013 16:55, Michael Garrett <[email protected]> wrote: >> Is this a slowdown on all platforms or just Windows? I never noticed this >> under Linux. It's much better when I turn "echo python output" off, but I >> want it on. Or, maybe there is a callback I can add that will disable output >> when pasting roto nodes? >> >> This is a fair amount of roto and adds about 80 MB to the size of the script >> - which has issues re: autosave as mentioned by Deke in the other thread. >> I'm on Windows 7 64 bit/Nuke 7.0v5. >> >> Thanks, >> Michael > > _______________________________________________ > 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
