Hi SESI,

Easy to reproduce:

1. Inside an RSL VOP network, add a ParameterVOP.
2. Change the parameter's type to either “9 floats (matrix3)” or “4 floats (vector4)” and boom!

I know these are not native rsl types, but crashing is maybe a little too dramatic

which version of Houdini does it happen in? A Bug of a similar nature has already been submitted , but it occurs only in certain build versions.

rafal
which version of Houdini does it happen in? A Bug of a similar nature has already been submitted , but it occurs only in certain build versions.

Houdini 8.0.421
PRMan 12.0

BUT… JC just tried it and it didn't crash for him.

We've since discovered that it only crashes if the shader is being displayed in the viewport (i.e: there is a viewport displaying the network).

I've submitted a bug. Thanks.

We've had similar nastiness in 8.0.403.

Wierdly, certain VOPs have started setting vector4 inputs as default (seen in Max and Mult) and sporadically break (especially in a big network). The Null VOP completely breaks networks tto.

Actually, we saw that a Parameter or a Constant vector4 VOP would in itself produce bad code without a value.

Personally, I think VOPs need a bit tidying up and more functionality in RSL VOPs.
Louis

PS, what's the plan for dealing with dependancies when you get multiple copies of a VOP network?

PPS, a VOP palette (like the shader palette) would be nice! :wink: