xpu vdb render issue

   1866   5   1
User Avatar
Member
106 posts
Joined:
Offline
Hello again everyone,
I'm still going about emissive stuff

This time I am wondering if there is an issue with xpu when rendering vdb volumes (density)?
I am importing a vdb density volume into Solaris and I'm giving it a volume shader where I pipe in the density into the emissive input of the volume shader. I am also multiplying this density with a constant value.

When I render this with Karma cpu I get an expected result, but when simply switching to xpu I get something completely different. It seems to just render out a big box of a volume. Please see the attached image.

Why is this happening? What can I do to get things to render correctly in xpu?

Thanks,
Dag
Edited by Dougie0047 - Dec. 14, 2023 14:14:43

Attachments:
xpu_vdb_issue.png (4.3 MB)

User Avatar
Staff
584 posts
Joined: May 2019
Offline
Are you using the kma_volume VOP?
Are you able to post the scene?
User Avatar
Member
106 posts
Joined:
Offline
@brians : Thanks for your reply. Yes, I am using the kma_volume vop. I cannot post the entire scene, but I was able to reproduce the issue in the attached example file.
I am using Houdini Indie 20.0.544, on Windows 10.
Should I perhaps bug report this issue?

Thanks,
Dag

Attachments:
xpu_vdb_render_failure_example.hiplc (346.0 KB)

User Avatar
Staff
584 posts
Joined: May 2019
Offline
Dougie0047
Should I perhaps bug report this issue?

Yes that would be great.
Thanks!
User Avatar
Member
24 posts
Joined: April 2018
Offline
Encountered the same issue. Any updates on what causes it or if it is logged?
User Avatar
Staff
77 posts
Joined: May 2022
Offline
Hi,

Thansk for sharing the hip file.

- The Mtlx_geomprop node is reading "density" field whereas the "volume_0" prim sampling field is "gas".
- The geomprop node is strict typing. The "gas" field is of float type whereas the "mtlxgeompropvalue1" is configured for Vector3.
This needs to be change to float type as well otherwise it returns the default value.
- You would want to also assign a valid material for "volume_1"

Attachments:
xpu_vdb_render_failure_example.hiplc (358.3 KB)

  • Quick Links