• Fixed the laggy pan/zoom which occurred when a heavy fragment shaderwas used.
• Gamma and LUTs are only applied in unpremultiplied space whentransparency is on.

• Fixed the laggy pan/zoom which occurred when a heavy fragment shaderwas used.
• Gamma and LUTs are only applied in unpremultiplied space whentransparency is on.

• Fixed the laggy pan/zoom which occurred when a heavy fragment shaderwas used.
• Gamma and LUTs are only applied in unpremultiplied space whentransparency is on.

• Fixed the laggy pan/zoom which occurred when a heavy fragment shaderwas used.
• Gamma and LUTs are only applied in unpremultiplied space whentransparency is on.

Added new support for RenderMan RiCurve primitives. There are now three new detail attributes that can be set to control the output of open polys to RenderMan: "ri_curveinterpolation", "ri_curvebasis" and "ri_curvestep". "ri_curveinterpolation" should be set to either "linear" or "cubic". "ri_curvebasis" can be set to any standard RenderMan basis or a custom basis matrix. When "ri_curvestep" is omitted, the value in "ri_curvebasis" is used to determine the correct step size if possible. The RiCurve Basis parameter (renamed RiCurve Interpolation) in the RenderMan ROP is obsolete and may be removed from future versions. The environment variables HOUDINI_RMAN_CURVE_STEP and HOUDINI_RMAN_CURVE_BASIS are also obsolete and may be removed from future versions.

Added new support for RenderMan RiCurve primitives. There are now three new detail attributes that can be set to control the output of open polys to RenderMan: "ri_curveinterpolation", "ri_curvebasis" and "ri_curvestep". "ri_curveinterpolation" should be set to either "linear" or "cubic". "ri_curvebasis" can be set to any standard RenderMan basis or a custom basis matrix. When "ri_curvestep" is omitted, the value in "ri_curvebasis" is used to determine the correct step size if possible. The RiCurve Basis parameter (renamed RiCurve Interpolation) in the RenderMan ROP is obsolete and may be removed from future versions. The environment variables HOUDINI_RMAN_CURVE_STEP and HOUDINI_RMAN_CURVE_BASIS are also obsolete and may be removed from future versions.

Added new support for RenderMan RiCurve primitives. There are now three new detail attributes that can be set to control the output of open polys to RenderMan: "ri_curveinterpolation", "ri_curvebasis" and "ri_curvestep". "ri_curveinterpolation" should be set to either "linear" or "cubic". "ri_curvebasis" can be set to any standard RenderMan basis or a custom basis matrix. When "ri_curvestep" is omitted, the value in "ri_curvebasis" is used to determine the correct step size if possible. The RiCurve Basis parameter (renamed RiCurve Interpolation) in the RenderMan ROP is obsolete and may be removed from future versions. The environment variables HOUDINI_RMAN_CURVE_STEP and HOUDINI_RMAN_CURVE_BASIS are also obsolete and may be removed from future versions.

Added new support for RenderMan RiCurve primitives. There are now three new detail attributes that can be set to control the output of open polys to RenderMan: "ri_curveinterpolation", "ri_curvebasis" and "ri_curvestep". "ri_curveinterpolation" should be set to either "linear" or "cubic". "ri_curvebasis" can be set to any standard RenderMan basis or a custom basis matrix. When "ri_curvestep" is omitted, the value in "ri_curvebasis" is used to determine the correct step size if possible. The RiCurve Basis parameter (renamed RiCurve Interpolation) in the RenderMan ROP is obsolete and may be removed from future versions. The environment variables HOUDINI_RMAN_CURVE_STEP and HOUDINI_RMAN_CURVE_BASIS are also obsolete and may be removed from future versions.

Added new support for RenderMan RiCurve primitives. There are now three new detail attributes that can be set to control the output of open polys to RenderMan: "ri_curveinterpolation", "ri_curvebasis" and "ri_curvestep". "ri_curveinterpolation" should be set to either "linear" or "cubic". "ri_curvebasis" can be set to any standard RenderMan basis or a custom basis matrix. When "ri_curvestep" is omitted, the value in "ri_curvebasis" is used to determine the correct step size if possible. The RiCurve Basis parameter (renamed RiCurve Interpolation) in the RenderMan ROP is obsolete and may be removed from future versions. The environment variables HOUDINI_RMAN_CURVE_STEP and HOUDINI_RMAN_CURVE_BASIS are also obsolete and may be removed from future versions.

Panning and zooming in mplay with fragment shaders enabled no longer causes the image to lag behind the mouse. Only the latest mouse position is used, resulting in much snappier panning and zooming.

Panning and zooming in mplay with fragment shaders enabled no longer causes the image to lag behind the mouse. Only the latest mouse position is used, resulting in much snappier panning and zooming.

Panning and zooming in mplay with fragment shaders enabled no longer causes the image to lag behind the mouse. Only the latest mouse position is used, resulting in much snappier panning and zooming.

Panning and zooming in mplay with fragment shaders enabled no longer causes the image to lag behind the mouse. Only the latest mouse position is used, resulting in much snappier panning and zooming.

Panning and zooming in mplay with fragment shaders enabled no longer causes the image to lag behind the mouse. Only the latest mouse position is used, resulting in much snappier panning and zooming.

The Bounce and Friction values read by the RBD Solver are now clamped from below at 0. This prevents meaningless values causing the simulation to explode.

The Bounce and Friction values read by the RBD Solver are now clamped from below at 0. This prevents meaningless values causing the simulation to explode.

The Bounce and Friction values read by the RBD Solver are now clamped from below at 0. This prevents meaningless values causing the simulation to explode.

The Bounce and Friction values read by the RBD Solver are now clamped from below at 0. This prevents meaningless values causing the simulation to explode.

The Bounce and Friction values read by the RBD Solver are now clamped from below at 0. This prevents meaningless values causing the simulation to explode.

The POP Solver in DOPs is now ready for use. To use this solver, just feed a POP Object into a POP Setup, and point the POP Setup node to a POP Node or POP Network.