Open topic with navigation
On start-up, Nuke scans various directories for files that customize the behavior of Nuke. It looks for information on favorite directories, menu options, image formats, gizmos, NDK plug-ins, Python scripts, generic TCL scripts, and preferences.
WARNING: It’s worth saying that you should edit Python files with care as mistakes could stop Nuke from running.
For more information on Python in Nuke, see The Script Editor and Python or the Python Developer’s Guide (Help > Documentation).
Nuke looks in specific subdirectories of the user’s home directory and the Nuke application directory as follows:
• Mac OS X:
drive letter:\Program Files\Nuke8.0v7\plugins\nukescripts or
drive letter:\Program Files (x86)\Nuke8.0v7\plugins\nukescripts
In the .nuke directory, which can be found under the directory pointed to by the HOME environment variable. If this variable is not set (which is common), the .nuke directory will be under the folder specified by the USERPROFILE environment variable - which is generally of the form drive letter:\Documents and Settings\login name\ (Windows XP) or drive letter:\Users\login name\ (Windows Vista).
To find out if the HOME and USERPROFILE environment variables are set and where they are pointing at, enter %HOME% or %USERPROFILE% into the address bar in Windows Explorer. If the environment variable is set, the folder it’s pointing at is opened. If it’s not set, you get an error.
drive letter:\Program Files\Nuke8.0v7\plugins
If you want Nuke to look for plug-ins somewhere else rather than in these default locations, you can also define a common plug-in path yourself. Thus, by defining the Nuke plug-in path, you can assign yourself a common shared directory from which to control Nuke for multiple artists. See Defining the Nuke Plug-in Path for more information.