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 14.0v2

# Release Date

19 January 2023

# Qualified Operating Systems

• macOS Big Sur (11.x) or macOS Monterey (12.x). Nuke is currently supported under Rosetta emulation on Apple's new Apple Silicon hardware and M1 chips. Native support is not currently available and Foundry is planning to support the Nuke family natively on Apple's M1 and M2 hardware at a later date.

Article: For more information on Foundry products and supported macOS versions, see Foundry Knowledge Base article Q100592.

• Windows 10 (64-bit) and Windows 11 (64-bit)

• CentOS 7.6 (64-bit), or later

Note: The currently supported version of VFX Reference Platform includes library versions that are only compatible with CentOS 7.6, 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.5 (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 11.1, or above. On Windows and Linux, CUDA graphics drivers are bundled with the regular drivers for your NVIDIA GPU. Driver versions 456.81 (Windows) and 455.32 (Linux), or above are required. See https://www.nvidia.com/Download/Find.aspx for more information on compatible drivers.

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

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

## Simulate Physical Lens Behavior with Bokeh

Nuke 14.0v2 includes a new node, Bokeh, which is a native version of a plug-in originally developed by Peregrine Labs and acquired by Foundry in 2022. The native version of Bokeh in Nuke is backwards compatible with version 1.4.8 of the pgBokeh plug-in. Bokeh defocuses an image according to a Z depth map, Deep data, or Camera information and allows you to control where the focal plane lies so you can focus on specific elements in an image, and simulate real-world lenses. You can also control the shape of the defocus kernel using the Kernel input.

See the Bokeh reference documentation for more information.

# Feature Enhancements

• ID 525528 - 3D Arch: UsdProcessingEngine documentation is now available through the Help > Documentation menu.

# Bug Fixes

• ID 159324 - Python Documentation: The hiero.core.nuke.launchNuke() function was not documented correctly in the Hiero Python Developers Guide.

• ID 506934 - CopyCat: Collapsing the Preview panel in the Viewer did not redrawn it next to the contact sheet as expected.

• ID 509958 - 3D Arch: Inserting a TimeClip node between a texture node connected to a geometry img input and a geometry node caused the texture to flicker.

• ID 514129 - 3D Arch: Deselection in the Vertex selection and Face selection modes did not work as expected.

• ID 516157 - 3D Arch: SpotLight did not work as expected with ShapingAPI attributes.

• ID 516624 - 3D Arch: Changing the Camera projection_mode did not change the camera wireframe in the 3D Viewer as expected.

• ID 519331 - 3D Arch: Camera4 nodes did not always pick up animation data from scene inputs.

• ID 519664 - 3D Arch: Scaling on GeoTransform with Prim Transform Order set to Append affected the scale of the handles unexpectedly.

• ID 519980 - 3D Arch: Projected output from the ScanlineRender2 did not always match the output from the Viewer.

• ID 521379 - 3D Arch: Connecting a Camera downstream of a GeoImport node made the scene disappear in the Viewer.

• ID 521704 - Python Documentation: The Hiero Python Developers Guide Included a typo.

• ID 522833 - 3D Arch: Rendering a DirectLight through ScanlineRender did not illuminate the correct side of geometry.

• ID 522835 - 3D Arch: Rendering a PointLight through ScanlineRender did light geometry in all directions as expected.

• ID 523203 - 3D Arch: Error: Failed verification: ' primInfo ' was continually printed on the command line when transforming prims.

• ID 523484 - Python API: 3D Arch attributes with empty array values incorrectly returned None.

• ID 523858 - 3D Arch: The Scene Graph tab search function didn't always work as expected on large scenes.

• ID 524172 - 3D Arch: The 3D Viewer and ScanlineRender shader output was not always consistent.

• ID 524405 - 3D Arch: Searching in the Scene Graph for a string with a large number of results caused Nuke to become unresponsive.

• ID 524470 - 3D Arch: Connecting the output of certain ScanlineRender nodes to the Viewer caused Nuke to crash.

• ID 524723 - Linux Ubuntu distros only: Using a Wacom pen with UI Scaling set to 1.5 offset the pointer position incorrectly.

• ID 524877/525578 - 3D Arch: Rendering a texture with animated transforms through ScanlineRender produced a pink hue incorrectly.

• ID 524901 - 3D Arch: Using relative paths in GeoInstance knobs caused Nuke to become unresponsive.

• ID 525462 - 3D Arch: The 3D texture cache occasionally retained textures from deleted node.

• ID 525570 - 3D Arch: GeomOp cached materials were not cleared as expected when connections changed.

• ID 525586 - 3D Arch: Local Parent TRS knobs were ignored when the Viewer was locked in a camera node.

• ID 525730 - 3D Arch: The display_color and display_opacity knobs could not be animated in prim node Properties panels.

• ID 526012 - 3D Arch: Changing the full size format of ScanlineRender output using the Project Settings caused Nuke to crash.

• ID 526069 - OCIO: Saving a project file with the OCIO config set to a new ACES 1.3 config caused Nuke Studio and Hiero to treat the configs as custom configs, which caused load problems on other machines.

• ID 526139 - 3D Arch: ScanlineRender did not render animated materials as expected.

• ID 526170 - 3D Arch: Certain USD assets were slower to load with Display Materials disabled in the GeoImport controls.

• ID 526188 - 3D Arch: Drag selecting in the Viewer with Object selection mode active did not highlight selections as expected.

• ID 526219 - 3D Arch: Duplicating prims with GeoInstance produced multiple Duplicate item errors on the command line.

• ID 526473 - ARRIRAW: Changing the file path in a Read node and then saving and reloading the script displayed multiple knob errors unexpectedly.

• ID 526511 - 3D Arch: Classic Nuke 3D Light nodes had authoring enabled for Color and Intensity.

• ID 526644 - Node Graph: Pressing Tab in the Node Graph to search for nodes had a delayed response time.

• ID 527584 - OCIO: NamedTransform selection was failing on script loading.

• ID 527630 - Read/Write: Writing all channels to a multiview .exr did not work as expected.

• ID 528117 - 3D Arch: GeoPrune did not prune Lights as expected.

• ID 528316 - Expressions: Copy/pasting expression linked nodes in the Node Graph discarded the expression link.

• ID 528541 - ReadGeo: The Scenegraph tab Load column in the node Properties was empty when importing .usd files.

• ID 528667 - Documentation The OpenTimelineIO version listed in the third-party library list was incorrect.

• ID 531816 - 3D Arch: Null prims in imported geometry caused Nuke to crash.

• ID 531993 - AIR: AIR nodes, such as Upscale, displayed errors on the command line when CUDA wasn't installed on the machine.

• ID 532002 - Python API: Calling OfxPropertySuiteV1::propGetInt() for the parameter kFnOfxImageEffectPropView caused Nuke to crash.

# New Known Issues Specific to Nuke 14.0

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

• ID 532211 - Windows only: QEventDispatcher messages are displayed in the command prompt, but they can be ignored.

• ID 532078 - Bokeh: Attaching an image to the Kernel input does not work as expected in Viewer downrez and proxy modes.

• ID 527100 - AIR: On machine running under Lovelace GPUs, a message that the kernels need caching displays on the command line despite there being no need for PTX caching.

• ID 526530 - CatFileCreator: Converted .cat files from Nuke 14 cannot be used in earlier versions of Nuke.
As a workaround, convert the .cat file in the version of Nuke you intend to use, such as Nuke 13.2v5.

• ID 526245 - UnrealReader: Disabling Advanced > Cinematic Quality in the node Properties occasionally displays incorrect output on multiple passes.

• ID 526041 - 3D Arch: Payload overrides in the Scene Graph do not work as expected for nested payloads.

• ID 525872 - 3D Arch: The GeoDrawMode node's Draw Color can not be animated as expected.

• ID 525863 - 3D Arch: DirectLight has much brighter intensity when rendered through ScanlineRender than in the 3D Viewer.

• ID 525819 - 3D Arch: Display Color animation in Nuke geometry nodes, such as GeoCube, is not displayed as expected when rendered through ScanlineRender.

• ID 525817 - 3D Arch: Display Opacity changes in Nuke geometry nodes, such as GeoCube, are not displayed as expected when rendered through ScanlineRender.

• ID 525816 - 3D Arch: Display Opacity changes are not displayed as expected when blended against the background.

• ID 525807 - UnrealReader: The OCIOConfigurationIsEnabled knob name on the Advanced tab contains a typo.

• ID 525714 - 3D Arch: Selections in the 3D Viewer are added to selections from the Scene Graph tab when scene graph locations are dropped in a node's Mask control.

• ID 525575 - CameraTracker: CameraTrackerPointCloud nodes incorrectly display point data in the 2D output from ScanlineRender.

• ID 524835 - OCIONamedTransform: The Viewer error when no transform is selected contains a [ (square bracket).

• ID 524626 - 3D Arch: Hit detection in the 3D Viewer is slower than in previous versions of Nuke, which causes delayed response times.

• ID 524411 - Read/Write: Reading certain ARRI Alexa 35 files displays an arrimxf_json_deserialize error message on the command line.

• ID 522999 - 3D Arch: CameraTrackerPointCloud displays as a red node, rather than green to indicate that it is a legacy 3D system node.

• ID 522873 - Read/Write: Connecting a Viewer to a Read node that references an ARRI Alexa 35 file causes Nuke to crash if the thumbnail is still rendering.

• ID 521937 - 3D Arch: Changing the active state of materials in the scene graph disables the material for the current Viewer node.
As a workaround, create a new Viewer node and connect it to the scene.

• ID 521907 - 3D Arch: Points in point clouds generated from CameraTracker data default to a size too large for the Viewer.

• ID 521508 - 3D Arch: The bounding box does not always follow its geometry downstream of a GeoMerge node.

• ID 521133 - 3D Arch: Rotating geometry using the transform handles in the Viewer does not follow pointer movement as expected.

• ID 520821 - 3D Arch: The CameraTracker point cloud Point Size control does not scale as expected at large size values.

• ID 520716 - 3D Arch: The GeoImport > Display Materials checkbox does not always toggle materials on and off.

• ID 520622 - 3D Arch: The Draw Mode applied by GeoDrawMode nodes is not set consistently.

• ID 520296 - 3D Arch: Creating a GeoSphere or GeoCylinder node in the Node Graph labels the tab in the Properties panel incorrectly.

• ID 520282/519482 - UI: Moving the Licensing dialog around causes the window to jitter.

• ID 519987 - 3D Arch: Creating nodes Pythonically does not always create the expected node connections.

• ID 519068 - Windows Installer: Specifying a different install directory does not automatically create a Nuke container directory for the necessary Nuke files.
As a workaround, manually specify a container directory during install.

• ID 518874 - 3D Arch: Double-clicking prims in the Viewer does not open the associated Properties panel as expected.

• ID 518795 - 3D Arch: GeoCard always writes the control_point knob value in the Nuke script, even if it's set to the default value.

• ID 518654 - 3D Arch: Node names are occasionally drawn incorrectly at different Node Graph zoom levels.

• ID 518593 - 3D Arch: Setting the Mask to a prim that is not the node above a GeoDrawMode ignores the selected Draw Mode.

• ID 518581 - UnrealReader: The CompareMetaData node reads incorrect frame metadata from UnrealReader Write section rendered EXRs.

• ID 517980 - Windows Installer: The installer screen occasionally displays twice during installation.

• ID 516166 - 3D Arch: Pressing Enter to cycle through searched items in the Scene Graph allows items to be cycled through even if a contributing node is removed upstream.

• ID 516052 - 3D Arch: Projected textures in some customer scripts are placed incorrectly by ScanlineRender2.

• ID 515379 - 3D Arch: The GeoSphere default Height value is incorrect.

• ID 515370 - 3D Arch: Clicking Invert Selection in the GeoPrune properties does not update mask selections correctly in the Viewer.

• ID 515355 - 3D Arch: Scaling in World space after rotation skews the transform and scale handles incorrectly.

• ID 515353 - 3D Arch: Scaling in World space after rotation causes the rotation handles to wobble.

• ID 514854 - 3D Arch: Scale handles in World space don't work as expected if the pivot point of geometry is rotated.

• ID 514693 - 3D Arch: Handle rotations at large scale can become inconsistent and unstable.

• ID 514669 - 3D Arch: The Z-axis handle is not working in the Viewer Screen space.

• ID 514631 - 3D Arch: The match position menu (snap menu) doesn't work as expected in the new 3D system.

• ID 513943 - 3D Arch: The Localization controls are missing from GeoImport's node Properties.

• ID 513286 - 3D Arch: Vertex selection occasionally discards selected points.

• ID 513142 - 3D Arch: Vertex grouping does not grouping all selected vertices in PointCloudGenerator point clouds.

• ID 511940 - 3D Arch: Prims with no Kind assigned are ignored by the GeoDrawMode node.

• ID 511765 - 3D Transform Handles: Scaling a camera on a single axis does not always work as expected.

• ID 511107 - 3D Arch: Exclusion does not work as expected in the GeoCollection node.

• ID 510783 - 3D Arch: Small u_extent and v_extent values in GeoSphere/GeoRevolve(Sphere) cause textures to disappear in the Viewer.

• ID 505862 - 3D Pivot Point: Rotation stabilization doesn't work as expected in XYZ and ZYX rotation order mode.

# 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 | 13.2v1 to 13.2v2 | API and ABI |  |
Point | 13.1v1 to 13.2v1 | API |  |
Major | 13.0v1 to 14.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 13 and Nuke 14, the Axis node Class() changed from Axis3 to Axis4. In the toolbars.py file for the two releases, the entries for the Axis node appear as follows:
m3Dclassic.addCommand("Axis", "nuke.createNode(\"Axis3\")", icon="Axis.png", tag=MenuItemTag.Classic, node="Axis3", tagTarget=MenuItemTagTargetFlag.TabMenu)
m3D.addCommand("Axis", "nuke.createNode(\"Axis4\")", icon="Axis_3D.png", tag=MenuItemTag.Beta, node="Axis4")

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.