UDIM displacement exr not rendering in husk

   541   2   3
User Avatar
Member
1 posts
Joined: Sept. 2022
Offline
Hello,
We have a character with multiple UDIM tiles. The displacement is exported in 32 bit exr, every other texture in tif. Viewport renders show the displacement fine, however when launched on our farm the displacement does not render.

The file nomenclature is: 'filename'.<UDIM>.exr

In the scene graph details material binding for that mesh, it says that the path of the texture cannot be resolved. However when we point it to just one tile, for example 'filename'.1001.exr, it works just fine. Objects that have just one UDIM tile also are fine.

The other textures, using the same <UDIM> tag, and atlas tyle, are fine. It seems to come just from multiple UDIMS in exr format, when rendered with husk.

In the USD Rop node for the asset export, I have tried enabling/disabling relative paths under output processors, as that sometimes solved issues with missing textures, however that did not change anything in this case.

Displacement is enabled in a render geometry node in the lookdev scene. We have also tried enabling displacement directly in the render scene -- neither do anything when rendered on the farm, no matter what radius is set.

We are using Houdini 19.5.640, Renderman 25 and our dispatcher is Deadline.

We get no error messages in Deadline logs about this specific error, Renderman xml logs do not show any displacement bounds for the problematic meshes.

Are there any other things we can try to make it work? Thanks in advance.

Image Not Found

Edited by veronikanikulina - June 28, 2024 11:33:54

Attachments:
image_03.png (12.9 KB)

User Avatar
Staff
502 posts
Joined: June 2020
Offline
veronikanikulina
Viewport renders show the displacement fine, however when launched on our farm the displacement does not render.

If you manually run husk from the command-line, on the artist's machine (where things work in the viewport), what do you get?

veronikanikulina
In the scene graph details material binding for that mesh, it says that the path of the texture cannot be resolved.

Yes, this is a known issue we have a ticket for. If it shows as resolved when putting in a fixed number (i.e., 1001) then ignore the "cannot be resolved" message.

veronikanikulina
We are using Houdini 19.5.640, Renderman 25 and our dispatcher is Deadline.

Have you contacted the RenderMan team to discuss this?
User Avatar
Member
4 posts
Joined: Dec. 2016
Offline
Hello, this issue has been resolved thanks to the work of the team.

The idea was to enforce an attribute that Renderman needed absolutely to handle UDIMs. You can see it on the image below.
Also you should reassign the material after to enforce the changes.

Attachments:
Capture.PNG (82.5 KB)

  • Quick Links