Q100373: How to add plug-in paths to Nuke Studio and Hiero
This article explains how to add plug-in paths to Nuke Studio and Hiero, to load and use additional plug-ins and Python modules. This can be done using either the HIERO_PLUGIN_PATH environment variable or the
When Nuke Studio and Hiero scan for Python modules or plug-ins to import, they search all
<path>/Python/StartupUI locations for any Python modules or packages containing __init__.py files, or other plug-ins like gizmos. This means that your custom module or plug-in directory structure requires Python/Startup or Python/StartupUI directories defined.
The scanning is done first in all the Python/Startup folders and then in all the Python/StartupUI folders. Any Python startup scripts found are imported in alphabetical order and loaded as plug-ins for Nuke Studio and Hiero to use.
ENVIRONMENT VARIABLE METHOD
To affix an additional <path> locations to the list of plug-in paths that Nuke Studio and Hiero scan for, you can use the environment variable HIERO_PLUGIN_PATH. Multiple paths need to be separated by colon : , similar to how Nuke’s NUKE_PATH works.
For example, if you set HIERO_PLUGIN_PATH to
Information about how to set environment variables can be found in the following article: Q100015: How To Set Environment Variables
You can also append additional <path> locations using a the following Python commands:
Since Nuke Studio and Hiero look for Python modules or plug-ins under a
<path>/Python/StartupUI location, the new plug-in path appended using the command above needs to include either Python/Startup or Python/StartupUI explicitly in the file path.
For example, if you run the following line of code:
Nuke Studio and Hiero will scan the following directories in order:
These lines of code are usually included in a init.py file inside the user's .nuke folder, inside a Python/Startup directory.
More information on how to use the Python/Startup and Python/StartupUI directories can be found here: Q100142: How to execute Hiero Python code in NukeStudio on startup
We're sorry to hear thatPlease tell us why