When locking a camera to the view, the default behaviour is now to use the camera pivot. This will cause your viewport to tumble about the center of the camera. To get the old behaviour, hit the camera options (+ beside the camera selector) and change the pivot to the view source.

When locking a camera to the view, the default behaviour is now to use the camera pivot. This will cause your viewport to tumble about the center of the camera. To get the old behaviour, hit the camera options (+ beside the camera selector) and change the pivot to the view source.

The Sphere, Circle, Tube, and Torus all generate points in different orders in certain axis orientations. This is to make the top/down, and left/right orientation of points when the desired axis is "up" be consistent. To get the old behaviour, append a transform sop with a rotation of 180 degrees. The old behaviour is also restored by the HOUDINI4_COMPATIBILITY flag.

The Sphere, Circle, Tube, and Torus all generate points in different orders in certain axis orientations. This is to make the top/down, and left/right orientation of points when the desired axis is "up" be consistent. To get the old behaviour, append a transform sop with a rotation of 180 degrees. The old behaviour is also restored by the HOUDINI4_COMPATIBILITY flag.

The Sphere, Circle, Tube, and Torus all generate points in different orders in certain axis orientations. This is to make the top/down, and left/right orientation of points when the desired axis is "up" be consistent. To get the old behaviour, append a transform sop with a rotation of 180 degrees. The old behaviour is also restored by the HOUDINI4_COMPATIBILITY flag.

The Sphere, Circle, Tube, and Torus all generate points in different orders in certain axis orientations. This is to make the top/down, and left/right orientation of points when the desired axis is "up" be consistent. To get the old behaviour, append a transform sop with a rotation of 180 degrees. The old behaviour is also restored by the HOUDINI4_COMPATIBILITY flag.

The Sphere, Circle, Tube, and Torus all generate points in different orders in certain axis orientations. This is to make the top/down, and left/right orientation of points when the desired axis is "up" be consistent. To get the old behaviour, append a transform sop with a rotation of 180 degrees. The old behaviour is also restored by the HOUDINI4_COMPATIBILITY flag.

Sweep, Revolve, Skin all convert meshes to polygons by default now. Turn this off for the old behaviour.

Sweep, Revolve, Skin all convert meshes to polygons by default now. Turn this off for the old behaviour.

Sweep, Revolve, Skin all convert meshes to polygons by default now. Turn this off for the old behaviour.

Sweep, Revolve, Skin all convert meshes to polygons by default now. Turn this off for the old behaviour.

Sweep, Revolve, Skin all convert meshes to polygons by default now. Turn this off for the old behaviour.

Backward compatibility is a goal we always keep in mind from one major release to the next. Sometimes, however, a new and better technology cannot be embedded in the fabric of the software without dislocating an older technology, often causing an incompatibility with the previous release.

The purpose of this file is to ease the user's transition to a new release by documenting the unexpected changes in the way existing functions work. Anything from a change of hotkey to a change in file format or default parameter value should be recorded here. parameter value should be recorded here.

Backward compatibility is a goal we always keep in mind from one major release to the next. Sometimes, however, a new and better technology cannot be embedded in the fabric of the software without dislocating an older technology, often causing an incompatibility with the previous release.

The purpose of this file is to ease the user's transition to a new release by documenting the unexpected changes in the way existing functions work. Anything from a change of hotkey to a change in file format or default parameter value should be recorded here. parameter value should be recorded here.

Backward compatibility is a goal we always keep in mind from one major release to the next. Sometimes, however, a new and better technology cannot be embedded in the fabric of the software without dislocating an older technology, often causing an incompatibility with the previous release.

The purpose of this file is to ease the user's transition to a new release by documenting the unexpected changes in the way existing functions work. Anything from a change of hotkey to a change in file format or default parameter value should be recorded here. parameter value should be recorded here.

Backward compatibility is a goal we always keep in mind from one major release to the next. Sometimes, however, a new and better technology cannot be embedded in the fabric of the software without dislocating an older technology, often causing an incompatibility with the previous release.

The purpose of this file is to ease the user's transition to a new release by documenting the unexpected changes in the way existing functions work. Anything from a change of hotkey to a change in file format or default parameter value should be recorded here. parameter value should be recorded here.

Backward compatibility is a goal we always keep in mind from one major release to the next. Sometimes, however, a new and better technology cannot be embedded in the fabric of the software without dislocating an older technology, often causing an incompatibility with the previous release.

The purpose of this file is to ease the user's transition to a new release by documenting the unexpected changes in the way existing functions work. Anything from a change of hotkey to a change in file format or default parameter value should be recorded here. parameter value should be recorded here.