hi all, i faced that issue a few years ago, autosaving was taking my hands off Nuke and took such a long time. i was on window, and autosaving through network. so i changed my autosave preferences to a local drive. the issue went away. i kept this setting adding the minutes in the autosave file : [getenv AUTOSAVE_PATH]/[file tail [value root.name]]_[date %M].autosave
(the AUTOSAVE_PATH is seted in my nuke_launch.sh file, but could be easily seted in menu.py ) ok, this is quite fubar in my autosave folder and have to clean it (manually) at least once a month. but i have more control on the autosave files when bad things happens.. wrong user operations, crashes, corrupted files... i can roll back up to 60 minutes... and sometimes more if I'm lucky. this happened really few times. but it was enough for me to keep things like that. i've added a shortcut in browsing panel to my AUTOSAVE_PATH. and to come back in the original subject / question, I never faced that issue again, even today with Nuke 7.0v6 - Mac OSX. regards. Aurélyen Daudet - Nuke & Compositing Teacher adau...@artfx.fr - http://www.artfx.fr - http://blog.artfx.fr
<<signature_artfx.png>>
_______________________________________________ Nuke-python mailing list Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
