Defining the Nuke Plug-in Path

To define the plug-in path:

1.

On each artist’s machine, create an environment variable called NUKE_PATH.

2.

Assign the NUKE_PATH environment variable to the path name of the directory where files related to Nuke customization will reside.

For example, on Mac using a csh or tcsh shell:

setenv NUKE_PATH /SharedDisk/Nuke

Or, if you're using a bash or ksh shell:

export NUKE_PATH=/SharedDisk/Nuke

Loading a plug-in (plugin_find()) searches the NUKE_PATH until the first plug-in is located, ensuring that only the most local plug-in is loaded. For example if the NUKE_PATH variable contains:

project_dir:studio_dir:company_dir

The path is searched in the following order until the first plug-in is located:

• ~/.nuke

• project_dir

• studio_dir

• company_dir

• nuke_dir

However, the NUKE_PATH environment variable is parsed in reverse order when loading init.py and menu.py and all discovered copies are used. This allows localized settings to override more global ones. So, with the directory hierarchy above, init.py scripts would execute as follows:

• nuke_dir/init.py

• company_dir/init.py

• studio_dir/init.py

• project_dir/init.py

• ~/.nuke/init.py