May 20th, 2010,07:13 PM
A few methods come to mind.
Brute force: move your preferences6.nk file out of your ~/.nuke directory. Nuke will create a new preferences6.nk file on startup, and reset the 'autosave filename', and 'disk cache' paths.
Cons: All your custom preferences won't exist (you could copy the needed settings over from your moved preferences6.nk file if you wanted, using a text editor).
----------
..or open your existing preferences6.nk file in a text editor, and find the following:
AutoSaveName ...
DiskCachePath ...
set them to:
AutoSaveName [firstof [value root.name] [getenv NUKE_TEMP_DIR]/].autosave
DiskCachePath /tmp [getenv NUKE_TEMP_DIR]
----------
Possible different approach:
Launching Nuke from a terminal/cmd prompt, set the NUKE_TEMP_DIR environment variable before using the Nuke launch command.. (wording will depend on if you are using bash, tcsh, etc)
(i.e. setenv NUKE_TEMP_DIR /tmp/ )
*../tmp/ being whatever directory you want
..it might overide the preference6.nk file.. but I haven't tested this yet.
Last edited by doodle; May 20th, 2010 at 07:25 PM.
Sometimes you're just looking at the wrong side of the table