Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Contents

Welcome to RenderMan 23.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 23.0.

This current release offers support for:

  • Katana 3.0
  • Katana 3.1
  • Katana 3.2
  • Katana 3.5 (beta)
  • RenderMan ProServer 23.0

Please see the release notes below for all the new capabilities and known issues!

What's New

  • Preset Browser for Materials and Environments

 

Additional Changes

 

Miscellaneous Changes

  • Materials set at instance source locations are ignored

 

Known Limitations

 

Live Rendering

  • Creating a mesh light from existing geometry will duplicate the geometry in-render. Restart the render to remove the duplicate.

  • Cannot change a geometry primitive type during live rendering (e.g. from NURBS to polymesh)
  • When assigning a material to a Scene Graph location, that location must be enabled in the live render working set

  • Live render edits to the visible attribute need group locations to be "included with children" in the Live Render Working Set

 

Katana Limitation

  • Instanced lights with filters using the "Light Filter" coordsys have an incorrect transform. The workaround is to promote the light filter to a shared light filter using a light filter reference.
  • When rendering to "it" from Katana, do not stop the render from "it", abort the render from Katana. Your Katana session may freeze for a time if you abort from "it". If you make this mistake you can restore Katana to operation by terminating the prman render process manually. This will be fixed in a future version. You can also avoid this entirely by rendering to the Katana Monitor.
  • We do not receive live render edits from Katana for nodes added at the end of the node graph, right above the Render node.  If a no-op node (e.g. Merge) is inserted above the Render node and the node is added above that then the edit is received.
  • Any live updates will cause interactive motion blur to be disabled. The render must be restarted.