Release Notes for Nuke and Hiero 13.2v8

Release Date

08 June 2023

Qualified Operating Systems

macOS Big Sur (11.x) or macOS 12.x (Monterey). Nuke is currently supported under Rosetta emulation on Apple's new Apple Silicon hardware and M1 chips. Native support is not currently available and Foundry is planning to support the Nuke family natively on Apple's M1 and M2 hardware at a later date.

Article:  For more information on Foundry products and supported macOS versions, see Foundry Knowledge Base article Q100592.

Windows 10 (64-bit)

CentOS 7.4 to 7.6 (64-bit)

Note:  The currently supported version of VFX Reference Platform includes library versions that are only compatible with CentOS 7.4, or later. Nuke is qualified on the Centos 7.4, 7.5, and 7.6 distributions.

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 W6600

AMD Radeon PRO W6800

AMD Radeon Pro W5700

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 feature enhancements in this release.

Bug Fixes

• ID 235633 - VectorBlur: Copy/pasting or adding VectorBlur2 nodes to a new script incorrectly swapped the U and V channels or motionvector channels.

• ID 336204 - Running Nuke with more than 64 threads caused rendering to fail.

• ID 405867 - Versioning: Scanning for versions didn't work as expected with UNC file paths as path substitutions in the Preferences.

• ID 413798 - Closing or clearing certain scripts caused Nuke to crash.

• ID 420589 - C_CameraSolver: Running out of memory produced different results when matching and solving rigs.

• ID 479601 - Project Bin: Moving items from one bin to another was occasionally sluggish.

• ID 496164 - Viewer: Wireframe textures only appeared on geometry in the 3D Viewer with Hydra (Storm) enabled in the Viewer node Properties.

• ID 512199 - Exporting a sequence containing comp containers and a BurnIn effect track caused Nuke Studio to crash on exit.

• ID 514323 - Cryptomatte: Setting the Manifest Source control to Metadata did not always persist after closing and reopening the Properties panel.

• ID 514325 - Cryptomatte: Nuke could not locate manifest files on disk when the Cryptomatte node's input contained merged image and metadata from multiple source files.

• ID 519080 - Read/Write: Nuke Studio projects containing Sony .mxf files did not display all Read node options as expected.

• ID 519425 - BlinkScript: Kernels that compare Booleans to a number did not work as expected in timeline soft effects.

• ID 520364 - Monitor Out: The bottom few code values (<5/1023) were not accessible in Nuke from Blackmagic Design cards outputting 10-bit values.

• ID 527095 - Documentation: The Hiero developer documentation for incorrectly specified <HIERO_PATH>/StartupUI as the custom guide directory.

• ID 527103 - Python: Adding to the ~/.nuke/Python/Startup or ~/.nuke/Python/StartupUI directories did not work as expected.

• ID 537565 - Read/Write: The MXF Reader did not read pixel aspect ratio correctly.

• ID 537704 - Versioning: Loading a comp container referencing an incompatible Nuke script through the versioning system caused Nuke Studio to crash.

• ID 538721 - OCIO: The Write node's Properties > OCIO tab incorrectly included a swap input/output button.

• ID 539131 - The Bokeh node in the Node Graph was the wrong color.

• ID 539219 - CopyCat: The ABME model from the Cattery did not work as expected.

• ID 539795 - Documentation: The helpCommandRequestHandler function attempted to load example scripts from the wrong location.

• ID 541124 - Camera: Loading a USD file containing a Y-axis value of 90 or -90 did not accurately reproduce the values in Nuke.

New Known Issues Specific to Nuke 13.2

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

• ID 543807 - Export: Changing the Export To path in the timeline Export dialog displays an outdated hiero.core.Project.projectRoot() deprecation warning.

• ID 537358 - CopyCat: Training with large datasets of different sizes occasionally fails.

• ID 534260 - Monitor Out: Node Graph 10-bit 422 output from AJA devices with legal ranges enabled is incorrect.

• ID 524273 - CopyCat: Restarting training after encountering an error causes the contact sheet output to render black.

• ID 524096 - Monitor Out: Blackmagic Design cards do not output 1.5G signals to Phabrix test tools as expected.

• ID 522688 - Nuke Indie: Writing container .mov and .mxf files with Render in background enabled does not work as expected.

• ID 520410 - Inference: The kernel compilation progress bar does not display on machines with Ampere GPUs when Inference is the first node used.

• ID 519874 - 3D Transform Handles: Rotating the camera around a Card with different XYZ scale values causes the handles to distort.

• ID 519224 - NDI: The stream name is not always displayed when a project is opened.
As a workaround, disable and re-enable Monitor Out.

• ID 519126 - CopyCat: The contact sheet created in the checkpoint directory is rgba and the .png files are premultiplied. Depending on the software used to view the images, they could appear blank.

• ID 518254 - CopyCat: Training with the Preview input connected to an image with shuffled A and B layers does not work as expected.
As a workaround, leave the Preview disconnected and use the contact sheet to monitor training.

• ID 510063 - 3D Pivot Point: Snapping doesn't work as expected on very small or very large scale geometry.

• ID 509300 - CopyCat: Using crops with 8+ channel training causes corrupted contact sheet.

• ID 508661 - CopyCat: MacOS Having reads with environment variables as inputs causes Nuke to crash.

• ID 508116 - 3D Pivot Point: Drag-rotate on geometry with a large scale value doesn't work as expected.

• ID 507327 - CopyCat: Preview cannot be fetched if preview is connected to remove.

• ID 507325 - CopyCat: Channels set to none for input causes seg fault.

• ID 506965 - MO NDI: Long NDI sender names get truncated.

• ID 506918 - CopyCat: Resuming after changing cropsize makes contact sheet wrong size.

• ID 506569 - MRQ Deferred Rendering: Result of "Use 32 Bit Post Process Materials" option still rendered when disabled.

• ID 506360 - CopyCat: Resuming with different model size throws wrong error.

• ID 506004 - Arriraw 7: When legacy mxf file is loaded with SDK7, some knob values do not match SDK 6.2 version.

• ID 505687 - 3D Pivot Point: Match Geo to selection ignores and overrides pivot point transformations.

• ID 504819 - 3D Transform Handles: The pivot point of the geometry is affected by the scale changes downstream.

• ID 504645 - IV & MO: NDI signals are seen twice by the NDI receiver app.

• ID 504542 - CopyCat: Epochs set to minus value crashes.

• ID 504406 - CopyCat: Error in the viewer stays on when training.

• ID 504191 - IV & MO: Crash when closing while playing back with NDI active.

• ID 504013 - 3D Transform Handles: Negative Scaling on TransformGeo affecting ParticalEmmiter: intermittent incorrect scales on other axes.

• ID 503829 - 3D Transform Handles: Rotating the camera on the Z-axis causes the Card3D node's screen space handles to change alignment in the 2D Viewer.

• ID 503687 - IV & MO: Not all of the knobs on the Monitor Out strip show their knob name in the tooltip.

• ID 503684 - IV & MO: Monitor Out strip shows stereo controls on launch.

• ID 503338 - 3D Pivot Point: Geometry position and orientation occasionally behave inconsistently.

• ID 502942 - IV & MO: User needs to expand the Viewer MO panel to reveal options.

• ID 502843 - IV & MO: Use Viewer Gamma/ Gain displays on in the MO strip when disabled in properties.

• ID 502793 - IV & MO: Loading an nk file doesn't open all floating windows.

• ID 502495 - CopyCat: Slow down when caching at the start.

• ID 502404 - IV & MO: MO viewer list does not update when a viewer node is copy/pasted.

• ID 502395 - IV & MO: Viewer list doesn't appear to be in a logical order.

• ID 502394 - IV & MO: Output is not sent to MO device unless the related viewer is visible.

• ID 502226 - IV & MO: Floating windows open in same position and size as the most recently closed floating window

• ID 501785 - BM RAW: Incorrect Color space and gamma in attached project.

• ID 501700 - 3D Pivot Point: Object jumps when drag rotating pivot in non-default transform order.

• ID 501525 - CopyCat: Error message is wrong when cancelling training.

• ID 501442 - 3D Pivot Point: Scale affects the pivot drag rotate algorithm.

• ID 501261 - macOS Monterey: Nuke Studio Qt windows slow to update upon resize.

• ID 500156 - OTIO: Warning status appear when different frame rate clips are detected in timeline.

• ID 500138 - 3D Transform Handles: Rotating in screen and world space after scaling in screen space doesn't work as expected.

• ID 499468 - 3D Transform Handles: Handles size is affected by scale change downstream.

• ID 499442 - 3D Transform Handles: Translating rotated pivot point if the geometry was scaled or rotated doesn't work as expected.

• ID 499383 - 3D Transform Handles: Rotate doesn't work as expected on small scale geometry.

• ID 498754 - PUBLIC: Nuke will sometimes fail to launch due to installed software or external hardware connected to the Windows machine.

• ID 498140 - 3D Pivot Point: The snap menu options in the EditGeo nodes don't work as expected.

• ID 498139 - 3D Pivot Point: Match selection doesn't work as expected when pivot control are not at their default values.

• ID 497459 - 3D Transform Handles: Changing values directly inside knobs does not respect pivot compensation.

• ID 497372 - MO NDI: Monitor Out metadata - frameIndex does not work.

• ID 496332 - Linux only: Changing toolbar/handles mode Pythonically doesn't update 3D handles in the Viewer as expected.

• ID 495515 - 3D Transform Handles: Scaling parent transforms negatively causes the orientation of handles to behave unexpectedly.

• ID 492637 - 3D Transform Handles: Free rotate shrinks/grows during rotation in 2D view.

• ID 491143 - MO NDI: - Horizontal flop in the MO Node DNW (Nuke).

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






13.1v1 to 13.1v2





13.0v1 to 13.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")