Contents
Welcome to RenderMan 22.0 for Katana
RenderMan for Katana (RfK) capitalizes on the changes made for newer versions of Katana and continues full support of the latest RenderMan ProServer 22.0.
We're excited to have improved Live Rendering. All manner of changes and edits can be made during a Live Rendering session. Waits are minimal and results are stunning, the renderer will continue to refine your image continuously should you take a coffee break and pick up where you left off on your return.
This current release offers support for:
- Katana 2.6
- Katana 3.0
- RenderMan ProServer 22.0
Please see the release notes below for all the new capabilities and known issues!
What's New
Better Defaults
Additional Changes
Miscellaneous Changes
Known Limitations
Live Rendering
- Updates to attributes will cause interactive motion blur to fail to render. The render must be restarted.
Creating a mesh light from existing geometry will duplicate the geometry in-render. Restart the render to remove the duplicate.
Alpha limitations
Monitor performance, needs improvements
- OpenVDB
New parallel AlembicIn_prman not supported yet with Importomatic
Dicing cameras do not work
Viewer 3.0 light viewer plugins and light modifier plugins not yet functional
Deformation motion blur for blobbies and volumes not yet supported
NURBS trim curves don't render
Display and Sample Filters not yet included
Lights in nested instances do not render
Checkpoint + recovery not yet functional in Alpha
- Projections do not render correctly.
- Stereo cameras do not render
- Holdouts not available in Alpha
Baking not available in Alpha
Clipping planes not available in Alpha
Polygons with holes
Material assignment to archives do not function correctly in Alpha
Alembic pass-through via AlembicIn_prman and Alembic proxy support in Viewer
Env var for DSO Procedurals
Integer AOVs ??
Katana Limitation
- When a Prune node is added at the end of the node graph, right above the Render node, we do not receive an edit from Katana. If a no-op node (e.g. Merge) is inserted above the Render node and the Prune is added above that then the delete edit is received and the Prune works properly.