...
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.
- The grouping membership attribute no longer automatically prepends the value set with a "" (empty double quotes). This is to allow fuller functionality to match the RenderMan attribute syntax. That syntax allows: "" - add to the membership specified at a higher level, "-" - remove from the membership specified at a higher level, "" - replace the membership.
- 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 creating light filters in GafferThree
- camera fov motion blur
Improvements since RenderMan 22.07b
Array user attributes are now supported.
There is a new node called PrmanCameraSettings for setting camera settings
Added
new offscreen displacement bound primAttribute, please see: displacementbound:offscreen
Material IDs are now available for the PxrCryptomatte sample filter
Improvements since RenderMan 22.06b
RfK's script and Op for automatically converting attributes from 21 to 22 is now correctly handling the conversion of "prmanStatements.orientation" to "prmanStatements.attributes.ReverseOrientation" and "prmanStatements.primAttributes.Orientation".
Arbitrary clipping planes are now supported
Reorganized the PrmanObjectStatements node to improve clarity and workflow
The
Improvements since RenderMan 22.05b
Added theglobal traversal setting "flattenInstanceSources"
indicates whether instance sources should be flattened internally in the renderer. By default this is on which is the most efficient and flexible for the common case. Disabling this option allows deeper nesting of instance sources with the caveat that RenderMan only supports
4 levels of nesting, and it prevents per-instance variation on instance source children. This can be overridden locally by the local PrmanObjectStatements parameter - "traversal.flattenInstanceSource" See the documentation on Instancing for an explanation of benefits and limitations
OpenEXR outputs containing "Ci,a" as the first four channels will now write out an EXR with R,G,B,A as the first four channels (i.e. "asrgba" will be enabled for all beauty renders
)
The global statistics option "endofframe" is no longer deleted. It is now renamed to "level" and any non-zero (enabling) values are correctly preserved by setting "level" to True.
Manipulator cycling is done with "Tab" instead of "Y"
Katana 3.0: The Hydra Viewer now visualizes PxrEnvDayLight.
.
Improvements since RenderMan 22.04b
Added extensibility to RfK's procedural argument parsing. Now RfK will look for an attribute "argsConversionFunc" which is the name of a attribute function for custom argument conversion
Add support for prman command line options "woff", "logfile", and "loglevel
"
Improvements since RenderMan 22.03b
Improvements since RenderMan 22.02b
RfK will now use the basis from the alembic file unless
Improvements since RenderMan 22.01b
overridden by the curve.basis setting in PrmanObjectStatements (NOTE: only supported with AlembicInPrman
initially)
The default type in PrmanOutputChannelDefine is now "color"
Live render edits to ROI / cropWindow now use the intersection of the two attributes
Alembic cameras now use the camera settings from prmanGlobalStatements
OSL parameters now have connection type checking for the inputs and ouputs of PrmanShadingNode
OSL parameters support a "tag" hint in the metadata to allow users to specify a connection type for the parameter. For multiple types on outputs, use a "|" to delimit the options (eg "struct|manifold")
RfK now supports connections between any color, normal, point, and vector parameters
Attribute "trace.displacements" are now automatically upgraded to the current "boolean" type. Previous values of '2' are now reset to '1'.
Unknown scenegraph location types no longer emit warning "Location type not recognized". These unknown location types still default internally to a group location.
Known Limitations
Live Rendering
- Updates to attributes will cause interactive motion blur to fail to render. The render must be restarted.
- Starting a live render with a crop window set will fail.
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)
- 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
Beta 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.
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 based on the improvements to 3.0