The Foundry Katana 3.6v2

ID 437314 - When adding a tab of a type for which another tab previously existed, but was closed, callbacks of type Callbacks.Type.onTabCreated were executed, even though the tab was not created from scratch, but rather the previously closed tab was recycled.
ID 434639 - When duplicating an item in the Catalog tab, an exception was raised. (This issue was a regression in Katana 3.5v1.)
ID 432861 - Python code snippets on the Callbacks and Events page of the Katana Developer Guide failed to import Katana-specific Python modules.
ID 437321 - Light types in the Add PRMan Light and Add PRMan Light Filter submenus in the context menu of GafferThree were wrongly sorted alphabetically, not in the intended order that is suggested by their keyboard shortcuts, and that is shown in the RenderMan for Katana documentation.
ID 431375 - Occasionally, when called concurrently from multiple threads, the AssetReferencedOp could cause a crash. Note that, in this case, the Op may still load the same DSOs from different threads, but does so in a thread-safe manner.
ID 433277 - When using the Geolib3-MT Runtime, any action that causes the Op execution root to be reset (e.g. calling Cook Interface resetRoot()) was ineffective for input-scene-derived locations below immediate children.
ID 418273 - When a crop window was specified for the render, the Monitor Layer in the Viewer (Hydra) tab would cause GL errors, and the rendered image could appear with noise.
ID 432345 - When a Viewer (Hydra) tab was destroyed, its internal ViewerDelegate object was not correctly freed due to some circular dependencies in Python keeping the last reference alive.
ID 434897 - A small memory leak occurred in the Monitor Layer's internal code.
ID 435194 - When closing a Viewer (Hydra) tab with its Monitor Layer turned on, and then starting a Preview Render, an exception was raised.
ID 416235 - Nodes inside a NetworkMaterialCreate node that was itself contained within a LiveGroup node wrongly appeared at the same position until the LiveGroup contents were edited. (This issue was a regression in Katana 3.2v2.)
ID 427776 - In the Network Material context, shading nodes which exposed a parameter page group named Parameters could not be interacted with in the Node Graph tab.
ID 433292 - While creating a new connection between shading node ports and pointing at a target shading node, pressing a keyboard shortcut like Alt+3 to modify that node's view state wrongly modified a different, selected shading node instead.
ID 441089 - In the Network Material context, when using a PrmanShadingNode node of nodeType PxrMatteId in the Node Graph tab, the node's Parameters sub-page, also named Parameters, was closed, and could not be opened by clicking the page header. (This issue was a regression in Katana 3.2v2.)
ID 432887 - When undoing the deletion of a (shading) node in a NetworkMaterialEdit, the Node Graph tab could get out out of sync with the Op, causing Python exceptions to be raised.
ID 434565 - When changing a NetworkMaterialEdit node's sceneGraphLocation parameter after entering the node, the node wrongly applied edits to the previously edited scene graph location, rather than the new scene graph location.
ID 437443 - When entering a NetworkMaterialEdit node inside of a locked, uneditable LiveGroup node while a render was in progress, exceptions were raised, and the rendered result may have looked different than the expected result.
ID 437904 - NetworkMaterialEdit nodes could sporadically fail to update their contents when the upstream material changed if the NetworkMaterialEdit was directly connected to a NetworkMaterialCreate and the view flag was set on the NetworkMaterialCreate.
ID 439074 - When using a NetworkMaterialEdit node to make edits to the value of a string type parameter on a shading node, if the parameter was edited more than once, the resulting material.nodes attribute data relating to the node used an invalid hierarchy.
ID 436820 - When modifying a node graph containing nodes whose names are driven by Python-based parameter expressions, a large number of unnecessary events were being processed, leading to an increase in execution time. (This issue was a regression in Katana 3.2v5.)
ID 438864 - When copying or dragging a parameter or attribute representing an array of values, or a group containing such parameters or attributes, the corresponding MIME data of format 'policy/xml' was clamped to a hard-coded maximum of 16 values for each array. This limit was introduced in Katana 1.1v1 to avoid generating large amounts of XML text for very large arrays of values. This value can now be customized by setting the new environment variable KATANA_VALUEPOLICY_MIMEDATA_ARRAY_SIZELIMIT to a numeric value (default: 16).
ID 435094 - When starting a Live Render after clearing Katana's Catalog tab by choosing its Clear Catalog command, Python exceptions were raised. (This issue was a regression in Katana 3.2v3.)
ID 441807 - The use of std::unordered_map and std::unordered_set in the AttributeKeyedCache.h header has been replaced with std::map and std::set equivalents, in order to avoid exposing std::_Hashtable names in the FnGeolibSDK library. The Boost equivalents can be used instead by setting the new ATTRIBUTEKEYEDCACHE_USE_BOOST define to some value when building code that uses the AttributeKeyedCache.h header.
ID 433908 - The Katana licensing dialog erroneously contained a message stating that the duration of a Katana trial was 15 days. This duration was recently increased to 90 days. The mention of a specific number of days was removed from the dialog now.

Officially Supported Operating Systems
- Windows 7 64-bit or higher
- Linux 64-bit operating system (CentOS/RHEL 6)

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+