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.0v9

# Release Date

28 June 2022

# 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

There are no new features in this release.

# Feature Enhancements

There are no feature enhancements in this release.

# Bug Fixes

• ID 415797 - High DPI: Node name text was not vertically centered.

• ID 428360 - DeepMerge: Holdout did not work as expected on volumetric data samples.

• ID 504266 - Export: Including additional frame handles occasionally caused misalignment of keyframes.

• ID 505472 - GridWarp/GridWarpTracker: Rendering from the command line with the Frame Server or a third-party renderer did not produce the same results as interactive renders.

• ID 505617 - Read/Write: Rendering .mov files with the H264 codec with high resolution inputs caused Nuke to crash.

• ID 507281 - Versioning: Changing the version of an unlinked track item occasionally selected the wrong version.

• ID 508287 - Soft Effects: Making changes to certain soft effect controls in the Properties panel caused the Viewer to flicker.

# New Known Issues Specific to Nuke 13.0

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

• ID 511611 - AIR: Changing the CUDA_CACHE_PATH to any value other than the default causes Nuke to recompile kernels every time they are required.

• ID 509293 - CopyCat: Entering a Checkpoint File with no file extension fails and displays the wrong error message.

• ID 508894 - Profile: Hardware usage calculations do not work as expected when a Profile node is connected to an Inference node.

• ID 501518 - CopyCat: Checkboxes in the Properties > Graph tab are difficult to toggle on and off.

• ID 499823 - CopyCat: The tooltip for the Graph dropdown on the Graph tab is incorrect.

• ID 498878 - CopyCat: Expression nodes supplying temporal data (frames) are not evaluated correctly.
As a workaround, render the output of the Expression node and then train the network using the files on disk instead.

• ID 497323 - Monitor Out: 12 bit 4:4:4 RGB outputs do not work as expected in UHD display mode.

• ID 495149 - Viewer: Enabling use GPU for Viewer when possible in the Viewer Properties panel with dithering algorithm set to low frequency causes the Viewer to display no image.
As a workaround with OCIO color management, you can check Enable OCIO GPU path for the GPU Viewer in the Project Settings.

Note: The workaround does not apply to projects running under Nuke color management.

• ID 494848 - Monitor Out: The timeline Viewer framerate counter does not work as expected with Blackmagic Design cards.

• ID 494532 - Color Management: Clearing or closing and reopening a comp in Nuke causes the Project Settings > Color > color management control to reset to the default Nuke value.

• ID 493421 - OCIODisplay: Copying an OCIODisplay node or effect between the timeline and node graph environments does not retain gamma and gain values.

• ID 492259 - Monitor Out: Resizing a floating monitor out window with title safe guides enabled causes the monitor to flicker.

• ID 492248 - Upscale: Setting Project Settings > Color > OCIO config to nuke-default and upscaling an image causes an unexpected color shift.

• ID 485000 - CopyCat: The description box for error values on the Loss/Step graph does not scale correctly with larger values.

• 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 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 - Upscale: Viewing an Upscale node connected to very large scripts 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 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 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 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")