21 October 2026
KAT-12324 - Support was added for Nuke 17.1.
ID 615277 - The Syntax Highlighter parameter in the USD Text View tab is now on by default.
ID 622465 - Arrays longer than 30 characters are now truncated by default to allow for more important information to be read. An option for this can be found when pressing the cog icon in the USD Text View tab. This is persistent with saving your Katana layout.
ID 622466 - Syntax highlighting and mode options in the USD Text View tab are now saved with the layout.
ID 622486 - A new Prim parameter can be found allowing the user to inspect the data on a single prim in the USD Text View tab.
ID 622514 - Options for pinning and pausing are now available for the USD Text View tab. Pause means to stop all and any updates. Pin means to pin the selected node, while still listening for updates and refreshes based on changes..
ID 624334 - The UsdStageDefine node can now set metadata onto the root layer of the UsdStage.
KAT-12373 - The bundled OpenEXR version has been upgraded to 3.2.12
ID 619685 - The “Your First Katana” example project wasn’t sourcing textures correctly when using newer versions of RendermanForKatana.
ID 622382 - When rendering pointcloud locations using the hdPrman render delegate in the Hydra Viewport, materials assigned to these locations were not displayed in the Viewport.
ID 622498 - When materials were assigned to instances they did not display in the Viewer tab when using the hdPrman render delegate, although the same materials would render correctly when using the render plugin RendermanForKatana.
ID 619689 - When saving a Katana layout, an obscure exception could appear.
ID 623437 - When the state badge in GenericAssign-based ramps was toggled, two Undo entries would be added to the Undo stack; subsequent attempts to undo the operation would result in yet another Undo entry added to the stack, preventing the user from undoing to an older checkpoint.
KAT-7096 - When returning min and max attributes by Nodes2DAPI.FrameBuffer.queryScanline(), results could be inconsistent and would sometimes cause a crash.
ID 248961 - When a worker sent a "done working" message result which wass waiting to be drained on the main thread, a second message could be sent to that same worker during the draining. When that worker was queried to check if it is working, it could give a false negative result that the worker was no longer working - when it was. When this happened, things like wrong frames could be drawn to the catalogue, or scene in the viewer.
ID 474266 - When a client is reused it can sometimes receive old messages from jobs that had not finished being completed by workers that have been mislabelled as finished working, this client would have no notice of them causing unexpected results.
ID 622211 - The UsdSuperLayer Editor widget could retrieve the incoming stage and state too many times when changing local values in the Parameters tab.
ID 622212 - In UI sessions with multiple tabs and features utilising the same UsdSuperLayer, the input stage could be requested from each independently, resulting in repeated unnecessary stage retrieval.
KAT-12385 - When a Live Render was terminated, Katana would continue to emit events for updating render data, which would cause a progressive slowdown in the application. This was a regression introduced in Katana 8.5v2 / 9.5v2.
KAT-12513 - When the frame was changed while Live Renders were in progress, a new Catalog Item, and its associated render process, would be wrongly spawned. This was a regression introduced in Katana 8.5v2 / 9.5v2.
ID 623278 - When knots were inserted in a float ramp widget that had been configured with Catmull-Rom interpolation and no initial knot, a crash could be produced.
ID 624050 - When shader properties were set using the UsdMaterial node, it would fail to set the array type [] affix on properties.
ID 624498 - UsdLayerExport resolved assetId’s with Katana’s AssetAPI prior to handing over to USD’s asset resolution, which resulted in dual resolution.
KAT-7080 - Engines which required reading the input stage via `GetInputStage()` could sometimes fail to compose the stage due to not applying the AssetResolverContexts specified on the UsdStageDefine nodes in all cases.
ID 622962 - When using a UsdSuperLayer node with Show Incoming Scene enabled, prims authored directly in the content layer under a payload-bearing ancestor did not appear in the tree view.
ID 623284 - When a UsdSuperLayer-based node that had authored array-like properties was imported into Katana (e.g. either by loading a project or pasting a previously copied node), an exception could be encountered as the array length for the default value parameter was miscalculated.
ID 623382 - When the base prim path was changed in UsdSuperLayer-derived node (such as the UsdGaffer), the currently selected prim in the tree view in the node editor would be inadvertently deselected.
KAT-12321 - When a prim was renamed while its properties were still shown in the Parameters tab of any UsdSuperLayer-derived nodes (such as the UsdGaffer), a rare crash could be seen when additional prims were added to the node.
KAT-12522 - Specifying a SubEngine within the UsdSuperLayer node which specified a pattern was ignored and overwritten with the current prims path.
ID 580249 - When manipulating transformations for both Geolib and USD locations/prims at the same time, the manipulator handle will ping to the center of the USD mesh.
ID 579376 - When using Pattern-Based Collections with the include and exclude widgets in conjunction with the membershipExpression widget on the UsdCollection node; will not correctly update and is currently not supported. This is due to a known issue with USD.
NOTE: More info can be found on the USD thread: https://forum.aousd.org/t/problems-with-pattern-based-collections/1197/7. Katana's Pattern-Based Collection widget computes collection membership using membership expressions, therefore it does not currently handle relationship-mode collections correctly.
ID 586965 - When using USD's stitch method for stitching layers, it does not retain blocked attributes.
ID 588881 - When using the pivotTranslate parameter on the UsdTransformEdit node, it currently has no effect.
ID 618268 - When setting a transformation for a light within the UsdGaffer, the option Disable Interactive Transforms becomes unavailable from the treeview's right-click context menu. A workaround is to disable transforms within the Transform subtab by setting the makeInteractive property to No.
KAT-12244 - UsdMetadataSet doesn't remove existing metadata when changing the metadata name in Layer Mode
| Minimum | Recommended | |
|---|---|---|
| CPU | Dual-core processor | |
| Storage | 3.5+ GB available for installation | |
| System RAM | 1+ GB available | |
| Graphics RAM | 1+ GB available | 2+ GB available |
| Display | 1920 x 1080 | |
| OpenGL | OpenGL 4.5+ (see note below) | |
The configurations listed below are those that Foundry have tested with Katana. Due to the constantly changing nature and wide variety of computer hardware available in the market, Foundry is unable to officially certify hardware. The list below can be used as a recommendation and does not guarantee that it meets your particular needs.
NVIDIA Quadro RTX 4000
NVIDIA Quadro RTX A4000
NVIDIA Quadro RTX A3000
NVIDIA Quadro P4000
Please download and install the latest graphics driver from the NVIDIA website.
If you encounter any issues, please contact Customer Support directly through the Support Portal at the following address: https://support.foundry.com.
Copyright © 2026 The Foundry Visionmongers Ltd.