![]() ![]() For a high-level overview of important changes in the Katana 6.0 line, please see the accompanying What's New in Katana 6.0 document. Seamlessly collaborate, reduce feedback loops, and holistically achieve that perfect final render. These release notes describe changes from Katana 5.0v4 to 6.0v1. Any changes made in Katana automatically update in Nuke for a more holistic view of the creative process. ![]() Katana 5.0 allows look development and lighting artists to stream their live renders to a running version of Nuke, so they can view their work in context of the final comp, in near-real time. Itâs just round the corner-no longer will lighting artists lose hours of productivity thanks to the power of KatanaNuke, connected. ( Katana 3.2 is actually using USD 19.05.) TP 420667 - The FnKatImport.SetDebugBinaries() Python API function never had any effect in commercial Katana, and has now been marked as deprecated. These libraries are provided in the Katana distribution, in separate directories under $ to ensure these libraries are visible to Katana plug-ins.Are you ready for the age of the Super-Artist? TP 420580 - The External Software page in the Katana Developer Guide wrongly listed the version of USD being used in Katana 3.2 as version 0.8. Katana version 7.0v1 has dependencies on the following third-party libraries: Note:Due to Python's handling of imports on case-insensitive platforms (see PEP 235), it is not possible to run Katana from a file system location on a network-attached storage device (NAS) that has been set up with mount options for case-insensitive names.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |