Fixed crash when deleting a custom object under certain circumstances if a "picking" parameter was promoted up.

When a node was reference copied, then the original node was renamed in a network editor in list view mode, the copy would generate a bunch of warnings. These warnings were because the channel references in the switcher parameters were not updated to use the new node name. Now these references do get updated properly. In addition, when doing a reference copy we no longer channel reference folder parameters.

When a node was reference copied, then the original node was renamed in a network editor in list view mode, the copy would generate a bunch of warnings. These warnings were because the channel references in the switcher parameters were not updated to use the new node name. Now these references do get updated properly. In addition, when doing a reference copy we no longer channel reference folder parameters.

When a node was reference copied, then the original node was renamed in a network editor in list view mode, the copy would generate a bunch of warnings. These warnings were because the channel references in the switcher parameters were not updated to use the new node name. Now these references do get updated properly. In addition, when doing a reference copy we no longer channel reference folder parameters.

When a node was reference copied, then the original node was renamed in a network editor in list view mode, the copy would generate a bunch of warnings. These warnings were because the channel references in the switcher parameters were not updated to use the new node name. Now these references do get updated properly. In addition, when doing a reference copy we no longer channel reference folder parameters.

When a node was reference copied, then the original node was renamed in a network editor in list view mode, the copy would generate a bunch of warnings. These warnings were because the channel references in the switcher parameters were not updated to use the new node name. Now these references do get updated properly. In addition, when doing a reference copy we no longer channel reference folder parameters.

The MatchTopology SOP has been added. This SOP tries to reorder primitive and point numbers so two geometries will have matching point and primitive numbers. It does this by looking at the connectivity of geometry, and does not rely in any way on point positions.

In cases where the match is ambiguous, it highlights the ambiguous cases and the user can specify additional point mappings to clarify the situation.

The MatchTopology SOP has been added. This SOP tries to reorder primitive and point numbers so two geometries will have matching point and primitive numbers. It does this by looking at the connectivity of geometry, and does not rely in any way on point positions.

In cases where the match is ambiguous, it highlights the ambiguous cases and the user can specify additional point mappings to clarify the situation.

The MatchTopology SOP has been added. This SOP tries to reorder primitive and point numbers so two geometries will have matching point and primitive numbers. It does this by looking at the connectivity of geometry, and does not rely in any way on point positions.

In cases where the match is ambiguous, it highlights the ambiguous cases and the user can specify additional point mappings to clarify the situation.

The MatchTopology SOP has been added. This SOP tries to reorder primitive and point numbers so two geometries will have matching point and primitive numbers. It does this by looking at the connectivity of geometry, and does not rely in any way on point positions.

In cases where the match is ambiguous, it highlights the ambiguous cases and the user can specify additional point mappings to clarify the situation.

The MatchTopology SOP has been added. This SOP tries to reorder primitive and point numbers so two geometries will have matching point and primitive numbers. It does this by looking at the connectivity of geometry, and does not rely in any way on point positions.

In cases where the match is ambiguous, it highlights the ambiguous cases and the user can specify additional point mappings to clarify the situation.

Fixed bug introduced in 6.2.42 where clicking on the interrupt button in the interrupt dialog caused Houdini to prematurely quit.

Fixed bug introduced in 6.2.42 where clicking on the interrupt button in the interrupt dialog caused Houdini to prematurely quit.

Fixed bug introduced in 6.2.42 where clicking on the interrupt button in the interrupt dialog caused Houdini to prematurely quit.

Fixed bug introduced in 6.2.42 where clicking on the interrupt button in the interrupt dialog caused Houdini to prematurely quit.

Fixed bug introduced in 6.2.42 where clicking on the interrupt button in the interrupt dialog caused Houdini to prematurely quit.

Changed vertex attribute transfers. Destination vertices are now mapped to the closest position and primitive in the source geometry. If the mapped position coincides with a source point, then the source primitive is determined from the set of source primitives that share that point by selecting the closest angle bisector at the corresponding source vertex to the angle bisector at the destination vertex. Similarly, if the mapped position lies on a source edge, then the destination bisector is used to determine which of the two source primitives that share the edge best correspond to the destination primitive. The vertex attribute at the mapped position is determined using a barycentric-like interpolation scheme. Consequently, the sample count, kernel function, and kernel radius parameter do not affect the source interpolation process. However, the kernel function still participates in the source-destination blending process.

Changed vertex attribute transfers. Destination vertices are now mapped to the closest position and primitive in the source geometry. If the mapped position coincides with a source point, then the source primitive is determined from the set of source primitives that share that point by selecting the closest angle bisector at the corresponding source vertex to the angle bisector at the destination vertex. Similarly, if the mapped position lies on a source edge, then the destination bisector is used to determine which of the two source primitives that share the edge best correspond to the destination primitive. The vertex attribute at the mapped position is determined using a barycentric-like interpolation scheme. Consequently, the sample count, kernel function, and kernel radius parameter do not affect the source interpolation process. However, the kernel function still participates in the source-destination blending process.

Changed vertex attribute transfers. Destination vertices are now mapped to the closest position and primitive in the source geometry. If the mapped position coincides with a source point, then the source primitive is determined from the set of source primitives that share that point by selecting the closest angle bisector at the corresponding source vertex to the angle bisector at the destination vertex. Similarly, if the mapped position lies on a source edge, then the destination bisector is used to determine which of the two source primitives that share the edge best correspond to the destination primitive. The vertex attribute at the mapped position is determined using a barycentric-like interpolation scheme. Consequently, the sample count, kernel function, and kernel radius parameter do not affect the source interpolation process. However, the kernel function still participates in the source-destination blending process.

Changed vertex attribute transfers. Destination vertices are now mapped to the closest position and primitive in the source geometry. If the mapped position coincides with a source point, then the source primitive is determined from the set of source primitives that share that point by selecting the closest angle bisector at the corresponding source vertex to the angle bisector at the destination vertex. Similarly, if the mapped position lies on a source edge, then the destination bisector is used to determine which of the two source primitives that share the edge best correspond to the destination primitive. The vertex attribute at the mapped position is determined using a barycentric-like interpolation scheme. Consequently, the sample count, kernel function, and kernel radius parameter do not affect the source interpolation process. However, the kernel function still participates in the source-destination blending process.