Release Notes for Nuke and Hiero 12.2v10
30 November 2021
Warning: As a result of the current COVID-19 government recommendations here in the UK, much of the Nuke team is still working from home. Currently, 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.x) or macOS Catalina (10.15.x)
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.
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.
• Radeon™ RX 480
• Radeon™ Pro WX 7100
• Radeon™ Pro WX 9100
• Radeon™ Pro WX 8200
• Radeon™ Pro W5700
Note: For information on the recommended driver for each GPU, see https://www.amd.com/en/support
• On Mac, AMD GPUs are supported on any late 2013 Mac Pro, mid 2015 MacBook Pros onward, and late 2017 iMac Pros.
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 494822 - Versioning: A new versionscanner.log file is created when you version clips and shots up and down in the Project bin or timeline. This file keeps track of all version changes and is a useful tool for troubleshooting and debugging. The file is stored in NUKE_TEMP_DIR/logs. For example, on Windows:
• ID 152698 - Precomp: Copying and pasting Precomp nodes pasted the new node on top of the old one.
• ID 374335 - DeepRead format information in the Viewer's 2D image information was 1 pixel smaller than the actual format.
• ID 391032 - DeepRead: Using Tcl and Python expressions in the file control displayed a Plugin Error message.
• ID 405652 - Node lifetimeStart knob values were not saved in the Nuke script if the start or end values were 0.
• ID 419049 - Timeline Editing: Sequences of .exr shots with large amounts of embedded metadata created excessively large Nuke Studio projects.
• ID 420354 - Workspaces: Node panels did not update correctly if the Properties panel was open on a second monitor.
• ID 426901 - R3D: In IPP2 Custom mode, enabling the Use GPU checkbox displayed grading controls from the IPP2 Pipeline incorrectly.
• ID 447233 - Particles: Moving in 3D space during playback from a ParticleFlock node caused Nuke to crash.
• ID 461944 - Python: Changing a Read node image sequence to a container file format Pythonically caused Nuke to crash if the postage stamp mode in the Preferences was set to Static frame.
• ID 468596 - macOS only: Modal dialog prompts added to menu.py always displayed behind the splash screen on start-up and could not be dismissed.
• ID 471966 - Python: Adding a tab to the Preferences dialog using the Tab_Knob function did not display the tab as expected.
• ID 483350 - Read/Write: Loading unknown file types after loading a .mov file caused Nuke to crash.
• ID 484135 - Linux Only: Nuke 12.2 used more RAM than Nuke 12.1 builds and clearing the cache freed up less memory.
• ID 484808 - Multi-Project Edit: Dragging or copying and pasting a sequence into another project duplicated bin sequences.
• ID 485052 - Read/Write: Changing the Read node File control from an .arx file to another wrapper format displayed errors or caused Nuke to crash.
• ID 485345 - MOV: Playback occasionally stalled on the last frame of certain .mov files.
• ID 485480 - Project Bin: Dragging bin items to locations in the same pane moved the items without displaying a confirmation dialog.
• ID 487285 - Reloading large LiveGroup and Precomp nodes was slow in large scripts.
• ID 487299 - Localization: Creating a new project with localization enabled and then creating a comp from the timeline caused Nuke Studio and Hiero to save the .nk file in the localization directory.
• ID 487657 - Flipbooking: Setting a custom OCIO config using an environment variable and then flipbooking to HieroPlayer caused each flipbook to open in a different HieroPlayer session.
• ID 487789 - Script Editor: Commenting out multiple lines using Ctrl/Cmd+/ did not work as expected.
• ID 489439 - Sync Review: HieroPlayer could not host or connect to sync sessions unless Nuke or Hiero were launched on the machine first.
• ID 489498 - Export: Executing Build Track > From Export Tag occasionally displayed blank frames in the Viewer.
• ID 489578 - Export: Executing Build Track > From Export Tag occasionally ignored metadata in Text soft effects.
• ID 492229 - Sync Review: Clicking the Connect button a few times with an invalid Host name occasionally caused the application to crash.
• ID 492443 - Soft Effects: Copying effects from Nuke Indie to Nuke Studio Non-Commercial was enabled incorrectly.
• ID 492587 - Nuke Indie: The Tags panel could not be accessed as expected.
• ID 494776 - Create Comp: Saving a comp and then returning to the timeline environment occasionally stopped some shots displaying as expected in the timeline Viewer.
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 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 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 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 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 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 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")