-
UsdMaterialBake nodes now also export prmanStatements.attributes set on a location.
-
The following changes have been made in the parameter interface of UsdMaterialBake nodes:
- The fileName parameter was renamed to looksFilename (note the lower-case
n
). - The fileFormat parameter was renamed to looksFileFormat.
- The createCompleteUsdAssemblyFile parameter was added, which controls whether a USD assembly file is written alongside the baked material looks file. The USD assembly file references the looks file (looksFilename) and a particular payload file (see payloadFilename below). Defaults to No. When set to Yes, the following additional parameters appear:
- assemblyFilename -- the name of the assembly file to write.
- payloadFilename -- the name of a file to reference as a payload in the assembly file to write.
Warning: The changes in parameter inferface of UsdMaterailBake nodes are not compatible with earlier releases, meaning that attemping to open a Katana project with the new nodes with an earlier plugin results in Python exceptions being raised.
- The fileName parameter was renamed to looksFilename (note the lower-case
-
UsdIn nodes will now import material.layout attributes, allowing for the shading nodes to be edited inside of NetworkMaterialEdit nodes, retaining any positional, color or viewstate information relating to USD's
UsdUINodeGraphNodeAPI
. -
Boost::filesystem added as a dependency onto usdKatana library for bugfix ID 462435.
- ID 440214 - Issue #11: (Windows only)
.lib
files were not installed along with.dll
files for the usdKatana and vtKatana libraries inplugins\Resources\Usd\lib\
and the shipped plug-ins inplugins\Resources\Usd\plugin\Libs\
. - ID 440218 - Issue #9: When installing the Katana USD Plug-ins, public class headers were not installed correctly in
plugins/Resources/Usd/include/<library name>/
. - ID 446328 - When exporting and then importing a material via UsdMaterialBake and UsdIn nodes, the grouping of parameters in pages was not restored correctly.
- ID 453346 - When exporting material information using a UsdMaterialBake node, child material locations with no local change were not exported.
- ID 462435 - When using UsdIn nodes to load USD assets that use textures containing
<UDIM>
tokens in their filenames, spurious warning messages about unresolved asset paths were logged. - ID 462544 - When loading a USD asset that made use of a
TfToken
primvar into the Hydra Viewer, a warning message was logged, and the primvar was ignored. - ID 463889 - When creating shading nodes from USD, a wrong target renderer was set in certain cases.
- TP 459692 - [USD I/O] Supporting Ramp widgets with UsdExport and Import
- TP 462544 - TfToken primvar type was not being handled which results in a warning
- The evaluateUsdSkelBindings checkbox was added to the parameter interface of UsdIn nodes, adding support for importing bound and rigged models with the UsdSkel schema. When turned on, the skinning will be applied to each prim that is bound to a skeleton.
- New options have been added to disable: UsdExport and UsdRenderInfoPlugin. These are described in the BUILDING.md file.
- TP 458445 - [USD I/O] Fixed narrowing conversion warning/error
- TP 459446 - Added sdr and ndr dependencies and fixed bundling of some Python files.
- TP 458445 - Small fixes to remove standalone compilation warnings.
- TP 455245 - Fixing terminal export and import for shaders.
- The UsdExport changes are not compatible with Katana releases older than
Katana 4.0v1 due to API changes in
LookFileBakeAPI
. Disable the UsdExport subdirectory when building for Katana 3. See Github Issue #19: TheFoundryVisionmongers#19 for more information on upcoming build changes to support building the latest Katana USD Plug-ins against older Katana releases. - The list of renderers that are available inside NetworkMaterialCreate nodes,
which can be accessed by pressing the Shift+Tab keyboard shortcut, adds all
items where their RenderInfoPlugin returns true to
isNodeTypeSupported("ShadingNode")
. In order to support the display of USD shading nodes, the list now also includes renderers for which render info plug-ins, but no render plug-ins are available (viewer-only renderers), if they meet this condition. - The Katana USD plug-ins used to always use the default renderer as the
target
for the shaders. We now useusd
as the renderer name for shaders which start withUsd
, which includes the shading node designed for UsdPreviewSurface. - UsdLux light shaders, such as
UsdLuxDiskLight
andUsdLuxRectLight
, are now available for use inGafferThree
nodes. - ID 447533 - The UsdExport Output Format plug-in, which is designed to work
with UsdMaterialBake nodes, has been hidden from the
outputFormat
parameter of LookFileBake nodes using the newHidden
class variable introduced in feature enhancement ID 448056. - ID 447802 - The
USD_KATANA_ALLOW_CUSTOM_MATERIAL_SCOPES
environment variable of the Katana USD Plug-ins is now set to true by default. If set to false, this will limit material assignments to materials scoped under a Looks location. - ID 447804 - The
USD_KATANA_ADD_CUSTOM_PROPERTIES
environment variable of the Katana USD Plug-ins is now set to true by default. If set to false, this will silently ignore custom properties. - GitHub Issue #6 - Pull Request #7 - Avoid flattening face-varying primvars during import.
- TP 420782 - Fixing issues when building inside the Katana build pipeline
- TP 427390(Issue #3) - Fixed incorrect lib prefix during USD linking using the USE_KATANA_THIRDPARTY_LIBS option
- Changed variable requirement from
PYTHON_EXECUTABLE
toPython_EXECUTABLE
to be inline with thefindPython
provided by CMake. - Changed the build process to make the use of CMake config files as optional.
- Added a new set of options for building which simplify the build_script to
use the libraries and headers shipped with Katana, ensuring compatibility with
our USD. See the new
USE_KATANA_THIRDPARTY_LIBS
section in theBuilding.md
- Updated
Building.md
to document new build options. - Added new
SetupInterfaces.cmake
to cover new build interface options. - Fixed issue where headers defined under the PUBLIC_HEADERS argument were not installed into an include folder in the install folder.
- Removed the :kat:node:
Pxr
prefix from the node type names to make them match Katana naming conventions, eg. :kat:node:UsdIn
instead of :kat:node:PxrUsdIn
. SeeTable of Name Changes
_. - Changed the name of the Op types to ensure we don't clash with externally-built Katana USD Plug-ins.
- Updated Attribute names to more generic names.
- Removed automatic creation of
prmanStatements
. Only added ifprman
is a loaded renderer. - Added a
Support.cmake
file to support the Pixar macro usage in build scripts. - Created a root
CMakeLists.txt
in order to replace the USD coreCMakeLists.txt
. - Ensured the CMake builds work on Windows and Linux with Katana's
fnUsd
libraries. - Using CMake configurations over absolute library paths for portability.
- Added
Bootstrap
tousdKatana
libraries to set up Katana plug-ins. - Changed use of
std::regex
toboost::regex
due to issues with GCC 4.8.x and C++11std::regex
. - Patched issues with builds on Visual Studio 15.
- Modified
vtKatana
library to exportlong
data type. - Removed deprecated code support for RenderMan coshaders.
- Removed deprecated code for the USD
VMP
. - Removed header files which were no longer used in
KatanaPluginApi
. - Added support for flushing of caches to UsdIn Op type (was previously taken care of by removed USD VMP - see f)).
- Updated Apache 2.0 licenses and added
NOTICE.txt
. - Updated
README.md
and addedBUILDING.md
. - Updated the default option for
USD_ABC_WRITE_UV_AS_ST_TEXCOORD2FARRAY
to be "true" from "false", to ensure the USD Alembic plug-in imports uv attributes into the st arbitrary attribute location; matching the behavior of :kat:node:Alembic_In
nodes. - Our plug-in uses
fnpxr
python modules.
- Initial code started from 19.11 USD extracting the third_party/katana folder. https://github.com/PixarAnimationStudios/USD/blob/master/CHANGELOG.md