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 14.0v3

# Release Date

23 February 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 7.6 (64-bit), or later

Note: The currently supported version of VFX Reference Platform includes library versions that are only compatible with CentOS 7.6, 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.5 (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 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 https://www.nvidia.com/Download/Find.aspx for more information on compatible drivers.

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

• ID 505463 - Non-Commercial: BlinkScript is now supported in Nuke Non-Commercial.

• ID 523882 - Read/Write: Support for the ALEXA Mini LF .mxf ProRes codec has been improved.

# Bug Fixes

• ID 154613 - Read/Write: Sony .mxf HDR files with RGB values >1 were clamped at 1 in the timeline Viewer.

• ID 278964 - Monitor Out: 8-bit and 10-bit output was slightly below 100% of the legal ranges with video safe level activated.

• ID 475398 - Monitor Out: Blackmagic Design cards output incorrect 10-bit values.

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

• ID 500103 - Stereo: Rendering stereo images with the frame server enabled or disabled or from the terminal produced different results from RayRender.

• ID 504611 - Stereo: Entering %V in a Write node's file control stopped metadata passing through when read file was enabled.

• ID 507113 - Python: Adding a custom knob and then clicking the edit knobs button in the Properties panel caused Nuke to crash.

• ID 509491 - Viewing a ScanlineRender node downstream of an EdgeExtend node caused Nuke to crash.

• ID 510025 - Python: Calling nuke.layers() returned the layers incorrectly.

• ID 511641 - Viewing a Transform node downstream of an InPaint node caused Nuke to crash.

• ID 513148 - UI: The last three characters in the Versioning popup on the timeline were hidden behind a scrollbar.

• ID 513480 - Gizmos: Updating certain gizmos with new knobs caused Nuke to crash.

• ID 519235 - Frame Server: Closing Nuke displayed an error on the command line.

• ID 520355 - OCIODisplay: The gain and gamma values could not be undone, redone, or reset in soft effects.

• ID 522873 - Read/Write: Connecting a Viewer to a Read node that referenced an ARRI Alexa 35 file caused Nuke to crash if the thumbnail was still rendering.

• ID 523609 - Read/Write: Certain .mxf files created using FFmpeg displayed at the wrong resolution.

• ID 525647 - Timeline Editing: Exporting a sequence displayed unexpected command line messages.

• ID 525655 - Read/Write: Exporting .mov files as ProRes Mov 4444 displayed a Warning: Could not find value "<colorspace>" for "monitorLut". It will be appended to the menu list error message.

• ID 527773 - Cryptomatte: Viewing a Cryptomatte node connected to an .exr with certain metadata upstream caused Nuke to crash.

• ID 527947 - BlinkScript: Certain kernels failed to compile on NVIDIA RTX 4000 series GPUs.

• ID 528062 - OCIO: Soft Effects that rely on a specific config loaded the Preferences config instead of the Project Settings config in Nuke Studio/Hiero.

• ID 528302 - OCIO: Selecting the v2.1 Studio ACES config in the Preferences and then closing and reopening Nuke displayed a Warning: Could not find value "sRGB - Display/ACES 1.0 - SDR Video" for "monitorLut" error message.

• ID 528356 - OCIO: The Preferences > Project Defaults > Color Management settings reverted unexpectedly to OCIO > custom.

• ID 528596 - Python: Calling nuke.clone() in terminal mode caused Nuke to crash.

• ID 532603 - Colorspace: The ARRILogC4 encoding curve was incorrect.

• ID 533394 - Read/Write: Reading Alexa 35 files and using the OpenVPCal toolset caused Nuke to crash.

• ID 533800 - macOS only: Creating a Keylight node caused Nuke to crash.

• ID 534212 - 3D Arch: libnuke incorrectly linked against USD libraries.

• ID 534550 - Nuke Indie: Creating GridWarp nodes did not work as expected.

• ID 534562 - Nuke Indie: Creating Reformat nodes did not work as expected.

# New Known Issues Specific to Nuke 14.0

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

• ID 534720 - Read/Write: ARRI RAW Alexa 35 timecode metadata is off by -1 frame when read in Nuke Studio.

• ID 534623 - Read/Write: Nuke Studio and Hiero do not always interpret the FPS of ARRI RAW Alexa 35 footage correctly.
As a workaround, change the frame rate manually by right-clicking on the clip in the Project bin and selecting Set Frame Rate.

• 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 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 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/519482 - 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 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 517657 - 3d Arch: Instanceable Reference and Point Instanced geometry is un-selectable in the Viewer.

• 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 514631 - 3D Arch: The match position menu (snap menu) doesn't work as expected in the new 3D system.

• 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 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 | Example | Compatibility | Recompile | Rewrite
--- | --- | --- | --- | ---
Version | 13.2v1 to 13.2v2 | API and ABI |  |
Point | 13.1v1 to 13.2v1 | API |  |
Major | 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 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 13 and Nuke 14, the Axis node Class() changed from Axis3 to Axis4. In the toolbars.py 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")