...

• Shading
  
  • PxrUnified integrator does not yet support all the standard rendering features.
  • <primstr:nameofvalue> substitution of data from a constant primvar or user attribute on an object for dynamic filename substitution is not yet working for the gettextureinfo() OSL call.
  • Using the ' . ' character in the handle for an OSL shader could cause unpredictable results during re-rendering.
  • The RixTexture::TextureDerivatives calls always returns RixTexture::InvalidFile for non-texture-atlas files. This will be restored in 26.1.
• General rendering
  • Load on demand procedurals are not supported anymore, all procedurals are now loaded immediately.
  • RenderMan does not read point data from OpenVDB files.
  • Per-Instance baking is not supported, only the reference instance.
  • 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.
  • 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.
  • Analytical lights placed inside non-aggregate 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.
  • Indirect Path Guiding in the PxrUnified integrator causes a crash.
• Bridge Products:
  • RfH: Soloing MaterialX Lama nodes in complex shading networks can give an incorrect result.

...