Search TipsRelease Notes for Nuke and Hiero 11.3v4
Release Date
02 May 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 |
AMD FirePro W8100 |
||
|
AMD FirePro W9100 |
AMD FirePro W9100 |
||
|
AMD Radeon R9 Fury X |
AMD Radeon R9 Fury X |
||
|
AMD Radeon RX 480 |
AMD Radeon RX 480 |
||
|
AMD Radeon Pro WX 7100 |
AMD Radeon Pro WX 7100 |
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
Deep
The DeepHoldout and DeepMerge nodes now include a compute occluded samples control. When enabled, the values of samples from main are affected by the occlusion values of the holdout samples in front of them. When disabled, holdout occlusion is ignored.
For example:
M = main sample
H = holdout sample
M0 remains unchanged since there are no holdout samples before it. M2 is affected by the combined H0, H1, and H2 holdout samples and M4 is affected by all holdout samples.
Additionally, the DeepMerge drop zero threshold control is now included in DeepHoldout, allowing you to filter out samples whose alpha value falls below this threshold, such as those caused by floating point inaccuracy.
Bug Fixes
• ID 320261 - Linux only: GPU accelerated Convolve2 nodes in some customer scripts printed Error: filter input is missing rgba in the Viewer.
• ID 322910 - Deep: DeepMerge nodes set to holdout produced a less accurate result when compared to DeepHoldout nodes.
• ID 324076 - DeepHoldout: Alpha occlusions did not holdout correctly.
• ID 330903 - Deep: The DeepHoldout and DeepMerge in holdout mode produced different results.
• ID 376892 - DeepMerge: Setting operation to holdout combined alpha values if the B input was semi-transparent and behind the A input.
• ID 386217 - LensDistortion: Adding a LensDistortion2 node to the Node Graph displayed a Warning: enumeration index value cannot be converted to int for item Lanczos4 message on the command line.
• ID 389350 - Linux only: Reading in .mxf files displayed a GLIBC_2.14' not found error.
• ID 390303 - Deep: The knob names and tooltips for the DeepHoldout and DeepMerge nodes were misleading.
New Known Issues Specific to Nuke 11.3
This section covers new known issues and gives workarounds for them, where appropriate.
• ID 376534 - Timeline Multi-View: Switching to and from the timeline Viewer OpenGL Stereo mode causes playback to pause. Press play to resume playback.
• ID 366048 - Linux only: 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 |
11.0v1 to 11.0v2 |
API and ABI |
|
|
|
Point |
11.0v1 to 11.2v1 |
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
• ID 380807 - Python: You can now set node icons in the Node Graph Pythonically using the setCustomIcon() function.
Feature Enhancements
There are no feature enhancements in this release.
Bug Fixes
• ID 378856 - Python: Setting the default value knob Root.views() in the init.py file did not work as expected.
• ID 387422 - Documentation: The ParallelFor API was not documented in the Nuke NDK documentation.
