Release Notes for Nuke and Hiero 14.0v8

Release Date

8th August 2024

New Features

There are no new features in this maintenance release.

Feature Enhancements

Monitor Out

  • ID 565937 - “Show Panel” option for Output Transform

    For users who register their own viewer processes directly in Nuke the “show panel” option in the View Transform menu has always been extremely useful. This functionality has now also been added to the Monitor Out Output Transform.
    This allows users to easily access the node properties for the custom viewer process being applied to the monitor out device.

Performance

  • ID 541293 - Nuke requires significantly less resources for GUI path processing so that calling nuke.suspendPathProcessing() is unnecessary for large scripts.

Bug Fixes

Rotopaint

  • ID 407519 - Nuke no longer crashes when cloning in a Rotopaint node with multiple Views in use and multiple Viewers open, on Windows.

  • ID 565898 - Paint strokes were painted in the wrong View, when multiple Views were in use and with two Viewers.

3D

  • ID 498140 - Snap_menu options fuctionality works as expected in EditGeo node

  • ID 502363 - Match geo and Match pivot point now orient correctly

  • ID 505168 - Match selected position and orientation now snaps the correct geometry to a selection when multiple geo nodes are selected at once and their snap properties used

  • ID 510063 - Pivot point snapping works as expected if the user is snapping geometry at a very small or very large scale

  • ID 525897 - AppendClip as texture input for new geometry does not animate

  • ID 537386 - A NoneType object is not subscriptable error occurs when using the Snap Menu on points in a Point Cloud

  • ID 554540 - Querying a pivot knob on Camera/Axis/Light nodes returns an obsolete knob when using node.knobs() but an XYZ knob when using node.knob() and node[knob]

  • ID 564690 - The snap_menu can produce a "local variable 'normal' referenced before assignment" error when used on certain Alembic geometry subsets

  • ID 568259 - The z-axis of Axis node snapped to GeoImported .abc no longer points in opposite direction of expected

  • ID 568825 - Nuke no longer crashes when deleting a ReadGeo node

  • ID 569309 - Camera locator correctly populates the local parent xform values

  • ID 572296 - Specify Matrix doesn't work in the Local Matrix new 3D nodes, like GeoCard/GeoCube/Camera4/Axis4

Color

  • ID 560178 - Updated the OCIO link in context tab's tooltip for all relevant OCIO nodes.

Compare

  • ID 557623 - Filtering by tags in the Viewer buffer does not work if there are track items above the tagged track

Node

  • ID 162897 - PostageStamp node breaks concatenation

Performance

  • ID 539682 - GUI path processing still happens in terminal mode, using more RAM than necessary

  • ID 554606 - Nuke freezes intermittently when using a custom script

Python

  • ID 561182 - Soft effects/SubtrackItems don't always update their color on the timeline until the timeline is active or given focus

  • ID 567213 - A playback error that was caused when reconnecting the media of an invalid clip added via Python has been fixed

  • ID 572096 - Running nuke.math with Vector2, Vector3(), or Vector4() produces a TypeError

Shortcuts

  • ID 431980 - The Script Editor does not receive focus when a clip is selected on the Timeline and using the CMD+Enter hotkey in Studio/Hiero

Soft Effects/Transitions

  • ID 563857 - Adding a clip below a track with effects does not remove the effects

Sync Review

  • ID 457706 - Cursors are now cleared from the viewer when a user leaves a session

  • ID 517713 - Clip knob changes not synced when using Sync Review

  • ID 541659 - Client Sync Review sessions crash when importing many clips quickly

  • ID 542767 - Copy and pasting or duplicating bin items doesn't get synced between Sync Review sessions

  • ID 579815 - Versioning is slower while a Sync Session is active

  • ID 580906 - UI performance decreases when a Sync Session is active

  • ID 580907 - Playback performance can change unexpectedly when a Sync Session is active

Timeline

  • ID 330729 - Video tracks in studio overlap when resized

  • ID 555265 - Inactive Dissolve now shows the original frame (instead of black).

  • ID 568750 - Nuke Studio / Hiero crash on exit if the Timeline/Sequence panel is floating with more than one pane in the floating panel

UI

  • ID 541692 - Node keyframes don't get updated by upstream time nodes in the Dope Sheet if the Viewer is automatically connected to the time node when it is created

  • ID 567027 - A comment has been added to the Audio Device preference to make it clear that it doesn't work with Monitor Out

  • ID 574167 - Dope Sheet updates correctly when adding a time node after an animated node.

  • ID 575351 - Script report 'Total nodes' count fixed to include nodes inside sub Groups, properly representing the actual node total.

Viewer

  • ID 575849 - Changing the Viewer's layer while comparing now displays the correct layer.

New Known Issues Specific to Nuke 14.0

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

  • ID 577000 - Python's logging module no longer prints to both the Script Editor and Command Prompt, instead just printing to the Command Prompt.

  • ID 581553 - Incorrect results can be returned when using node.knob.frame() or the "frame" expression on certain nodes upstream of a TimeOffset.

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.

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.

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