hjd

hjd

About Me

Connect

LOCATION
Not Specified
WEBSITE

Houdini Skills

Availability

Not Specified

Recent Forum Posts

Converting to H14 Feb. 13, 2015, 9:30 a.m.

After some more testing, it appears the node swaps actually happen on a few of our digital assets.

I get these errors in the houdini console when loading an affected *.otl

Error: Couldn't remove old operator type definition sesi_temporary:op/null
Error: Couldn't remove old operator type definition sesi_temporary:op/merge
oplibSop/null?Sop/null Error(1): Expecting open brace
oplibSop/merge?Sop/merge Error(1): Expecting open brace

Unable to find dialog script for merge
at oplibSop/merge?Sop/merge.



After working through all the various issues by replacing types, and having found that some of the type-changed SOP_Nulls had mysteriously changed into SOP_merge nodes it would be nice to :

a) Have item hover hilighting in the change-type uber-list of all nodes
b) multiple-selection type-replacement
c) a proper dialog that can filter types when replacing types.
d) make it illegal to have two nodes with the same short-name OR show the full node name sop_null / sop_athing etc rather than just the nice name in the change-type list.
e) Be able to filter and search for nodes by their type as well as their unique network-name.

Converting to H14 Feb. 13, 2015, 7:17 a.m.

Hi, after installing H14 and sorting out HAPI code changes and HDK plugin changes, ive found that the DigitalAssets loaded from H13 have had Null and Merge nodes changed into ‘default-nodes’ with the same name and phantom “Utility” type as the ‘proper’ nodes.

There are a lot of instance of this in our digital assets and the ‘default-node’ does not allow a zero-geometry as input like the proper SOP_Null node does, instantly breaking our digital assets with optional inputs.

All of the SOP_Merge nodes are also not working.

Is there an HScript or other process / command I can run to replace the “Utility” versions with the proper versions?

The attached picture shows the default-node proxy object and the two versions of the “Null” node now available the proper one is the “Digital Assets” one.

VEX intrinsic bounds July 15, 2014, 6:48 a.m.

Hi, I want to quickly and efficiently get the centre of a polygon in an attribWrangle node. Rather than get the positions for the linear vertices for the vertices for the primitive and manually get the average, I though i could use the primitive intrinsic “bounds”.

Using :
primintrinsic(0, “bounds”, @primnum );

I find that i can get the values in a vector4 or vector(3), but that means I can only get the first four values out of the six-value attribute.
Trying to return into a 6-float array doesnt work, returning to a matrix3 ( nine floats ) doesnt work. returning to a string doesnt work.

Is there any way to actually get at the data in the intrinsic or shall i resign myself to “maybe in Houdini 14 …” and do the slow vertex-averaging ?