The Foundry Katana 3.2v1
The Foundry Katana 3.2v1 | 333.8 mb
The Foundry launches the newer update to its professional look development and lighting tool. Apart from fixes in the detected issues, this version hosts a couple of noteworthy enhancements as well.
Feature Enhancements
- TP 81998 / BZ 39875 - Previously in Katana, holding the Ctrl key and selecting a Backdrop node will select all the nodes that are touching the Backdrop. This is opposite of how this interaction is handled in Nuke.
- Now, this interaction has been reversed so that selecting a Backdrop will select the nodes that are touching it and holding Ctrl will now only select the Backdrop node itself. Additionally the single action of clicking & dragging a Backdrop will now drag the Backdrop and all of the nodes inside of it, similarly to Nuke.
- TP 129274 / BZ 51768 - The Katana Developer Guide documentation of attribute conventions for material locations with material group attributes that represent Network Materials has been completed, corrected, and extended to cover the additional layout information that is stored for Network Materials created by NetworkMaterialGroup nodes.
- TP 356529 - Support for opening example projects by double-clicking on the tree item in the Example Projects tab's tree widget.
- Hydra Viewer errors about 'point' scope UVs not being supported are logged once only now.
- The PyUtilModule.CatalogManager Python module has been renamed to PyUtilModule.CatalogAPI.
- The Z ordering of Backdrop nodes can now be controlled by the [ and ] keyboard shortcuts, to bring Backdrop nodes to the back and front respectively. As part of this feature, the Send to Back checkbox has been removed from the Edit Backdrop Node dialog.
- The attribute conventions for Network Materials have been extended to cover information about the layout of a shading node network, taking into account additional nodes such as Backdrop, Dot, Switch, and VariableSwitch nodes, each with their position and color. Storing this additional information will allows us to build tools to recreate a visual representation of a Network Material downstream, even if the attributes are imported via Look Files or other means. (See also TP 129274.)
- The section on Writing Renderer Plug-ins in the Katana Developer Guide has been extended to include details on customizing a renderer plug-in's layered menu when viewing the contents of a NetworkMaterialGroup node in a Node Graph tab.
- The FnAttribute API has been extended with a getSize() function for attributes, which returns the total memory in bytes that was allocated when an attribute was created. This new function is available in the C API, the C++ wrapper, the Python bindings, and the OpScript/Lua API.
- We now ship the shared libraries for Boost 1.61.0. This is a requirement for being able to use shared USD Python libraries and modules.
- Katana 3.2 now uses a Foundry-namespaced and renamed shared library for TBB (libtbb2017_Foundry.so on Linux) and TBB Memory Allocator (libtbbmalloc2017_Foundry.so on Linux) based on TBB 2017 Update 8, in order to reduce conflicts of having multiple TBB arenas in one session.
- The Hydra Viewer has been upgraded to USD 19.05 built with the shared USD libraries, which are now shipped with Katana.
- TP 394745 - The tooltip of attributes in the Attributes tab has been extended to include the size of a given attribute in memory in bytes.
- TP 394987 - The ID of a catalog item is now sent to the renderboot executable as part of the renderboot command line:
-sequenceID <sequenceID>
- The sequence ID can be used to obtain the corresponding catalog item by using a Python function of the CatalogAPI module:
CatalogAPI.FindCatalogItemBySequenceID(<sequenceID: int>) –> CatalogAPI.CatalogItem.CatalogItem
- The AttributeUpgrade node type, which was used to address attribute convention changes between Katana 1.x and 2.x, is now deprecated, and has been hidden from node creation menus in the Node Graph tab.
- Developer documentation on building, installing, and using custom Hydra Render Delegates as plug-ins for Katana's Hydra Viewer has been added to the Writing Plug-ins section of the Katana Developer Guide.
- The NetworkMaterialGroup node type has been renamed to NetworkMaterialCreate. Documentation and NodegraphAPI hints have been updated to reflect the change. An upgrade script is provided to upgrade existing Katana projects that were created during the alpha and beta cycle of Katana 3.2v1 to the new name.
- The version of 3Delight that we ship with Katana has been upgraded to version 1.5.9. For more information, refer to the 3Delight Cloud Changelog.
- The version of the USD library we're using in Katana's Hydra Viewer is now shown in the About Katana dialog, accessible via Help > About Katana.
Bug Fixes
Katana Developer Guide
- TP 85230 / BZ 41203 - A few incorrect file system location paths of source code example files in the Katana Developer Guide have been corrected.
- TP 323246 - Internal members of Python classes, such as __dict__, were wrongly exposed in the Katana Developer Guide.
- TP 381467 - Bold formatting of UI-related terms, such as titles of tabs, was not applied correctly in a few cases, causing double asterisks to show up instead.
- TP 381468 - Some documented functions were wrongly shown as "Undocumented", notably UI4.Widgets.SceneGraphView.ViewLink.ViewLink.getUpdateSuppressor() and PackageSuperToolAPI.BaseEditor.BaseEditor.getSceneGraphViewTerminalOps().
- TP 398999 - The Nodes3DAPI.PortOpClient.NodeTraversalEndpointsSpec class was wrongly shown as "Undocumented".
- TP 399000 - All headlines were wrongly missing from the documentation of the SceneGraphView widget class, making it hard to make sense of the information presented.
- TP 399002 - Code formatting was not applied correctly in a few cases, causing formatting syntax to show up in verbatim, or causing links to break.
- TP 399003 - Documentation of the getInputPortAndGraphState() function was missing from instances of the Nodes3DAPI.Node3D class, and was also not included in the Katana Developer Guide.
- TP 399012 - The hierarchy of the Attributes (C++) page was inconsistent with the hierarchy of the corresponding OpScript/Lua and Python pages.
- TP 399013 - The following issues in the Katana Developer Guide were fixed:
. Node-related functions on the Working with Nodes > Connecting Nodes page were incorrectly listed as belonging to the Nodes3DAPI.Node3D class. They're actually defined on the underlying NodegraphAPI.Node class.
. The Node Properties documentation contained a broken link to the NodegraphAPI.Parameter documentation.
. The documentation of NodegraphAPI.Parameter.reorderChild() and reorderChildren() functions was wrongly duplicated.
. The signatures of deprecated functions were wrongly shown as a single unbroken lines, unnecessarily extending the width of the respective page, and making the parameter names and types hard to read.
. Documentation of Attribute Modifier Plug-ins, a legacy API that shouldn't be used anymore, was missing from the Katana Developer Guide.
- TP 399014 - A few header files of Geolib3's and Katana's plug-in APIs contained issues in the documentation of parameters and return values.
- TP 399018 - The following issues in the Katana Developer Guide were fixed:
. Descriptions of member variables in the Viewer Location Events documentation were missing.
. FnBaseLocator callback function pointer types did not appear or appeared incorrectly, and were not linked correctly in the signature of the FnBaseLocatorVDC::registerLocator() static function.
. The wrong callback function pointer type was used for the overridesBaseGeometry parameter of the FnBaseLocatorVDC::registerLocator() static function.
. BuilderMode and BuilderBuildMode references of the GroupBuilder class incorrectly linked to the respective typedefs instead of enums.
. Functions in the FnGeolibCookInterface API that accept callback function pointers for deleting private data were not parsed correctly, and appeared as single lines without breaks, exceeding the page boundary.
- TP 399981 - Multiple typos in the Katana Developer Guide have been fixed.
- TP 400452 - When the documentation preference was set to local, the API Reference > Parameter Expressions and API Reference > C++ APIs commands in the Help menu of the Katana main window did not link to the correct location in the Katana Developer Guide.
Other Bug Fixes
- TP 71317 / BZ 36414 - When attempting to undo the creation of a SuperTool-based node, such as GafferThree, an exception was raised.
- TP 216997 - Materials created via a NetworkMaterialSplice node were of the deprecated type shading network material, instead of the material type.
- TP 356705 - Manipulating locations during a Live Render could cause continuous live updates (during the manipulation) to stop working for all locations.
- TP 386841 - When FnGeolibCookInterfaceUtils::cookDaps() was invoked from multiple threads, it would fail to correctly read the default attributes on occasions. This affected Ops that relied on that function, e.g. the AdjustScreenWindowResolve Op, which on occasion failed with an error message: Error getting string value from StringAttribute. The GenericAssign DAP is now thread-safe.
- TP 394990 - The dead _initKeyboardShortcutCallbacks() Python function was removed from the KeyboardShortcutManagerMixin class, in order to avoid possible confusion about its use.
- TP 396842 - When refreshing the tree view of a material group attribute on a material location whose attributes are displayed in the Attributes tab, all items in the tree view were collapsed. Now, the expanded state of items is retained when refreshing the tree view.
- TP 397791 - The initialization of plug-ins used by Default Attribute Producers at render time was not thread safe, and could cause the render process to crash.
- TP 400154 - When loading internal example projects, areas of the node network were not visible, depending on the chosen main window layout and screen resolution. Now, upon loading an example project, the Node Graph tab will automatically frame all nodes.
- TP 81998 / BZ 39875 - Previously in Katana, holding the Ctrl key and selecting a Backdrop node will select all the nodes that are touching the Backdrop. This is opposite of how this interaction is handled in Nuke.
- Now, this interaction has been reversed so that selecting a Backdrop will select the nodes that are touching it and holding Ctrl will now only select the Backdrop node itself. Additionally the single action of clicking & dragging a Backdrop will now drag the Backdrop and all of the nodes inside of it, similarly to Nuke.
- TP 129274 / BZ 51768 - The Katana Developer Guide documentation of attribute conventions for material locations with material group attributes that represent Network Materials has been completed, corrected, and extended to cover the additional layout information that is stored for Network Materials created by NetworkMaterialGroup nodes.
- TP 356529 - Support for opening example projects by double-clicking on the tree item in the Example Projects tab's tree widget.
- Hydra Viewer errors about 'point' scope UVs not being supported are logged once only now.
- The PyUtilModule.CatalogManager Python module has been renamed to PyUtilModule.CatalogAPI.
- The Z ordering of Backdrop nodes can now be controlled by the [ and ] keyboard shortcuts, to bring Backdrop nodes to the back and front respectively. As part of this feature, the Send to Back checkbox has been removed from the Edit Backdrop Node dialog.
- The attribute conventions for Network Materials have been extended to cover information about the layout of a shading node network, taking into account additional nodes such as Backdrop, Dot, Switch, and VariableSwitch nodes, each with their position and color. Storing this additional information will allows us to build tools to recreate a visual representation of a Network Material downstream, even if the attributes are imported via Look Files or other means. (See also TP 129274.)
- The section on Writing Renderer Plug-ins in the Katana Developer Guide has been extended to include details on customizing a renderer plug-in's layered menu when viewing the contents of a NetworkMaterialGroup node in a Node Graph tab.
- The FnAttribute API has been extended with a getSize() function for attributes, which returns the total memory in bytes that was allocated when an attribute was created. This new function is available in the C API, the C++ wrapper, the Python bindings, and the OpScript/Lua API.
- We now ship the shared libraries for Boost 1.61.0. This is a requirement for being able to use shared USD Python libraries and modules.
- Katana 3.2 now uses a Foundry-namespaced and renamed shared library for TBB (libtbb2017_Foundry.so on Linux) and TBB Memory Allocator (libtbbmalloc2017_Foundry.so on Linux) based on TBB 2017 Update 8, in order to reduce conflicts of having multiple TBB arenas in one session.
- The Hydra Viewer has been upgraded to USD 19.05 built with the shared USD libraries, which are now shipped with Katana.
- TP 394745 - The tooltip of attributes in the Attributes tab has been extended to include the size of a given attribute in memory in bytes.
- TP 394987 - The ID of a catalog item is now sent to the renderboot executable as part of the renderboot command line:
-sequenceID <sequenceID>
- The sequence ID can be used to obtain the corresponding catalog item by using a Python function of the CatalogAPI module:
CatalogAPI.FindCatalogItemBySequenceID(<sequenceID: int>) –> CatalogAPI.CatalogItem.CatalogItem
- The AttributeUpgrade node type, which was used to address attribute convention changes between Katana 1.x and 2.x, is now deprecated, and has been hidden from node creation menus in the Node Graph tab.
- Developer documentation on building, installing, and using custom Hydra Render Delegates as plug-ins for Katana's Hydra Viewer has been added to the Writing Plug-ins section of the Katana Developer Guide.
- The NetworkMaterialGroup node type has been renamed to NetworkMaterialCreate. Documentation and NodegraphAPI hints have been updated to reflect the change. An upgrade script is provided to upgrade existing Katana projects that were created during the alpha and beta cycle of Katana 3.2v1 to the new name.
- The version of 3Delight that we ship with Katana has been upgraded to version 1.5.9. For more information, refer to the 3Delight Cloud Changelog.
- The version of the USD library we're using in Katana's Hydra Viewer is now shown in the About Katana dialog, accessible via Help > About Katana.
Bug Fixes
Katana Developer Guide
- TP 85230 / BZ 41203 - A few incorrect file system location paths of source code example files in the Katana Developer Guide have been corrected.
- TP 323246 - Internal members of Python classes, such as __dict__, were wrongly exposed in the Katana Developer Guide.
- TP 381467 - Bold formatting of UI-related terms, such as titles of tabs, was not applied correctly in a few cases, causing double asterisks to show up instead.
- TP 381468 - Some documented functions were wrongly shown as "Undocumented", notably UI4.Widgets.SceneGraphView.ViewLink.ViewLink.getUpdateSuppressor() and PackageSuperToolAPI.BaseEditor.BaseEditor.getSceneGraphViewTerminalOps().
- TP 398999 - The Nodes3DAPI.PortOpClient.NodeTraversalEndpointsSpec class was wrongly shown as "Undocumented".
- TP 399000 - All headlines were wrongly missing from the documentation of the SceneGraphView widget class, making it hard to make sense of the information presented.
- TP 399002 - Code formatting was not applied correctly in a few cases, causing formatting syntax to show up in verbatim, or causing links to break.
- TP 399003 - Documentation of the getInputPortAndGraphState() function was missing from instances of the Nodes3DAPI.Node3D class, and was also not included in the Katana Developer Guide.
- TP 399012 - The hierarchy of the Attributes (C++) page was inconsistent with the hierarchy of the corresponding OpScript/Lua and Python pages.
- TP 399013 - The following issues in the Katana Developer Guide were fixed:
. Node-related functions on the Working with Nodes > Connecting Nodes page were incorrectly listed as belonging to the Nodes3DAPI.Node3D class. They're actually defined on the underlying NodegraphAPI.Node class.
. The Node Properties documentation contained a broken link to the NodegraphAPI.Parameter documentation.
. The documentation of NodegraphAPI.Parameter.reorderChild() and reorderChildren() functions was wrongly duplicated.
. The signatures of deprecated functions were wrongly shown as a single unbroken lines, unnecessarily extending the width of the respective page, and making the parameter names and types hard to read.
. Documentation of Attribute Modifier Plug-ins, a legacy API that shouldn't be used anymore, was missing from the Katana Developer Guide.
- TP 399014 - A few header files of Geolib3's and Katana's plug-in APIs contained issues in the documentation of parameters and return values.
- TP 399018 - The following issues in the Katana Developer Guide were fixed:
. Descriptions of member variables in the Viewer Location Events documentation were missing.
. FnBaseLocator callback function pointer types did not appear or appeared incorrectly, and were not linked correctly in the signature of the FnBaseLocatorVDC::registerLocator() static function.
. The wrong callback function pointer type was used for the overridesBaseGeometry parameter of the FnBaseLocatorVDC::registerLocator() static function.
. BuilderMode and BuilderBuildMode references of the GroupBuilder class incorrectly linked to the respective typedefs instead of enums.
. Functions in the FnGeolibCookInterface API that accept callback function pointers for deleting private data were not parsed correctly, and appeared as single lines without breaks, exceeding the page boundary.
- TP 399981 - Multiple typos in the Katana Developer Guide have been fixed.
- TP 400452 - When the documentation preference was set to local, the API Reference > Parameter Expressions and API Reference > C++ APIs commands in the Help menu of the Katana main window did not link to the correct location in the Katana Developer Guide.
Other Bug Fixes
- TP 71317 / BZ 36414 - When attempting to undo the creation of a SuperTool-based node, such as GafferThree, an exception was raised.
- TP 216997 - Materials created via a NetworkMaterialSplice node were of the deprecated type shading network material, instead of the material type.
- TP 356705 - Manipulating locations during a Live Render could cause continuous live updates (during the manipulation) to stop working for all locations.
- TP 386841 - When FnGeolibCookInterfaceUtils::cookDaps() was invoked from multiple threads, it would fail to correctly read the default attributes on occasions. This affected Ops that relied on that function, e.g. the AdjustScreenWindowResolve Op, which on occasion failed with an error message: Error getting string value from StringAttribute. The GenericAssign DAP is now thread-safe.
- TP 394990 - The dead _initKeyboardShortcutCallbacks() Python function was removed from the KeyboardShortcutManagerMixin class, in order to avoid possible confusion about its use.
- TP 396842 - When refreshing the tree view of a material group attribute on a material location whose attributes are displayed in the Attributes tab, all items in the tree view were collapsed. Now, the expanded state of items is retained when refreshing the tree view.
- TP 397791 - The initialization of plug-ins used by Default Attribute Producers at render time was not thread safe, and could cause the render process to crash.
- TP 400154 - When loading internal example projects, areas of the node network were not visible, depending on the chosen main window layout and screen resolution. Now, upon loading an example project, the Node Graph tab will automatically frame all nodes.
The Foundry Katana 3.2 revamps the software’s material node graph, with the new Network Material Create Node introducing a more conventional left-to-right workflow, plus a range of other standard UX features.
Those include the option to collapse nodes to save screen space, add dot or switch nodes to control the layout of connections, and set up custom coloured backdrops to identify regions of the graph visually. Users can also group parts of a material node network into Shading Group nodes, making it possible to set up nested networks. Foundry tells us that it hopes to roll out similar workflows in the wider node graph in future.
The Hydra viewer has been updated to USD 19.05, and now supports multiple render delegates. Support for multi-cam rendering, random walk SSS and better hair shading in 3Delight. The bundled version of 3Delight gets a new workflow for rendering multiple camera views simultaneously, intended to enable artists to check assets from different angles during look development.
Other new features in 3Delight include support for random walk subsurface scattering, the option to use displacement maps directly with the Principled shader, and improvements to hair and fur shading. The renderer is also now multithreaded by default, improving scene export times “between 30% to 400%”.
Katana 3.2 builds the foundations for a completely overhauled look development user experience. Enjoy a cleaner, artist-focused material node graph UI with and faster, production-savvy workflows!
The Foundry is a leading global developer of creative software used to deliver high-end visual effects and 3D content for the design, visualization and entertainment industries. The portfolio empowers artists to create inspiring and technical images and visual experiences in media production (film, commercials, episodic television, gaming, and virtual and augmented reality), and product and industrial design.
The company was founded in 1996 and is headquartered in London, with offices in Silicon Valley, Manchester, Los Angeles, Shanghai, Dublin and Austin. In November 2015 Alex Mahon was appointed as CEO while Bill Collis became president.
Product: The Foundry Katana
Version: 3.2v1
Supported Architectures: x64
Website Home Page : www.foundry.com
Language: english
System Requirements: PC *
Supported Operating Systems: *
Size: 333.8 mb
Officially Supported Operating Systems
- Windows 7 64-bit or higher
Hardware Requirements
CPU: Dual-core processor
Storage: 1+ GB available for installation
System RAM: 1+ GB available
Graphics RAM: 1+ GB available: 2+ GB available (Recommended)
Display: 800 x 600: 1920 x 1080 (Recommended)
OpenGL OpenGL: 4.3+
- Windows 7 64-bit or higher
Hardware Requirements
CPU: Dual-core processor
Storage: 1+ GB available for installation
System RAM: 1+ GB available
Graphics RAM: 1+ GB available: 2+ GB available (Recommended)
Display: 800 x 600: 1920 x 1080 (Recommended)
OpenGL OpenGL: 4.3+
Please visit my blog
Added by 3% of the overall size of the archive of information for the restoration
No mirrors please
![The Foundry Katana 3.2v1]()
Added by 3% of the overall size of the archive of information for the restoration
No mirrors please
The Foundry Katana 3.2v1
