Release Notes for Nuke and Hiero 13.0v3
01 July 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.
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 https://developer.nvidia.com/cuda-gpus
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 https://www.nvidia.com/Download/Find.aspx 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 https://www.amd.com/en/support
• 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.
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.
Several new OCIO soft effects have been added to Nuke Studio and Hiero and the Colorspace soft effect has been renamed for clarity:
• OCIO ColorSpace
• OCIO Display Transform
• OCIO Log Convert
• OCIO Look Transform
See Soft Effects in Nuke's Online Help for more information.
• ID 474434 - Non-Commercial: The CopyCat and Inference nodes can now be used in NukeX Non-Commercial mode.
• ID 475760 - OCIO: Setting isdata: true in your OCIO config file for a certain colorspace now bypasses the Viewer Transform. This is useful for colorspaces using non-color data channels such as the normals pass in multi-pass renders.
• ID 273650 - OCIO: Looks were not applied to the Nuke Studio Viewer as expected.
• ID 358709 - Documentation: A layer command was missing attributes in the Nuke Python Developer's Guide for Channels.
• ID 360410 - Selecting File > New Comp in Nuke did not carry command-line arguments, such as --safe, over to the new Nuke script.
• ID 392571 - Soft Effects: Copying and pasting a shot that included a cloned soft effect removed the effect on the copy.
• ID 428258 - Python: Commenting out the last line of code in the Script Editor caused Nuke to become unresponsive.
• ID 437414 - Windows only: Pressing V to display available versions on an offline shot caused Nuke Studio to crash.
• ID 444711 - Assert: Adding an Assert node between transforms broke concatenation.
• ID 453576/472075 - Tags: Selecting a new icon for a tag did not update the tag icon in the Viewer as expected.
• ID 458752 - Licensing: Nuke did not display licensing errors as expected.
• ID 466816 - Read/Write: Certain .mp4/.mov files caused Nuke to become unresponsive during playback of the last frame.
• ID 467080 - Export: Re-exporting comps occasionally displayed an out of frame range warning in the Viewer after scanning for versions and then versioning up.
• ID 469046 - Soft Effects: Some effects were displayed in different colors between Nuke Studio and Hiero or HieroPlayer.
• ID 469260 - Read/Write: Failure to decode a frame from certain .mov/.mp4 files written with a "non-intra" codec caused Nuke to become unresponsive.
• ID 470531 - Retiming: Attempting to retime a clip on an odd number frame at clip-level, resulted in frame offsets in exported shots.
• ID 470569 - Retiming: Exporting a shot with frame handles beyond the source clip handle range and then clicking Build Track from Export Tag reimported the shot with an offset if the source clip did not start at frame 1.
• ID 471672 - Viewers: Disabling tracks in a sequence did not update the timeline Viewer as expected.
• ID 473399 - Viewing the output of certain scripts including a Merge (under), Shuffle, and Write node caused Nuke to crash.
• ID 473689 - Sync Review: Importing files during a Sync Review session occasionally caused Nuke Studio to crash.
• ID 475236 - Project Bin: Deleting bin items from certain Nuke Studio projects was occasionally slow.
• ID 475297 - Viewers: Selecting Audio and Video in the timeline Viewer settings did not display the audio waveform.
• ID 475479 - HieroPlayer: Opening the Preferences and then clicking OK without making any changes caused HieroPlayer to crash.
• ID 475778 - Group: Copying/pasting or loading Group nodes from ToolSets placed the node incorrectly in the Node Graph.
• ID 476091 - Export: Re-exporting comps and then opening the new comp occasionally displayed a no such file or directory error.
• ID 476207 - Cryptomatte: The example plug-in did not work as expected.
• ID 476360 - C_Stitcher: The output of C_Stitcher was re-rendered for every scanline in the Viewer.
• ID 477141 - Read/Write: The Render to timeline option was missing from the Nuke Studio Render dialog.
• ID 477320 - Python: Some files were missing from the Flipbooking with External Applications pyQtExamples directory.
New Known Issues Specific to Nuke 13.0
This section covers new known issues and gives workarounds for them, where appropriate.
• ID 482618 - Windows only: The NDK Examples index.html page is missing from:
As a workaround, use this location instead:
• ID 472519 - CopyCat: Training a network using multi-layer source and ground truth images, such as .exr files, does not work as expected.
As a workaround, use a Shuffle node to remove all layers except rbga.
• ID 470149 - CopyCat: Training cannot be resumed from the command line. For example, using copyCatNode.knob('resumeTraining').execute() displays an optimizer error.
As a workaround, open the script in GUI mode and click Resume Training.
• ID 470014 - macOS only: Canceling the CopyCat training progress bar during the validating inputs phase causes Nuke to display an error message.
• ID 470012 - CopyCat: Canceling the training progress bar during the caching inputs phase causes Nuke to crash.
• ID 470001 - CopyCat: The Batch Size tooltip should state that the size must be less than or equal to the number of image pairs in the data set.
• ID 469655 - Monitor Out: Title safe format not showing on perimeter edges of Monitor Out.
• ID 469593 - Monitor Out: The Monitor Out panel tab is difficult to access.
• ID 469578 - Monitor Out: Crashing when changing resolution modes during playback.
• ID 469262 - Monitor Out: Prior to Nuke 13.0v1 it was possible to have multiple Monitor Out devices.
• ID 469132 - USD: Light3 panel shows a small broken column after using read from file.
• ID 468999 - AIR: Using the Deblur, Inference, or Upscale nodes on large images occasionally causes Nuke to crash.
• ID 468980 - Monitor Out: Switching between files that have different aspect ratios leaves behind some of the previous image in the floating window.
• ID 468665 - Nuke Studio: White screen display when scaling the timeline Viewer.
• ID 467984 - USD: Camera3 doesn't show the full camera Path.
• ID 467270 - USD: Can't highlight multiple items in the SceneGraph.
• ID 467265 - USD: Highlight selections gets stuck within the SceneGraph.
• ID 467257 - USD: Pressing Spacebar in the SceneGraph disables items and opens the panel in full-screen at the same time.
• ID 467229 - USD: Layout issues with the Type column when resizing the SceneGraph.
• ID 467209 - USD: Importing a USD with the R hotkey doesn't display the filename in the SceneGraph.
• ID 467198 - CopyCat: Clicking the refresh button above the graph does not update the Runs table.
• ID 467195 - macOS only: Switching desktop while an Upscale node is processing displays an OMP: Warning #190: Forking a process while a parallel region is active is potentially unsafe error message repeatedly on the command line.
• ID 466734 - CopyCat: Stopping training on the CPU and then resuming on the GPU, and the opposite GPU to CPU, does not work as expected.
• ID 465112 - Hydra: Viewing animated USD's file will playback faster, when moving the camera / dragging a selection box over the viewer.
• ID 464964 - Installing Nuke 13.0 takes significantly longer than Nuke 12.2.
• ID 464442 - Cryptomatte: Clicking the Clear button under the Matte List cannot be undone as expected.
• ID 463253 - Hydra: Solid color applied in Hydra Viewer when set to textured in the Display Settings.
• ID 462011 - macOS only: Certain machines running Big Sur display QWidgetWindow() command line errors on start up.
• ID 461710 - USD: Axis, Camera and Light in Viewer are set to default until selected.
• ID 459921 - Toggling the Materials checkbox in the Hydra Viewer causes the grid to display incorrectly.
• ID 459512 - CopyCat: The Properties panel does not always update to reflect changes to upstream channels.
As a workaround, close and reopen the Properties panel.
• ID 458511 - CopyCat: The visibility control in the Graphs tab is reset by the next update if it is toggled while training is running.
• ID 458509 - CopyCat: Enabling or disabling Log Scale in the Graphs tab causes graph updates to lag.
• ID 458508 - CopyCat: Training does not currently stop or display an error if a NaN value is encountered.
• ID 457886 - USD: Alembic .abc items not graying out when read from file is checked until refresh.
• ID 457608 - Monitor Out: Some menus in Monitor Out Strip overflow menu not functional.
• ID 456513 - QPainter error messages printed to the terminal.
• ID 448430 - Monitor Out: Floating window occasionally not minimizing in Nuke Studio.
• ID 445909 - MO SDI: Video Legal Range not working correctly (AJA).
• ID 445560 - macOS only: MO XDR: Nuke occasionally crashes on setting Monitor Out workspace when using XDR monitor.
• ID 443270 - Monitor Out: GUI strip updates as viewer spawns.
• ID 441488 - Nuke crashes when executing the Marcom2D script with command line -c 8G.
• ID 440212 - Nuke crashes when executing the Marcom2D script in command line.
• ID 427838 - Windows only: Monitor Out: Moving floating window to 4K monitor crashes or scales incorrectly.
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.
12.0v1 to 12.0v2
API and ABI
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 toolbars.py 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 toolbars.py 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")