Search Tips

Search is based on keyword.

`Ex: "Procedures"`

Do not search with natural language

`Ex: "How do I write a new procedure?"`

Give Feedback Support Portal

# Release Notes for Nuke and Hiero 13.0v4

# Release Date

28 July 2021

Warning: As a result of the current COVID-19 government recommendations here in the UK, much of the Nuke team is still working from home. Currently, 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.

#### NVIDIA

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.

#### AMD

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.

#### 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

## HieroPlayer - Now Free with Nuke and NukeX

HieroPlayer is now a free annual subscription with your Nuke or NukeX license. Simply renew your existing Nuke or NukeX license to receive your HieroPlayer entitlement or fill in the on-demand form.

HieroPlayer is an artist desktop review tool that lets you play back shots or a sequence and compare versions of renders quickly, letting you easily see your work in the context of the VFX timeline.

See HieroPlayer Free with Nuke for more information.

# Feature Enhancements

• ID 481030 - HieroPlayer now supports track blending in the same way as Nuke Studio and Hiero.
See Blending Tracks on the Timeline for more information.

• ID 481534 - HieroPlayer now includes several new workspaces tailored to specific tasks, including Flipbook Player, Reviewing, and Sync Session.

# Bug Fixes

• ID 282435 - HieroPlayer: Random shots on the timeline were occasionally locked.

• ID 378555 - Localization: Playback during localization of source files did not perform as expected.

• ID 427913 - Monitor Out: Looping a sequence occasionally skipped frames on the monitor and in the timeline Viewer.

• ID 436068/443679 - Sync Review: Reviewing large projects referencing remote server footage was sluggish and occasionally caused reconnection issues or the application to crash.

• ID 437414 - Windows only: Pressing V to display available versions on an offline shot caused Nuke Studio to crash.

• ID 440884 - Sync Review: Clicking the update button in a client session with Viewer A/B mode active disconnected the client.

• ID 465300 - Read/Write: Certain Photo - JPEG encoded .mov files with non-standard format sizes caused Nuke Studio to crash.

• ID 469710 - Read/Write: Certain .mov files caused Nuke Studio and Hiero to crash.

• ID 473394 - Sync Review: Client sessions occasionally disconnected from the host when reviewing in large projects.

• ID 473395 - Sync Review: Pushing changes from a client to the host occasionally disconnected or caused the application to crash.

• ID 474853 - Cryptomatte: Selecting mattes with opacity values less than 1 did not work as expected.

• ID 477143 - OCIO: Using Set Media Color Transform on a bin clip and enabling OCIO/ACES did not always update the Read node's colorspace control as expected.

• ID 481790 - Localization: Opening a project containing localized files caused Nuke Studio to become unresponsive.

• ID 482494 - HieroPlayer: Saving a custom workspace over a default workspace and assigning a different keyboard shortcut caused the order of existing keyboard shortcuts to display incorrectly.

• ID 482618 - Windows only: The NDK Examples index.html page is missing from:
<install_dir>/Documentation/NDKExamples

# New Known Issues Specific to Nuke 13.0

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

• 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 471681 - CopyCat: Training a network from the command prompt with the -X argument (execute only the specified node) occasionally fails.

• 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 - Monitor Out: Video Legal Range not working correctly with certain AJA cards.

• 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.

# 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 | Example | Compatibility | Recompile | Rewrite
--- | --- | --- | --- | ---
Version | 12.0v1 to 12.0v2 | API and ABI |  |
Point | 12.0v1 to 12.1v1 | API |  |
Major | 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 Hiero's node toolbar, contains all the current node class names and is located in <install_directory>/plugins/nukescripts/ for reference.
As an example, between Hiero 9 and Hiero 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")