Fixed an HQueue bug where a job sometimes became indefinitely attached to a client machine. This led to "Client <hostname> is reporting job XXXXXX which does not exist." errors when the job was deleted from the system.

Fixed potential tiling artifacts when a shader outputs empty BSDF.

Fixed potential tiling artifacts when a shader outputs empty BSDF.

Fixed potential tiling artifacts when a shader outputs empty BSDF.

Fixed potential tiling artifacts when a shader outputs empty BSDF.

Fixed potential tiling artifacts when a shader outputs empty BSDF.

Fixed an issue with pdg.WorkItemHolder.addWorkItemFromJSON not correctly adding output files to the new work item when used in a static processor node. This issue also affected the JSON Input TOP node.

Fixed an issue with pdg.WorkItemHolder.addWorkItemFromJSON not correctly adding output files to the new work item when used in a static processor node. This issue also affected the JSON Input TOP node.

Fixed an issue with pdg.WorkItemHolder.addWorkItemFromJSON not correctly adding output files to the new work item when used in a static processor node. This issue also affected the JSON Input TOP node.

Fixed an issue with pdg.WorkItemHolder.addWorkItemFromJSON not correctly adding output files to the new work item when used in a static processor node. This issue also affected the JSON Input TOP node.

The Ground Explosion, Aerial Explosion, and Bonfire have been tweaked. The sparse pyro shelves now default to having the display flag on the pyrobake volume sop where appropriate.

Fixed a bug in the Copy to Points SOP that could produce incorrect results when the number of template points exceeded 1024.

Fixed a bug in the Copy to Points SOP that could produce incorrect results when the number of template points exceeded 1024.

Fixed a bug in the Copy to Points SOP that could produce incorrect results when the number of template points exceeded 1024.

Fixed a bug in the Copy to Points SOP that could produce incorrect results when the number of template points exceeded 1024.

Fixed a bug in the Copy to Points SOP that could produce incorrect results when the number of template points exceeded 1024.

In the LightMixer LOP, the transforms tab will now use the same working set as the sliders and attributes tab. Collections, however, will be evaluated for hteir contents and each of those will be added to the transforms tab directly.

In the LightMixer LOP, the transforms tab will now use the same working set as the sliders and attributes tab. Collections, however, will be evaluated for hteir contents and each of those will be added to the transforms tab directly.

In the LightMixer LOP, the transforms tab will now use the same working set as the sliders and attributes tab. Collections, however, will be evaluated for hteir contents and each of those will be added to the transforms tab directly.

In the LightMixer LOP, the transforms tab will now use the same working set as the sliders and attributes tab. Collections, however, will be evaluated for hteir contents and each of those will be added to the transforms tab directly.

In the LightMixer LOP, the transforms tab will now use the same working set as the sliders and attributes tab. Collections, however, will be evaluated for hteir contents and each of those will be added to the transforms tab directly.

When using the -j option with Houdini to limit the number of processors it uses, apply that same limit to the USD library. A value specified with the PXR_WORK_THREAD_LIMIT environment variable still takes priority over this setting.

When using the -j option with Houdini to limit the number of processors it uses, apply that same limit to the USD library. A value specified with the PXR_WORK_THREAD_LIMIT environment variable still takes priority over this setting.

When using the -j option with Houdini to limit the number of processors it uses, apply that same limit to the USD library. A value specified with the PXR_WORK_THREAD_LIMIT environment variable still takes priority over this setting.

When using the -j option with Houdini to limit the number of processors it uses, apply that same limit to the USD library. A value specified with the PXR_WORK_THREAD_LIMIT environment variable still takes priority over this setting.