Community
Arnold for Houdini Forum
Rendering with Arnold in Houdini and Solaris using the HtoA plug-in.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

SOLVED: Toon Shader in Solaris contour filter locks up CPU, eats RAM

0 REPLIES 0
Reply
Message 1 of 1
areito.echevarria
194 Views, 0 Replies

SOLVED: Toon Shader in Solaris contour filter locks up CPU, eats RAM

Hello,

I am having trouble getting the contour filter to function as expected with the toon shader in Solaris. When I set the filter type to contour and then render, CPU and RAM usage shoot up to 100% and the machine is locked up for some time. This is with a scene consisting of a few cubes. I am able to get the toon shader and contour filter to work fine in the regular HtoA Houdini Arnold ROP output workflow, the issue is specific to Solaris.

I am doing the following:

I import simple cubes geo from sops, apply a simple toon shader, lights, camera then create:
A render Var node with; Data type: color4f, Source Name: color, Source type: Raw, Format: color4f
Then create a Render Product node pointing to that render var node.
Then create a Render Settings node pointing to the render product,

Then when I render, the CPU and memory go to 100% for 10-15 minutes and nothing is ever rendered. This does not happen using the same input data in the regular HtoA workflow, I get an image with a contour edge as expected with no unusual CPU or RAM usage.

This is with Houdini 18.5.499 and htoa-5.6.0.2_rbd4662c_houdini-18.5.499

Is this expected? Anything else I can try?

Cheers,

EDIT: the problem was the view-port render settings were over riding my USD render settings and turning on progressive rendering, which apparently will cause slowdown and memory consumption with the contour filter. Thanks!

Tags (2)
Labels (2)
0 REPLIES 0

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums