See Environment Variables for more information on setting environment variables.įor more information, see Nuke as a Python Module in the Nuke developer documentation. If you want to use Nuke interactively, and you have a nuke_i license, set the NUKE_INTERACTIVE environment variable to 1. The import nuke function checks-out a nuke_r render license by default. 2.Īt the Python prompt, use the import nuke declaration to make Nuke’s Script Editor functions and commands (such as () to add a Blur node) available in your chosen Python interpreter. Tip:You can also use relative paths to the directory containing the usrlocal.pth file. Note:Foundry cannot provide customer support for third-party Python interpreters.Īdd the file path for Nuke's site-packages directory to the usrlocal.pth file in your Python 3.9.10 install.įor example, if you're running on Windows, add C:\Program Files\ Nuke 15.0v2\lib\site-packages to the usrlocal.pth file. See Environment Variables for more information. On Windows, if you are trying to import the Nuke module into a third-party Python interpreter, you can add C:\Program Files\Nuke to your PATH environment variable. This process is only necessary once and should take about half an hour. Instead, use the Python build that ships with Nuke, which can be found here: To use Cop圜at, Deblur, Inference, or Upscale on Ampere GPUs in Nuke 13.2, the CUDA kernels need to compile the first time you use them. Note:Importing Nuke as a Python module is unavailable on macOS. You can import Nuke as a module into a third-party Python 3.9.10 interpreter, granting full access to the Nuke Python-API, but from within a native Python interpreter instead of Nuke.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |