Release Notes for Nuke and Hiero 14.0v7

Release Date

22 February 2024

New Features

There are no new features in this maintenance release.

Feature Enhancements

There are no new features in this maintenance release.

Bug Fixes

• ID 501531 - [PUBLIC] PTGui presets give an error when importing with the C_CameraSolver node if additional views exist

• ID 525492 - [hDStorm] Tooltips added to the options in the Render Settings dropdown in the Viewer Properties

• ID 545842 - [PUBLIC] Certain MXF files are given incorrect pixel aspect ratios when read by Nuke

• ID 546685 - LayerContactSheet crashes nuke when attached to F_VectorGenerator

• ID 549911 - [3D Arch][Scene Graph] Multiple selection activate/deactivate doesn't work

• ID 550373 - Removed CameraTracker and DepthGenerator from side toolbar menu of NukeAssist

• ID 554335 - VFX22 PoissonRecon package used for 14.0

• ID 556666 - [PUBLIC] Nuke takes longer to render in the Viewer when first picking material in the Cryptomatte node with a multichannel EXR

• ID 557963 - [Cryptomatte] Doesn’t pick mattes with alpha values of 0.5 or less

• ID 559616 - Transformed image textures now display correctly in the 3D View compared to the 2D View

• ID 564372 - [PUBLIC] Nuke crashes on launch due to OpenCL Error

New Known Issues Specific to Nuke 14.0

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

• ID 557881 - [PUBLIC] Nuke freezes when a Tracker node has upstream localized footage, and has a node expression linked to it, displaying it's Curve Editor

• ID 556775 - [PUBLIC] Bokeh node applies an offset to Bloom and Chromic Optical Artifacts when Bokeh node is applied to non-RGB channels

• ID 556270 - [PUBLIC] Looping through hiero.ui.windowManager().windows(), returning the parent widget's currentWidget results in RuntimeError: Internal C++ object (PySide2.QtWidgets.QWidget) already deleted

• ID 554409 - [PUBLIC] Nuke UI stops working correct when spanning multiple monitors when using High DPI/UI Scaling

• ID 554287 - [Blink] Using BoxBlur2D kernel with high values will cause a crash

• ID 552509 - [Timeline] Audio pop when playback is stopped

• ID 552108 - [Scene Graph] Merge input scene in light nodes doesn't work if we connect other light node as input

• ID 552039 - Memory Leak when loading too many alexa 35/mxf files

• ID 551521 - [PUBLIC] Bokeh node not able to use back focus correctly

• ID 550120 - [PUBLIC] Classic 3D System snap_menu options produce a "NoneType object is not subscriptable" error if a disabled ReadGeo node is present

• ID 549833 - [PUBLIC] Nuke Studio can display an incorrect OCIO config Version when the OCIO environment variable is used

• ID 548895 - [PUBLIC] Adjusting the pattern and search areas of the Tracker node's track anchor creates a keyframe at frame 1 or on your reference frame

• ID 548744 - [OCIO] ACES 1.3 - 'Burn in the LUT' in Flipbook does not work for LUTs that are not Raw

• ID 547297 - [Scenegraph] Payloads in payloads cannot be overridden by scenegraph

• ID 546715 - [OCIOv2.1] - Aliases within an OCIO config behave differently without Roles

• ID 541715 - [OCIO] Nuke does not load the saved view transform for some display devices - ACES 1.3

• ID 541400 - [PUBLIC] A "Could not create reader" error occurs when loading ARRI Alexa 35 MXF footage in Terminal or Execute mode

• ID 538323 - [PUBLIC] Nuke displays random colors in Viewer when a value of 0.00001 is used in one of the RGB channels on certain CPU's

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

• ID 536924 - [Scene Graph] "Path" column UI breaks with a large scenegraph

• ID 536861 - [PUBLIC] Specific knobs are missing when a MOV or MXF Write node is created on Mac and FileIO is installed

• ID 536645 - [PUBLIC] OCIO with a low LUT sample size calculated incorrectly in the Viewer when the GPU is toggled on

• ID 536529 - [MO SDI] AJA T-Tap Pro - Is wrongly outputting HD dual link RGB

• ID 533781 - [PUBLIC] OCIOColorSpace produces incorrect transforms for some negative color values on certain CPUs creating artifacts

• ID 532211 - Window shows "QEventDispatcher" from the terminal

• ID 532078 - [Bokeh] Bokeh doesn't work correctly in downrez and proxy mode if it is using kernel input

• ID 532049 - [PUBLIC] Nuke's MSI installer doesn't register Nuke as the default app for .nk files when installed on Windows

• ID 527611 - [PUBLIC] QtWebSockets is missing from Nuke 14

• ID 526127 - [QT] Clicking on Menu Icon remains in a clicked state

• ID 526078 - Tab Menu capitilizations shortcuts not working as expected

• ID 526061 - [3D Arch] Error message flood terminal when USD asset is imported into Nuke

• ID 525872 - [3D Arch] Authoring knobs: GeoDrawMode color does not animate

• ID 525819 - [3D Arch][ScanlineRender] Animated display colour in built-in geo nodes is not rendered correctly by ScanlineRender2

• ID 525817 - [3D Arch][ScanlineRender] Display opacity knob of built-in geo nodes have no effect on image rendered by Scanline Render 2

• ID 525816 - [3D Arch] Display opacity changes are not evident in HdStorm Metal when blending against the background

• ID 525581 - OCIO Configuration load memory errors

• ID 525575 - CameraTrackerPointCloud continues to show data by default when it didn't before

• ID 524963 - [3D Arch][SceneGraph] Background pattern changes when scrolling

• ID 524835 - [OCIONamedTransform] The Viewer error when no transform is selected contains a [.

• ID 524626 - [3D Arch] Viewer hit-detect delay when moving mouse

• ID 524274 - [PUBLIC] Nuke Studio does not apply colour transforms correctly to ARRI Alexa 35 footage when changing the arri_colorspace knob

• ID 524134 - [3D Arch] Changing "Local Parent Xform" value on a camera does not update 3D viewer's look-through

• ID 522999 - [3D Arch][3D UX] CameraTrackerPointCloud node has wrong default colour

• ID 521937 - [3D Arch][Scenegraph] Changing the active state of material scopes not working as expected

• ID 521907 - [3D Arch] Default scale of the points generator to match old pointCloudGenerator

• ID 521133 - [3D Arch] GeoCube is incorrectly rotated if it has a parent transform

• ID 520821 - [3D Arch] GeoCameraTrackerPoints Point size knob stops scaling at a certain size

• ID 520716 - [3D Arch] Materials checkbox for import nodes not working for some scenes

• ID 520622 - [3D Arch] GeoDrawMode > apply_draw_mode checkbox not setting consistently

• ID 520296 - [3D Arch] GeoRevolve tab in Properties menu for GeoCylinder and GeoSphere

• ID 520282 - Scaling errors when moving the Licensing UI window

• ID 519987 - [3D Arch] Creating nodes through python create unexpected connections

• ID 519068 - [Installer] Installer doesn't create Nuke directory

• ID 518874 - [3D Arch] Double-clicking geo in the viewport does not open last selected node in properties panel

• ID 518593 - [3D Arch] GeoDrawMode doesn't work with path masking and node inbetween

• ID 517982 - Uninstaller doesn't clean up start menu shortcuts when multiple accounts logged in on a machine

• ID 517980 - Installer screen momentarily appears again executing MSI installer

• ID 516052 - [3D Arch] [ScanlineRender] projected textures in some ClientScripts are placed incorrectly rendered in 2D

• ID 515379 - [3D Arch] GeoSphere height is twice the height knob

• ID 515355 - [3D Arch][3D UX] Scaling in world space after rotation skews transform and scale handles

• ID 515353 - [3D Arch][3D UX] Scaling in world space after rotation is causing rotation handles to wobble

• ID 514854 - [3D Arch][3D UX] Scale handles in world space doesn't work as expected if the pivot point of geometry was rotated

• ID 514693 - [3D Arch][3D UX]Rotations with handles at large scale become inconsistent and unstable

• ID 514669 - [3D Arch][3D UX] Z-Axis handle not working in screen-space

• ID 513943 - [3D Arch] Localization knobs are missing from GeoImport

• ID 513664 - "Matches" value and name highlights will not update if the node being viewed adds or removes Geo that's name matches the current search

• ID 513286 - [3D Arch] Selection: Vertex selection erroneously throws away points

• ID 511765 - [3D Transform Handles] Scaling camera on Axis doesn't work as expected

• ID 511107 - [3D Arch] GeoCollection: exclusions not working

• ID 510783 - [3D Arch] GeoSphere: Small u_extent and v_extent values of GeoSphere are causing texture to disappear in the viewer

• ID 505862 - [3D Pivot Point] Pivot point rotation stabilization doesn't work in XYZ and ZYX rotation orders

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