Release Notes for Nuke and Hiero 17.1v2

Release Date

24 September 2026

Feature Enhancements

Live Groups

  • ID 610349 - Added the --all modifier to the -x command line flag. Running -x --all now renders all Write nodes across all LiveGroups and Precomps, including those nested within each other.

Bug Fixes

Annotations

  • NUKE-8196 - Shapes and paint strokes flicker while scrubbing in a Sync Review session

  • NUKE-8575 - Playback will not show annotations if they're too slow to cache

Compare Versions

  • ID 622173 - Adding and adjusting a Softeffect while in Compare Versions doesn't update the clip in the B Buffer

Export

  • ID 619647 - When the Write node 'channels' knob is changed, the Writer does not get a knob_changed() callback.

Flipbook

  • ID 605403 - Nuke crashes when rendering a flipbook, if you have an invalid OCIO config set in your Project Settings

Graph Scope Variables

  • NUKE-9472 - GSVs changed by the user, then changed by a knobChanged callback, now update correctly in the UI

  • ID 617621 - Nuke crashes when using setGsvValue() on the Root during startup.

OpenTimelineIO

  • NUKE-7601 - Asset file paths relative to the OTIO file location are now resolved during conform.

  • NUKE-7600 - Soft Effects relating to OCIO imported via OTIO are now resolved on import, rather than requiring a project reload.

Performance

  • ID 624170 - Nuke crashes when clearing the script after adding layers with "add\_layer" in the Node Graph.

  • ID 624960 - Nuke crashes when .nk scripts containing Primatte nodes are cleared or closed.

Python

  • ID 617159 - ocionuke.config.getOCIOConfig() does not account for Path Substitutions or Filename Filters

  • ID 158083 - BackdropNode.selectNodes() and BackdropNode.getNodes() don't work in Terminal mode

Known Issues

3D

  • NUKE-8005 - GeoBindMaterial crash when targeting instance

  • NUKE-8022 - Legacy ReadGeo node is crashing when alembic camera files are added

  • NUKE-25156 - Use of the presence knob on supporting shaders (e.g. FillShader, ConstantShader) is not functional

  • NUKE-7636 - Scrubbing the color knob on some GeoLight nodes can cause the output from ScanlineRender2 or SplatRender to get stuck on the wrong color

  • NUKE-8181 - PreviewSurface format is incorrect on all but diffuse input

  • NUKE-8130 - TimeOffset nodes are ignoring Layer Break nodes

  • NUKE-8063 - Copying a Light with Color Temperature enabled, disables the temperature knob after pasting

  • NUKE-7901 - Axis ops visible in a viewer connected to a separate stage

  • NUKE-7814 - GeoBreakLayer doesn't work with GeoMerge set to duplicate prims in place

  • NUKE-7959 - Live Read camera state is interrupted and irretrievable by snapshotting frame links

  • NUKE-7623 - GeomOp errors are not reported when opening a script

  • NUKE-7622 - Crash when loading a script with a GeoPython node that calls nuke.message

Annotations

  • NUKE-8438 - When Annotations is enabled on the Viewer, using the space bar to expand and collapse the Viewer stops working

  • NUKE-8316 - Shift + Box Selections doesn't add to the current selection

  • NUKE-7986 - Annotations are stretched when Sequence has a pixel ratio of 2

  • NUKE-7940 - Arrow keys to change Annotation tool properties requires Shift modifier

Contact Sheet

  • NUKE-7632 - Moving the In and Out points, displays a preview of the current sequence

  • NUKE-7613 - Enabling Stack View will enter on the same page index that the user is looking at before entering Stack View

  • NUKE-7611 - Long expressions/text show in full in the Contact Sheet settings drop down

  • NUKE-7561 - Contact sheet in tracks mode is out of sync with sequence if we recycle sequence viewer, NukeStudio

Compare Versions

  • NUKE-7591 - Versions Compare does not show B Buffer Border when opening a clip in Timeline View

  • NUKE-7977 - Comparing two clips with a pixel ratio of 2 in horizontal mode has overlapping clips.

  • NUKE-7889 - Flip, Flop happens per Buffer instead of per Viewer

  • NUKE-7879 - Switching Sequences while in CompareVersions doesn't switch both Buffers

File Formats

  • NUKE-7640 - Channel filters are not applied when set via Python with a Read properties panel open. As a workaround uncheck "Disable Extra Channels" after setting the Filter Masks e.g. _exrReadNode.knob("disable\_extra\_channels").setValue(False)_,

  • NUKE-8109 - An error state may persist on a Read node incorrectly after modifying the EXR channel filtering expression

  • NUKE-7950 - In the EXR Channel Filter controls the text on the Finished Editing Filters button is cropped on some displays.

Hydra 2.0 Rendering

  • NUKE-7584 - Alpha isn’t rendered for Ci output when using Renderman in the GeoRender node.

  • NUKE-7620 - Nuke can crash when using Renderman XPU in GeoRender, with output set to instanceId or elementId

  • NUKE-7627 - Having two Renderman Hydra delegates in your scene can cause Nuke to crash, even if they are not active at the same time

Monitor Out

  • NUKE-7976 - MonitorOut image is positioned incorrectly when a clip with a pixel ratio of 2 is only loaded into Buffer B with horizontal mode

  • NUKE-7961 - Enabling the Format overlay causes the Monitor Out image to be positioned incorrectly when in interactive mode

  • NUKE-7960 - Displays modes that use as pixel ratio of 2:1 are square formats

  • NUKE-7965 - Interactive Mode only shows one view when the Viewer is set to some of the stereo modes

OpenAssetIO

  • NUKE-7904 - Nuke will not launch if an asset manager JSON file contains errors

Splats

  • NUKE-7577 - SplatRender does not support all camera projection modes in the Camera node

  • NUKE-8221 - Attaching GeoViewScene to a node containing a Splat can cause Nuke to crash

  • NUKE-7881 - GeoPointsToMesh doesn't support splats or normals attributes

  • NUKE-8228 - TimeOffset nodes cannot be modified in the DopeSheet when connected to the GeoSequencer

Spreadsheet

  • NUKE-7884 - Setting a negative value into the Src In knob that would return a negative value, instead set the wrong value completely

Qualified Operating Systems

  • macOS Sequoia (15.x), or macOS Tahoe (26.x)

  • Apple has confirmed that macOS Tahoe (26.x) is the final version to support Intel-based Mac machines, with all future macOS releases only supporting Apple silicon.

    To align with this transition, Nuke 17.1 is the last release line to support Intel-based Mac machines. All following releases of Nuke for macOS will only support Apple silicon hardware.

    Important: There are two versions of Nuke 17.1 available to download from our website - one without Intel-based Mac support and one with Intel-based Mac support. Make sure to download the correct version.

    During this time while the Nuke 17.1 release line continues to support Intel-based Macs, test coverage for these devices will be limited. Our support for Intel-based Macs will be limited to addressing critical stability issues and blockers. We will not be providing ongoing, full-scale feature support or routine maintenance for this platform.

    With Nuke 17.1 serving as the final release line to officially support Apple Intel hardware, this is intended to assist with your transition planning as you look toward future hardware upgrades.

    We recommend that users on Intel hardware consider these versions as the final major upgrade path and migrate to M-series hardware for continued compatibility with future Nuke releases.

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

  • Windows 11 (64-bit)

  • Linux Rocky 9.0 (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 Rocky 9.0.

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. See the Release notes for full details of requirements for GPU acceleration based on your Nuke version.

NVIDIA

An NVIDIA GPU with graphics drivers capable of running CUDA 12.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 12.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:

  • AMD Radeon PRO W7900

  • AMD Radeon PRO W6600

  • AMD Radeon PRO W6800

  • AMD Radeon Pro W5700

  • AMD Radeon RX 6800 XT

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

For information on the recommended driver for each GPU, see https://www.amd.com/en/support

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.

Apple M Series

Native support for Apple silicon hardware began with Nuke 15.0 and later versions. The following machines has been tested.

  • Mac Pro
  • Mac Studio
  • Mac Mini
  • MacBook Pro

WARNING: Although AMD GPUs are enabled on other Mac models, they are not officially supported and are used at your own risk.

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