Release Notes for Nuke and Hiero 13.1v5
07 July 2022
Qualified Operating Systems
• macOS Catalina (10.15.x) or macOS Big Sur (11.x)
• Windows 10 (64-bit)
• CentOS 7.4 (64-bit), or later
Note: The currently supported version of VFX Reference Platform includes library versions that are only compatible with CentOS 7.4, or later. Nuke is qualified on the Centos 7.4, 7.5, and 7.6 distributions.
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.
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.
• AMD Radeon PRO W6600
• AMD Radeon PRO W6800
• AMD Radeon Pro W5700
• 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.
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.
There are no feature enhancements in this release.
• ID 404412 - AAF: Certain .aaf files with retimes were interpreted incorrectly as full length clips in Hiero or Nuke Studio.
• ID 428360 - DeepMerge: Holdout did not work as expected on volumetric data samples.
• ID 504266 - Export: Including additional frame handles occasionally caused misalignment of keyframes.
• ID 505472 - GridWarp/GridWarpTracker: Rendering from the command line with the Frame Server or a third-party renderer did not produce the same results as interactive renders.
• ID 507281 - Versioning: Changing the version of an unlinked track item occasionally selected the wrong version.
• ID 507925 - Topdown Rendering: Setting file type to mov and then changing the FPS in a Write node's Properties panel caused Nuke to crash.
• ID 508287 - Soft Effects: Making changes to certain soft effect controls in the Properties panel caused the Viewer to flicker.
• ID 510729 - CatFileCreator: Connecting a Viewer to a CatFileCreator node caused Nuke to crash.
• ID 510841 - AAF: Importing certain .aaf files from Avid or Resolve didn't align some shots in the timeline as expected.
• ID 511446 - Ocula Plug-ins: Disabling Use GPU if available in the node Properties panel with O_DisparityGenerator connected to O_DisparityViewer caused Nuke to crash.
New Known Issues Specific to Nuke 13.1
This section covers new known issues and gives workarounds for them, where appropriate.
• ID 507478 - 3D Viewer: Setting a custom object interaction speed value in the Preferences causes object rotation to behave erratically on the x-axis.
• ID 504398 - Monitor Out: Clicking Enable Monitor Out in the ViewerMonitorOut Properties with Device set to Floating Window displays a black frame before displaying the correct output.
• ID 504131 - OCIOv2: Inverting LUTs with large input values occasionally produces NaN (Not a Number) RGB samples in the Viewer.
• ID 503741 - OCIOv2: Loading certain ACES 1.2 OCIO config files displays OCIO LookTransform error: empty destination color space name errors in the Viewer.
• ID 503682 - 3D Transform Handles: Negative scale values on certain axes within imported geometry occasionally causes inconsistent scaling on other axes.
• ID 500698 - MergeGeo: Connecting MergeGeo nodes downstream of TransformGeo nodes causes Nuke to crash.
• ID 498115 - Viewing a shot in the RAW colorspace does not register changes to the Viewer gamma and gain controls as expected.
• ID 495298 - OCIOv2: Setting the OCIO_ACTIVE_DISPLAYS environment variable in Nuke Studio displays an error message.
As a workaround, set the OCIO environment variable to a valid config to suppress the error.
• ID 495297 - OCIOv2: Setting an invalid OCIO_ACTIVE_DISPLAYS environment variable and then selecting the aces_1.1 OCIO config causes some LUT settings to error or display blank.
• ID 495294 - OCIOv2: Setting an invalid OCIO_ACTIVE_DISPLAYS environment variable in Nuke displays an error on the command line.
• ID 492660 - Metadata: The ordering of multiple ModifyMetaData soft effects is reversed in the Metadata view.
• ID 492019 - Python: CatFileCreator custom knobs cannot be changed Pythonically unless the node Properties are open.
• ID 489310 - 3D Transform Handles: The highlighting on transform handles is not reset as expected with multiple Viewers open.
• ID 488896 - CatFileCreator: Executing CatFileCreator nodes from the command line with the -ti arguments does not work as expected.
• ID 488557 - Hydra Viewer: MergeMat does not work as expected with projections.
As a workaround, use Nuke's standard Viewer to view your scene.
• ID 488480 - Hydra Viewer: The alpha channel does not affect material transparency as expected.
• ID 488473 - Hydra Viewer: Meshes do not display textures correctly through ScanlineRender nodes during Viewer caching.
• ID 487606 - OCIOv2: Playback does not display as expected with a LUT soft effect applied that references a .csp file.
• ID 487522 - BM RAW: Video Assist files in the Project bin do not currently display thumbnails.
• ID 487001 - Hydra Viewer: BasicMaterial nodes do not show material diffuse clearly with the default settings.
• ID 486522 - 3D Transform Handles: The back of rotation handles are currently selectable in the 2D Viewer.
• ID 485347 - Multi-Project Edit: Dragging and dropping clips from multiple projects into an empty timeline does not work as expected.
• ID 485038 - Project Bin: Selecting the root project shifts the focus incorrectly in the Project panel.
• ID 485037 - Multi-Project Edit: Pasting a sequence into a bin does not paste any referenced clips/bins in to the same bin.
• ID 485033 - Multi-Project Edit: Pasting a sequence into a bin expands all contents by default.
• ID 484399 - 3D Viewer: Changing the display type for one 3D object incorrectly affects other objects.
• ID 484159 - 3D Transform Handles: The uniform scale control's drag behavior is dependent on the camera angle.
• ID 484094 - 3D Transform Handles: Dragging a uniform scale handle outside the Viewer does not work as expected.
• ID 483956 - Monitor Out: The mouse pointer position is inaccurate if the aspect ratios for Viewer and physical monitor don't match.
• ID 483819 - 3D Transform Handles: Transform handles appear deformed when viewed through ScanlineRender and zoomed out in 2D Viewer.
• ID 483447 - Hydra Viewer: Certain animated .usd assets are not displayed correctly in some timeline frames.
• ID 482659 - 3D Transform Handles: The scale handles do not work as expected in perspective.
• ID 481818 - 3D Transform Handles: The translate handles do not work as expected in perspective.
• ID 476685 - Soft Effects: OCIODisplay knob values are not preserved when pasted to the Node Graph.
• ID 475494 - Cryptomatte: Using Picker Add/Remove on Tcl expressions incorrectly replaces them with the underlying value.
• ID 471780 - OCIODisplay: Certain error messages include a typo.
• ID 470037 - Python: Cryptomatte selection behavior is inconsistent.
• ID 459009 - OCIOv2: Nuke's Viewer colorspaces incorrectly include (default) in the name.
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.
13.1v1 to 13.1v2
API and ABI
13.0v1 to 13.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")