Ernesto Muñoz Faba

emunoz

About Me

EXPERTISE
Technical Director

Connect

LOCATION
Valencias, Spain
WEBSITE

Houdini Skills

ADVANCED
Python
BEGINNER
Procedural Modeling  | Environments  | Digital Assets  | Solaris  | PDG  | VEX

Availability

I am currently employed at Hampa Studios

Recent Forum Posts

Send one job per work item to deadline in a PDG network Oct. 10, 2024, 5:22 a.m.

Hi!
After some trial and error i found a solution. It's very simple, but it can be a little confusing at first.
I'm using Houdini 20.5, in previous versions the behaviour might be different, as indicated in the second note in the documentation page (Deadline Scheduler TOP docs [www.sidefx.com]

What i wanted was for each work item to be executed as a separate job on the farm. For that, I need to set the Default Scheduler of the topnet to a deadline scheduler (the one inside the network) You need to check the Inherit Local Environment in the deadline scheduler (Job Params tab > Deadline Command Environment)

With those two settings, when the top network is cooked, each work item is sent to the farm as a separate job.

I hope this helps if any one is having a similar problem.

Send one job per work item to deadline in a PDG network Sept. 25, 2024, 8:54 a.m.

Hi!

I'm using Houdini 20.5 and need to submit a PDG network to a Deadline render farm. The farm is working, and I've successfully managed to send the TOP network to be executed as a job on the farm.

However, by default, it submits everything as a single job, with all work items running within that job on the same machine. Is there a way to configure the Deadline Scheduler so that each work item is submitted and executed as a separate job, potentially running on different machines? I've been searching for a solution but haven't been able to figure it out.

Thank you for all!

Modifying the projection geometry in the drawCurve node Aug. 9, 2024, 8:28 a.m.

Hello Houdini community,

I'm relatively new to Houdini, and this is my first question on the forum, so please bear with me.

I'm trying to extend the behavior of the drawCurve node, so I created an HDA that is a copy of the original node. My goal is to modify the projection geometry used by the stroke node inside the HDA. I successfully changed the guide geometry, and it works perfectly. However, simply changing the guide geometry isn't sufficient because it doesn't affect the actual geometry that the stroke node uses for projection.

What’s puzzling me is that there seems to be no direct connection between the input of the drawCurve node and the input of the stroke1 node. How is stroke1 determining which geometry to use for the projection? If I can figure out how the projection geometry is being passed to stroke1, I could modify it in the same way I modified the guide geometry.

Could someone guide me on how to approach this?