Search Tips

Search is based on keyword.

`Ex: "Procedures"`

Do not search with natural language

`Ex: "How do I write a new procedure?"`

Give Feedback Support Portal

# Release Notes for Nuke and Hiero 13.0v6

# Release Date

02 December 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

Note: Installing Nuke 13.0 takes significantly longer than Nuke 12.2 builds, particularly on Windows OS, due to the upgrade to Python 3 and the addition of the PyTorch library.

• macOS Catalina (10.15.x) or macOS Big Sur (11.x)

• Windows 10 (64-bit)

• CentOS 7.4, 7.5, and 7.6 (64-bit)

Note: The VFX Platform 2020 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.

#### 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 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.

#### 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

• ID 488270 - Inference: Loading Nuke 13.1 .cat files containing custom knobs in Nuke 13.0 now displays an error message.

• ID 493594 - Python: You can now set/get the value() of the Monitor Out viewer knob, similar to the other knobs in the MonitorOutNode Properties and UI strip.

• 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:

C:/Users/<username>/AppData/Local/Temp/nuke/logs/versionscanner.log

# Bug Fixes

• ID 152698 - Precomp: Copying and pasting Precomp nodes pasted the new node on top of the old one.

• ID 160086 - Blink API: The blinkBlurAndGain example plug-in did not compile correctly.

• ID 374335 - DeepRead format information in the Viewer's 2D image information was 1 pixel smaller than the actual format.

• ID 379217 - Read/Write: Rendered .exr files did not obtain their node_hash from the Write node.

• 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 447233 - Particles: Moving in 3D space during playback from a ParticleFlock node caused Nuke to crash.

• ID 445909 - Monitor Out: Video Legal Range did not working correctly with certain AJA cards.

• 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 474297 - Cryptomatte: Undoing actions in Read nodes with a Cryptomatte node in the script did not always work as expected.

• ID 476386 - Frame Server: FrameServerThreads did not initiate the self.logger as expected.

• ID 476430 - Cryptomatte: Blender cryptomatte files did not import into Nuke as expected.

• ID 480813 - Python: Calling list.sort() on a list of nodes did not work as expected.

• 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 485295 - Licensing: Hiero incorrectly checked out a hiero_i and nukestudio_i license if both were available.

• 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 486845 - Camera: Reloading a script caused the Camera node to default to the first camera available in the associated .fbx or .abc file when read from file was enabled.

• 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 488530 - Node Graph: Dragging a node onto an existing connection occasionally produced unexpected results.

• ID 489214 - CopyCat: Starting training when the playhead was not on the first frame of a clip with more than 100 frames displayed an error message.

• 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 490592 - Monitor Out: Switching between the timeline and comp environment did not retain the Output Transform knob value as expected.

• ID 490663 - CopyCat: Clicking Create Inference did not work as expected if the Data Directory file path contained spaces.

• ID 491033 - Monitor Out: The Video Legal Range control did not work as expected with AJA cards over HDMI in Nuke.

• ID 491173 - Monitor Out: The Video Legal Range control was applied twice with AJA cards in Nuke Studio.

• ID 491569/491574 - Monitor Out: Looping clips with certain cards enabled occasionally caused tearing or frame skips on the monitor display.

• ID 491583 - NDK Documentation: The Cryptomatte and Tetrahedron example files were missing from the examples directory.

• ID 491881 - Windows only: Read node error displays in the Viewer, such as missing colorspaces, occasionally caused Nuke to crash.

• 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 13.0

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

• ID 495149 - Viewer: Enabling use GPU for Viewer when possible in the Viewer Properties panel with dithering algorithm set to low frequency causes the Viewer to display no image.
As a workaround with OCIO color management, you can check Enable OCIO GPU path for the GPU Viewer in the Project Settings.

Note: The workaround does not apply to projects running under Nuke color management.

• ID 494532 - Color Management: Clearing or closing and reopening a comp in Nuke causes the Project Settings > Color > color management control to reset to the default Nuke value.

• ID 492259 - Monitor Out: Resizing a floating monitor out window with title safe guides enabled causes the monitor to flicker.

• ID 492248 - Upscale: Setting Project Settings > Color > OCIO config to nuke-default and upscaling an image causes an unexpected color shift.

• ID 488817 - Hydra: The Project3D node's project on control always projects on both faces regardless of the option chosen.

• ID 486238 - Inference: Previewing a CopyCat .ost file in the application file browser causes Nuke to crash.

• ID 485000 - CopyCat: The description box for error values on the Loss/Step graph does not scale correctly with larger values.

• ID 472519 - CopyCat: Training a network using multi-layer source and ground truth images, such as .exr files, does not work as expected.
As a workaround, use a Shuffle node to remove all layers except rbga.

• ID 470014 - macOS only: Canceling the CopyCat training progress bar during the validating inputs phase causes Nuke to display an error message.

• ID 470012 - CopyCat: Canceling the training progress bar during the caching inputs phase causes Nuke to crash.

• ID 469655 - Monitor Out: Title safe format not showing on perimeter edges of Monitor Out.

• ID 469593 - Monitor Out: The Monitor Out panel tab is difficult to access.

• ID 469578 - Monitor Out: Crashing when changing resolution modes during playback.

• ID 469262 - Monitor Out: Prior to Nuke 13.0v1 it was possible to have multiple Monitor Out devices.

• ID 469132 - USD: Light3 panel shows a small broken column after using read from file.

• ID 468980 - Monitor Out: Switching between files that have different aspect ratios leaves behind some of the previous image in the floating window.

• ID 468665 - Nuke Studio: White screen display when scaling the timeline Viewer.

• ID 467984 - USD: Camera3 doesn't show the full camera Path.

• ID 467265 - USD: Highlight selections gets stuck within the SceneGraph.

• ID 467257 - USD: Pressing Spacebar in the SceneGraph disables items and opens the panel in full-screen at the same time.

• ID 467229 - USD: Layout issues with the Type column when resizing the SceneGraph.

• ID 467209 - USD: Importing a USD with the R hotkey doesn't display the filename in the SceneGraph.

• ID 467198 - CopyCat: Clicking the refresh button above the graph does not update the Runs table.

• ID 467195 - macOS only: Switching desktop while an Upscale node is processing displays an OMP: Warning #190: Forking a process while a parallel region is active is potentially unsafe error message repeatedly on the command line.

• ID 465112 - Hydra: Viewing animated USD's file will playback faster, when moving the camera / dragging a selection box over the viewer.

• ID 464964 - Installing Nuke 13.0 takes significantly longer than Nuke 12.2.

• ID 464442 - Cryptomatte: Clicking the Clear button under the Matte List cannot be undone as expected.

• ID 463253 - Hydra: Solid color applied in Hydra Viewer when set to textured in the Display Settings.

• ID 462011 - macOS only: Certain machines running Big Sur display QWidgetWindow() command line errors on start up.

• ID 461710 - USD: Axis, Camera and Light in Viewer are set to default until selected.

• ID 459921 - Toggling the Materials checkbox in the Hydra Viewer causes the grid to display incorrectly.

• ID 459512 - CopyCat: The Properties panel does not always update to reflect changes to upstream channels.
As a workaround, close and reopen the Properties panel.

• ID 458511 - CopyCat: The visibility control in the Graphs tab is reset by the next update if it is toggled while training is running.

• ID 458509 - CopyCat: Enabling or disabling Log Scale in the Graphs tab causes graph updates to lag.

• ID 458508 - CopyCat: Training does not currently stop or display an error if a NaN value is encountered.

• ID 457886 - USD: Alembic .abc items not graying out when read from file is checked until refresh.

• ID 457608 - Monitor Out: Some menus in Monitor Out Strip overflow menu not functional.

• ID 456513 - QPainter error messages printed to the terminal.

• ID 448430 - Monitor Out: Floating window occasionally not minimizing in Nuke Studio.

• ID 445560 - macOS only: MO XDR: Nuke occasionally crashes on setting Monitor Out workspace when using XDR monitor.

• ID 443270 - Monitor Out: GUI strip updates as viewer spawns.

• ID 441488 - Nuke crashes when executing the Marcom2D script with command line -c 8G.

• ID 440212 - Nuke crashes when executing the Marcom2D script in command line.

• ID 427838 - Windows only: Monitor Out: Moving floating window to 4K monitor crashes or scales incorrectly.

# 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 | 12.0v1 to 12.0v2 | API and ABI |  |
Point | 12.0v1 to 12.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 Hiero's node toolbar, contains all the current node class names and is located in <install_directory>/plugins/nukescripts/ for reference.
As an example, between Hiero 9 and Hiero 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")

Did you find this helpful?

Yes No

## Sorry you didn't find this helpful

Why wasn't this helpful? (check all that apply)

Couldn't find what I was looking for
Instructions are confusing
Instructions didn't work
Title is misleading
Content is out-of-date
The translation is poor

Thanks for your feedback.

If you can't find what you're looking for or you have a workflow question, please try Foundry Support.

If you have any thoughts on how we can improve our learning content, please email the Documentation team using the button below.

That's great!

Thanks for taking time to give us feedback.