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.3v2

# Release Date

07 February 2019

# Qualified Operating Systems

• macOS High Sierra (10.13) or macOS Mojave (10.14)

• 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, AMD GPUs are supported on any Mac Pro running Mac OS X Mavericks (10.9.3 ), mid 2015 MacBook Pros onward, and late 2017 iMac Pros. 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.

Warning: Although AMD GPUs are enabled on Mac Pros manufactured prior to the late 2013 model, 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 FirePro W9100s.

# New Features

There are no new features in this release.

# Feature Enhancements

• ID 375738/379636 - R3D SDK: The HDR2084 gamma curve was incorrect and has been superseded by a new st2084 curve.

• ID 377230 - Particles: Details of the Particle Performance API improvements have been added to the Nuke NDK Development Guide.

• ID 378349 - AMD GPUs are now enabled on Mac Pros manufactured prior to the late 2013 model, but they are not officially supported and are used at your own risk.

# Bug Fixes

• ID 155871 - ParticleDrag: The steps per frame control in the ParticleSettings node was not taken into account when applying drag. For example, with 10 steps per frame, the drag factor was applied 10 times in the full frame. This resulted in far slower particles than in the original script.

• ID 182027 - Export: Manually typing values into float sliders inserted .0 into the value.

• ID 200229 - SmartVectors: Canceling a write operation in the SmartVector node displayed a misleading error message or caused Nuke to become unresponsive.

• ID 238890 - Write: Rendering multiple views using OCIO color management produced inconsistent colorspace values between views.

• ID 270934 - Timeline Disk Caching: Caching sequences containing gaps in the timeline did not update the cache button correctly.

• ID 361048 - Node Graph: Saving and clearing scripts containing cloned nodes caused Nuke to crash.

• ID 361176 - Export: Shot referring to transcoded clips as the image source in the Export dialog displayed an error on export.

• ID 365600 - Sony SDK: Reading in certain .mxf files displayed a warning message on the command line.

• ID 366511 - Particles: Caching certain heavy simulations was slower than in previous versions of Nuke.

• ID 367089 - ARRIRAW: Dragging certain .ari files into the Node Graph momentarily showed an error on the Read node.

• ID 369203 - Sony SDK: Certain .mxf files did not playback as expected due to decoding errors.

• ID 372273 - LiveGroups: Knobs exposed on a locked, child LiveGroup were not locked when the parent LiveGroup was published.

• ID 373055 - Channel Management: Loading a script that exceeded the channel limit caused all Read nodes in the script to display an error.

• ID 373170 - Sony SDK: Setting the Gamut control to Rec709 did not match the Colorspace node's sRGB output.

• ID 373222 - Timeline Caching: Certain interface components did not update correctly when the Clip Reformat option was changed.

• ID 373227 - LiveGroups: Undoing edits to a LiveGroup did not return the group's state to editable.

• ID 373429 - Multi-View Timelines: The view order was reversed when the Viewer was set to Squeezed Above Below.

• ID 373458 - Sony SDK: Undoing changes to certain Read node controls displayed an error.

• ID 373543 - Colorspace: S-Log2 expected IRE range data which was inconsistent with S-Log1 and S-Log3.

• ID 373862 - ARRIRAW: Loading a legacy script automatically set Read node's Processing > Sharpness knobs to 0, but did not display a warning.

• ID 374142 - macOS only: Cloning certain custom knobs using Shift and drag-and-drop did not work as expected.

• ID 374767 - LiveGroups: The knob override popup did not always behave predictably.

• ID 375568 - LiveGroups: Keyed knobs exposed on LiveGroups were loaded as overrides incorrectly.

• ID 376623 - Soft Effects: Setting a Timewarp effect to Predefined > Reverse in the Curve Editor's right-click menu displayed an error.

• ID 377901 - ARRIRAW: The playback cache always cached frames at full resolution, despite the Viewer settings.

• ID 378060 - LiveGroups: Displaying a dialog when running Nuke in terminal mode using the -t command line flag caused Nuke to crash.

• ID 379209/379210 - R3D SDK: Undoing changes to the Color Space or Gamma Curve controls displayed an invalid LUT error.

• ID 379243 - ARRIRAW: The st2084 LUT multiplied shots with soft effects incorrectly.

• ID 380082 - Opening certain legacy projects caused Nuke Studio to crash.

# New Known Issues Specific to Nuke 11.3

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

• ID 376045 - ARRIRAW: Dropping files with more than one period in the file name from the Project panel to the Node Graph displays a temporary error on the Read node.

• ID 374982 - Windows only: LiveGroups knob override indicators don't display or update immediately in the Properties panel.

• ID 373072 - Sony SDK: Setting Resolution to Eighth displayed dead pixels in the Viewer for certain clips.

• ID 366048 - Linux only: Running heavy Particles simulations occasionally display the OS not responding error dialog.

# Developer Notes

Here are the changes relevant to developers. See Help > Documentation from the Nuke menu bar or https://learn.foundry.com/nuke/developers/113/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

• ID 374902 - LiveGroups: The node.makeEditable() function did not have a visible return value.

Can't find what you're looking for? Use our feedback widget on the right to request more information.
You must accept cookies from learn.foundry.com and disable any ad-blockers to provide feedback.