5 December 2024
We are excited to start the journey towards enabling a native Multishot compositing workflow in Nuke. We want to support artists in becoming more efficient, giving them more control and making Multishot workflows easier.
This beta includes the early release of some features allowing for ongoing testing and development to ensure we deliver meaningful and impactful workflows in upcoming releases.
You can see a workflow example here: GSV Workflow Example
Graph Scope Variables (GSVs) are the backbone that enables a native Multishot compositing workflow in Nuke. GSVs allow you to define, store and access the data required for multiple contexts or scopes in a single Nuke script.
The workflow, however, becomes more powerful when combined with Group nodes. A Group node defines the “Scope” part of the Graph Scope Variables feature and introduces the ability to inherit and override variables.
We have added a new VariableSwitch node, to allow users to switch between different shots or scopes using variables. The new VariableSwitch node works similarly to the Switch node but enables you to create “split and join” workflows based on the variables set for your Multishot workflow.
We have also added a new VariableGroup node, to allow users to define variables or scopes. This works similarly to the regular Group node, but for every new VariableGroup created, a corresponding VariableGroup item is created in the Variables tab in the Project Settings. Inside the VariableGroup node, the Variables tab contains a single GsvKnob, which allows the user to create, edit and remove variables and variable sets.
To easily interact with the available Variables in a script, we have added a Variables Panel.
To be able to switch between the different values, first set the Variables you wish to expose in the Variables tab in the Project Settings. Once the visibility is On (eye icon in the Variables tab) the Variable will appear in the Variable Panel.
LiveGroups now allow the user to define local variables on the LiveGroup itself, much like the VariableGroup. On publish these variables are written into the LiveGroup .nk script and will be loaded as local variables for LiveGroup instances which use that same .nk script.
We have extended the command line interface to include support for specifying Graph Scope Variables so that scripts can be rendered using the correct shot context as shown below:
./Nuke16.0 --gsv \<variable1>:\<value1> -F \<framerange> -X Write1 \<path_to_your_nuke_script>
Multiple variables can be specified using a “,” separated list as below:
./Nuke16.0 --gsv \<variable1>:\<value1>,\<variable2>:\<value2> -F \<framerange> -X Write1 \<path_to_your_nuke_script>
As a sequence example you could use variables like the one below in your Write nodes:
/project/%{seq}/%{shot}_key.####.exr
And render using the next command line:
./Nuke16.0 --gsv seq:seq030,shot:Sh100 -F 1101-1105 -X Write1 \<path_to_your_nuke_script>
The new Group View feature gives artists a convenient way to see inside and edit the contents of multiple Group nodes, without having to jump to different tabs, making it faster and easier to adjust your comp in multiple different groups at the same time.
Group nodes are also an integral part of the new multishot and Graph Scope Variables feature, providing a way to organise and manage multiple scopes, so being able to see inside those Groups from the main DAG is really useful in those workflows.
A new way to perform compressed video file exports of sequences in Nuke Studio and Hiero.
Based on Nuke Studios real time playback engine, the new render engine enables you to perform accelerated exports to ProRes, DNxHD, DNxHR, as well as H264 movies with an average 12 fold increase in performance relative to the existing export mechanism. This means you are likely to see multi-real time performance in most cases, depending on your source and destination formats.
Introducing Multichannel Soft Effects in Hiero and Nuke Studio.
Multilayer EXRs are now visible and can be modified within the timeline.
Streamline workflows:
Use channels creatively:
Send to Nuke as Creative Intent:
BlinkScript Editor Updates
The built in BlinkScript editor has been updated to support common IDE functionality. Making the day-to-day creation of BlinkScript effects in Nuke, seamless and intuitive for both new and existing users.
The following behaviours have been added:
Library Files
The addition of Library Files allows users to share common functions and code snippets across multiple kernels and projects. Previously the same functions would need to be rewritten for every single kernel, wasting effort and introducing possible errors in the process. With Library Files, these common functions or libraries can be reused and centrally updated across a studio's blink effects. This means that common classes only need to be written once, and you can now add your own inbuilt functions.
Safety Rails
BlinkScripts are a powerful tool, and the editor gives you the complete control to make and break things. The introduction of Safety Rails makes it simpler to catch problems when prototyping new BlinkScripts and makes it less dramatic when mistakes happen. Combined with the addition of the println() function you are now also able to troubleshoot out-of-bounds pixel accesses. Information and any errors this might catch are now logged directly in the terminal.
Core node improvements
With the new 3D system continuing its development journey we wanted to take some time to make sure the nodes you work use most frequently were being updated based on user feedback and to introduce some new features and workflows with them.
Within this first batch of core node improvements we have updates to the GeoCard, GeoCube, GeoSphere and GeoCylinder nodes which improve UI layout, tooltips, path defaults and more.
The GeoTransform node see's an updated UI for commonly used masking and an updated snap menu that allows you to snap to vetex points just like you always could, but also introduces new workflows that allow you to snap to a prims bounding box, which is useful when you want to quickly bring your transform jack set at the origin to a prim elsewhere in your scene.
The GeoMerge and GeoScene node, have the A pipe appearing by default now which means you can drag these nodes into pipes and have them connect irrespective of if it's connecting to a B or A input (previously would only connnect to a B pipe) and a new option called 'Isolate Prims From' makes merging isolated or pruned pipes more intuitive, where you see the result of both pruned pipes combined, unlike the Deisolate workflow which allows you to work on isolated prims, but when merging will reactivate the entire stage.
All geo modifier nodes have had their defaults set to 'All' rather than lastModified. This change as many others is thanks to user feedback and now when using the new nodes the behaviour will be more akin to the classic system and changing node graph topology won't be prone to changing the output of the script as could happen with LastModified as the default. A note to artists though, with All being the default please be mindful of what you are going to modify if working in large stages.
GeoXformPrim node
We have introduced a new GeoXformPrim node, with the ability to switch between Create and Edit modes, so that you can now create xforms inside your scene graph for better scene graph management and the abilityt to edit pre-existing ones.
GeoConstrain node
We have introduced a new GeoConstrain node, to give artists the ability to constrain one prim to another via multiple different constrain types, such as LookAt, Transformation and Parent. Artists can also offset this constraint in space and time, allowing for even greater control.
ScanlineRender2 - Motion blur and AOV output improvements
ScanlineRender2 has been progressing significantly as we have been building the new 3D system. With this release we have focused on giving artists greater control over how they render out of Nuke, with new workflows around motion blur, aov outputs and much more.
We have also started the building blocks for ray tracing, with ScanlineRender2 now being a ray traced architecture by default and controls for the ray depth bounce available. Please note though that this work is still ongoing as shader support for lights and materials will need to be fully implemented to support rendering your imported stages.
This ray traced architecture is targeting for compositors needs, so shouldn't be thought of as a replacement to large scale scene renders. Instead this is all about expanding a compositors toolset to get render passes they need at a late stage in production and allow them to create more complex renders from Nuke when adding in composited elements.
USD Version 24.05
Each release we are dedicated to providing users an up to date version of USD, so for this release we have also updated to USD version 24.05, giving access to all the bug fixes and features included in this version.
FoundryGL
On macOS, Nuke is no longer using Apple's system OpenGL library and instead is using Foundry's alternative, FoundryGL. The reason for this change is that Apple has deprecated OpenGL and may remove it in future macOS versions.
While this change should have no impact for users per se, some external dependencies, such as third party plugins and user-provided libraries, may need to be modified and/or rebuilt.
Documentation for FoundryGL is provided in Appendix A of the NDK Dev Guide.
NOTE: Windows and Linux versions will continue to use the system OpenGL and are unaffected by FoundryGL.
In 16.0 we continue improving Nuke’s OpenAssetIO integration to support larger, more flexible pipelines. This release includes updates to the OpenAssetIO libraries and OpenAssetIO-MediaCreation, adding support for C++ and hybrid Python/C++ manager plugins, allowing hot code paths (such as resolve) to be written in fast C++, whilst the remainder of a plugin is written in Python.
OpenAssetIO library updates:
ID 589542 -
Foundry licensing now uses RLM 16 client. See Reprise Release Notes for full details.
Improved support for customers using cloud licensing who have enabled MAC address randomisation.
Improved host ID checks for cloud based licensing to prevent frequent license log outs when changing between networks.
Addresses issues some customers experienced acquiring a license when using Nuke in different locales.
Customer's with valid non-commercial licenses were unable to open Nuke due to a licensing error.
Some macOS users were unable to determine the host ID.
RLM license consumption was incorrect if multiple hosts on the network shared the same host name.
ID 165214 - Added animated snapping to Snap Menu and Python API to get vertex positions from arbitrary number of frames.
ID 424269 - Added the ability to snap geo to animated geometry using the snapping menu
ID 513388 - GeoSphere and GeoCylinder no provide the ability to create half spheres and half cylinders
ID 514422 - 'mat' input is automatically connected if a Geo node is created downstream
ID 566219 - Create missing Xform parents automatically with the 'Create Missing Parents' knob
ID 566223 - Can now animate GeoSource node's Visibility Knob from the UI.
ID 566225 - Geo node main pipe and mat input pipes positions updated
ID 568095 - Reorganised knobs for the Geocard UI.
ID 568096 - Reorganised knobs for the Geocube UI.
ID 568098 - Added tooltips for Geocard knobs.
ID 568099 - Added tooltips for Geocube knobs.
ID 568100 - Tooltips have been added for each knob for the nodes GeoSphere/GeoCylinder/GeoRevolve
ID 568101 - Removed old lens distortion section from the lens distortion tab of Geocard.
ID 568102 - New dropdown knob for quick mask selection options on geo modifier nodes
ID 576936 - 'All Included Children' and 'Default Prim' Mask options removed from Mask knob
ID 576938 - New Select Path Mask knob added to geo modifier nodes
ID 576939 - GeoTransform applies the transformation to the top most Xform prims when "All Roots" is selected.
ID 578319 - GeoMerge now defaults to having both the A and B pipe by default to allow for consistent connection behaviour to 2D merge nodes
ID 576560 -
The two argument (frame, view) OutputContext class constructor is being deprecated,
and its use is now strongly discouraged. The construction of OutputContext objects must require careful construction especially if the object is used for comparison, that has to consider proxy information, frame, view and the recently added Graph Scope. Badly initialized OutputContext objects can cause undefined behaviour in nuke depending on how and where there are used.
The previous default constructor has been updated to initialize the GraphScopePtr member to nullptr. It's advised to not use this constructor. A copy constructor from a Nuke provided OutputContext is preferred to ensure correct proxy and Graph Scope initialisation.
ID 232446 -
Add println logging function to aid debugging
ID 587935 - Support has been added for OpenFX OfxDrawSuiteV1
ID 588795 - Support for OpenFX has been updated to OpenFX 1.5.
ID 567672 - Hard-selected track items now display dashes to indicate which channels are present.
ID 575489 - The Inference Soft Effect in the timeline is now multichannel aware.
ID 575534 - Soft Effects show a visual indication when they are using a mask.
ID 577343 - Blinkscript Soft Effect works with multiple layers.
ID 578290 - Users can create new layers in the timeline, which become available in the viewer and in downstream soft effects.
ID 579039 -
You can now set In and Out points with "U" and "Shift+U" while the Viewer is active.
ID 148535 - Color Soft Effects have a channel dropdown
ID 569813 - There is a new Hue Correct soft effect.
ID 575293 - Lens Distortion affects all layers.
ID 575528 - Soft Effects can premult and unpremult using any layer.
ID 575564 - There is a new Soft Effect in the timeline: FilterErode. It runs on Blink, which means it is faster to process. It has a corresponding node in the nodegraph called BlinkFilterErode.
ID 587516 - The Soft Effects sub-menu has been changed to be better aligned with the nodegraph, and to be easier to read:
ID 560171 - A Preference has been added under the Panels > Timeline section that allows a user to choose whether Timeline Auto selector is active or deactivated.
Further than this an application startup environment variable is now available.
ID 565696 - Python has been updated to 3.11.
ID 565697 - Qt and PySide have been updated to version 6.5. There are significant changes in Qt 6 for both Python and C++ developers, developers should consult the "Porting to Qt 6" guide in the Qt documentation, and the "Porting Applications from PySide2 to PySide6" guide in the PySide documentation for details and advice on how to migrate.
ID 565700 - OpenEXR has been updated to version 3.2
ID 565702 - OpenSubdiv has been updated to version 3.6
ID 565704 - OpenVDB has been updated to version 11
ID 565705 - OpenColorIO has been updated to version 2.3
ID 565706 - Boost has been updated to version 1.82
ID 590376 - 3D Rotation handles draw with lower segment count
ID 568413 - GeoCard now only adds time samples as necessary.
ID 571981 - Geo nodes now pass their material input to group nodes
ID 572297 - Error messages no longer display at the top of the 3D viewer if you are viewing a node network which does not contain the erring node
ID 574010 - GeoUVProject cylindrical and spherical projections align correctly
ID 577351 - Nuke does not crash when selecting vertices or faces in classic 3D system geometry imported from USD files containing empty meshes or point clouds.
ID 579263 - Textures are updating in the viewer
ID 586173 - Constraint node - Scale broken when maintain offset if unchecked
ID 586675 - The 3d materials knob on the Viewer Node correctly affects materials
ID 587367 - Rotate is on by default for new snap menu
ID 587906 - Transform handles incorrectly scaled in 2D viewer
ID 587937 - Fixed incorrect/not showing tooltip for GeoConstrain.
ID 588118 - GeoConstrain vertex/face picker will pick on non-target prims
ID 588175 - GeoImport: Changing frame range while path in erred state no longer crashes Nuke
ID 588300 - The animated geo to selection snap option correctly snaps the geometry over the full frame range.
ID 588472 - Fixed crash on clicking the select path mask knob where the mask was an empty string.
ID 588860 - Negative values for the scene time offset for Scanline Render 2 now produce the right result.
ID 588863 - ScanlineRender2 no longer renders default material as black if no background image is connected.
ID 588890 - The custom size knob for Scanline Render 2 is now acting as the tooltip states.
ID 585862 - Overrides of channels knob are not saved
ID 586424 - Link node arrows disappear on collapse to group undo + redo
ID 586459 - Crash when trying to create link of GeoExport node
ID 577396 - Hiding and showing any GL widget causes it to freeze
ID 578471 - Extra lines rendered when vertices selected (and console error message)
ID 580232 - Manipulating the 3D handles is slow and interactivity is delayed (macOS)
ID 581530 - Entering full screen mode behaves differently (macOS)
ID 584834 - When using PyOpenGL with FoundryGL on MacOS Nuke 16 and later may behave unpredictably because PyOpenGL is linked with the system OpenGL framework rather than the FoundryGL framework shipped with Nuke.
Nuke ships with a PyOpenGL platform plugin that can be used to load the FoundryGL framework instead, in order to activate the plugin please include the following Python code before importing from PyOpenGL:
from nukescripts import setupPyOpenGL
nukescripts.setupPyOpenGL()
This code is a no-op on non-FoundryGL platforms, so is safe to include in cross-platform Python code.
ID 585967 - Drag and dropping footage from the Timeline Viewer will continue to flash on screen (MacOS) - Wacom
ID 587261 - Lines in the Curve Editor doesn't match previous nuke
ID 587784 - Setting Fullscreen to Monitor 2 in Preferences is not honoured - macOS
ID 588443 - Moving an item with transparency in the viewer adds a black background (macOS)
ID 588824 - 3D Grid is not rendering correctly (macOS)
ID 589228 - Transform handles and bounding box lines disappear when outside the edge of the viewer (macOS)
ID 586046 - Upscale: When using python to automate rendering with upscale, it complains that "No Cat file is selected".
ID 586051 - Inference: when infering certain custom .cat files (e.g. RealESRGAN) there will be no output image and an error in the viewer/terminal saying "Failed to copy output tensor to images".
ID 586053 - Upscale: Tiling is disabled
ID 586054 - Inference: when inferring on a non-existing or incorrect .cat file the error message is wrong
ID 586757 - Inference: Hitting out of memory on compute device error doesn't print in the terminal
ID 584121 - Nuke crashes when connecting inputs of linked or cloned Furnace nodes
ID 586747 - Furnace nodes crashes Nuke
ID 576668 - Read node does not update if the file does not contain frame data
ID 582763 - GVP does not update if the Variables tab in properties is not open
ID 584679 - Undoing a deleted link node will remove the UI link indication line
ID 585800 - Read nodes error in nodegraph when UI context is changed downstream
ID 587287 - Fix unlinking nodes in Python
ID 588902 - Postage stamps error when changing UI Context
ID 588986 - LiveGroup overrides for multiple knob rows not working
ID 590060 - Changing Variable list options from the GUI does not save changes
ID 585447 - Write node inside a VariableGroup is not using inherited variables when written out
ID 589310 - VariableSwitch does not pick up values from downstream VariableGroups
ID 589524 - Double clicking eye for variable visibility causes incorrect behaviour
ID 581447 - Unable to select soft effect with Soft effect selector whilst active playhead is present on current shot
ID 588083 - Fixed crash on exit when MonitorOut is enabled.
ID 589056 - Timeline viewer info bar covers bottom of image
ID 585991 - Drag and dropping files can lead to crash on macOS (Wacom)
ID 587350 - Tab menu can appear twice
ID 588163 - Cannot drag with Wacom tablet (macOS)
ID 588431 - Using the Alt+S hotkey will cause the mouse cursor to switch to the resize cursor
ID 588433 - Viewer/UI is lighter with external display and enableHDR pref on (macOS)
ID 588444 - Nodes toolbar menus are narrower causing issues with BETA tags
ID 588475 - Pressing "D" with the viewer in focus does not disable selected node (macOS)
ID 569363 - TimeOffset and Frameholds no longer affect prims that have been deactivated via GeoPrune
ID 575077 - ScanlineRender2 overscan error - error notification due to wrong knob name
ID 575330 - GeoCard 'Control Points' knob becomes unaligned when the type is changed from 'none'
ID 575713 - Axis: load all prims and payloads even if AxisOp importer is only loading a single prim
ID 576826 - Scanline render2 producing jagged edges in shadow
ID 577583 - Popup scenegraph to replace existing mask rather than appending
ID 578276 - Camera node produces wrong path
ID 579086 - Prim::setMetadataByDictKey(const Token&, const Token&, const Value&) method added
ID 579552 - GeoCard does not highlight when the node is selected
ID 579729 - Framehold not working when connected to the material input of GeoCard/GeoCube
ID 581736 - GeoXform in edit mode sets new nodes created under it as children of the modified node
ID 581737 - Switching GeoXform node from edit mode to create mode duplicates the node connected to it in the viewer
ID 582055 - Flaky behaviour when deforming GeoCard in the Bicubic mode of GeoCube deform tab
ID 582899 - ScanlineRender doesn't produce correct normals
ID 583116 - SLR2 not updating animated objects in windows OS
ID 583624 - Scenegraph overrides payloads load rules set in the node graph
ID 584419 - New snap menu pivot to bbox has unexpected results for some imported assets
ID 584677 - GeoPointsToMesh only handles default/vertex normals
ID 584735 - PoissonMesh and GeoPointsToMesh often hang
ID 584997 - Snap menu's pivot-to (orientation only) affects geometry if scale knobs are not all 1
ID 585615 - Matching expressions don't work with list based collections
ID 586470 - Hydra output on Intel Mac with Intel GPU has random colors and doesn't clear on redraw
ID 586966 - Translation issue for assets with z or x axis facing up in nuke
ID 587190 - Clipping plane disrupts geo in viewer when looking through camera
ID 587425 - Bleeding issues addressed in face mode selection
ID 587675 - Environment Lights Displaying upside down in the Hydra Viewer
ID 587677 - slr2 stripey Z depth output
ID 587941 - GeoConstrain Local Matrix has no effect if Specify Matrix is enabled
ID 588710 - GeoInstance transform doesn't animate
ID 589529 - Crash connecting an old camera or Axis to a GeoScene node
ID 590139 - GeoCard: should display the Rows/Columns when selected like the classic system
ID 590140 - GeoCard: doesn't always display materials with an alpha less then one
ID 590142 - GeoCard: double clicking GeoCard node should show the node as selected in the 3D viewer
ID 584226 - When a bracket is off screen, and then scrolled to, it is not highlighted
ID 588560 - Special Characters break the indicator
ID 588764 - The Safety Rails feature of BlinkScripts for guarding against out-of-bounds access is not enabled on the GPUs of Intel Macs
ID 589602 - Blink Kernels with Live Library Files error on script load
ID 589603 - Missing Library Files have an OK status when a script is loaded
ID 590444 - BlinkScript Editor draws off the edge of the screen when viewing large kernels
ID 588447 - Changing sequence resolution messes up the player layout
ID 589424 - Proxy scale only changes the first ClipPlayer
ID 589426 - ContactSheet Cog Icon moves when zooming in
ID 589427 - Pressing "V" over the contactSheet only displays the first Clip item versions
ID 589428 - Deleting Clips for the timeline sequence doesn't re-layout the contract sheet
ID 589431 - Viewer hotkeys and Viewer Image controls doesn't update till moving the mouse over the viewer
ID 589452 - Monitor Out only outputs the first clip
ID 589458 - Setting In and Out points in the ContactSheet also set them in the Timeline
ID 589474 - Cloned soft effects are border-highlighted in Pick Mode
ID 589489 - Timeline Tools are blurred when Pick Mode is active
ID 589491 - Spreadsheet selections
ID 589492 - Playback renders with alpha channels for EXRs
ID 589639 - Comparing sequences with different resolutions scales the images in the viewer relative to their respective resolutions
ID 589882 - Hangs when setting disabling Track Blending
ID 590045 - Preview players no longer have a gap between them
ID 590069 - When GlobalMonitorOut is disabled and ContactSheet Env Var is enabled, the MonitorOut Panel doesn't work
ID 590681 - While in TagSelection Mode, Adding tags into clips on the timeline rapidly increases memory usage
ID 588458 - Save values and filepath on export
ID 588460 - Allow multi selection for Views dropdown
ID 588463 - Change default export value to ProRes 422 HQ
ID 588464 - Default output transform should indicate the default colorspace
ID 588466 - Align Codec knob
ID 588522 - Open lastly used tab
ID 588966 - Add error messages / output when trying to export invalid filepath / extension
ID 589001 - Export hangs when exporting h264 file on specific linux machine
ID 589135 - Exported file with audio is few frames longer
ID 589137 - Exporting shot directly from timeline will show both TDE and Advance export tabs
ID 589369 - Memory usage increases on each export
ID 589526 - Default resize
ID 590316 - Incorrect pixel aspect ratio when exporting to PAL / NTSC
ID 590332 - Studio crashes when reading some mxf files
ID 590359 - 'Missing knobs' errors when exporting to Blackmagic Film Generation 5 output transform
ID 590381 - Shifted gap when exporting timeline with gaps using TDE
ID 590447 - Poor quality export of h264 file
ID 590448 - Audio settings ignored on export
ID 590451 - Incorrect timecode after exporting with TDE
ID 591046 - Quick Export only supports sequence export
ID 591047 - Audio is disabled on Beta 3 due to a known issue
ID 591048 - Ranges is unavailable in Beta 3 and will default to Whole Sequence
ID 591049 - Include Annotations is unavailable in Beta 3
ID 591050 - H.264 Advanced knobs will not affect output quality in Beta 3; only the Codec Profile knobs. H.264 is fixed at the highest quality for this Beta
ID 591051 - Advanced Settings for Apple ProRes, DNxHD and DNxHR in Beta 3 have no effect
ID 586417 - Python link() uses absolute path breaking copy/paste
ID 590472 - LookUpCurve knob is not linking
ID 585808 - UI line width is limited to 16 pixels (macOS)
ID 587863 - Nuke viewer capped at 60 fps (macOS)
ID 589414 - GeoCube is sometimes rendered as solid bright white (macOS)
ID 587583 - (Windows) Crash using older AMD drivers. Crash with 31.0.12027.9001 on a Radeon Pro WX 7100. No crash with 31.0.21916.1002 and 31.0.21018.6011 on a Radeon Pro WX 7100, and 32.0.11027.1003 on a AMD Radeon RX6700 XT.
ID 588360 - Additional keyframe no longer added for copied transform effects
ID 572587 - non-group nodes root item shows as unnamed
ID 574870 - A script without root variables will conceal group variables from the panel in saved scripts
ID 577486 - Middle click changes the hit group
ID 579481 - VariableSwitch Does not evaluate variable values with a space
ID 580854 - New Variable Sets are clearing same named Variable Groups and are unrecoverable (Undo/Redo)
ID 584180 - List dropdown needs double clicking
ID 584182 - Selecting a list option on an inherited variable will change the variable type to string
ID 584371 - Custom OCIO config knob not containing GSV string expansion
ID 584375 - Localisation doesn't work correctly for a single read node that switches shots via GSVs
ID 584377 - The height of the Label input box is larger than elsewhere (see the same widget for editing user knobs to the right)
ID 584589 - getDataType returns a non-existant variable as a string
ID 584590 - List type can contain an empty item
ID 584851 - Unsetting inherited variable shows visibility toggle
ID 585811 - Tab key will enable and disable a variables visibility
ID 586469 - UI link indication line remains from group to node if the linked node in the group is deleted
ID 586956 - Python function Node.overrideKnob missing undo
ID 586964 - Python 'link' function does not work as expected
ID 587036 - Disabled GSV knob is not scrollable
ID 587110 - Link node arrow disappears if we undo show group view
ID 587139 - Link nodes Copied/Cut from Group to main DAG have Linked node badges and override buttons even if they unlinked
ID 587222 - Double-clicking a root variable's visibility on VariableGroup inherited variable will break the connection [UI]
ID 587493 - User knobs added to linked nodes cause nuke to crash
ID 587589 - Cutting (CMD+X) a linked node, then cloning the parent and then pasting creates a cloned link
ID 587593 - Copy/Cut with nothing selected results in : 'Cannot copy/cut across multiple groups' error
ID 587722 - Closing timeline project can cause 'Variables' panel to disappear
ID 588192 - GeoImport Gsv file knob is not working as expected passing string vars
ID 589109 - Nodes in an input tree of a var group should see the variables defined by it
ID 589418 - Line arrow remains between Groups even when the link node is removed
ID 589521 - Removed selected List Type variables will remain in the list options
ID 589692 - When creating a new variable or folder, the new entry is difficult to see
ID 589706 - Updating variables using python does not update value until user clicks on the Variable panel
ID 590066 - Grouping input node crashes Nuke
ID 590072 - Grouping a group with a child link node breaks link
ID 590241 - Overwriting variable inherited from the root in VariableGroup node also overwrites the value of the variable added inside VariableGroup if it has the same name
ID 590243 - Variable Switch - Thumbnails will error temporarily before resolving with networked files
ID 590296 - Copy and paste nodes into LiveGroup should unlink
ID 590303 - Removing the currently selected list option visible in the variable panel doesn't remove the list item in the variable tab
ID 590305 - Exporting group to gizmo with linked nodes will unlink nodes inside the group
ID 590306 - Creating Precomp with linked node and selected no change option will unlink nodes in main DAG
ID 590348 - Variable name entry in VariableSwitch will be doubled with __default__ prefix if variable with same name exists in VariableSet or VariableGroup
ID 590424 - Changing the Root node GSV values causes some Nodes in the graph to have the incorrect uiContext (meaning they might show incorrect postage stamps, handles etc)
ID 589858 - Dragging the Variables tab Edit mode Pen will get stuck in highlight mode
ID 580110 - Knob values inherited from an asset are no longer highlighted after undoing a user change
ID 586349 - Knob values don't update on restart or clear caches
ID 586454 - Terminal warnings if OPENASSETIO_DEFAULT_CONFIG is set
ID 590469 - Incorrect rendering of some OFX plugins
ID 580026 - Active playhead selection prevents use of select track tool for other shots in the sequence
ID 580654 - Hard selecting an already soft-selected item with select or effect selector tool doesn't update the UI
ID 582613 - Shift + Dragging on an empty spot of the timeline causes the current soft selection to go into a hard selection
ID 586456 - AVP renderer doesn't work in Nuke
ID 587345 - Nuke take longer to open
ID 587691 - Moving mouse in and out of Curve Editor and Dope Sheet widgets causes the playheads to update - Timeline
ID 587877 - Floating monitor out window stuttering around while moving (Windows)
ID 590011 - Some enumeration knobs not displaying options after a panel has been floated
ID 590432 - UI Scaling options remained greyed out from the prefrences
ID 580551 - Paused image has a 1px blur when zoomed in at around 180-220%
ID 589226 - Viewer zoom control is unreadable at most zoom levels
ID 589601 - When selecting stacked text nodes, trying to transform the text via the handles instead selects the text
macOS Ventura (13.x), or macOS Sonoma (14.x)
For more information on Foundry products and supported macOS versions, see Foundry Knowledge Base article
Q100592.
Windows 10 (64-bit) or Windows 11 (64-bit)
Linux Rocky 9.0 (64-bit)
Nuke requires libnuma to run under Linux distributions, the library is required by the Nablet H264 Codec SDK.
The currently supported version of VFX Reference Platform includes library versions that are only compatible with Rocky 9.0.
Other operating systems may work, but have not been fully tested.
If you want to enable Nuke to calculate certain nodes using the GPU, there are some additional requirements.
An NVIDIA GPU with graphics drivers capable of running CUDA 11.8, or above. A list of the compute capabilities of NVIDIA GPUs is available at https://developer.nvidia.com/cuda-gpus
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.8, or above. On Windows and Linux, CUDA graphics drivers are bundled with the regular drivers for your NVIDIA GPU. Driver versions 522.06 (Windows) and 520.61.05 (Linux), or above are required. See https://www.nvidia.com/Download/Find.aspx for more information on compatible drivers.
We recommend using the latest graphics drivers, where possible, regardless of operating system.
Bitwise 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:
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 RX 6800 XT
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:
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.
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.
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.
Training using the CopyCat node requires an NVIDIA GPU, with compute capability 3.5 or above; or MacOS Apple silicon integrated GPUs.
If an appropriate GPU is not available, Inference and other machine learning plug-ins can run on the CPU with significantly degraded performance.
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 | 14.0v1 to 14.0v2 | API and ABI | ||
| Point | 14.0v1 to 14.1v1 | API | ⬤ | |
| Major | 14.0v1 to 15.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")
Copyright © 2024 The Foundry Visionmongers Ltd.