...
Additional Changes
Miscellaneous Changes
- Materials set at instance source locations are ignored
Dicing cameras are now specified as a camera's scenegraph location. The "worldcamera" and "framecamera" options are no longer supported. This also removes the need to add the dicing camera to a RenderOutputDefine to use the full camera path.
- 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
- Integrator settings are now configured with 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 supported:
- "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
Info |
---|
Improvements since RenderMan 22.01b
|
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.
- Adding a portal light to a dome light doesn't delete the dome light
- 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
- Some parameters in PrmanGlobalStatements and PrmanObjectStatements are read-only. These parameters are not yet supported.
- 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.
- User defined attribute identifier id are not respected
- Prman's errorHandlers are not supported
- NURBS trim curves don't render
- Lights in nested instances do not render
- Texture Projections do not render correctly
- 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
- 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: Hydra Viewer light 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.
- There are a few live render limitations in Katana 2.6 that have been resolved in Katana 3.0.