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 11.2v7

# Release Date

19 September 2019

# Qualified Operating Systems

• macOS Sierra (10.12) or macOS High Sierra (10.13)

• Windows 7 or Windows 10 (64-bit)

• CentOS 6 or CentOS 7 (64-bit)

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 2.0 (Fermi) or above. A list of the compute capabilities of NVIDIA GPUs is available at www.nvidia.co.uk/object/cuda_gpus_uk.html.

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 8.0 & 6.5 or above.

• On Windows and Linux, CUDA graphics drivers are bundled with the regular drivers for your NVIDIA GPU. Driver version r361 or above is required.

Go to http://www.nvidia.com/Download/Find.aspx?lang=en-us for more information.

• On Mac, the CUDA driver is separate from the NVIDIA graphics driver and must be installed, if you don't have it already. The minimum requirement is driver version r361 which can be downloaded from www.nvidia.com/drivers.

Note: We recommend using the latest graphics drivers, where possible, regardless of operating system.

#### AMD

• On Windows and Linux, an AMD GPU and driver from the following list:

Windows GPU | Driver | Linux GPU | Driver
--- | --- | --- | ---
AMD FirePro W8100 | 17.Q2.1 | AMD FirePro W8100 | 17.Q2.1
AMD FirePro W9100 | 17.Q2.1 | AMD FirePro W9100 | 17.Q2.1
AMD Radeon R9 Fury X | 17.4.3 - 17.6.2 | AMD Radeon R9 Fury X | 17.10
AMD Radeon RX 480 | 17.Q2.1 | AMD Radeon RX 480 | 17.Q2.1
AMD Radeon Pro WX 7100 | 17.4.3 - 17.6.2 | AMD Radeon Pro WX 7100 | 17.10

Note: Other AMD GPUs may work, but have not been fully tested.

• On Mac an AMD FirePro GPU on late 2013 Mac Pro 6,1, mid 2015 MacBook Pro 11,5, and late 2016 MacBook Pro 13,3, running OS X 10.9.3 'Mavericks', or later.

### Mac GPUs

Nuke supports GPU-enabled nodes on the late 2013 Mac Pro 6,1, mid 2015 MacBook Pro 11,5, and late 2016 MacBook Pro 13,3, (running OS X 10.9.3 'Mavericks', or later), including a new Enable multi-GPU support option. When enabled in the preferences, GPU processing is shared between the available GPUs for extra processing speed.

Note: To ensure you get the best performance from OpenCL GPUs, we recommend updating Mavericks to 10.9.5, or above for full functionality. However:
If you're running an earlier version of Mac OS X than 10.9.5 and processing images greater than 4 mega pixels resolution, VectorGenerator, Kronos, and MotionBlur do not support GPU acceleration.
If you're running an earlier version of Mac OS X than 10.9.4, Kronos and MotionBlur do not support GPU acceleration.

# New Features

There are no new features in this release.

# Feature Enhancements

There are no feature enhancements in this release.

# Bug Fixes

• ID 158765 - DeepRecolor: Enabling target input alpha flattened Deep channels that should not be affected.

• ID 242922 - Timeline Editing: Using the Slip tool in sequences with multiple tracks in the Viewer occasionally caused Nuke Studio to become unresponsive.

• ID 347416 - Deep: Writing output containing Deep data using the standard Write node caused Nuke to crash.

• ID 349303 - Text: Changing the opacity of text shifted the output to the left and created artifacts in the Viewer.

• ID 350840 - Linux only: Labels in the Node Graph became unreadable at certain zoom levels.

• ID 352422 - Read/Write: Importing a previously exported .mov clip displayed a PAL format warning.

• ID 362521 - Roto/Rotopaint: The tooltip for adjusting B-spline tension in the Properties panel ? button was incorrect.

• ID 378932 - Running stereo scripts containing nodes in an error state in terminal mode with the continueOnError=False argument rendered frames incorrectly.

• ID 381706 - Documentation: The description of the keyboard shortcut for adding custom tags (Ctrl/Cmd+Y) was ambiguous.

• ID 387321 - Read/Write: The Write node's first part control did not work expected when write full layer names was enabled.

• ID 388199 - macOS only: Launching Nuke Assist enabled the Frame Server incorrectly.

• ID 390486 - Read/Write: Opening multiple projects while elements were still loading caused Nuke Studio to crash.

• ID 392348 - Text: Expressions resulting in Unicode characters were not displayed correctly.

• ID 393519 - Deep: Using DeepHoldout operations on multi-sample deep images produced artifacts.

• ID 399956 - ARRIRRAW: Interaction with ARRIRAW footage in Nuke was sluggish.

• ID 402361 - OCIO: All LUTs from config files were loaded, even if they were not used, causing Nuke to start up more slowly.

# New Known Issues Specific to Nuke 11.2

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

• ID 400857 - Card3D: The 3D Viewer rotation handles do not work as expected.
As a workaround, adjust the rotation using the Properties panel rotate controls to activate the handles.

• ID 394503 - Localization: The priority list for localization is not always honored when localization begins.

• ID 370989 - Windows only: Adding soft effects or retimes to shots with certain aspect ratios causes renders to timeout.

• ID 356283 - ARRIRAW: The Read node's aspect ratio control displays the ratio incorrectly.

• ID 355719 - ARRIRAW: Deprecated resolution modes are not labeled in Nuke.

# Developer Notes

Here are the changes relevant to developers. See Help > Documentation from the Nuke menu bar or https://learn.foundry.com/nuke/developers/112/ndkdevguide/appendixc/index.html for more information.

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 | 10.0v1 to 10.0v2 | API and ABI |  |
Point | 10.0v1 to 10.5v1 | API |  |
Major | 10.0v1 to 11.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")

## New Features

There are no new features in this release.

## Feature Enhancements

There are no feature enhancements in this release.

## Bug Fixes

There are no bug fixes in this release.

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.