Release Notes for Nuke and Hiero 14.0v5

Release Date

08 June 2023

Qualified Operating Systems

macOS Big Sur (11.x) or macOS Monterey (12.x). 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) and Windows 11 (64-bit)

CentOS/RHEL 7.6 to 7.9 (64-bit)

Note:  The currently supported version of VFX Reference Platform includes library versions that are only compatible with CentOS/RHEL 7.6 to 7.9.

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.5 (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 11.1, or above. On Windows and Linux, CUDA graphics drivers are bundled with the regular drivers for your NVIDIA GPU. Driver versions 456.81 (Windows) and 455.32 (Linux), or above are required. See for more information on compatible drivers.

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 maintenance release.

Feature Enhancements

There are no new features in this maintenance release.

Bug Fixes

• ID 131049 - Timeline Editing: Exporting Version token number 00 from the Export dialog did not work as expected.

• ID 143546 - Timeline Viewer: Viewer masks were incorrect when the pixel aspect ratio was not 1.0 or anamorphic.

• 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 434757 - Annotations: Exporting annotations from Nuke Studio with OFlow retimes applied did not work as expected.

• ID 475288 - Stereoscopic: Setting the Viewer output to Stereo Mode > Interlaced rendered black frames.

• ID 501428 - Localization: Right-clicking a shot and selecting Localize > Sequence/Track/Shot did not work as expected when the Preferences > Localization mode control was set to manual.

• ID 503740 - Create Comp: Using Create Comp Special with multiple clips selected and the HIERO_DISABLE_THUMBNAILS environment variable set caused exports to fail with 'object is null' errors.

• ID 505412 - Transitions: Exporting shots using the Process as Shots export template incorrectly included fade transitions on the exported shots.

• ID 505570 - Read/Write: Importing an .m4a file after a .mov file displayed an error in the Error Console.

• ID 511781 - Python: Using the Python API to remove a non-existent version caused Nuke Studio/Hiero to crash.

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

• ID 513044 - Python: Creating tags Pythonically in Nuke Studio/Hiero 13.1v2, and later, was significantly slower than previous releases

• ID 513425 - Transitions: Reformatting a sequence caused fades to render incorrectly.

• 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 523488 - Python: Importing the nuke module displayed an irrelevant Warning: preferences are only used in GUI mode error.

• ID 524283 - Linux only: Loading projects with missing fonts caused Nuke Studio/Hiero to become unresponsive.

• 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 528015 - 3DArch: The GeoUVProject node did not apply the Camera projection correctly.

• ID 531812 - Transitions: Using fade in/fade out transitions with mask blend by alpha enabled on a blend track caused exports fail.

• ID 533567 - Monitor Out: AJA T-Tap Pro did not work as expected at 4K resolutions over HDMI.

• ID 536131 - Read/Write: the ARRI Alexa 35 entrance_pupil_offset metadata key was spelled incorrectly.

• 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 537994 - CopyCat: Certain Nuke scripts created blank contact sheets during training.

• ID 538571 - Camera3: Adjusting the frame_rate knob did not work as expected.

• 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 539657 - 3D Arch: Attaching a Viewer to a PointsGenerator node caused Nuke to crash.

New Known Issues Specific to Nuke 14.0

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

• ID 543070 - Windows only: Importing Nuke as module in an external Python install does not currently work as expected.

• ID 538340 - CopyCat: Running Nuke on machines without CUDA installed stops CopyCat working as expected.

• ID 535819 - Read/Write: Breaking out layers from .psd files does not work as expected if the file contains non-ASCII characters.

• ID 532211 - Windows only: QEventDispatcher messages are displayed in the command prompt, but they can be ignored.

• ID 532078 - Bokeh: Attaching an image to the Kernel input does not work as expected in Viewer downrez and proxy modes.

• ID 532049 - Windows only: The .msi installer doesn't register Nuke as the default app for .nk files.

• ID 526530 - CatFileCreator: Converted .cat files from Nuke 14 cannot be used in earlier versions of Nuke.
As a workaround, convert the .cat file in the version of Nuke you intend to use, such as Nuke 13.2v5.

• ID 526041 - 3D Arch: Payload overrides in the Scene Graph do not work as expected for nested payloads.

• ID 525872 - 3D Arch: The GeoDrawMode node's Draw Color can not be animated as expected.

• ID 525863 - 3D Arch: DirectLight has much brighter intensity when rendered through ScanlineRender than in the 3D Viewer.

• ID 525819 - 3D Arch: Display Color animation in Nuke geometry nodes, such as GeoCube, is not displayed as expected when rendered through ScanlineRender.

• ID 525817 - 3D Arch: Display Opacity changes in Nuke geometry nodes, such as GeoCube, are not displayed as expected when rendered through ScanlineRender.

• ID 525816 - 3D Arch: Display Opacity changes are not displayed as expected when blended against the background.

• ID 525714 - 3D Arch: Selections in the 3D Viewer are added to selections from the Scene Graph tab when scene graph locations are dropped in a node's Mask control.

• ID 525575 - CameraTracker: CameraTrackerPointCloud nodes incorrectly display point data in the 2D output from ScanlineRender.

• ID 524963 - 3D Arch: The Scene Graph background pattern changes when scrolling through objects in the list.

• ID 524835 - OCIONamedTransform: The Viewer error when no transform is selected contains a [ (square bracket).

• ID 524626 - 3D Arch: Hit detection in the 3D Viewer is slower than in previous versions of Nuke, which causes delayed response times.

• ID 524412 - CopyCat: The training loss graph does not auto-scale as expected on the X-axis.

• ID 524274 - Read/Write: Color transforms are not applied correctly to ARRI Alexa 35 footage after changing the arri_colorspace knob.

• ID 522999 - 3D Arch: CameraTrackerPointCloud displays as a red node, rather than green to indicate that it is a legacy 3D system node.

• ID 521937 - 3D Arch: Changing the active state of materials in the scene graph disables the material for the current Viewer node.
As a workaround, create a new Viewer node and connect it to the scene.

• ID 521907 - 3D Arch: Points in point clouds generated from CameraTracker data default to a size too large for the Viewer.

• ID 521508 - 3D Arch: The bounding box does not always follow its geometry downstream of a GeoMerge node.

• ID 521133 - 3D Arch: Rotating geometry using the transform handles in the Viewer does not follow pointer movement as expected.

• ID 520821 - 3D Arch: The CameraTracker point cloud Point Size control does not scale as expected at large size values.

• ID 520716 - 3D Arch: The GeoImport > Display Materials checkbox does not always toggle materials on and off.

• ID 520622 - 3D Arch: The Draw Mode applied by GeoDrawMode nodes is not set consistently.

• ID 520296 - 3D Arch: Creating a GeoSphere or GeoCylinder node in the Node Graph labels the tab in the Properties panel incorrectly.

• ID 520282 - UI: Moving the Licensing dialog around causes the window to jitter.

• ID 519987 - 3D Arch: Creating nodes Pythonically does not always create the expected node connections.

• ID 519482 - 3D Arch: Projecting onto a GeoCylinder does not match the results from the legacy system Cylinder node in the Hydra Viewer.

• ID 519068 - Windows Installer: Specifying a different install directory does not automatically create a Nuke container directory for the necessary Nuke files.
As a workaround, manually specify a container directory during install.

• ID 518874 - 3D Arch: Double-clicking prims in the Viewer does not open the associated Properties panel as expected.

• ID 518795 - 3D Arch: GeoCard always writes the control_point knob value in the Nuke script, even if it's set to the default value.

• ID 518654 - 3D Arch: Node names are occasionally drawn incorrectly at different Node Graph zoom levels.

• ID 518593 - 3D Arch: Setting the Mask to a prim that is not the node above a GeoDrawMode ignores the selected Draw Mode.

• ID 518581 - UnrealReader: The CompareMetaData node reads incorrect frame metadata from UnrealReader Write section rendered EXRs.

• ID 517980 - Windows Installer: The installer screen occasionally displays twice during installation.

• ID 516166 - 3D Arch: Pressing Enter to cycle through searched items in the Scene Graph allows items to be cycled through even if a contributing node is removed upstream.

• ID 516052 - 3D Arch: Projected textures in some customer scripts are placed incorrectly by ScanlineRender2.

• ID 515379 - 3D Arch: The GeoSphere default Height value is incorrect.

• ID 515370 - 3D Arch: Clicking Invert Selection in the GeoPrune properties does not update mask selections correctly in the Viewer.

• ID 515355 - 3D Arch: Scaling in World space after rotation skews the transform and scale handles incorrectly.

• ID 515353 - 3D Arch: Scaling in World space after rotation causes the rotation handles to wobble.

• ID 514854 - 3D Arch: Scale handles in World space don't work as expected if the pivot point of geometry is rotated.

• ID 514693 - 3D Arch: Handle rotations at large scale can become inconsistent and unstable.

• ID 514669 - 3D Arch: The Z-axis handle is not working in the Viewer Screen space.

• ID 513943 - 3D Arch: The Localization controls are missing from GeoImport's node Properties.

• ID 513286 - 3D Arch: Vertex selection occasionally discards selected points.

• ID 513142 - 3D Arch: Vertex grouping does not grouping all selected vertices in PointCloudGenerator point clouds.

• ID 511940 - 3D Arch: Prims with no Kind assigned are ignored by the GeoDrawMode node.

• ID 511765 - 3D Transform Handles: Scaling a camera on a single axis does not always work as expected.

• ID 511107 - 3D Arch: Exclusion does not work as expected in the GeoCollection node.

• ID 510783 - 3D Arch: Small u_extent and v_extent values in GeoSphere/GeoRevolve(Sphere) cause textures to disappear in the Viewer.

• ID 506930 - CopyCat: Disconnecting and reconnecting the Preview input occasionally causes the contact sheet to behave inconsistently.

• ID 505862 - 3D Pivot Point: Rotation stabilization doesn't work as expected in XYZ and ZYX rotation order mode.

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.2v1 to 13.2v2





13.1v1 to 13.2v1




13.0v1 to 14.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 13 and Nuke 14, the Axis node Class() changed from Axis3 to Axis4. In the file for the two releases, the entries for the Axis node appear as follows:

m3Dclassic.addCommand("Axis", "nuke.createNode(\"Axis3\")", icon="Axis.png", tag=MenuItemTag.Classic, node="Axis3", tagTarget=MenuItemTagTargetFlag.TabMenu)

m3D.addCommand("Axis", "nuke.createNode(\"Axis4\")", icon="Axis_3D.png", tag=MenuItemTag.Beta, node="Axis4")