Release Notes for Nuke and Hiero 12.2v7
10 June 2021
Warning: As a result of the current COVID-19 lockdown here in the UK, Foundry cannot guarantee that our usual high standards of QA have been applied to Nuke's monitor output functionality, including VR headset support, in this release.
Qualified Operating Systems
• macOS Mojave (10.14) or macOS Catalina (10.15)
Note: We recommend macOS Mojave customers update to 10.14.6 to take advantage of performance enhancements.
• Windows 10 (64-bit)
• CentOS 7.4, 7.5, and 7.6 (64-bit)
Note: The VFX Platform 2019 upgrade includes library versions that are only compatible with CentOS 7.4, or later.
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.
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.
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 WX 7100
• AMD Radeon Pro W 5700
• AMD Radeon Pro WX 8200
• 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.
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.
There are no new features in this release.
• ID 140786/148736/407810 - Backdrop: Creating a Backdrop node now places the backdrop near the mouse pointer's location if no other node is selected.
• ID 167882 - WriteGeo: Exporting an .fbx file with an upper case file extension did not work as expected.
• ID 360410 - Selecting File > New Comp in Nuke did not carry command-line arguments, such as --safe, over to the new Nuke script.
• ID 437414 - Windows only: Pressing V to display available versions on an offline shot caused Nuke Studio to crash.
• ID 446363 - Node Properties undo/redo/reset controls were disabled when making adjustments with a Shuffle2 node upstream.
• ID 453576/472075 - Tags: Selecting a new icon for a tag did not update the tag icon in the Viewer as expected.
• ID 456647 - UI: Resizing the Node Graph map to 0 caused nodes in the Node Graph to disappear.
• ID 458752 - Licensing: Nuke 12.2 did not display licensing errors as expected.
• ID 467080 - Export: Re-exporting comps occasionally displayed an out of frame range warning in the Viewer after scanning for versions and then versioning up.
• ID 469046 - Soft Effects: Some effects were displayed in different colors between Nuke Studio and Hiero or HieroPlayer.
• ID 470096 - Python: Clicking the Load column for items in a custom sceneView_Knob cleared the object name in the Scenegraph.
• ID 470388 - ABC: Deselecting locator items in an Alembic ReadGeo import and then clicking Create all-in-one node caused the import of all objects to fail.
• ID 470531 - Retiming: Attempting to retime a clip on an odd number frame at clip-level, resulted in frame offsets in exported shots.
• ID 470569 - Retiming: Exporting a shot with frame handles beyond the source clip handle range and then clicking Build Track from Export Tag reimported the shot with an offset if the source clip did not start at frame 1.
• ID 470881 - Text: The clip to control didn't handle black outside correctly.
• ID 470999 - AddChannels: The format_size knob didn't handle black outside correctly.
• ID 471672 - Viewers: Disabling tracks in a sequence did not update the timeline Viewer as expected.
• ID 473324 - WriteGeo: File format detection behaved differently to the Write node.
• ID 473689 - Sync Review: Importing files during a Sync Review session occasionally caused Nuke Studio to crash.
• ID 475297 - Viewers: Selecting Audio and Video in the timeline Viewer settings did not display the audio waveform.
• ID 475778 - Group: Copying/pasting or loading Group nodes from ToolSets placed the node incorrectly in the Node Graph.
• ID 476091 - Export: Re-exporting comps and then opening the new comp occasionally displayed a no such file or directory error.
New Known Issues Specific to Nuke 12.2
This section covers new known issues and gives workarounds for them, where appropriate.
Note: Changes to the way motion vectors are calculated in Nuke 12.2 cause any node using the Local option for motion estimation, such as Kronos and VectorGenerator, to render slightly different vectors when compared to legacy versions of Nuke. The default Regularized motion estimation method is unaffected.
• ID 482618 - Windows only: The NDK Examples index.html page is missing from:
As a workaround, use this location instead:
• ID 475140 - Documentation: The Hiero Python Developer's Guide does not currently ship with Nuke builds.
• ID 474957 - Monitor Output: The AJA T-Tap device does not currently work with Nuke.
• ID 472462 - Frame Server: Nuke frame server processes do not currently free RAM after completing a render.
• ID 472336 - Linux only: Adding certain MOV/QuickTime files containing audio to timeline causes Nuke Studio to crash.
• ID 471373 - macOS Nuke Indie only: C_STMap is incorrectly recognized as a custom plug-in and cannot be loaded.
• ID 470465 - Preferences: The Performance > Hardware > disable blink cache control has a misleading label and tooltip.
• ID 468956 - Read/Write: Importing .aaf files with the file browser Preview panel open causes Nuke Studio to crash.
• ID 466754 - USD: Enabling read from file in a Camera or Axis node's Properties and then clicking No in the popup does not disable read from file as expected.
• ID 466720 - USD: Copy/pasting a .usd file from a browser into the Node Graph adds a / (forward slash) to the file path and displays a No such file or directory error.
As a workaround, delete the / and press enter to display the import dialog as normal.
• ID 466485 - Linux only: Nuke can not read .r3d files without CUDA libraries available on the machine.
As a workaround, you can manually install the CUDA libraries from NVIDIA, even if you don't have an NVIDIA GPU installed.
• ID 465300 - Read/Write: Certain Photo - JPEG encoded .mov files with non-standard format sizes cause Nuke Studio to crash.
• ID 461944 - Python: Changing a Read node from an image sequence to a container file format Pythonically causes Nuke to crash if the Read node has postage stamp set to a static frame.
• ID 460411 - Read/Write: Rereading a .mov encoded with mov32 settings using the file control in legacy scripts causes Nuke to crash.
• ID 460240 - masOS only: Existing export presets using the deprecated mov32 codecs cause Hiero to crash on export.
As a workaround, recreate the preset in a Hiero 12.2 release
• ID 460038 - Particles: Secondary particles emitted from other particles do not render as expected.
• ID 459859 - ACES: Nuke Studio incorrectly allows artists to alter the R3D IPP2 colorspaces in Read nodes using IPP2 Custom selection, which results in Half Float ACES Linear colorspace mismatches between Nuke Studio and Nuke.
• ID 459609 - USD: The Scenegraph does not automatically expand the first layer of items when loaded for the first time.
• ID 448524 - macOS only: The resolution restriction informational message for Nuke Indie contains incorrect text.
• ID 444347 - Export: Presets that rely on mov32 do not populate the Content field in the Export dialog.
• ID 443296 - Windows only: The Nuke Indie icon is incorrect.
• ID 442165 - MOV: Writing out .mov files using the H.264 codec at resolutions above the 4K limit imposed by the codec causes Nuke to crash.
• ID 441979 - USD: Deselecting a group in the USD importer and then enabling view entire scenegraph does not load the group.
• ID 441555 - USD: Clicking Cancel in the USD import dialog and then enabling view entire scenegraph does not load the .usd file as expected.
• ID 441439 - R3D: Red decode CPU performance is slower in Nuke 12.2 compared to 12.1 builds.
• ID 440943 - USD: Expanding parent and children groups in the scenegraph manually does not create the horizontal scroll bar correctly.
As a workaround, right-click and select expand all to display the scroll bar.
• ID 440884 - Sync Review: Clicking the update button in a Client session with Viewer A/B mode active disconnects the Client.
• ID 440057 - Roaming: Hiero license roaming with a Nuke Studio license stack is not working as expected.
As a workaround, launch Nuke Studio and select License > Roaming and then set the Workspace to Conforming.
• ID 439856 - Sync Review: Client sessions do not cache sequences as expected when the Viewer A/B mode is active on the Host before the Client connects.
• ID 439011 - ApplyMaterial: Selecting filter > name and then clicking choose incorrectly displays Load state icons.
• ID 439002 - ApplyMaterial: Selecting filter > name and then clicking choose allows editing of the read-only names in the scenegraph.
• ID 436560/436551 - Sync Review: The formatting in the Sync Session panel and Host and Connect dialogs is inconsistent.
• ID 434956 - USD: Columns in the Scenegraph tab can only be rearranged once.
• ID 434574 - File Formats Update: Reading .mxf files in the HybridLogGamma colorspace defaults to linear incorrectly.
• ID 432438 - Vertex UV values are occasionally displayed incorrectly for .abc and .usd files.
• ID 430779 - File Formats Update: All deprecated IPP2 .r3d colorspaces appear the same as current colorspaces.
• ID 430760 - File Formats Update: DRAGONcolor2 and REDcolor4 use the same IPP2 .r3d colorspace.
• ID 429788 - macOS only: Legacy mov32 presets are no longer retained, choosing a preset always displays the Don't show this message dialog.
• ID 426901 - File Formats Update: In IPP2 Custom mode, enabling the Use GPU checkbox displays grading controls from the IPP2 Pipeline incorrectly.
• ID 425200 - Read/Write: Legacy Write node Motion JPEG A/B files do not display the Quality control with mov64 selected as the encoder.
• ID 424070 - RIP: Ops requesting unused inputs occasionally prevent images being released from the device cache.
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.
12.0v1 to 12.0v2
API and ABI
12.0v1 to 12.1v1
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")