Eric Sheng


About Me

Not Specified
Not Specified


Recent Forum Posts

few more questions [updated] July 16, 2019, 11:15 p.m.

Hi Ken,
Thank you for pointing out the Invoke node, and it looks interesting. But after playing it for several hours, I still can't figure it out, a simple question which has stuck me for a long time, how to create a HieghtField Import/Export TOP node runs as fast as the Geometry Import TOP node and does the job just like the HF_Import/Export SOP node?

few more questions [updated] July 16, 2019, 2:36 a.m.

Hi, Ken:
Can we create our own In Process TOP nodes? I can see the Python Script TOP node is somehow running in process, but what if I want to manipulate the geometry a little bit, I need to use an HDA Processor or the ROP Geometry Output node which is not “in process” and slow to cook.


Is there any way to create custom lightweight geometry processor TOP node? July 14, 2019, 10:44 p.m.

For example, the Geometry Import node is very fast to cook, but what if I want to import height maps as height fields, I have to create an hda to make the import function, then drop down an HDA Processor node in TOP net and cook it. But the HDA Processor node is fairly slow to cook compared to the Built-in Geometry Import node. As far as I understand, the HDA Processor node need to run individual Houdini thread for every workitem in the background, while the Geometry Import node functions like “Evaluating In Process” as how the Python Script node works.
Is there any way to create such lightweight TOP node like the Geometry Import node?