The Foundry Katana 3.1v5 | 312.3 mb
The Foundry launches the newer update to its professional look development and lighting tool. This update include new Feature Enhancements and bug fixes that improve the 3.1v4 release.
Katana 3.1v5 Release Notes - Release Date 18 June 2019:
Feature Enhancements
- Support for collapsed event handlers, which receive events of the same type to be processed in batches in a single handler call, have been reinstated. This notably improves performance.
- TP 391983 - The Viewer API is now able to cook multiple Viewer Proxy Op chains per Viewer update (up to a fixed limit, currently set at 1024). Distinct, uncached proxies are therefore now produced at a much higher rate.
- As part of this change, the asynchronous Geolib Runtime (used by the Katana UI) has been made more responsive to changes committed as transactions in the specific case that multiple Geolib Runtime Clients are scheduled to cook individual, costly scene graph locations.
- TP 129361 / BZ 51777 - Katana set the RenderMan RMAN_DSOPATH environment variable during application startup to an out-of-date value. Now, Katana no longer sets that environment variable.
- TP 386322 - When making a connection to a node's input port via the port's context menu, Katana crashed. (This issue was a regression in Katana 3.1v1.)
- TP 387349 - When calling Interface.RenameChild() in an OpScript node's Lua script with the same source and destination scene graph location name, the location in question was wrongly deleted.
- TP 387484 - When undoing/redoing interactive transform edits in the Hydra Viewer, a Live Render using RenderMan did not update correctly. (This issue was a regression in Katana 3.0v4.)
- TP 389671 - When right-clicking inside the Material Interface tree widget of an edited NetworkMaterial node and clicking away to dismiss the context menu, an additional context menu appeared. (This issue was a regression in Katana 3.1v1.)
- TP 389706 - When choosing a version of a Look File with Enforce this Version being enabled in the parameter interface of a LookFileManager node, a Python exception was raised. (This issue was a regression in Katana 3.1v1.)
- TP 390136 - When loading a Katana project that contained a non-contributing, dimmed node while launching Katana, e.g. by specifying an –asset to load from the command line, all nodes were incorrectly dimmed in the Node Graph tab after load. (This issue was a regression in Katana 3.1v1.)
- TP 390883 - When loading a Katana project containing LiveGroup nodes whose disable parameter was controlled via Python-based parameter expressions, a Python exception was raised due to infinite recursion. (This issue was a regression in Katana 3.1v1.)
- As part of a fix for this issue, calls of Utils.EventModule.ProcessAllEvents() and Utils.EventModule.ProcessEvents() while events are already processed are ignored now. This avoids overloading the Python stack unnecessarily.
- TP 392102 - When adding a light to a GafferThree node via the Parameters tab while Katana's 3D Update Mode was set to Pen-up, an exception was raised. In certain circumstances, new lights were then created every time the user triggered a 3D update or flushed caches. (This issue was a regression in Katana 3.1v3.)
- TP 392701 - No warning dialog was displayed when saving a project with unpublished LiveGroups in Edit mode, potentially resulting in changes being accidentally discarded. (This issue was a regression in Katana 3.1v1.)
- TP 393425 - When choosing the Search Entire Incoming Scene or Search Incoming Scene from Scene Graph Selection commands in the Action menu of an edited LookFileLightAndConstraintActivator node, an exception was raised. (This issue was a regression in Katana 3.1v1.)
- TP 393461 - The bound attribute was wrongly documented as being of type float[6] instead of double[6] on the Attribute Conventions > Transformations and Bounds page of the Katana Developer Guide.
- TP 393692 - The getAssetDisplayName() function of a custom Asset API plug-in was called an unusually high number of times during Katana project load.
- TP 394042 - When attempting to bind custom actions against widgets using UI4.App.KeyboardShortcutManager.BindActions(), a Python exception was raised. (This issue was a regression in Katana 3.1v1.)
- TP 394773 - When loading a Katana project containing thousands of nodes that are connected to a viewed node while the Dim Nodes Not Contributing to Viewed Node or Dim Nodes Unconnected to Viewed Node options in the Node Graph tab's Edit menu were turned on, loading took a lot longer than expected. (This issue was a regression in Katana 3.1v1.)
- TP 393301 - Loading and reverting a Katana project took longer in Katana 3.1 than in Katana 3.0 due to collapsed event handlers only receiving a single event per call, rather than a collection of events. (This issue was a regression in Katana 3.1v1.)
- TP 386322 - When making a connection to a node's input port via the port's context menu, Katana crashed. (This issue was a regression in Katana 3.1v1.)
- TP 387349 - When calling Interface.RenameChild() in an OpScript node's Lua script with the same source and destination scene graph location name, the location in question was wrongly deleted.
- TP 387484 - When undoing/redoing interactive transform edits in the Hydra Viewer, a Live Render using RenderMan did not update correctly. (This issue was a regression in Katana 3.0v4.)
- TP 389671 - When right-clicking inside the Material Interface tree widget of an edited NetworkMaterial node and clicking away to dismiss the context menu, an additional context menu appeared. (This issue was a regression in Katana 3.1v1.)
- TP 389706 - When choosing a version of a Look File with Enforce this Version being enabled in the parameter interface of a LookFileManager node, a Python exception was raised. (This issue was a regression in Katana 3.1v1.)
- TP 390136 - When loading a Katana project that contained a non-contributing, dimmed node while launching Katana, e.g. by specifying an –asset to load from the command line, all nodes were incorrectly dimmed in the Node Graph tab after load. (This issue was a regression in Katana 3.1v1.)
- TP 390883 - When loading a Katana project containing LiveGroup nodes whose disable parameter was controlled via Python-based parameter expressions, a Python exception was raised due to infinite recursion. (This issue was a regression in Katana 3.1v1.)
- As part of a fix for this issue, calls of Utils.EventModule.ProcessAllEvents() and Utils.EventModule.ProcessEvents() while events are already processed are ignored now. This avoids overloading the Python stack unnecessarily.
- TP 392102 - When adding a light to a GafferThree node via the Parameters tab while Katana's 3D Update Mode was set to Pen-up, an exception was raised. In certain circumstances, new lights were then created every time the user triggered a 3D update or flushed caches. (This issue was a regression in Katana 3.1v3.)
- TP 392701 - No warning dialog was displayed when saving a project with unpublished LiveGroups in Edit mode, potentially resulting in changes being accidentally discarded. (This issue was a regression in Katana 3.1v1.)
- TP 393425 - When choosing the Search Entire Incoming Scene or Search Incoming Scene from Scene Graph Selection commands in the Action menu of an edited LookFileLightAndConstraintActivator node, an exception was raised. (This issue was a regression in Katana 3.1v1.)
- TP 393461 - The bound attribute was wrongly documented as being of type float[6] instead of double[6] on the Attribute Conventions > Transformations and Bounds page of the Katana Developer Guide.
- TP 393692 - The getAssetDisplayName() function of a custom Asset API plug-in was called an unusually high number of times during Katana project load.
- TP 394042 - When attempting to bind custom actions against widgets using UI4.App.KeyboardShortcutManager.BindActions(), a Python exception was raised. (This issue was a regression in Katana 3.1v1.)
- TP 394773 - When loading a Katana project containing thousands of nodes that are connected to a viewed node while the Dim Nodes Not Contributing to Viewed Node or Dim Nodes Unconnected to Viewed Node options in the Node Graph tab's Edit menu were turned on, loading took a lot longer than expected. (This issue was a regression in Katana 3.1v1.)
- TP 393301 - Loading and reverting a Katana project took longer in Katana 3.1 than in Katana 3.0 due to collapsed event handlers only receiving a single event per call, rather than a collection of events. (This issue was a regression in Katana 3.1v1.)
The Foundry Katana is a 3D application specifically designed for the needs of look development and lighting in an asset-based pipeline. Originally developed at Sony Pictures Imageworks, Katana has been their core tool for look development and lighting for all their productions since Spider-Man 3, Beowulf, and Surf’s Up!. Katana provides a very general framework for efficient look development and lighting, with the goals of scalability, flexibility, and supporting an asset-based pipeline.
Katana is used in VFX, broadcast, and animation as a post-processing tool for final lighting. It uses a recipe approach to establishing lighting, making it easier for users to establish a lighting profile that can be reused in other scenes or projects.
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.1v5
Supported Architectures: x64
Website Home Page : www.foundry.com
Language: english
System Requirements: PC *
Supported Operating Systems: *
Size: 312.3 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
Added by 3% of the overall size of the archive of information for the restoration
No mirrors please