Release Notes for Nuke and Hiero 13.2v3

Release Date

28 July 2022

Qualified Operating Systems

• macOS Big Sur (11.x) or macOS 12.x (Monterey) on Intel chips only. Apple M1 is tested on Rosetta emulation to ensure new functionality runs as expected on M1 hardware. (We are working toward native Apple Silicon support in future releases.)

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

• Windows 10 (64-bit)

• CentOS 7.4 (64-bit), or later

Note:  The currently supported version of VFX Reference Platform includes library versions that are only compatible with CentOS 7.4, or later. Nuke is qualified on the Centos 7.4, 7.5, and 7.6 distributions.

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

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.

New Features

There are no new features in this release.

Feature Enhancements

There are no feature enhancements in this release.

Bug Fixes

• ID 373092 - Monitor Out: After a gap in the timeline, the first frame of a shot during playback on the monitor was occasionally the last frame of the previous shot.

• ID 410015 - Windows only: Monitor output from AJA Kona 4 cards using HDMI was split incorrectly in to four images on the monitor.

• ID 489557 - Project Bin: Holding Alt and dragging more than three items from one bin to another bin caused the application to crash.

• ID 501884 - Timeline Editing: Blended shots that did not start at frame 0, incorrectly offset the last frame of the blend track by 1 frame.

• ID 502092 - Shuffle [S] was missing from the Tab menu after running Update.

• ID 503741 - OCIOv2: Loading certain ACES 1.2 OCIO config files displayed OCIO LookTransform error: empty destination color space name errors in the Viewer.

• ID 504131 - OCIOv2: Inverting LUTs with large input values occasionally produced NaN (Not a Number) RGB samples in the Viewer.

• ID 504266 - Export: Including additional frame handles occasionally caused misalignment of keyframes.

• ID 504386 - 3D Pivot Point: Pivot drag rotate did not work as expected.

• ID 505214/505672 - Monitor Out: The SDI legal range button's state was not always saved or loaded correctly.

• ID 507281 - Versioning: Changing the version of an unlinked track item occasionally selected the wrong version.

• ID 507284 - Monitor Out: The legal range checkbox in the Monitor Out strip was missing.

• ID 507829 - Monitor Out: Switching between the Timeline and Compositing environments with Monitor Out active in Nuke 13.2 was not as intuitive as in 13.1.

• ID 507925 - Topdown Rendering: Setting file type to mov and then changing the FPS in a Write node's Properties panel caused Nuke to crash.

• ID 508152 - Monitor Out: Closing the application with Monitor Out enabled occasionally caused a crash.

• ID 509243 - Read/Write: Embedding new channels into an .exr file with the Write node's interleave control set to channels caused Nuke to crash.

• ID 509997 - Export: Exporting a sequence to a .mov file displayed an error despite completing successfully.

• ID 510643 - Transitions: Adding fade out to a shot in a sequence and then extending the fade length displayed a Missing file error.

• ID 510673 - macOS only: Adjusting a fade out transition to the length of the shot locked the fade at that length.

• ID 510729 - CatFileCreator: Connecting a Viewer to a CatFileCreator node caused Nuke to crash.

• ID 510841 - AAF: Importing certain .aaf files from Avid or Resolve didn't align some shots in the timeline as expected.

• ID 511136 - UnrealReader: Connecting a Camera node to the UnrealReader camera input caused Nuke to crash.

• ID 511446 - Ocula Plug-ins: Disabling Use GPU if available in the node Properties panel with O_DisparityGenerator connected to O_DisparityViewer caused Nuke to crash.

• ID 512762 - Read/Write: Rendering stereo views from .exr files only rendered one view.

New Known Issues Specific to Nuke 13.2

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

• ID 509300 - CopyCat: Training with cropped images containing more than four channels renders corrupt contact sheet data.

• ID 508661 - macOS only: Using environment variables in CopyCat's Data Directory path causes Nuke to crash.

• ID 507327 - CopyCat: Training does not work as expected if a Remove node is inserted between the input node and the CopyCat Preview input.

• ID 507325 - CopyCat: Connecting an Input with no channels, displayed as Channels: none in the CopyCat Properties panel, and then clicking Start Training causes Nuke to crash.

• ID 506965 - Monitor out: Long Nuke script names create truncated NDI sender names, which can result in only one unique stream regardless of how many Viewers are sending a signal.
As a workaround, avoid using long Nuke script names to allow multiple streams from the same script.

• ID 506918 - CopyCat: Changing the Crop Size and then resuming training creates contact sheets at the wrong size.

• ID 506569 - UnrealReader: The enabled/disabled state of the Use 32 Bit Post Process Materials checkbox is not always respected by the render output.
If UnrealReader fails to respect the enabled/disabled state, restart the Unreal Editor project to reset the controls.

• ID 506360 - CopyCat: Resuming training after changing the Model Size displays a generic error message.

• ID 506004 - ARRIRAW: Reading legacy .mxf files with SDK 7.0 does not match all knob values when compared to SDK 6.2.

• ID 504819 - 3D Transform Handles: Geometry pivot points are affected incorrectly by downstream scale changes.

• ID 504645 - Monitor Out: NDI signals from Nuke Studio are listed twice in the NDI monitor.

• ID 504542 - CopyCat: Setting the Epochs control to a negative number and then starting training causes Nuke to crash.

• ID 504406 - CopyCat: Errors displayed in the Viewer do not disappear as expected during subsequent training runs.

• ID 504191 - Monitor Out: Closing Nuke Studio during playback while broadcasting the timeline Viewer over NDI causes the application to crash on exit.

• ID 504013 - 3D Transform Handles: Negative scaling values in TransformGeo nodes cause inconsistent scaling in upstream ParticleEmitter nodes.

• ID 503687 - Monitor Out: Some controls in the Monitor Out panel in Nuke Studio do not display the knob name in their tooltips.

• ID 503684 - Monitor Out: The Monitor Out panel in Nuke Studio always displays stereo controls, even if the project does not contain multiple views.

• ID 502942 - Monitor Out: The Viewer Monitor Out pane does not display all controls as expected.
As a workaround, resize the pane to cause the controls to appear.

• ID 502843 - Monitor Out: The Use Viewer Gamma / Gain controls are not enabled and disabled consistently between the Properties and Monitor Out pane.

• ID 502793 - Monitor Out: Loading certain .nk scripts does not open all floating windows as expected.

• ID 502495 - CopyCat: Caching during training is slower when compared to earlier Nuke builds.

• ID 502404 - Monitor Out: The Viewer list does not update as expected when a Viewer node is copied and pasted in the Node Graph.

• ID 502395 - Monitor Out: The list of available Viewers is not ordered correctly.

• ID 502394 - Monitor Out: Output is not sent to monitor out devices unless the related Viewer is the active Viewer.

• ID 502226 - Monitor Out: The floating window size is used incorrectly for all panes undocked from the interface.

• ID 501785 - BM RAW: Certain files display with incorrect colorspace and gamma values.

• ID 501700 - 3D Pivot Point: Rotating the pivot point by dragging in a non-default transform order causes the object to jump unexpectedly.

• ID 501525 - CopyCat: Canceling training displays a misleading error message.

• ID 501442 - 3D Pivot Point: Object scale is not always maintained by the pivot rotate algorithm.

• ID 501261 - macOS Monterey only: Resizing UI elements is slow to update.

• ID 500156 - OTIO: Timelines containing shots with different frame rates displays a warning message incorrectly.

• ID 500138 - 3D Transform Handles: Scaling in Screen space and then rotating in Screen and World space doesn't work as expected.

• ID 499468 - 3D Transform Handles: Handle size is unexpectedly affected by scale changes downstream.

• ID 499442 - 3D Transform Handles: Translating a rotated pivot point on geometry that is scaled or rotated doesn't work as expected.

• ID 498754 - Windows only: Nuke occasionally fails to launch due to external hardware connected to the machine.
As a workaround, disconnect any unnecessary hardware such as web cams or additional audio hardware before launching Nuke.

• ID 497372 - Monitor Out: frameIndex metadata does not work as expected.

• ID 492637 - 3D Transform Handles: Using the free rotate tool on certain objects causes them to scale during rotation in the 2D Viewer.

• ID 491143 - Monitor Out: Enabling Horizontal Flop in the ViewerMonitorOut Properties does not work as expected.

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.1v1 to 13.1v2	API and ABI
Point	13.0v1 to 13.1v1	API
Major	12.0v1 to 13.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 9 and Nuke 10, the CameraShake node Class() changed from CameraShake2 to CameraShake3. In the toolbars.py file for the two releases, the entries for the CameraShake node appear as follows:

m.addCommand("CameraShake", "nuke.createNode(\"CameraShake2\")", icon="CameraShake.png")
m.addCommand("CameraShake", "nuke.createNode(\"CameraShake3\")", icon="CameraShake.png")