• Added motion blurred FOV capabilities and a detail modifier to the PxrCamera plugin
• Camera options such as depth of field and FOV must be specified through a projection plugin.
• Alpha and RGBA color sets are now supported. RGBA color sets are emitted as "color colorSetName" and "float colorSetNameA" to allow for ease of shader binding.
• Increased default precision for RIB export to 9
• Added Attribute "displacementbound" "int offscreen", please see the Primitive Variables section for an explanation
• Improved adaptive sampling when using checkpointing
• JIT compilation of OSL shaders now executes in parallel
• Added support for interactive arbitrary clipping planes
• Volume instancing is fully supported, however, density (and motion blur) cannot be altered per instance.
• Removed the PxrRollingShutter plugin, the functionality exists in PxrCamera
• PxrHairColor allows for either rec709/sRGB or ACEScg for Physical Mode
• Improved texture filtering results, we improved mipmapping level selection at grazing angles.
• Crop windows are no longer limited to the (0,0) to (1,1) square. Going outside the unit square will add overscan
• Cryptomattes now respect the crop window rather than adding black padding. Now they are always autocropped which may reduce size further.
• Cryptomatte now defaults to scanline EXR (ZIPS) output. This improves performance in Nuke at the cost of larger files.
• PxrCryptomatte now supports checkpointing
• Improved transparency handling in PxrCryptomatte
• Improvements in point rendering, more speed and less memory usage reported in many scenes. Note point mesh lights are not supported and points cannot be used as closed volumes
• Improved shadow tracing performance, especially on scenes where lights may not contribute to a point being shaded
• Alembic geometry is treated as instances when "-instanced" flag is specified
• Better handling of OpenVDB containers with zero density
• PxrSurface can now report its IOR when using nested dielectrics, removing the need for users to manually specify the attribute. The attribute is deprecated.
• Bump Adjust Amount is now defaulted to 1 (it was 0) to remove possible artifacts preemptively when a normal is below the horizon
• Bump mapping has been improved to avoid light leaking
• The exrinfo utility now automatically truncates the display of very long strings from the image header.  Use its new -full option to show these in full without truncation
• The "-d type" command line option now overrides the display type for all displays, not just the primary one
• Improved the calibration of timing statistics on Linux
• Methods in the the RixRNG.h header have been changed to be more typesafe
• Various fixes to volume rendering in 22 will result in different looks in volume rendering from pervious versions, they may appear (much) brighter depending on lighting circumstance.
• Added a new Primvar for points, falloffpower, float. I f not supplied, or set to zero, the points will have a hard edge. A value of 1 is a "reasonable" value that emulates the usual cosine based falloff; this will likely be the goto value for most people doing volumetric particle effects. Values between 0 and 1 makes the falloff faster, eroding the point faster - point has "less presence". Values higher than 1 (up to infinity) makes the falloff slower to the point of being non-existent.
• Defaulted the following patterns to Object Space:
  • PxrPrimvar
  • PxrVariable
  • PxrManifold3DN
  • PxrRoundCube
  • PxrManifold3D
• Introduced a new Hider option: "int sampleoffset". This allows several images to be rendered in parallel (with different sampleoffset) and then combined. (Essentially: Users can separate a single render across multiple nodes to share the work and then combine them when complete using a post process.)
  • With non-adaptive sampling: Let's say you render four images with 256 samples each, with sampleoffsets 0, 256, 512, and 768. If you combine those four images, you'll get exactly the same image as if you had rendered a single image with 1024 samples.
  • With adaptive sampling: Let's say you again render four images, each with "maxsamples" 256, with sampleoffsets 0, 256, 512, and 768. Let's say that due to adaptive sampling, some given pixel only gets 64 pixel samples in each of the four images. Then the combined image has been rendered with sample numbers 0-63, 256-319, 512-575, and 768-831. Due to the stratification of the samples, this is not quite as good as if you had rendered a single image with 256 consecutive samples. (However, it is, of course, quite a bit better than rendering a single image with only 64 samples.)
• Support lights in procedurals. This change allows for:
  • lights to be inside of groups and obey the usual instancing rules (one light in a single group master will yield multiple 'lights' when the group is instanced multiple times)
  • lights to be inside procedurals
  • lights to be inside ObjectBegin/ObjectEnd blocks, included nested ones

Known Limitations

Interactive/Live Rendering Limitations

• Crop window edits are restricted to fall inside the original crop window
• Bucket order or size cannot be changed during live rendering
• min and max samples settings cannot be altered during live rendering
• Changes to Presence do not update when using the opacity cache option
• Motion Blur will disappear during interactive rendering with scene changes
• Displacement does not update on changes
• Objects are not re-diced during interactive sessions
• Mesh lights cannot be interchanged as geometry without restart.

RenderMan Pro Server

• PxrUnified integrator is currently experimental as it does not yet support all the standard rendering features.
• Meshlights cannot be instanced
• Load on demand procedurals are not supported anymore, all procedurals are now loaded immediately
• We do not read point data from OpenVDB files
• PxrSurface back diffuse color is not output to the albedo color AOV
• Analytical lights placed inside volumes may yield artifacts when made visible to the camera. As a work around, the light camera visibility should be turned off, and a geometry with a similar shape should be used (visible to camera, invisible to transmission and indirect rays), with the proper emissive bxdf.
• Using the ' . ' character in the handle for an OSL shader could cause unpredictable results during re-rendering.
• Per-Instance baking is not supported, only the reference instance.
• 3d baking: no direct bake-to-ptex support.
• PxrBakePointCloud cannot directly render ptex.
• Sample/Display filter plug-ins do not have access to lighting services for light dependent effects, e.g. lens flare.
• Adding new mesh light on existing geometry during IPR results in double geometry.
• Motion blurred polygons do not motion blur normals when deformed. Use Subdivision meshes instead.
• PxrUPBP is no longer supported
• When attempting to access an array primvar, you must first check the size of the array primvar and allocate the appropriate space. Not doing so may lead to a crash.
• Points and curves cannot be used as geometric lights.

• Deformation motion blurred volumes don't currently work with densityFloatPrimVar or densityColorPrimVar. You will need to use a PxrPrimVar node connected to densityFloat and densityColor instead.

  Note
  The Centos KDE style "Oxygen" installs a version of Qt and sets the user's environment variable QT_PLUGIN_PATH forcing "it" and LocalQueue to attempt to load an incompatible Qt library. Either avoid installing the Oxygen theme or unset QT_PLUGIN_PATH before running "it" or LocalQueue. Other KDE styles may also install this theme.