When generating RIB files of subdivision surfaces with different shaders applied, Houdini needs to output two separate subdivision surface primitives. This creates a dis-continuity that is different than the original surface. This behaviour has been "fixed" so that the resulting separate primitives should now meet correctly at their seam. This behaviour can be turned off (though we believe it is correct) by setting the environment variable HOUDINI_DISCONNECT_RIB_SUBD.

When generating RIB files of subdivision surfaces with different shaders applied, Houdini needs to output two separate subdivision surface primitives. This creates a dis-continuity that is different than the original surface. This behaviour has been "fixed" so that the resulting separate primitives should now meet correctly at their seam. This behaviour can be turned off (though we believe it is correct) by setting the environment variable HOUDINI_DISCONNECT_RIB_SUBD.

When generating RIB files of subdivision surfaces with different shaders applied, Houdini needs to output two separate subdivision surface primitives. This creates a dis-continuity that is different than the original surface. This behaviour has been "fixed" so that the resulting separate primitives should now meet correctly at their seam. This behaviour can be turned off (though we believe it is correct) by setting the environment variable HOUDINI_DISCONNECT_RIB_SUBD.

When generating RIB files of subdivision surfaces with different shaders applied, Houdini needs to output two separate subdivision surface primitives. This creates a dis-continuity that is different than the original surface. This behaviour has been "fixed" so that the resulting separate primitives should now meet correctly at their seam. This behaviour can be turned off (though we believe it is correct) by setting the environment variable HOUDINI_DISCONNECT_RIB_SUBD.

When generating RIB files of subdivision surfaces with different shaders applied, Houdini needs to output two separate subdivision surface primitives. This creates a dis-continuity that is different than the original surface. This behaviour has been "fixed" so that the resulting separate primitives should now meet correctly at their seam. This behaviour can be turned off (though we believe it is correct) by setting the environment variable HOUDINI_DISCONNECT_RIB_SUBD.

When generating RIB files of subdivision surfaces with different shaders applied, Houdini needs to output two separate subdivision surface primitives. This creates a dis-continuity that is different than the original surface. This behaviour has been "fixed" so that the resulting separate primitives should now meet correctly at their seam. This behaviour can be turned off (though we believe it is correct) by setting the environment variable HOUDINI_DISCONNECT_RIB_SUBD.

Updated the experimental edit/sculpt SOP. Sculpts are no longer confined to the selected geometry. Also fixed a bug in mirroring the current edit. This SOP is not enabled yet.

Updated the experimental edit/sculpt SOP. Sculpts are no longer confined to the selected geometry. Also fixed a bug in mirroring the current edit. This SOP is not enabled yet.

Updated the experimental edit/sculpt SOP. Sculpts are no longer confined to the selected geometry. Also fixed a bug in mirroring the current edit. This SOP is not enabled yet.

Updated the experimental edit/sculpt SOP. Sculpts are no longer confined to the selected geometry. Also fixed a bug in mirroring the current edit. This SOP is not enabled yet.

Updated the experimental edit/sculpt SOP. Sculpts are no longer confined to the selected geometry. Also fixed a bug in mirroring the current edit. This SOP is not enabled yet.

Updated the experimental edit/sculpt SOP. Sculpts are no longer confined to the selected geometry. Also fixed a bug in mirroring the current edit. This SOP is not enabled yet.

Pane linking is now governed only by the 1/2/3 buttons. Tie to Parent and Tie to Current are now removed. This is a bigger change than it might sound. The internal path now includes what used to be the "current" node. Thus, the network view will say /obj/model/box1 when viewing the network of /obj/model with box1 the node whose parameters are being viewed.

Pane linking is now governed only by the 1/2/3 buttons. Tie to Parent and Tie to Current are now removed. This is a bigger change than it might sound. The internal path now includes what used to be the "current" node. Thus, the network view will say /obj/model/box1 when viewing the network of /obj/model with box1 the node whose parameters are being viewed.

Pane linking is now governed only by the 1/2/3 buttons. Tie to Parent and Tie to Current are now removed. This is a bigger change than it might sound. The internal path now includes what used to be the "current" node. Thus, the network view will say /obj/model/box1 when viewing the network of /obj/model with box1 the node whose parameters are being viewed.

Pane linking is now governed only by the 1/2/3 buttons. Tie to Parent and Tie to Current are now removed. This is a bigger change than it might sound. The internal path now includes what used to be the "current" node. Thus, the network view will say /obj/model/box1 when viewing the network of /obj/model with box1 the node whose parameters are being viewed.

Pane linking is now governed only by the 1/2/3 buttons. Tie to Parent and Tie to Current are now removed. This is a bigger change than it might sound. The internal path now includes what used to be the "current" node. Thus, the network view will say /obj/model/box1 when viewing the network of /obj/model with box1 the node whose parameters are being viewed.

Pane linking is now governed only by the 1/2/3 buttons. Tie to Parent and Tie to Current are now removed. This is a bigger change than it might sound. The internal path now includes what used to be the "current" node. Thus, the network view will say /obj/model/box1 when viewing the network of /obj/model with box1 the node whose parameters are being viewed.

Rendering from PRman to MPlay now shows frames past 1. Since v6.2.64, mplay would not increase the frame range as more frames were rendered, making it appear that the frames were not rendering. This could be worked around by manually updating the frame range.

Rendering from PRman to MPlay now shows frames past 1. Since v6.2.64, mplay would not increase the frame range as more frames were rendered, making it appear that the frames were not rendering. This could be worked around by manually updating the frame range.

Rendering from PRman to MPlay now shows frames past 1. Since v6.2.64, mplay would not increase the frame range as more frames were rendered, making it appear that the frames were not rendering. This could be worked around by manually updating the frame range.

Rendering from PRman to MPlay now shows frames past 1. Since v6.2.64, mplay would not increase the frame range as more frames were rendered, making it appear that the frames were not rendering. This could be worked around by manually updating the frame range.