12 August 2021
These release notes describe changes from Katana 4.0v5 to 4.5v1.010005a.
The version of USD used in Katana has been upgraded to USD 21.05, re-introducing support for using different Hydra Render Delegates in Katana's Hydra-powered Viewer tab.
As part of this work, the menus of the Viewer tab have been rearranged for clarity:
A new Render Delegate Toolbar appears in the top-right corner of viewports in the tab, and allows for pausing, resuming, and stopping of drawing with the chosen Hydra Render Delegate, provided that Render Delegate supports these features.
Katana 4.5v1 includes a number of improvements for authoring shading node networks in NetworkMaterialCreate and NetworkMaterialEdit nodes:
When creating a connection between shading nodes, shading nodes that appear in the Collapsed or Connected Only view states are now temporarily Expanded while pointing at them. This makes it easier to quickly create connections without having to manually change the view states of shading nodes.
A new showPagesConnectedOnly preference has been added to the nodegraph category of preferences, to control whether pages are shown when shading nodes appear in the Connected Only view state.
Appearance and behavior of Dot nodes:
Dot nodes have been redesigned to be smaller, and their ports have been removed.
Connections between Dot nodes are now drawn as straight lines instead of bezier curves, allowing for a more organized appearance of shading node networks.
Input connections on selected shading nodes can now optionally be hidden, in order to declutter shading node networks.
User parameters can now be added to NetworkMaterialCreate and ShadingGroup nodes.
Macros created from within NetworkMaterialCreate or NetworkMaterialEdit nodes can now easily be created in those types of nodes from the node creation menus.
The size of the footer of a shading node is now smaller and no longer contains the node type name.
The versions of third-party libraries used in Katana have been updated to match those of the calendar year 2020 specification of the VFX Reference Platform, with the exception of Python, which remains at Python 2.7 in Katana 4.5v1. As the second part of the dual release of Katana 4.5v1/5.0v1, the full upgrade to Python 3 will be included in Katana 5.0v1.
In support of the upgrade to Python 3 in Katana 5.0v1, almost all of Katana's Python C extension APIs in Katana 4.5v1/5.0v1 have been rewritten using pybind11, adding improved docstrings and better error feedback. All imports of Python modules across the Katana codebase have been updated to work in Python 3, where imports are absolute by default.
A number of features that were deprecated in previous lines of releases have been removed, in order to avoid porting work that would have otherwise been necessary to make them compatible with new versions of third-party libraries in Katana 4.5v1/5.0v1 and with Python 3 in Katana 5.0v1:
When selecting objects while a Render Delegate other than GL (HdStorm) is chosen, the selected objects will now be highlighted as filled by default, since wireframes cannot be drawn out-of-the-box by most other Render Delegates. A new Display > Selection menu in the Viewer tab allows users to choose between this Fill appearance and an Outline appearance.
The menus of the Viewer tab have been rearranged for clarity:
All Network Materials will be passed through to Hydra and the chosen Render Delegate starting from the terminal nodes described in the material.terminals attribute. In order to find the correct terminals to use, the chosen Render Delegate's material render context will take precedence over a fallback of the usdSurface terminal, which will always be checked. If no terminals exist, the default material will be used.
For each terminal token under HdMaterialTerminalTokens we generate a terminal to search for by concatenating the material render context with the terminal token, e.g: glslfxSurface or glslfxDisplacement for HdStorm. If we find a terminal which matches this, we return the attached Material Network. If no match is found, we look through some known naming differences. For example, HdStorm's Render Delegate returns glslfx, but we know that the terminal name to look for is usdSurface for the surface token type. There are a few other instances of this for Render Delegates we have tested. If a known naming conversion fails, we will always fall back to reading the usd prefixed terminal, e.g usdSurface, usdDisplacement, or usdVolume.
The Hydra Viewer now supports reading arbitrary primvar data, which can be passed to UsdPrimvarReader_<type> nodes, e.g. UsdPrimvarReader_float2. The structure of this data must follow Katana's attribute convention for Arbitrary Attributes, and is read from GroupAttributes under the geometry.arbitrary attribute on a geometry location.
Hydra Render Delegates will now always draw until they have converged. The View > Hydra Renderer > Redraw Until Converged toggled menu item, which was previously provided to control this behavior, has been removed.
The Katana Scene Delegate will now read any parameter asked for via the GetLightParam() method in Hydra from the renderer's LightParams attributes for the light location. We convert the Hydra naming convention of colon-separated words into lower camel-case to match the majority of Katana attributes. For example, my:light:param becomes myLightParam. We will always check for usdLightParams as a fallback if we can't find requested attributes under the renderer's LightParams.
The Katana Basic Material now uses a UsdPreviewSurface shader node with a UsdPrimvarReader_float3 node reading the displayColor attribute plugged into the diffuseColor, using a fallback color value of 0.2f, 0.2f, 0.2f.
A dialog for editing settings of the Render Delegate that has been chosen for drawing the scene has been added to the Viewer tab. It can be opened by choosing Display > Render Delegate Settings from the Viewer tab's menu bar.
While the choice of Render Delegate is not saved to Katana's layout files, values for settings can be, so that they are applied automatically when switching between layouts or Render Delegates.
Light parameters are cast to the type matching the node input in USD's SdrRegistry where a node exists for the light and a matching input name is found.
A new Render Delegate Toolbar appears in the top-right corner of viewports in the Viewer tab. It contains tool buttons for pausing, resuming, and stopping of drawing with the chosen Hydra Render Delegate, provided that Render Delegate supports these features.
If the chosen Render Delegate supports pausing and resuming of rendering, the pause button will temporarily pause the render, halting the use of CPU resources, but not freeing memory resources.
If the chosen Render Delegate supports stopping of rendering, the stop button will stop the render at its current level of convergence, freeing CPU and memory resources.
The following functions have been added to the PyFnGeolibServices.XFormUtil Python module:
These functions are equivalent to those in the PyFnScenegraphAttr module, which is no longer available (see below).
Refer to the ScenegraphAttr Porting Guide in the Katana Developer Guide for more information.
The following changes have been made in support of creation of node networks in Layered Menu actions:
The boost libraries shipped with Katana are now namespaced as foundryboost.
ID 278590 - The splitter in the Example Projects window can now be resized to avoid cutting off the project names.
When pointing at layout menu items in the Layouts menu of Katana's main window, a thumbnail of the layout is now shown.
When a layout is saved, a preview image of the layout is generated and stored in the user's home directory. Layouts generated by previous versions of Katana won't have an associated image generated for them, and will subsequently not show such a layout previewed when pointing at their menu items.
The fixed-size message type icons for informational messages, warning messages, error messages, and questions that were used in message dialogs were replaced with new, scalable, Katana-style message type icons.
The tiny square icons that indicated log message types in the Messages tab and the View Messages popup have been replaced with the new scalable message type icons.
ID 475786 - The type of widget for displaying help text in Katana's help popups has been changed from QWebEngineView to QTextBrowser. QTextBrowser is a much more light-weight type of widget and loads help text much faster than QWebEngineView. A Help button has been added to the HTML editor widget type in Katana to link to the Qt documentation regarding the Supported HTML Subset in help text.
QTextBrowser was already used for the preview of help text in the Edit Help Text dialog, so that the preview and the resulting help popup now actually match. The help text in help popups also now scales with the application/fontSize preference, rather than being determined by separate font size and zoom factor settings.
The HTML editor widget type including its QTextBrowser-based preview area is also used for the text parameter of InfoCreate nodes.
ID 471638 - The view state of shading nodes in NetworkMaterialCreate and NetworkMaterialEdit nodes is now indicated with an icon in the top-left corner of the shading node's shape. When clicking that icon, the appearance of the shading node cycles through the available view states:
As part of this work, the names of the customizable keyboard shortcut actions for these view states have been modified to be more accurate, and to appear within the Node Graph Tab > Network Materials group:
Previously, the three actions appeared as:
ID 475290 - It is now possible to open the node creation context menu by right-clicking into the Node Graph tab's canvas after a NetworkMaterialCreate or NetworkMaterialEdit node has been entered.
ID 471642 - The new showPagesConnectedOnly preference has been added to the nodegraph category of preferences. The new preference controls whether pages are shown when shading nodes in NetworkMaterialCreate or NetworkMaterialEdit nodes appear in the Connected Only view state. The value of the preference can be changed from the new Show Pages (Connected Only) toggle menu item in the View menu of the Node Graph tab, when a NetworkMaterialCreate or NetworkMaterialEdit node has been entered.
Connections between Dot nodes in NetworkMaterialCreate and NetworkMaterialEdit nodes are now drawn as straight lines instead of bezier curves, allowing for a more organized appearance of shading node networks.
Dot nodes in NetworkMaterialCreate and NetworkMaterialEdit nodes have been redesigned to be smaller, and their ports have been removed. Connections can now be made by interacting with the body of the Dot node itself, by either dropping a connection on it to finish a new connection coming from another node, or by pressing the backtick character (`) key while pointing at the Dot node to start a new connection from the Dot node.
ID 410640 - When creating a connection between shading nodes in a NetworkMaterialCreate or NetworkMaterialEdit node, shading nodes that appear in the Collapsed or Connected Only view states are now temporarily Expanded while pointing at them, in order to make it easier to quickly create connections without having to manually change the view states of shading nodes.
Macros saved from within a NetworkMaterialCreate or NetworkMaterialEdit node can now easily be created in those types of nodes, as they now appear in the node creation menus when a node of one of those types has been entered.
The visibility of incoming connections for selected shading nodes within NetworkMaterialCreate and NetworkMaterialEdit nodes can now be toggled by using the Edit > Toggle Input Connections Visibility menu item in the Node Graph tab (default keyboard shortcut: Alt+H).
While no node is selected, the Alt+H keyboard shortcut can be held down in order to temporarily show input connections on all shading nodes for which input connections were previously hidden.
The size of the footer of a shading node is now smaller and no longer contains the node type name.
ViewerMaterialEdit nodes, which were deprecated in Katana 4.0v2, are no longer available in Katana 4.5v1.
The material.viewerShaderSource attribute convention, which only applied to the OpenSceneGraph-based legacy Viewer tab in Katana releases prior to Katana 4.5v1, was removed from the Katana Developer Guide.
The deprecated PyFnScenegraphAttr and PyScenegraphAttrFnAttributeBridge modules have been removed. The FnAttribute module should be used instead.
Refer to the ScenegraphAttr Porting Guide in the Katana Developer Guide for more information.
ID 126100 / BZ 51298 - The defunct applyAtLeaves parameter, which was shown when setting the attributeType parameter of an AttributeSet node to group, has been removed from AttributeSet nodes.
The Vecmath Python module, which included the vec2, vec3, vec4, quat, mat3, and mat4 classes, has been removed. Consider using PyImath as a replacement instead.
The ColorTimer, IBL, and Math submodules of the Nodes2DAPI_cmodule Python module have been removed.
The legacy FnKatImport module was removed. Python modules that were previously imported with the FnKatImport module can now be imported using standard Python import statements.
The pyutil_cmodule Python C extension module and the PyUtilModule.BezierModule Python module that it defined were removed.
The GeoAPI.Util.GenericAppenderUtil module is now deprecated. New functions in the existing Nodes3DAPI.GenericAssign module and the new Nodes3DAPI.GenericAssignRegistry module should be used instead.
It is now possible to create Dot nodes by pressing the . key, which was previously only possible while creating connections between nodes, or while nodes were selected. When pressing . while no connection is being created and while no nodes are selected, the new Dot node floats with the pointer, ready to be placed.
ID 463192 - It is now possible to edit user parameters for nodes that are implemented as SuperTools, for example:
This applies to all SuperTool-based node types, including custom SuperTools.
Katana's USD 21.05 package has been built with a PXR_LIB_PREFIX of fn, and the Python package for USD has been changed from pxr to fnpxr to ensure it does not clash with local USD Python packages.
The PXR_PLUGINPATH_NAME variable has been set to FNPXR_PLUGINPATH to match Katana 4.0.
The schema classes that are part of the Katana USD Plug-ins have been rebuilt using the usdGenSchema code generator script that ships with USD 21.05.
The visibility of locations with the usd.purpose attribute can now be toggled via the Display > Purposes submenu in the Viewer tab. See the entry on Purpose in the USD Glossary for a description of how this attribute is used by Hydra Render Delegates.
OpWrite nodes now default to C++14. In Windows, the default CMake generator is now Visual Studio 15 2017 Win64.
ID 438370 - The implementation of the Render API function RenderSettings::calculateCropWindow() incorrectly returned values based on a rounded "region of interest".
ID 310448 - When retrieving the XML text representation of a Katana attribute using the getXML() method, the resulting XML text contained an extra space in the text of the attribute's value.
ID 281274 - The FnAttribute.DelimiterEncode() function replaces forward slash (/) and period (.) characters in a given name or scene graph location path with other characters. The resulting encoded name can then be used as a child attribute name in GroupAttribute structures, where periods are used to denote attribute hierarchy.
Unfortunately, the previously-chosen other characters were not valid in the context of XML, so could not be written to and read from Katana project files. To address this, slashes and periods are now replaced by FnAttribute.DelimiterEncode() with Line Feed (\n) and Tab (\t) characters, respectively, which are safe to use in XML documents that follow the XML 1.0 specification. This change allows for round-tripping of attributes via XML text, as demonstrated in the following Python code example:
gb = FnAttribute.GroupBuilder()
inputAttr = gb.set(FnAttribute.DelimiterEncode('/root/world/taco'), 'xxx').build()
print(inputAttr.getXML())
outputAttr = FnAttribute.Attribute.parseXML(inputAttr.getXML())
print(outputAttr.getXML())
In previous lines of releases of Katana, the call of getXML() raised a ValueError exception with the following error message:
ValueError: Given string is not valid FnAttribute XML
ID 468072 - When a custom RenderMethod inherits from RenderInfo::DiskRenderMethod, Katana was not propagating the RenderMethod's original render method name to renderboot; instead, it would always set the name to RenderModes.DISK_RENDER (a.k.a. 'diskRender').
ID 476581 - The order in which plug-ins were loading during application startup was previously implicitly determined by the presence of the legacy Gaffer SuperTool: Python modules in Plugins folders in Katana resource directories were loaded as part of loading Python modules for SuperTools from SuperTools folders.
Python modules in Plugins folders are now explicitly loaded before Python modules in SuperTools folders.
ID 481447 - When deleting shading nodes inside of NetworkMaterialEdit nodes, stale references to those shading nodes were left in the resulting material.nodes, material.interface, and material.layout attributes.
ID 410528 - When editing the contents of NetworkMaterialCreate or ShadingGroup nodes using multiple Node Graph tabs, and filtering in the right-hand sidebar, the filtering across the Node Graph tabs could get out of sync with the underlying data.
ID 481353 - When choosing the Fit Backdrop Node to Selected Nodes command in the Node Graph tab's Edit menu for a number of selected nodes inside of a NetworkMaterialCreate or NetworkMaterialEdit node, the resulting Backdrop node is not positioned correctly. (This issue was a regression in Katana 4.0v5.)
ID 472942 - The Add tool button menu of the scenegraph > userColumns preference in Katana's Preferences dialog lists registered GenericAssign-based node types, to make it easy for users to add custom columns to the Scene Graph tab to show values of attributes that correspond to parameters of GenericAssign-powered nodes. The list of node types was not sorted alphabetically, and included names of node types that are meant to be hidden, for example GafferThree_LightMuteAndSolo (which is a type of node that is used internally in GafferThree).
ID 458746 - When sRGB textures were used as UDIM tiles, they were wrongly gamma-corrected twice, and subsequently appeared too bright.
ID 479097 - When using multiple Viewer (Hydra) tabs in a layout and making changes to a built-in (virtual) camera followed by starting a Live Render, a Python exception was raised from an event handler for camera changes. (This issue was a regression in Katana 3.6v1.)
ID 473813 - Setting the geometry.arbitrary.displayOpacity attribute had no effect on the default material used by the Hydra Viewer.
ID 485192 - When using a UsdIn node to import a USD file containing a 3-dimensional texture coordinate primvar named <primname>, the attributes under geometry.arbitrary.<primname> were not loaded completely.
ID 482198 - When using the isolatePath parameter on a UsdIn node that is loading a USD asset that uses light lists, UsdIn failed with an error message: UsdIn: Failed to compute katana path for usd path
ID 479726 - When setting the isolatePath parameter on a UsdIn node, and then trying to use a UsdInIsolate node, UsdIn failed with an error message: UsdIn: Failed to compute katana path for usd path
The value of the isolatePath parameter is now prefixed onto the USD stage mask path set up by UsdInIsolate.
When using isolatePath and UsdInIsolate in the same node graph, the mask created by UsdInIsolate (using Katana scene graph locations) did not take account of the UsdIn mask path which did not contain the locations cut out by setting UsdIn's isolatePath. This meant the USD stage was masked by locations which did not exist, causing errors.
ID 479729 - When using a UsdInIsolate node to isolate a location that did not exist, Katana crashed.
ID 484299 - usdImagingGL has been replaced by usdImaging as a dependency for the usdKatana library in KatanaUsdPlugins.
ID 478987 - When attempting to remove an input port or output port from a Group node that was locked, Katana crashed.
ID 478989 - When attempting to undo the removal of a port on a locked node, an exception was raised, and the undo history was cleared. (This issue was a regression in Katana 3.2v1.)
ID 114182 / BZ 49288 - When exporting a Catalog item you need to specify the export folder path to an existing folder. If the folder you're trying to export to does not exist on disk Katana will fail to export. (This issue is a regression in Katana 2.0v1.)
ID 427252 - Locators created via PrimitiveCreate nodes can be snapped to in all modes, rather than just the Lights, Cameras, and Locators mode.
ID 420882 - Changing between the Viewer (Hydra) tab's multipane layout options quickly can cause a crash or many error messages to be written to the terminal/console.
ID 380129 - Use of non-conformant GL anti-aliasing modes that employ supersampling reduces rendered point size by the supersampling scaling factor. Katana currently employs any reported anti-aliasing mode (up to a maximum sample count of 16): as a workaround, change the viewerHydra.antiAliasing preference to a lesser anti-aliasing mode.
ID 352167 - Textures loaded from Hydra shaders are not cleared or reloaded from disk when flushing caches.
ID 85118 / BZ 41152 - When editing parameters of a node that is part of a LiveGroup node and reloading the parent LiveGroup node, the UI state of the Parameters tab is reset. This includes scroll bar positions, selections of items, and selections of nested tabs (for example Object, Material and Linking tabs for a Gaffer node).
ID 84998 / BZ 41092 - When reloading a LiveGroup node's parameter interface and contents from its source, parameters of child nodes that are edited in floating panes disappear from those panes.
ID 84020 / BZ 40598 - Reverting a LiveGroup node does not revert its user parameters.
ID 84018 / BZ 40600 - Undoing a revert of an unpublished LiveGroup node does not restore the LiveGroup's editable and modified state.
ID 83061 / BZ 40237 - Nodes can be dragged into the Group bubble of a non-editable LiveGroup node.
ID 442604 - When "exploding" a NetworkMaterialEdit node in the Node Graph tab into its parts by selecting it and choosing Edit > Explode Selected Groups or pressing the U key, Python exceptions are raised.
ID 429775 - NetworkMaterialEdit nodes do not currently respect local Graph State changes, for example as performed by VariableSet nodes downstream.
ID 429302 - When editing a locked node inside a NetworkMaterialEdit node graph, the parameters will be shown at their default state.
ID 427408 - When entering a NetworkMaterialEdit node whose sceneGraphLocation parameter is empty, warnings are logged by the Geolib3 Runtime.
ID 423341 - In a NetworkMaterialEdit node graph, connections can be displayed incorrectly if a node's name begins with a number.
ID 402064 - In a ShadingGroup node graph, the connection between a Dot node and a shading node port can be wrongly colored in some cases.
ID 269449 - Choosing Edit Shader Parameters from the main wrench menu of Material nodes does not show wrench buttons next to shader parameters. This can be worked around by toggling the edit flag on the node. (This issue is a regression in Katana 2.5v1.)
ID 199304 - The namespace parameter on Material nodes wrongly allows the insertion of Unicode codepoints outside the ASCII range.
ID 191052 - Katana does not have any support for the texture reference object workflows of V-Ray for Maya.
ID 485687 - When undoing the creation of a ShadingGroup node in a NetworkMaterialCreate or NetworkMaterialEdit node, the undo history gets corrupted. (This issue is a regression in this Katana 4.5v1 alpha release.)
ID 485812 - The ifelse() function in the context of Python-based parameter expressions currently always evaluates to the first of the two given alternatives. (This issue is a regression in this Katana 4.5v1 alpha release.)
ID 188533 - Expressions linked to non-local parameters on not previously edited Material nodes can't be evaluated.
ID 105434 / BZ 47520 - Reference Expressions may not refer to dynamic parameters such as shader parameters.
ID 60457 / BZ 31790 - Setting an array or group parameter to an expression results in an invalid expression. Upon setting a valid expression (for example, an evaluation of an equivalent parameter on another node using getParam), the parameter is not immediately updated. To workaround this issue, close and reopen the parameter, or flush caches while the node is not edited.
ID 485613 - When attempting to obtain the XML text representation of a StringAttribute object in Python which contains characters outside of the C0 Controls and Basic Latin range, an exception is raised. (This issue is a regression in this Katana 4.5v1 alpha release.)
ID 485588 - When attempting to obtain the string representation of data of a ConstVector object in Python which contains characters outside of the C0 Controls and Basic Latin range, an exception is raised. (This issue is a regression in this Katana 4.5v1 alpha release.)
ID 381284 - The 3Delight renderer plug-in makes use of source material locations rather than resolved material attributes as a means of de-duplication. This can result in material data being lost when excluding material locations from the Render Working Set during a Live Render session.
ID 176598 - Use of nodes that modify Graph State Variables in Interactive Render Filters is not currently supported.
ID 74799 / BZ 36926 - The rendererSettings > displayOptions parameter of a RenderOutputDefine node for the PRMan renderer, shown when its type parameter is set to 'raw', cannot be set using the Parameters tab.
ID 70217 / BZ 36176 - The 2D node Disk Render Upstream Render Outputs option does not use the batch render method, batchRender, for upstream render nodes, instead using diskRender.
ID 70016 / BZ 36137 - Rendering repeatedly with a large number of AOVs consumes more and more memory, possibly leading to a crash when running out of memory.
ID 12517 / BZ 16168 - Only one Monitor tab may display the results of a Preview Render. The use of multiple Monitor tabs is not currently supported.
ID 373702 - Clicking in the Viewport and pressing a shortcut whilst the mouse is hovered in another widget will still send the event back to the 'focused' Viewport widget, for shortcuts where the widget hovered over does not handle the shortcut.
ID 208802 - Closing the Histogram tab after use leaves the Monitor tab unable to display rendered images.
ID 123558 / BZ 50911 - When changing an array parameter's tuple count/size, any corresponding attributes are not properly updated in the Attributes tab.
ID 112544 / BZ 49051 - The Viewer tab may lose sync with the Scene Graph tab when changes to expansion state are interrupted.
ID 107038 / BZ 47853 - Indication of attribute source nodes (such as the yellow 'glow' in the Node Graph tab) is unavailable as of Katana 2.0v1.
ID 71965 / BZ 36691 - State badges are currently shown for attribute values of dynamic array child parameters, even though only their parent array parameter should appear with a state badge.
ID 65347 / BZ 34949 - Using Compiz can lead to text fields not receiving focus events correctly due to an incompatibility between Compiz and Qt. Depending on your configuration, disabling Compiz "desktop effects" may resolve the problem.
ID 468287 - UsdIn is not retaining expanded view state information for shading nodes in a Network Material context.
ID 446730 - When trying to overwrite variants already baked from a UsdMaterialBake node, an error can be printed to the terminal, resulting in the USD file not being written. In this instance, flushing caches before overwriting the file should act as a workaround.
ID 381692 - (Windows only) When logging out and logging back in again, the colors in the UI are incorrect. For example, certain parts of certain types of tabs may appear with a white background color. (This issue is a regression in Katana 3.1v1, possibly caused by QTBUG-52728 - Paint bug and palette errors after some events in Windows)
ID 344118 - (Windows only) When installing Katana and opting to install the bundled version of 3Delight, the installation of 3Delight is made by modifying system-wide environment variables such as KATANA_RESOURCES. Thereafter, launching any version of Katana will pick up this installation of 3Delight, which may be incompatible with the version of Katana being launched.
NOTE: This issue does not affect Linux, where a bundled 3Delight installation is tied to its corresponding Katana installation.
ID 218742 - (Windows only) Katana must be installed to a path no longer than ~140 characters. Attempting to install to a longer path results in an unintuitive error: "The system cannot find the path specified."
ID 337653 - Katana logs deprecation warnings when loading the PyMockAsset, PyMultiMockAsset, and PyMockFileSeq shipping example Asset API plug-ins.
ID 84326 / BZ 40709 - The Alembic library does not support multiple process or thread access to an Alembic file. This means that a crash occurs when modifying an Alembic file outside Katana, while it's loaded in an open Katana scene. To avoid this, you must Flush Caches before attempting to update any modified Alembic files.
ID 80738 / BZ 39261 - Operations that lock and unlock nodes do not currently create entries in the Undo History, which can lead to an incorrect node graph state when undoing and redoing operations.
ID 70196 / BZ 36170 - Control keys (notably arrow keys) do not function as expected in shell mode.
| Minimum | Recommended | |
|---|---|---|
| CPU | Dual-core processor | |
| Storage | 1+ GB available for installation | |
| System RAM | 1+ GB available | |
| Graphics RAM | 1+ GB available | 2+ GB available |
| Display | 800 x 600 | 1920 x 1080 |
| OpenGL | OpenGL 4.3+ (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 M4000
NVIDIA Quadro P4000
NVIDIA Quadro K4000
NVIDIA Quadro K6000
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 © 2021 The Foundry Visionmongers Ltd.