About Me


Not Specified

Houdini Skills


Not Specified

Recent Forum Posts

slo2otl segmentation fault Feb. 11, 2013, 8:30 p.m.

You should add $RMANTREE/lib to $LD_LIBRARY_PATH for the shell you're using.

if necessary, make a symbolic link for that points to

slo2otl segmentation fault Feb. 11, 2013, 3:43 p.m.

You can view the python source on and see that it depends on two different binaries. “sloinfo”, which ships with prman, and “rmands”, which comes with houdini.

I would locate both binaries, and run ldd on them to see if there are any missing libs.

You might also be able to run hython in verbose mode (passing -v), but I'm not sure. (it could be a python issue, instead of the above)

Vex VopSop question. Nov. 7, 2012, 3:57 p.m.

hello I had a question about how these 2 differ from one another when use to deform geo.

I watched the CmiVFX Vex volume 1 and follow the twist deform formula, however I notice something. when Done in VopSop my deformation isn't as clean than when it's done in Vex. could someone explain to me why it does that?

I had thought the 2 were the same code.

plus on another question is why Vopsop vs Vex. performance?

thank you for any help.

Are you referring to the difference between implementing VEX in SOP's vs. a Displacement shader rendered with Mantra ?

If this is the case, the rendered result is much smoother since Mantra dices the geometry to a very fine level of detail, where SOP's is typically not using near as many polygons. (More info here [])

You can put down a subdivide SOP and crank up the levels until your result more closely resembles Mantra's output, but take caution not to set it too high, or things will get really slow.

A VOP SOP is processed in real time as you are working in Houdini, so it's going to be much slower than Mantra.

Hope that helps