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

# Release Date

10 September 2024

# Feature Enhancements

## Multishot

- ID 582610 - Prevent infinite loop on GsvKnob::from_script() TCL list follows the GSV value

# Bug Fixes

## Viewer Saturation Control

- ID 581172 - Saturation slider not present in the preferences for the viewer

## NodeGraph

- ID 378267 - 'tab_stats.dat' is saved into places other than the .nuke directory

## Group View

- ID 584104 - Group node has an additional arrow pipe

- ID 574798 - Connecting a viewer to a node outside a group causes the arrow to not draw correctly inside the group's node graph

- ID 582087 - Using Viewer hotkeys while inside a Group tab causes the main Node Graph to become active in Nuke Studio/Nuke Indie

## Versions

- ID 574495 - Nuke Studio/Hiero freezes when Scan for Versions encounters a corrupt file

## Exporting

- ID 516447 - Hiero unable to export clip length audio

- ID 562767 - Exporting comps creates unneeded ModifyMetaData nodes for all tagged frames in a sequence

## Sync Review

- ID 582517 - Connecting to a Sync Review session with causes projects to close

## 3D

- ID 582635 - The ParticleExpression node's new operator and the "only on new" condition work correctly for particles generated from ParticleSpawn nodes.

- ID 562533 - The frustum wireframe of Camera4 nodes does not represent its Window Translate, Window Scale, or Window Roll knobs

- ID 582051 - The GeoUVProject node produces incorrect results if indexed "st" attributes are present

## Python

- ID 567990 - hiero.ui.activeView() returns None when the Viewer is in fullscreen

- ID 581730 - Nuke's Script Editor no longer autofills PySide2 modules

## Timeline

- ID 275037 - Collapsing a track with a large number of soft effects no longer causes tracks to overlap.

- ID 582645 - Opening a project with a large stack of soft effects no longer results in overlapping tracks.

## File Formats

- ID 582984 - The Light Blend knob defaults to 1 instead of 100 when reading footage without the mxf/CameraMetadata/LEDWallColourTemperature metadata.

## BlinkScript

- ID 582842 - Loading or saving an rpp file, then changing the BlinkScript File path contents crashes Nuke

# Known Issues

## Group View

- ID 573822 - When creating a Group inside a Group in the new Group View, Nuke automatically switches to a new tab for the first group, which is undesirable with the new Group View feature.

- ID 582726 - Expression and clone link indications disappear when the respective node/s are added to a group

- ID 574009 - Bookmarked nodes in an open Group View are framed with an offset when jumping to those bookmarks.

## 3D

- ID 579263 - Textures are updating in the viewer

- ID 579501 - Timeoffset correctly affects connected animating textures

- ID 563587 - Scene not updating when 'Inverse Selection' checkbox is ticked on the 'GeoIsolate' node

- ID 563625 - Mouse selection not working on action options list after right clicking on groups in ReadGeo pop up - Classic 3D system

- ID 572604 - 3D Viewer Downrez crash with some textured scenes

- ID 563418 - Light options under 'node name' knob does not update while switching between the options - classic 3D system

- ID 577433 - SetAuthorMode works differently in GUI and terminal

## Timeline

- ID 569072 - Adjusting a track tag 'start' point to 0 causes the icon to disappear

- ID 572744 - Viewer Toolbar overflow menu displays last selected compare option, rather than what is shown when the menu is extended

- ID 582437 - Adding soft effect whilst timeline disk is caching will stop the process overall

## NodeGraph

- ID 567902 - RotoPaint doesn't recognise views created after node creation

- ID 565896 - Painting equal number of strokes on left and right viewer makes some strokes invisible in the viewer

- ID 573890 - Resaving script with offline media and reopening it throws errors

- ID 581156 - FrameRanged traits highlighting still present despite being overridden in the node (Copy/Paste)

## Machine Learning

- ID 572672 - CopyCat: Deleting a run from the run table hangs nuke

- ID 574733 - CopyCat: On MacOS, when hitting out of memory error when training copycat the error message is messy. When hitting out of memory error when using inference nodes, nuke will crash.

- ID 575423 - CopyCat: Time estimation will be incorrect (2-3x longer) when training with MultiResolution enabled.

- ID 577326 - CopyCat: On Windows os after training, PyTorch fails to release its cache..

## MacOS

- ID 575080 - Users who have upgraded to Sonoma may encounter an issue when launching Nuke, where licenses display an error. To resolve this issue, we recommend upgrading to Sonoma 14.5 or higher.

## OpenAssetIO

- ID 575828 - R3D_CDL support appears to crash assetized scripts

- ID 579556 - Assetisation of asset has a misleading error, should be a 'file not found' error

## Color

- ID 580590 - Rec.2100-HLG - Display/Raw view transform changes viewer colorspace on playback

# Qualified Operating Systems

- Nuke 15.0 and later support Apple's silicon hardware.

- macOS Ventura (13.x), or macOS Sonoma (14.x)

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

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