Release Notes for Nuke and Hiero 14.1v8

Release Date

21 May 2025

Bug Fixes

Licensing

  • ID 600187 - A required server-side change to our Teams licensing system affected communication between our Nuke products and the server. The result was that Teams license checkouts would fail, despite valid licenses being available on the server. The error message in the Licensing Dialog is copied below:
    "Team License Entitlement Installation Warning
    Selected entitlement did not contain all required features."
    The issue is now fixed.

Known Issues

3D

  • ID 532048 - DirectLight not illuminating scene objects in 3D Hydra

  • ID 544629 - Selected overlapping vertices not drawn

  • ID 583572 - Nuke crashes when viewing a DeepReformat node downstream of a ScanlineRender2 node, which has overscan and ray tracing enabled

BlinkScript

  • ID 538645 - Heavy Blinkscripts with multiple parameters will sometimes render incorrectly on Mac Arm

  • ID 594763 - Blinkscript doesn't create the correct variable type when mixing float2 and int, depending on the order in which they are called while GPU acceleration is enabled

CaraVR

  • ID 551945 - Undo command not removing all Camera Ingest nodes

Color

  • ID 537033 - OCIODisplay's display and view knobs not updated after changing OCIO config in Nuke

  • ID 543135 - Switching to another config loads wrong Input Transform

Exporting

  • ID 591686 - H264 Codec Profile setting is not saved inside Nuke Studio/Hiero Export Presets

File Import

  • ID 595653 - Certain JPEG 2000 MXF files do not load correctly in Nuke

Localization

  • ID 597039 - The Localization Policy Preference does not apply to the Timeline environment in Nuke Studio/Hiero

MacOS

  • ID 542483 - Floating point errors between ARM and INTEL hardware

  • ID 560317 - Playback/Caching of ProRes files is worse in Nuke Studio/Hiero 14.1/15.0 than 14.0 on macOS

Machine Learning

  • ID 551424 - CopyCat: When training on windows, the training progress bar takes some time to appear.

  • ID 553337 - The training Contact sheet doesn't reframe when selecting different trainings

  • ID 588838 - Training causes properties to scroll down automatically

Miscellaneous

  • ID 545900 - An OVRService (Open VR) error occurs when launching Nuke

Monitor Out

  • ID 548315 - Timeline - 12 bit 4:4:4 on BMD shows incorrect output when there is an aspect ratio mismatch between the Output Resolution and the Display Mode (Studio)

  • ID 563868 - Floating Window sometimes not rendering when switching between Timeline and Node Graph

  • ID 595100 - Fixed: The Monitor Out floating window incorrectly displays premultiplied images.

Node

  • ID 581199 - The UnrealReader's Picker knobs do not Add or Remove items from the Layer List

NodeGraph

  • ID 591075 - An error is given when rendering with a specific script in Nuke.

OpenAssetIO

  • ID 546692 - Nuke displays balReader not found with correct OpenAssetIO setup

  • ID 547439 - color profile appears to have not loaded errored for braw files

Performance

  • ID 595766 - Nuke takes longer to load while NUKE_PATH or .nuke contains a large amount of files

Soft Effects/Transitions

  • ID 548563 - Moving the denominator knobs in LensDistortion can cause UI to block. Workaround: work in proxy mode

  • ID 548998 - Soft effects in error state stop Inferences in the soft effect stack from affecting the viewer

  • ID 553436 - Black boxes appear in viewer when using BoxBlur2D kernel

  • ID 577543 - Moving the text soft effect in the viewer will only move the bounding box and not the text

Sync Review

  • ID 581464 - Adding soft effects will remove In and Out points from other session

  • ID 594417 - Adding an in/out ranged annotation removes in/out points of host during sync session

Timeline

  • ID 545782 - Disabling/Enabling Tracks and Track Items causes the UI Spinner to appear

  • ID 581186 - Clone soft effects do not update when the original is edited

  • ID 581508 - During looped playback, Switching between playheads, with disk-cache enabled and in/out points set, causes a long pause before playback resumes.

  • ID 593091 - The In/Out points are missing when duplicating a Sequence and viewing the timeline.

Viewer

  • ID 581510 - Zooming out to 1% and playing back the footage causes the paused image to downres

  • ID 588634 - Timeline Viewers can display incorrect results when Proxy Resolution is 1:1 and the zoom level changes

  • ID 592171 - The Viewer's playback range becomes locked when the Playhead is selected if the playback range was previously locked

Qualified Operating Systems

  • macOS Monterey (12.x), or macOS Ventura (13.x). Nuke 14.1 is supported under Rosetta emulation on Apple's silicon hardware and M1 and M2 chips. Native support is available in Nuke 15.0 on Apple's M1 and M2 hardware.

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

  • Windows 10 (64-bit) or Windows 11 (64-bit)

  • Linux 7.6 to 7.9 (64-bit)

    Nuke requires libnuma to run under Linux distributions, the library is required by the Nablet H264 Codec SDK.

    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.

NVIDIA

An NVIDIA GPU with graphics drivers capable of running CUDA 11.8, or above. A list of the compute capabilities of NVIDIA GPUs is available at https://developer.nvidia.com/cuda-gpus

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.8, or above. On Windows and Linux, CUDA graphics drivers are bundled with the regular drivers for your NVIDIA GPU. Driver versions 522.06 (Windows) and 520.61.05 (Linux), or above are required. See https://www.nvidia.com/Download/Find.aspx for more information on compatible drivers.

We recommend using the latest graphics drivers, where possible, regardless of operating system.

AMD

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

    Other AMD GPUs may work, but have not been fully tested.

    • AMD Radeon PRO W7900

    • AMD Radeon PRO W6600

    • AMD Radeon PRO W6800

    • AMD Radeon Pro W5700

    • AMD Radeon RX 6800 XT

    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.

    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.

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.

GPU Requirements for the Machine Learning Toolset

Training using the CopyCat node requires an NVIDIA GPU, with compute capability 3.5 or above; or MacOS Apple silicon integrated GPUs.

If an appropriate GPU is not available, Inference and other machine learning plug-ins can run on the CPU with significantly degraded performance.

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 14.0v1 to 14.0v2 API and ABI
Point 14.0v1 to 14.1v1 API ⬤
Major 14.0v1 to 15.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")