Release Notes for Nuke and Hiero 13.0v2

Release Date

29 April 2021

Warning:  As a result of the current COVID-19 lockdown here in the UK, Foundry cannot guarantee that our usual high standards of QA have been applied to Nuke's monitor output functionality, including VR headset support, in this release.

Qualified Operating Systems

Note:  Installing Nuke 13.0 takes significantly longer than Nuke 12.2 builds, particularly on Windows OS, due to the upgrade to Python 3 and the addition of the PyTorch library.

macOS Catalina (10.15.x) or macOS Big Sur (11.x)

Windows 10 (64-bit)

CentOS 7.4, 7.5, and 7.6 (64-bit)

Note:  The VFX Platform 2020 upgrade includes library versions that are only compatible with CentOS 7.4, or later.

Other operating systems may work, but have not been fully tested.

Requirements for Nuke's GPU Acceleration

If you want to enable Nuke to calculate certain nodes using the GPU, there are some additional requirements.


An NVIDIA GPU with compute capability 3.0 (Kepler) or above. A list of the compute capabilities of NVIDIA GPUs is available at

Note:  The compute capability is a property of the GPU hardware and can't be altered by a software update.

With graphics drivers capable of running CUDA 10.1 or above. On Windows and Linux, CUDA graphics drivers are bundled with the regular drivers for your NVIDIA GPU. Driver versions 418.96 (Windows) and 418.39 (Linux), or above are required. See for more information.

Note:  We recommend using the latest graphics drivers, where possible, regardless of operating system.


Note:  Bit-wise equality between GPU and CPU holds in most cases, but for some operations there are limitations to the accuracy possible with this configuration.

On Windows and Linux, an AMD GPU from the following list:

Note:  Other AMD GPUs may work, but have not been fully tested.

AMD Radeon Pro WX 7100

AMD Radeon Pro W 5700

AMD Radeon Pro WX 8200

AMD Radeon Pro WX 9100

AMD Radeon RX 6800 XT

Note:  For information on the recommended driver for each GPU, see

On Mac, integrated AMD GPUs are supported on the following Intel CPU Macs:

Any late 2013 Mac Pro onward (including 2019 Mac Pro),

Mid-2015 MacBook Pros onward, and

Late 2017 iMac Pros onward.

All supported Mac Pros include a multi-GPU support option, where applicable. Bitwise equality between GPU and CPU holds in most cases, but for some operations, there are limitations to the accuracy possible with this configuration.

Warning:  Although AMD GPUs are enabled on other Mac models, they are not officially supported and used at your own risk.

Multi-GPU Processing

Nuke's GPU support includes an Enable multi-GPU support option. When enabled in the preferences, GPU processing is shared between the available GPUs for extra processing speed.

Note:  Multi-GPU processing is only available for identical GPUs in the same machine. For example, two NVIDIA GeForce GTX 1080s or two AMD Radeon™ Pro WX 9100s.

New Features

There are no new features in this release.

Feature Enhancements

There are no features enhancements in this release.

Bug Fixes

• ID 140786 - Backdrop nodes should be created near pointer if nothing is selected.

• ID 148736 - Backdrop node to be placed correctly wherever it is created.

• ID 167882 - Read/Write: WriteGeo cannot export .fbx files with an upper case file extension.

• ID 390137 - When expression linking knobs, the value() method appears to return the incorrect value.

• ID 407810 - When Backdrop nodes are created, they are created to the right side of the Node Graph.

• ID 446363 - Node undo/redo/reset knobs are disabled when making adjustments with a Shuffle2 node upstream.

• ID 454180 - USD: Nuke crashes after copying and pasting cloned Camera/Axis node.

• ID 456647 - UI: Resizing the Node Graph map to 0 causes the nodes in the Node Graph to disappear.

• ID 466706 - USD: Undo doesn't work within the SceneGraph.

• ID 466814 - Duplicate Alembics not showing on scene node.

• ID 466845 - Hydra: Removing image input doesn't revert texture in Hydra viewport.

• ID 468386 - Cryptomatte: Plugging in a node above Cryptomatte forces the Manifest source to change.

• ID 468395 - Loading heavier geometry into the Hydra viewer then applying a Shader/Material causes the 2D viewer to have zoom/image issues.

• ID 468608 - User Knobs: Custom user knobs created in at root level duplicate when script is closed and re-opened.

• ID 468664 - Cryptomatte: Picker Add doesn't work with some of the matte names including special characters.

• ID 469145 - OCIOv2: When OCIO roles are hidden, changing Colour Management causes errors.

• ID 469401 - Cryptomatte: Scripts with Cryptomatte names including "," saved with the Cryptomatte Gizmo are not correctly interpreted by the Cryptomatte plug-in.

• ID 469412 - Runaway rescaling of the viewer with particular shaders.

• ID 469506 - OCIO Roles: Changing the config file with OCIO Roles disabled displays errors in the Project Settings.

• ID 469539 - Cryptomatte: Names including tabs not getting trimmed when copied/pasted into matte list.

• ID 469559 - OCIO Roles: The default Monitor Out LUT in the Project Settings is incorrect from ACES 1.0.3 and 1.1 configurations.

• ID 469648 - Hydra: Hydra Viewer shows incorrect texture for view from split knob.

• ID 470087 - Cryptomatte: Unable to use TCL expressions in the matteList knob.

• ID 470146 - Hydra: Hydra Viewer doesn't display the model builder preview texture.

• ID 470583 - Node Graph: Dragging and dropping a node selection with a Read node creates an input on the Read node and connects it.

• ID 470881 - Text node clip to knob doesn't handle black outside correctly.

• ID 470999 - AddChannels format_size knob doesn't handle black outside correctly.

• ID 471301 - Toggling the enableShadows knob in Hydra Viewer crashes Nuke.

• ID 471335 - .psd breakout Layers do not work.

• ID 471685 - OCIO Roles: Disabling OCIO roles causes errors for non-default color transform combo boxes.

• ID 471781 - OCIO: Viewer custom OCIO config crashes when incorrect file path is added.

• ID 471782 - OCIO: Viewer custom OCIO config crashes when colorspace cannot be found.

• ID 472719 - The Viewer becomes corrupt or multiplied when tabbing between 3D and 2D with a 3D object and Roto nodes upstream in the Hydra Viewer.

• ID 472732 - Cryptomatte: Cryptomatte plug-in resets layer selection when input is disconnected or modified by the addition of a Dot node.

• ID 473043 - Setting colorspace roles in Nuke Studio/Hiero results in Invalid LUT selected error.

• ID 473324 - Read/Write: WriteGeo file format detection different from Write.

• ID 473587 - Cryptomatte: Nuke crashes when changing input from multi-crypto-layer stream to single-crypto-later.

• ID 473744 - MacOS only: failing to catch exceptions in vectorizer.

New Known Issues Specific to Nuke 13.0

This section covers new known issues and gives workarounds for them, where appropriate.

• ID 427838 - Windows only: Monitor Out: Moving floating window to 4K monitor crashes or scales incorrectly.

• ID 440212 - Nuke crashes when executing the Marcom2D script in command line.

• ID 441488 - Nuke crashes when executing the Marcom2D script with command line -c 8G.

• ID 443270 - Monitor Out: GUI strip updates as viewer spawns.

• ID 445560 - MacOS only: MO XDR: Nuke occasionally crashes on setting Monitor Out workspace when using XDR monitor.

• ID 445909 - MO SDI: Video Legal Range not working correctly (AJA).

• ID 448430 - Monitor Out: Floating window occasionally not minimizing in Nuke Studio.

• ID 456513 - QPainter error messages printed to the terminal.

• ID 457608 - Monitor Out: Some menus in Monitor Out Strip overflow menu not functional.

• ID 457886 - USD: Alembic .abc items not graying out when read from file is checked until refresh.

• ID 459921 - Toggling the Materials checkbox in the Hydra Viewer causes the grid to display incorrectly.

• ID 461710 - USD: Axis, Camera and Light in Viewer are set to default until selected.

• ID 462011 - MacOS only: Certain machines running Big Sur display QWidgetWindow() command line errors on start up.

• ID 463253 - Hydra: Solid color applied in Hydra Viewer when set to textured in the Display Settings.

• ID 464964 - Installing 13.0 takes a significant of time amount compared to 12.2.

• ID 465112 - Hydra: Viewing animated USD's file will playback faster, when moving the camera / dragging a selection box over the viewer.

• ID 467209 - USD: Importing a USD with the R hotkey doesn't display the filename in the SceneGraph.

• ID 467229 - USD: Layout issues with Type column when resizing the SceneGraph.

• ID 467257 - USD: Pressing spacebar in the SceneGraph disables item and opens panel in full-screen at the same time.

• ID 467265 - USD: Highlight selections gets stuck within the SceneGraph.

• ID 467270 - USD: Can't hightlight multiple items in the SceneGraph.

• ID 467984 - USD: Camera3 doesn't show the full camera Path.

• ID 468665 - Nuke Studio: White screen display when scaling the Timeline Viewer

• ID 468980 - Monitor Out: Switching between files that have different aspect ratios will leave behind some of the previous image in the floating window.

• ID 469132 - USD: Light3 panel shows a small broken column after using read from file.

• ID 469262 - Monitor Out: Prior to Nuke 13.0v1 it was possible to have multiple Monitor Out devices.

• ID 469578 - Monitor Out: Crashing when changing resolution modes during playback.

• ID 469593 - Monitor Out: Monitor Out panel tab is difficult to access.

• ID 469655 - Monitor Out: Title safe 'Format' not showing on perimeter edges of Monitor Out.

Developer Notes

As Nuke develops, we sometimes have to make changes to the API and ABI under the hood. We try to keep these changes to a minimum and only for certain releases, but from time to time API and ABI compatibility is not guaranteed. See the following table for the situations when you may have to recompile your plug-ins and/or make changes to the source code.

Release Type






12.0v1 to 12.0v2





12.0v1 to 12.1v1




12.0v1 to 13.0v1


Additionally, node Class() names occasionally change between major releases. While these changes do not affect legacy scripts, you may not get the results you were expecting if a node class has been modified. The file, used to create Nuke's node toolbar, contains all the current node class names and is located in <install_directory>/plugins/nukescripts/ for reference.

As an example, between Nuke 9 and Nuke 10, the CameraShake node Class() changed from CameraShake2 to CameraShake3. In the file for the two releases, the entries for the CameraShake node appear as follows:

m.addCommand("CameraShake", "nuke.createNode(\"CameraShake2\")", icon="CameraShake.png")
m.addCommand("CameraShake", "nuke.createNode(\"CameraShake3\")", icon="CameraShake.png")