...
- Preset Browser for Materials and Environments
- Multi-threaded Katana Scenegraph traversal (faster time-to-first-pixel)
- Multi-threaded Alembic_In_Prman (improves speed when reading multiple alembics)
- Live add, delete and transform for geometry
- Live updates for light-linking
- Live light deleting
- Instanced lights
- Light array support
- Can assign light shader PxrMeshLight can be assigned to geometry using with a MaterialAssign node
- Cone angle now visualized on Viewer Modifiers
- 64-bit object IDs, consistent across disk/live/preview renders
...
Additional Changes
Miscellaneous Changes
- Cannot Materials set material at instance source locations are ignored
- PxrSphereLights with cone angles are now facing the correct direction
- Instance primvars are no longer supported. Use user attributes instead.
- Leaf level instancing now requires that locations with the instance.ID attribute have no children. RfK will not traverse past a location with instance.ID set.
- RIB Include has been removed
- RfK will now read args files for custom integrators
- Integrators Integrator settings are now configured via the PrmanIntegratorSettings nodewith a new node called PrmanIntegratorSettings. This node automatically picks up any integrators with Args files on RMAN_RIXPLUGINPATH.
- "insertWhen" directives for config.xml are removed pending new configuration
- Parameter Layout has been removed from PrmanGlobalStatements and PrmanObjectStatements
- Attributes in PrmanObjectStatements are now split into either an "attributes" or "primvars" group depending on whether the attribute can vary per instance.
- There have been a few changes related to cameras and PrmanGlobalStatements: -
- dofAspect was a hider setting, but is now found under prmanGlobalStatements.camera.depthOfField.dofAspect.
- Projection plugins can be created as materials assigned to /root. They are no longer available through PGS.
- backgroundColor can be created as a "PxrBackgroundDisplayFilter" assigned to /root. It is no longer available in PGS.
- The settings in the camera motionBlur section have changed and could not be automatically remapped.
- It is no longer necessary to create a camera with frameBeginCameraPath. All cameras in the scene will be created.
- No longer supportedDeprecated:
- "prmanGlobalSettings.plugin.instanceSourceMode"
- "prmanGlobalSettings.commandArguments.numThreadModeProcs"
- "textures" attribute group
- The PrmanLightFilterCreate macro has been removed in favor of light filters in GafferThree
- camera fov motion blur
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.
- Monitor performance can lag behind edits for large scenesCreating a mesh light from existing geometry will duplicate the geometry in-render. Restart the render to remove the duplicate.
- Volume edits will break the volume render.
- Adding a portal light to a dome light doesn't delete the dome light
- Cannot Live Render from Viewer camera
- Cannot change a geometry primitive type during live rendering (e.g. from NURBS to polymesh)
- When traversal is parallel, edits to a live material will affect only a subset of assigned geometry unless all of the assigned geometry starts out live or is made live at least once during the live render session.
- Edits to mesh light parameters require that the geometry location is enabled in the live render working set
- When assigning a material to a Scene Graph location, that location must be enabled in the live render working set
Alpha limitations
- If the environment variable RMAN_SHADERPATH or RMAN_RIXPLUGINPATH is set and doesn't include the default paths from RMANTREE then the default prman shaders are not found.
- Some parameters in PrmanGlobalStatements are read-only. These parameters are not yet supported.
- User defined attribute identifier id are not respected
- Light filters on light arrays are not yet supported
- New parallel Alembic_In_Prman not supported yet with Importomatic
- Prman's errorHandlers are not supported
- Dicing cameras do not work
- Deformation motion blur for blobbies and volumes not yet supported
- NURBS trim curves don't render
- Display and Sample Filters not yet supported
- Lights in nested instances do not render
- Checkpoint + recovery not yet functional
- Projections do not render correctlyStereo cameras do not render
- You can only render from the RenderSettings camera.
- Holdouts not available
- Baking not available
- Clipping planes not available
- Polygons with holes not supported
- Light filter linking not supported
- Live udpates to ROI and crop window not supported
- Display "interactiveDisplayOptions" not supported
- Deep output type not supported
- Integer AOVs are not available in RenderOutputDefine
- 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
- Instanced lights with parented filters using the "Light Filter" coordsys have incorrect transform
- Material matrix parameters of type double are not supported
- Material matrix array parameters are not supported
- Attribute "geometry.flip_t" is not currently supported
- Katana 3.0 only: Volumes and blobbies not yet functional.
- Katana 3.0 only: Hydra Viewer light viewer plugins and light modifier plugins not yet functional
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.