Running setenv with no arguments will report the correct values for $FPS and other channel-specific environment variables.

If a File SOP first loads a model with a large number of polygons, and then loads a model with a large number of tristrips, it used to be extremely slow. It is now the expected speed.

If a File SOP first loads a model with a large number of polygons, and then loads a model with a large number of tristrips, it used to be extremely slow. It is now the expected speed.

If a File SOP first loads a model with a large number of polygons, and then loads a model with a large number of tristrips, it used to be extremely slow. It is now the expected speed.

If a File SOP first loads a model with a large number of polygons, and then loads a model with a large number of tristrips, it used to be extremely slow. It is now the expected speed.

If a File SOP first loads a model with a large number of polygons, and then loads a model with a large number of tristrips, it used to be extremely slow. It is now the expected speed.

Added an option to the Switch VOP to set the output value to zero if the Switcher Inder value is outside the range of connected input values. The current and default behavior is to output the last connected input value in this case.

Added an option to the Switch VOP to set the output value to zero if the Switcher Inder value is outside the range of connected input values. The current and default behavior is to output the last connected input value in this case.

Added an option to the Switch VOP to set the output value to zero if the Switcher Inder value is outside the range of connected input values. The current and default behavior is to output the last connected input value in this case.

Added an option to the Switch VOP to set the output value to zero if the Switcher Inder value is outside the range of connected input values. The current and default behavior is to output the last connected input value in this case.

Added an option to the Switch VOP to set the output value to zero if the Switcher Inder value is outside the range of connected input values. The current and default behavior is to output the last connected input value in this case.

The background argument to all ray-tracing functions (i.e. occlusion, reflectlight, etc.) will now handle non-constant arguments properly. Previously, there were grid artifacts.

The background argument to all ray-tracing functions (i.e. occlusion, reflectlight, etc.) will now handle non-constant arguments properly. Previously, there were grid artifacts.

The background argument to all ray-tracing functions (i.e. occlusion, reflectlight, etc.) will now handle non-constant arguments properly. Previously, there were grid artifacts.

The background argument to all ray-tracing functions (i.e. occlusion, reflectlight, etc.) will now handle non-constant arguments properly. Previously, there were grid artifacts.

The background argument to all ray-tracing functions (i.e. occlusion, reflectlight, etc.) will now handle non-constant arguments properly. Previously, there were grid artifacts.

The tree gadgets in the worksheet and parameter panes now show the error state of the nodes.

The tree gadgets in the worksheet and parameter panes now show the error state of the nodes.

The tree gadgets in the worksheet and parameter panes now show the error state of the nodes.

The tree gadgets in the worksheet and parameter panes now show the error state of the nodes.

The tree gadgets in the worksheet and parameter panes now show the error state of the nodes.

Fixed a bug which would cause bad code to be generated when a Parameter VOP had a Parameter Name that was the same as one of the parameters of that VOP (such as "invisible" or "floatdef").

Fixed a bug which would cause bad code to be generated when a Parameter VOP had a Parameter Name that was the same as one of the parameters of that VOP (such as "invisible" or "floatdef").

Fixed a bug which would cause bad code to be generated when a Parameter VOP had a Parameter Name that was the same as one of the parameters of that VOP (such as "invisible" or "floatdef").

Fixed a bug which would cause bad code to be generated when a Parameter VOP had a Parameter Name that was the same as one of the parameters of that VOP (such as "invisible" or "floatdef").