Visualizing MaterialX VOP's
1824 10 1-
- frame_48
- Member
- 12 posts
- Joined: Feb. 2019
- Offline
Has anyone had consistent luck with using the Visualize (X) feature when building MaterialX shader networks? Some nodes it visualizes, some it does not, sometimes it works on CPU and not XPU etc. Not being able to debug and view components of shaders consistently makes building shaders very tedious. For instance plug a unified noise into a ramp constant and plug it into the shader, I can't get this to visualize on XPU.
-
- jsmack
- Member
- 7981 posts
- Joined: Sept. 2011
- Online
-
- goldleaf
- Staff
- 4193 posts
- Joined: Sept. 2007
- Offline
-
- rafal
- Staff
- 1454 posts
- Joined: July 2005
- Offline
jsmackThat's essentially what the shader translator authors when it sees the Visualize VOP. It's just does it in the Viewport Override layer, so there are less chances of the debugging making its way to the final rendering by mistake.
My workflow is to use the Surface Unlit shader
(In H20 it actually uses EDF+Surface shader, but in the next version it's simplified to use the Unlit surface shader).
-
- tomteller
- Member
- 10 posts
- Joined: March 2020
- Offline
-
- jsmack
- Member
- 7981 posts
- Joined: Sept. 2011
- Online
tomteller
Hey guys, it does look like a bug with XPU. I attached a quick sample scene. If you render with XPU and visualize the unified noise (inside materiallibrary1) you will notice it is broken / the frequency is not properly visualized. Switching to CPU seems to fix it. I'll submit a bug report too.
Best,
The error says the shader contains a node not handled by XPU, which makes sense since rafal said it uses EDF+Surface shader which XPU doesn't support. So I would take it that this feature is not implemented in XPU.
KarmaXPU: ShaderGraph _sg_s_85510A9F14EF37B1 has rootnode-type not handled by XPU, skipped
The visualize node also doesn't work with graphs that aren't part of the main shader graph, for example if you want to visualize three different values by packing them into a color3, the last node combine3 is not part of the material so the visualize node won't do anything.
Edited by jsmack - Nov. 21, 2023 15:06:44
-
- jsmack
- Member
- 7981 posts
- Joined: Sept. 2011
- Online
-
- ChristopherRutledge
- Member
- 411 posts
- Joined: Feb. 2017
- Online
im still confused about this, it seems to work differently than the unlit shader. would be great if this worked consistently. anyone know whats going on here?
is there documentation on this feature? having a hard time finding it, seems like this should be easier to understand...
is there documentation on this feature? having a hard time finding it, seems like this should be easier to understand...
Edited by ChristopherRutledge - July 22, 2024 15:26:15
-
- ChristopherRutledge
- Member
- 411 posts
- Joined: Feb. 2017
- Online
-
- asteraffect
- Member
- 3 posts
- Joined: July 2022
- Offline
-
- wanglifu
- Member
- 182 posts
- Joined: Feb. 2017
- Offline
-
- Quick Links